A.6:4.1.1 - AssuranceLane skeleton (informative)
An MVPK AssuranceLane is a publication face that teaches a specific audience how to adjudicate E-* claims against the relevant evidence carriers, including those produced in Work. It cites the boundary’s evidence-interface declarations and explains them without changing their semantics.
Minimal content (suggested):
- Scope: boundaryRef, version; viewRef and viewpointRef when view or viewpoint identity matters.
- Carrier inventory: carrier-class and carrier-schema refs (A.7 Carrier) + where to obtain them.
- E‑claim map: a table keyed by
E-*ID with: measurement conditions, carrierRef(s), join and correlation keys, and a reference to the canonicalE-*text that defines pass or fail criteria. - Operational policies: references to relevant
D-*duties (retention, access control, exposure), without redefining them. - Limitations: sampling, redaction, missing signals, expected false negatives and false positives.
An AssuranceLane explains adjudication. Add a new boundary claim to its governing source before using it in that face; a permission-looking claim needs its selected A6-AW-* object and basis.
Example (conceptual; uses view/viewpoint identity and the additional hypothetical header case in §4.2):
AssuranceLane:
viewRef: <ViewId>
viewpointRef: <ViewpointId>
boundaryRef: <BoundaryId>
version: <SemVer or revision>
evidence:
- E: E-OBS-1
carrierRefs: [Carrier.AuthorizationRecord, Carrier.AuditLogEntry]
measurement:
conditions: "on every request lacking header X (A-AC-1)"
vantage: "Operator and auditor pipeline"
correlation: ["traceId", "requestId"]
adjudication:
check: "query audit stream for code=NotAdmissible and join to traceId"
criteriaRef: "E-OBS-1 (pass or fail criteria live canonically in the E-claim)"
references: [A-AC-1, D-RET-1, Mechanism.AuditObservability]
The absence condition also covers a request that was not rejected. A claim of complete coverage requires the relevant request population to be accounted for separately from individual query joins.
Default placements (quadrant → stack layer / section):
- L → Signature.Laws (and, where appropriate, mechanism‑local semantic laws; never runtime gates)
- A → the canonical source of the governing admission rule; use
Mechanism.AdmissibilityConditionsfor mechanism applications and the applicable profile rule for A.21 gates - D → generic prescriptions, individual duties or commitments, recommendations-as-duty, prohibitions, and
A6-AW-NORM-GRANTclaims at their A.2.8 or A.2.8.PER subject pattern - E → actual occurrences, evaluated findings, and evidence claims, including
A6-AW-EXERCISE,A6-AW-WEAK,A6-AW-CONFLICT, andA6-AW-SOURCEwhen those claims are current
Related subject rules (informative):
- A.6.1 ↔ A‑quadrant:
U.Mechanism.AdmissibilityConditionsis the canonical source forA-*admission predicates of mechanism applications. - A.10 / B.3 ↔ E‑quadrant: when an
E-*claim needs a replayable source-to-use account, recover its A.10 evidence-provenance path and bounded use. A missing required path narrows or blocks only the unsupported use. Open B.3 only for a named assurance claim about an exact target and assurance use. - A.2.3 and F.12 ↔ D/E separation: a
U.PromiseContentstates the promised outcome and acceptance criteria; F.12 evaluates fulfilment using Work evidence. A general duty remains normative content, while an obtaining individual duty is one A.2.8U.Commitmentborne by an actual System or other admitted party. Any system-role kind or assignment used to establish applicability stays separate.D-*claims referenceA-*andE-*claims by ID or canonical location when needed.
This placement supports change through the dependencies:
- A realization, audit format or transport mechanism can change while the boundary declarations remain valid, provided their applicable constraints are still satisfied.
- A changed declaration requires reconsidering the uses that depend on it and communicating any consequential compatibility or version change.