Tracked atomic identities
Each entry preserves references and status. The register distinguishes requirements, evidence and deferred items.
Reconciliation of 4 October 2026TECHNICAL TRANSPARENCY
The solutions.
The evidence that accompanies them.
Requirements, checks and receipts let you assess work on the Core against precise criteria. Each result has a scope and a date.
Architecture
MCP connects the model; OAuth authorises sources. OCR, ingestion, Knowledge, memory and the scheduler build the operational process.
Explore the implementationsEvidence
Receipts distinguish a requirement from an executed test, the outcome of an individual change from verification of the complete product, and acquired data from a validated result.
Follow the Core’s flow05 / REQUIREMENTS, TESTS AND INTEGRITY
Behaviour is described.
Then put to the test.
Checks also cover negative cases: a changed source, a revoked permission, an expired approval, a lost lease, a timeout and an unverifiable result.
Backend and UI contracts
Backend and UI checks on the four changes in the technical batch.
Receipt of 4 October 2026Memory, gateway and scheduler
Ten suites include tests of approvals, model results and concurrency.
Execution of 19 September 2026What is checked beyond the positive result+
Memory: source and revision, conflicts, invalidation and the distinction between facts and hypotheses.
Approvals: exact content, affected resources, expiry and payload changes.
Model Gateway: parsing, outcomes, credentials, lease loss and takeover.
Scheduler: concurrency, resumption and fairness between queues and sources.
Integrity: manifests and hashes define the changes. The 4 October batch checked 1.449 files: four changed, 1.445 unchanged and zero unexpected differences.
The register counts requirements; the suites count tests within their respective scopes and dates. They are different measurements, retained with their evidence.
HOW TO READ A RESULT
Trace the origin.
Define what has been proven.
- 01
Identity and revision
The source and version define the material on which verification was performed.
- 02
Execution conditions
Permissions, connector status, session and environment are part of the evidence.
- 03
Outcome and receipt
Success, waiting, error and an unverifiable result remain distinct states.
For a technical exploration of the project and its development.
Contact OmniAgents