ARCHITECTURE / INSIDE OMNIAGENTS
Sources, memory, agents, permissions and tools work within the same process. The value lies in how these elements coordinate, preserve context and make the work verifiable.
TWO CYCLES, ONE ARCHITECTURE
The process that learns from sources is separate from the one that answers a question. They share memory, identity and rules.
Learning is configured and authorised. A change in a source can update the available context.
You use your compatible AI. The dashboard can remain closed while the Core is running and reachable.
TWO MEMORIES. YOUR INFORMATION ASSETS.
Chat memory and the Core’s internal memory have distinct tasks. Together, they give continuity to your work.
Conversations managed by the Core preserve messages and context, linked to the user, session and request. You can resume work with its references. Your AI provider’s private history remains separate.
Knowledge and Deep Memory organise knowledge, facts and connections derived from authorised sources. They preserve origin, revisions and status: useful context can be retrieved even in a new conversation.
Documents, content, conversations and the information assets of your environment remain under your control. The OmniAgents licence does not transfer ownership of the data to the provider.
Your memory does not become the property of OmniAgents.
Export, retention and deletion follow separate processes. Ending your subscription does not automatically delete your data.
THE PROCESS, STEP BY STEP
Open the details to see the mechanisms present in the code.
OmniAgents recognises the revision, checks the connection and preserves the point from which to resume. Unchanged items can be skipped before calling the model again.
Each source has separate progress tracking. Leases, checkpoints and receipts prevent a new revision from being confused with content already acquired. The frequency depends on the configured connector.
CORE MODULES · source-delta-supervisor.tsEmails, documents and attachments retain their identity, version and relationships. Reusing the same file does not erase the different places it came from.
Byte deduplication is separate from occurrences. Origin, account, revision, actor, correlation and the reference to the parent document are preserved.
CORE MODULES · connector-source-ingestion.tsText is extracted; coverage is checked. Only the subsequent process builds knowledge linked to what the model has actually processed.
Parsing and OCR record pages, coverage and parser versions. Full-source learning works in units, verifies contributions from the roles and consolidates knowledge. An imported file alone does not prove understanding.
CORE MODULES · canonical-document-learning.ts · canonical-source-learning.tsFacts, hypotheses and inferences have different states. If something changes or contradicts something else, the system can mark it as superseded, invalidated or requiring clarification.
Retrieval filters by role, validity and authorised scope. Foundation, the product guide and the organisation’s facts remain separate layers: a manual does not grant permissions or become a customer fact.
CORE MODULES · control-plane/memory.ts · product-knowledge.tsThe Core can involve Eric, a specialist or several areas of expertise. Eric brings together the contributions actually produced and returns a synthesis.
AI×9 describes nine coordinated roles. A simple question does not require nine calls; work with several professional outputs can activate the Council. Direct mode retains the selected specialist.
CORE MODULES · agents/runtime.tsThe system verifies identity, session, tool capabilities and applicable rules. When confirmation is needed, the activity remains on hold.
Without an explicit rule, execution is blocked. Available capabilities, role and permissions are checked again before the external effect. Sources and model responses cannot grant themselves new privileges.
CORE MODULES · control-plane/policy.ts · control-plane/registry.tsThe response is linked to the correct request. Completed, pending and requiring verification remain distinct outcomes, visible in the work process.
Closing a task and producing an effect on an external service are different forms of evidence. An ambiguous timeout remains unverified and requires reconciliation: automatically repeating a send could duplicate it.
CORE MODULES · control-plane/tasks.tsA CASE THAT CROSSES THE SYSTEM
“Compare the request received by email with the attached contract and the previous version. Highlight what has changed and prepare a reply.”
Email and PDF retain their relationships and revisions. A duplicate attachment does not lose its origin.
The system retrieves the authorised context and distinguishes explicit data, interpretations and points requiring clarification.
Research and communication can contribute to the dossier and draft. Eric combines the actual contributions.
Preparing is not the same as sending. Any send requires capabilities, permissions and confirmation when required.
You receive: a comparison of versions, source references, open questions and a draft. The outcome of any actions remains separate from the text of the response.
WORK LEAVES A TRACE
Operational metrics link sources, documents, the model, tools and recorded results. Business reports make the agents’ work understandable.
The Business experienceFollow activities over time and retrace the process that led to the result.
THE PURPOSE OF THE WORK DONE
Sources, knowledge, roles and memory belong to the Core. You can change a compatible AI connection without rebuilding everything.
An import is not understanding. A draft is not a send. An accepted request is not a verified result.
Identity, permissions, provenance and receipts accompany the process. An uncertain outcome remains visible as such.
