Connected context in AUGMTD is persisted work state retrieved when a brief, draft, search, or coworker run is produced. It can include synchronized email and calendar activity, enabled meeting material, selected documents, people, commitments, initiatives, memory, and prior conversation.
Persistence changes the starting point
A one-time context window disappears after the interaction. Durable work state lets later briefs and actions begin with previously connected threads, people, commitments, files, and events.
Retrieval should be scoped
AUGMTD retrieves context according to the surface and work being handled. Selected Drive or OneDrive files can be indexed without assuming access to an entire company repository.
Relationships create a work picture
Threads, meetings, commitments, people, events, and files can connect around an initiative so a user can see momentum, recent history, and a proposed next move together.
People can correct the system
Associations and summaries are probabilistic. Users can relink, dismiss, edit, regenerate, and update context when the system has made a weak connection.
Where the boundaries sit.
- Live context means synchronized and retrieved work state, not zero-latency access.
- Selected-file permissions and indexing status affect what can be retrieved.
- Context can be incomplete, stale, or incorrectly associated.
