ASCR means Agent State & Context Runtime Contract.
ASCR is a framework-neutral contract for exporting, validating, replaying, and auditing agent runtime state: event logs, context manifests, memory records, artifact manifests, capability manifests, approval events, and eval cases.
It is not an agent framework, memory database, observability dashboard, MCP replacement, A2A replacement, or cloud agent platform.
Modern agents act from compiled context: instructions, memories, artifacts, tool schemas, prior events, policies, approvals, and eval criteria. Existing frameworks and observability tools can show pieces of the run, but teams still need a portable way to answer:
- What happened in this run?
- What context did the model see, and why?
- Where did this memory come from, and is it still allowed?
- Which artifact version entered context?
- Which capability or approval allowed this action?
- Can this failure become an eval case?
ASCR defines the portable metadata and validation surface for those questions.
The initial toolkit includes:
ascr.run_event.v0.1ascr.context_manifest.v0.1ascr.memory_record.v0.1ascr.artifact_manifest.v0.1ascr.capability_manifest.v0.1ascr.approval_event.v0.1ascr.eval_case.v0.1
The CLI validates JSON and JSONL artifacts against required schema versions and required fields. It deliberately does not call providers, write to memory backends, execute workflows, or publish benchmark claims.
python3 -m ascr_toolkit.cli validate-sample
python3 -m unittest discover -s tests -vValidate a file:
python3 -m ascr_toolkit.cli validate samples/coding-agent/context-manifest.json
python3 -m ascr_toolkit.cli validate samples/coding-agent/run-events.jsonlCheck the public boundary:
python3 -m ascr_toolkit.cli boundary-check .CtxGov is the first public evidence/report-shape surface aligned to ASCR. ASCR is the separate standard/toolkit project. CtxGov does not define the ASCR standard, and ASCR does not inherit CtxGov private fixtures, private traces, or private release claims.
No public benchmark claim. No security guarantee. No provider/model compatibility claim. No adoption claim. No hosted runtime claim. No package publication claim. No live adapter claim. No stable standard claim.
Apache-2.0.