Technology · ACTA
Keep the operational record.
ACTA records what an agent intended, what it asserted, which context it was given and what happened — and lets that record be reconstructed and checked later. It is more than a hash ledger: the record carries meaning, lifecycle and the reasons items were included or left out.
Record
Intents, claims and state.
Intents
Standing goals and boundaries, recorded with a version and retired explicitly rather than silently dropped.
Claims
Subject–predicate–object assertions with a confidence. Superseding a claim points at the one it replaces; retraction is one-way and stays on record.
Memory
Notes and observations stored with tags. Retracting memory removes it from future context without deleting its history.
State roots
A hash committing to all active intents, claims and memory for a workspace at a point in time.
Context
Context that says what it used — and why.
For each task ACTA compiles a signed context bundle from active intents, resolved claims and relevant memory, fitted to a budget.
Exclusion manifest
Every compiled bundle can explain what was left out: superseded, retracted, conflicting or over budget.
Conflicts surfaced
Contradicting claims are reported as an action queue instead of being resolved silently.
Pins
A claim can be pinned so the budget never drops it. A pin never brings back a superseded or retracted claim.
Reuse
Answers that stay valid only while their basis holds.
Answer cache
A stored answer is returned only while the state root and declared volatility it was computed under still hold. Undeclared answers expire.
Training evidence
Dataset manifests, plans, checkpoints, runs, evaluations and outcomes can be notarized and their lineage verified. ACTA records evidence; it does not run training or make a model routable.
Node fabric
Enrolled nodes, typed jobs.
Compute nodes enroll with an identity and resource profile, send heartbeats, and claim typed jobs. Each job’s claim, start and result are recorded as evidence.
What ACTA does not claim.
Integrity, not truth
A verified entry is intact and correctly signed. That does not make the claim inside it correct.
Workspace-scoped
Reads and writes are scoped to the authenticated workspace. Other workspaces’ records are never returned.
Named versions
Only features in the running release are described here. The ACTA interoperability profile is a v1 draft pending publication.