OpenChainGraph Suite · ART-651

Authzen Conformance Fixture

Evaluates the 8-decision AuthZEN Authorization API 1.0 certification fixture (AUTHZEN-CONFORMANCE-BUILD-SPEC.md) through the spec-mandated subject/action/resource/context request envelope (Information Model §5, Access Evaluation API §6.1-6.2), against a local hand-authored FIXTURE_POLICY. AuthZEN is an OpenID Foundation open specification rather than a regulation or legal instrument , standards_basis is implements_standard against a published spec, per SO #38 Step 0. The spec itself is silent on PDP decision logic (§2: 'policy language... beyond the scope of this specification'), so the 8 decision outcomes are mechanical, hand-authored test-fixture policy (role/resource-state/action-parameter rules), not spec-mandated content; what IS spec-mandated and cited below is the request/response envelope shape and the boolean-only Decision semantics the fixture is expressed through. Also checks the §6.1 'context is OPTIONAL and must not change the decision' invariant on every decision.

compliance_controlZero PIIClient-side only

🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.

Scope & reliance

The Decision VALUE for each of the 8 fixture requests (whether alice/bob may read/write/delete a given record) is local hand-authored test policy rather than spec-mandated content , AuthZEN §2 explicitly places PDP policy logic out of scope ('The policy language, architecture, and state management aspects of a PDP are beyond the scope of this specification'). What is cited above and exercised by compute() is the request/response ENVELOPE (§5 Subject/Action/Resource, §6.1 request shape with OPTIONAL context, §6.2 response-is-a-Decision, §5.5 boolean-only decision semantics) and the §6.1 context-optional invariant, checked on every decision. CLAUSE-SILENT determination (SO #39(b)(ii), art-617 precedent): the fixture-policy rule table is a design choice named explicitly here, not an omission, and needs no further authority because it is not asserted as spec-mandated. No formal correctness proof exists for this node yet (compute_proof_ready: deferred); see the proof-status note below the results.

Policy Parameters (JSON)

policy_parameters (passed verbatim to compute())

Result

Proof status

This node ships compute_proof_ready: deferred. No formal correctness proof has been produced for this kernel; the result above is a deterministic recompute, verified by a property-test floor, not a proven one.

Execution Hash & §4 Artifact

SHA-256 execution hash (JCS canonical, RFC 8785):

Ask your agent

Copy this paragraph into Claude, OpenClaw, or any MCP-aware agent to run this exact tool, with this sample, and verify the artifact.

Run the AINumbers MCP tool `compute_authzen_conformance_fixture`. Task: Evaluate the AuthZEN Authorization API 1.0 8-decision certification fixture (or a caller-supplied override) against a local decision policy, through the spec-mandated request/response envelope, and reports per-decision agreement with the mandated outcomes and the context-optional invariant.
Call it with arguments: {"policy_parameters":{}}
Verify before trusting: call `verify_execution_hash` on mcp.ainumbers.co (https://mcp.ainumbers.co/mcp) with the parameter `claimed_hash` set to the returned `execution_hash`, passing the full artifact the run returned (the object containing `policy_parameters` + `output_payload` + `execution_hash`; equivalently `policy_parameters` + `output_payload` with `claimed_hash`), not the bare hash string.
Return the ledger link https://ledger.ainumbers.co/ so a human can re-verify without contacting us.
PII rule: All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.
Open the tool with the sample prefilled: https://ainumbers.co/chaingraph/art-651-authzen-conformance-fixture.html#p=v1.H4sIAAAAAAAA_wECAP3_e31Dv6ajAgAAAA