People, projects and tasks
After a meeting ends, OpenScribe reads its transcript and notes and updates pages for the people and projects it mentions, plus your tasks and deadlines. Every fact links back to the transcript line or note it came from, and anything you edit or remove by hand stays that way.
Email discussions#
Optional Outlook and (on self-hosted servers) Gmail access adds an Emails workspace beside Calendar, plus Emails tabs on people and projects. Gmail is off on scribe.akyonlabs.com. Connect one or more accounts from the Mailboxes chooser in Emails, choose which accounts to show and search retained discussions. Returning from Connect starts the first sync. The server checks connected mailboxes every five minutes, even after you close OpenScribe. When Calendar or a meeting adds a new person with an email address, the next check looks back 90 days for that address. New replies appear in the saved thread. Use Sync to check immediately. The progress bar shows how many saved addresses have been checked and how many messages have been saved. If Gmail asks OpenScribe to slow down, the sync waits and continues automatically. You can leave Emails and return to the same running sync. Use Reconnect when mailbox access needs renewal. Expand a thread to follow its messages, or open the original in Gmail or Outlook. The connection is read-only and does not import attachments.
Person matching uses saved email addresses. New projects and changes to saved project names or descriptions cause the server to check saved threads again. When showing threads, matching projects and checking tasks, OpenScribe automatically removes repeated quoted reply history per message while keeping the link to the original message in Gmail or Outlook. Project matching uses the workspace's decisions model after a private CPU service masks detected financial details, credentials and government IDs in the message and project context while keeping person names and discussion context. A thread can appear in Emails before its project links are ready. OpenScribe checks each section of a long thread and resumes unfinished matches in the background. If redaction is unavailable, project matching waits. Detection is not a guarantee that all sensitive details are removed.
Live Outlook acceptance is pending. Development checks use synthetic messages.
What each meeting updates#
| Part | Holds |
|---|---|
| Person | Roles, responsibilities, notes, links, locations, skills, connections, tasks, meetings |
| Project | Roles per person, responsibilities, milestones, notes, links, tasks |
| To-dos tab | One task list shared by the meeting, person and project views |
| Deadlines tab | Milestone dates plus task due dates on each page, without copying the tasks |
| Mind | The Mind tab maps all your people, projects, tags and linked meetings. Hover a record for its details, click it to highlight its connections and open its page beside the map, and zoom, pan or Fit to move around. Drag the divider to widen the page, or double-click it to reset |
Each page opens with a one-line tagline and a row of chips: email, linked projects or people, the next deadline, open to-dos, links such as a GitHub repository or Drive file, location and meetings. Below them, roles, responsibilities, notes, milestones, links and tasks are short rows, and each fact carries a small citation you can hover for the quote. Each page has its own To-dos, Deadlines and change history. Add detail adds a note, role, responsibility, link, skill, location, deadline or connection, with an optional date and related people, projects or tags. Links can point to any website and keep an editable label. Add task in the page menu adds a to-do.
Where facts come from#
Short facts: extraction writes a project tagline of one line and one short fact per item, and every link from the meeting keeps its address and a short name
Evidence: every extracted item cites one transcript segment or note. Click it to open the meeting at that moment
Your edits win: a task you completed or a due date you changed is never overwritten by a later meeting
Vague dates stay vague: "by next Friday" is kept as text and marked unconfirmed until it has a real date
Your own name is yours: in an imported meeting, a task given to your full name appears under My to-dos, with or without a middle initial
Unknown speakers stay unassigned: in a recorded meeting, a task from an unmapped voice gets no owner
Non-todos and non-projects are filtered out: interview Q&A answers, candidate methodology descriptions (such as code examples in parentheses), in-meeting mechanics, and generic role or meeting-format titles are skipped so only real commitments and named initiatives become tasks or projects
Removed means removed: an item you delete does not come back when the meeting is processed again, even reworded
History: every change is a dated revision you can compare and restore. Restoring creates a new revision
How people merge#
One resolver matches every participant and speaker to a person, in this order:
- You: the local microphone is always you
- Email: an email belongs to the person who has it. One of your emails means you
- Your name: a participant without email under your full name is you, unless you picked Not them for a person of that name
- Exact full name: a name of two or more words joins the one person with exactly that name
- Everyone else: one-word names, names several people share and the same name under two emails become a new person
Names compare without punctuation or a middle initial, so Ada B. Lovelace matches Ada Lovelace. No AI call decides a merge.
When a new person looks like an existing one, their page shows a quiet Maybe (name)? line with Merge and Not them. When two or more others share this person's exact name, they show instead as one N others share this name button. It lists each person with their email, role and to-dos, and you tick who to Merge into this person or keep apart with Not them. Merge into… in the page menu merges any two people by hand.
How projects match and merge#
Extraction receives your active project names and taglines. A paper, benchmark, milestone or abbreviated workstream keeps the existing project name when it refers to that project. For example, Y27 Paper Alignment can link to YOLO27. Saved aliases match directly, and unclear matches become suggestions. A meeting title that unambiguously names an existing project also links the meeting and its otherwise unassigned project references to that project.
Merging projects keeps the absorbed names as aliases and updates saved project names on meetings and recurring series, so their Mind connections follow the surviving project. Repeated active facts and tasks collapse while retaining their evidence, manual task edits, tags and completed state. Removed tasks stay removed. A merge suggestion between two existing projects appears on both pages and merges the proposed source into the candidate when accepted.
Saved projects with matching names, aliases or version abbreviations get a Maybe (name)? proposal to merge the newer project into the older one. Extraction also checks likely duplicates of projects it updated with the workspace's decisions model. Keep separate keeps both projects and remembers their IDs and name variants. Same-name projects group into one review, and Merge into… lets you choose another project by hand. Merges require confirmation and cannot be undone.
On upgrade, a startup repair adds these proposals for existing projects without merging them. It also links ended meetings with an unambiguous project in their title and fills their tasks' empty project references. Manually locked task projects and removed tasks stay as they are. Ambiguous titles stay unlinked.
Meetings and Ask in Mind#
Opening a meeting from Mind shows its transcript and other sections in one scrolling inspector. Back returns to the selected record, and Ask opens the shared dialog for that meeting. Ask follows the record or meeting you inspect. Recurring meetings show a session count and a Session N of M menu with dates. Imported Tactiq meetings carry the Tactiq logo, with source limitations in the tooltip.
Imported meetings#
Meetings imported from Tactiq or tldv keep each speaker's name as it appeared in the source. Mind processes imported meetings in the background, including meetings already in your workspace. Extraction resolves each name with the rules above. A label takes the email of the invitee with exactly that name, else the invitee email the model matched to that label alone. Group labels like Ana & Ben and generic labels like Speaker 2 stay unassigned, and an email is never invented.
More than one transcript of a call#
When OpenScribe, Tactiq and tl;dv have copies of the same call, you can open them on one meeting page. Use the source selector in Transcript to read a particular copy. Following a transcript citation opens the copy that contains the quote. The meeting has one set of tasks and knowledge updates.
On a phone, Meeting options opens the account and language controls. In Transcript, open Transcript actions to copy the selected source as text or Markdown, refresh it, or show the full transcript when following a citation. The session picker opens other dates in the series.
A recurring meeting can have a new occurrence every week. A shared title, attendee or room link alone does not join those occurrences. Review a suggested match before combining two uncertain copies, or keep them separate.
Reprocessing a meeting#
If a long transcript reaches the provider’s output limit, Mind retries it in smaller sections. It keeps the original citations and saves the result after all sections finish.
Running extraction again replaces that meeting's automatic tasks and details with the new result, so a reworded item does not appear twice. It keeps everything you created, edited or removed, and anything another meeting also cites. A failed or empty run deletes nothing.
Still current?#
The meetings list shows a small Still current? card with up to five items:
- Open tasks no meeting has mentioned in 14 days
- Deadlines more than a day past that are still open
After newer ended meetings finish extraction or incoming emails complete classification, OpenScribe checks unresolved tasks and active deadlines against strictly later evidence using the read-only task_resolution agent. Entries with no newer meetings or eligible emails are skipped without calling a model. When later transcripts, meeting notes or OPENSCRIBE_PII_URL-redacted emails cite completion, cancellation or a new concrete due date with a verified quote, OpenScribe updates the entry (done, canceled or rescheduled), links the supporting meeting citation and records an entity revision while preserving any manual status or due-date edits.
The card shows one item at a time with a 1 of N count, its source meeting and its age. The meeting title opens the cited part of that transcript. Pick Done, Later (hides it for 30 days) or Remove.
Mind pipelines, personas and feedback#
The backend stores matching and compaction as versioned agent pipelines. Admins can change candidate limits and decision thresholds in agent contracts under Execution pipeline and track captured user feedback in Personal training flywheel. Suggestions, extracted details, tasks and entity revisions include the producing agent version and tool trace.
The default Persona in the Mind toolbar is Work & Research. The optional Personal Health & Medical Visits persona adds clinician, condition, organ/system and medication labels on the same people and project records. The ontology API supports custom node and section overrides. Selecting this persona does not enable mobile capture or train a medical model.
Compaction runs after extraction and is also available from Compact in a page's More actions menu. It keeps a manual or newer detail, adds the older detail's citations and retains the superseded record in History. Duplicate open tasks combine their transcript citations while the original task remains a historical record. Different projects and assignees stay separate.
Each detail row offers Confirm detail and Revise detail (Outdated · move to History or moving between sections), and each task row offers Revise task (Already done, Not a to-do · move to Notes or moving to another project). The feedback API accepts OK, No and Revise. OK verifies an item without changing its text. No uses the existing removal and keep-separate rules. Revise can edit or move a fact, mark it outdated, complete a task or turn a non-todo into a cited note. Each action saves an owner-only feedback record with its agent trace and before/after output. Existing Merge and Keep separate actions save these records too. The training-readiness flag starts at 100 records and is a count marker only. No local training runs automatically.