ENGINEERING SELF-ASSESSMENT REFERENCE
Trace evidence
to your control review.
Inspect how ACGS decision and audit fields can support a record-keeping review, with gaps and operator responsibilities kept visible.
- 01
Identify the evidence
Locate decision, policy, argument-hash, and audit fields.
- 02
Review the mapping
Inspect the source’s field-level claims and explicit gaps.
- 03
Assess the whole system
Establish the applicable requirements and deployment controls separately.
What the source mapping examines
- Decision and policy context
- Fields that help reconstruct what was evaluated and which policy evidence was used.
- Argument commitments
- Hashes that bind the recorded decision to specific input values.
- Audit links
- Event references that connect the decision to retained local evidence.
- Supplied identities
- Actor and validator identifiers whose real-world authentication remains external.
Keep the mapping’s limits visible
The project’s Article 12 mapping documents candidate-stage field-level traceability and explicit gaps. Retention, durability, identity assurance, and interpretation of monitoring evidence need controls beyond a receipt schema.
The referenced example pack contains a development receipt and sample action. It is not production traffic or independent validation of every mapped control.
Read the engineering reference
The source mapping documents live in the private evaluation repository (request evaluation access at evaluation@acgs.ai); see Architecture & bounded contexts for the public receipt, grant, and audit field definitions. Consult the official regulation and appropriate advisers for applicability and current obligations. This page intentionally makes no deadline, fine, coverage-score, or compliance-scan promise.
Open the official regulation