Patents

Family Three: Unified context across AI models and knowledge systems

One authoritative context. Many models. Many sources. No AI provider owns the truth.

Embodied in HelixProvider-neutral contextPatent pending
Many sources · one authoritative context · many models
Conversations
Files
Email
Meetings
Enterprise artifacts
Semantic memory
Authoritative context fabricowned by no provider
Aprovider A
Bprovider B
Llocal model
No AI provider owns the truth
  • 1authoritative context fabric
  • 6kinds of source in that context
  • 4scope levels a participant is filtered by
  • 0AI providers that own the truth

Methods and Systems for Maintaining Unified Conversation Context Across Heterogeneous Reasoning Backends Using a Provider-Neutral Substrate and a Transcript Authority Decoupled From a Scoped Semantic Store. U.S. Provisional Patent Application No. 64/147,766 (patent pending). Embodied in the collaboration shell of Helix.

One fabric instead of scattered sources

Traditional AI systems inherit fragmented context from whichever tool or provider they happen to be using: conversations in one place, files in another, email, meetings and enterprise artifacts elsewhere, with no single complete view. This invention holds context in one authoritative context fabric that no provider owns, which any of many heterogeneous models can be grounded from.

Fragmented
Chat
A
Files
B
Email
L
each model sees whatever its own tool happens to hold
Unified
One fabrictranscript authority, semantic memory, revisions, provenance
A
B
L

The fabric keeps the transcript authority, the semantic memory, the revisions with their watermarks and the provenance of every source, and the shared thread is authoritative independently of any provider's native session.

Context is more than conversation

Context is the union of many knowledge sources: conversations and transcripts, files and documents, email, meetings, application or enterprise artifacts, and semantic knowledge. A chat history is one part of it, never the whole.

Conversations and transcripts
Files and documents
Email
Meetings
Enterprise artifacts
Semantic knowledge
the outer line is the whole context; the conversation is one region inside it
Region sizes are illustrative.

Context filtered by scope

Each participant receives context appropriate to its operating scope, system, project, work order or conversation, rather than the entire corpus. Context is filtered by scope, so a model sees only what it is authorised to see.

System
Project
Work order · where the participant is
Conversation in that work order
Another project
scope filter
the participant’s scope
inside the filter
outside it, never seen
An illustrative participant at one work order.

Shared authority, separate native continuity

The invention separates the authoritative shared context from each backend's own session continuity. Each provider keeps its native continuity for what it is good at, and none of those sessions becomes the record.

Shared authoritythe authoritative context fabric
Provider A session
Provider B session
Local session
each strip is that backend’s own native continuity; none of them is the shared record

What a provider remembers in its own session never stands in for the shared record.

Model memory is not system memory.

A grounding packet for the current moment

Each model receives a grounding packet reconstructed from the authoritative fabric at the current scope and the current revision, combined with that model's own provider-native continuity, rather than owning the full authoritative memory itself.

Provider A
Provider B
Local model
reconstructed from the fabric at the current scope and revision: the same for every model
that model’s provider-native continuity

Revisions under a watermark

Semantic memory evolves under explicit revisions, each change applied to the previous revision to produce the next, and a watermark records which revision a packet reflects. The authoritative historical thread stays traceable.

Revisions
between r17 and r18: a new meeting, a new file, a new conversation
Watermark
the packet records the revision it was built at
every earlier revision stays readable, so the thread is traceable
Revision numbers are illustrative.

Additive degradation

If one context source is temporarily unavailable, the system degrades additively: it grounds on the sources it has, names the one that is missing, and does not lose the thread.

Files
Email
Meetingsunavailable
Artifacts
Grounding packet
The thread goes on with the sources that answered.

Knowledge that outlives any session

Knowledge lifetime exceeds model session lifetime. Many systems contribute to one authoritative context, and many models can join, leave and resume without any one provider becoming the owner of the truth.

Shared knowledge
Model A
Model B
Local model
Session lengths are illustrative.