Skip to content

Reconcile participant semantic specifications with current contracts (ASR-506) #219

Closed

Description

@Brad-Edwards

Normative participant specifications and invariant oracles already exist. This issue owns their completeness and consistency, not a replacement semantic model.

A confirmed mismatch: the ACT-606 formal description still lists legacy offensive/defensive classification fields that the current model rejects.

Done when

  • Map behavior, interaction, visibility, timing, causality, and outcomes to current normative clauses, contracts, implementation, and tests.
  • Correct stale current guidance and unexplained gaps, including classification bindings and decision-surface v1/v2 semantics.
  • Preserve ADR status and amendment history: ADR-067/083 remain proposed; ADR-095 is the accepted executable decision-surface amendment. Accepted ADR changes follow ADR-059.
  • Distinguish executable invariants, bounded model checks, runtime tests, and unproved claims.
  • Give every uncovered clause a concrete owner and acceptance test; reconcile ASR-506 traceability from the resulting coverage.

#1342 owns author-facing identity/migration guidance. #220 owns the executable conformance corpus. Do not turn this issue into a second owner of those deliverables.

Current implementation and remaining acceptance

  • Include accepted ADR-108 through ADR-114 and current revised-control guidance in the consistency map; preserve proposed/historical ADR status.
  • The ACT-606 formal description still lists legacy offensive/defensive classification fields rejected by the current model. Correct current normative guidance through the governed process; do not restore those fields.

Review basis

Reviewed against origin/dev at 0fd7ca30b1f17965263533e1a610731e4ab8ad8a on 2026-10-29. These links identify the baseline; implementation must use the current governed contracts.

Requirements

  • ASR-506 — Participant Semantic Artifacts

Activity

  1. changed the title [-]Participant Semantic Artifacts (ASR-506)[/-] [+]Reconcile participant semantic specifications with current contracts (ASR-506)[/+] on Sep 21, 2026
  2. 6 remaining items

  3. Brad-Edwards commented on Oct 29, 2026

    @Brad-Edwards
    CollaboratorAuthor

    gc workflow phase recorded: plan (issue #219). Posted by the MCP server to enforce ordering between workflow steps (issue #794 MVP-2). Do not edit or delete — used by downstream tools to gate phase prerequisites.

    Resume existing PR #1471 on its own branch, with the real clean merge of current origin/dev already staged. Design: docs/decisions/issue-219-participant-semantic-consistency-design.md; binding preflight: docs/decisions/issue-219-asr-506-participant-semantic-consistency-preflight.md.

    1. ASR-506 behavior/interaction/visibility/timing/causality/outcome artifact clauses (Path D): retain and reconcile the existing five-part semantic coverage matrix and shared family summary. Map current contracts, implementation and exact tests; preserve the six facets and all I1–I18 headings. Existing source/row, path, evidence-class and owner/acceptance guards protect this reconciliation.
    2. Current classification and identity guidance (Path D): retain external concept bindings and retired-field rejection; add the admitted control_context inventory entry using DSL-118/ACT-620 authority. The existing closed-model inventory test currently fails, as do PBM-13 and runtime-mapping coverage checks. Add their missing coverage without restoring classification fields or introducing runtime behavior.
    3. Decision/amendment and evidence distinctions (Paths A/D): add a live ADR status/normative-source/evidence crosswalk for ADR-067/083/095 and accepted ADR-108–114 (plus ADR-115's backend boundary). Add a failing structural crosswalk test before the table. Reuse the ADR parser and existing test resolver. Extend evidence import detection through local test helpers with a failing case before repair; keep abstract, bounded, runtime and proof evidence separate.
    4. Current support and uncovered clauses (Path D): link revised-control guidance; refresh closed gap owners from delivered tests. Record concrete existing open owners and target acceptance cases for residual guarantees. Keep Complete participant conformance coverage, including identity boundaries (ASR-507) #220's corpus and Update participant guidance and migration paths #1342's identity/migration ownership. Do not treat controlled-provider demonstrations as native qualification, independent reproduction, transfer or universal equivalence.
    5. Traceability and governance: update ASR-506's record and exact 219.json path assignments. Preserve its DRAFT lifecycle while the matrix documents incomplete obligations; record actual artifact and test links without promoting other requirements. Preserve historical captures and accepted ADR bytes/pins. No schema, publication ledger, vocabulary, package version or changelog changes are planned.

    Security: preserve closed parsing, exact offline binding resolution, cut/epoch/digest joins, separate participant/assurance planes, authenticated owner/effect boundaries and redacted diagnostics. Maintainability: reuse the existing matrix, guard module, ADR parser and governance manifest. Extensibility: append clause and revision-bound evidence records, without another model, registry or conformance runner. Whole-repository consumers: requirement governance/order, authority manifest, ADR pins, assurance fulfillment, semantic coverage, nox/hygiene, CI and Sonar.

    Verification: RAES_REQUIREMENT_UID=ASR-506 throughout. Existing baseline: 3 meaningful matrix failures, 23 passes; 39 incumbent semantic checks and 19 newer runtime-evidence checks pass. Run only the issue's explicit pytest module and selected cited cases locally, plus file-local policy, targeted requirement/ADR/coverage and Vale checks. CI owns full test, integration, fuzz, completion and repository-wide policy suites. Then required pre-push review, canonical publish/synchronization, existing PR update, hosted checks and readiness; user owns merge.

  4. Brad-Edwards commented on Oct 29, 2026

    @Brad-Edwards
    CollaboratorAuthor

    Document consistency before push

    Issue #219; branch 219-behavior-model-retired-classification-refs; pickup 6487849182.

    Design digest: 37bc439d82100524e970f862cba838c054d710751ddd0641a5dbac6423bfbe34.

    • docs/decisions/issue-219-participant-semantic-consistency-design.md (1de68ec844763b7853f9480ca69937ccca2ab912ea824dd0539cb6d10fa68ec1)

    Compared current merged dev contracts and source with ACT-606 control_context inventory, PBM-13, runtime mapping, and the 90-row consistency index. All 30 issue-specific structural tests pass after meaningful red failures; 39 incumbent and 19 newer evidence checks passed. Live ADR parser confirms proposed ADR-067/083 and accepted ADR-095/108–115. Historical v1 versus actionable v2 semantics, offline classifications, selected versus delivered context, separate effect/observation facts and native/proof nonclaims remain intact. Refreshed open owners and precise acceptance cases; ASR-506 remains DRAFT with 25 partial rows. Internal normative documents preserve stable invariant headings; public-reader style applies to public documentation, and no public page changed. Reviewed terminology and terse prose against official local STE text. Run the trusted document baseline for this candidate.

    Candidate tree: 20a908eb5e55ccd722cc178df02bc0901ccbdf71.
    Document check: vale: server-owned baseline (Vale.Repetition)
    Checker identity: a9749df8f46a9b49cf48ed4d14b737dd480f2c3a1a933959433a535c894408b7.

  5. Brad-Edwards commented on Oct 29, 2026

    @Brad-Edwards
    CollaboratorAuthor

    gc_codex_review — sanitized deferred publication for issue #219, cycle 1 of 1
    Reviewed revision: a746fd4a8e38ac37d4fd37ce8b37e456791ede3575edd60f903dc8308bb3a08b

    Architectural read

    The review covered all 29 files in two slices. The matrix reuses existing authorities, distinguishes bounded tests from stronger claims, and records gap owners and acceptance cases. No blocking architecture, code-quality, or exploitable security finding was identified.

    Verdict: ship

    Findings

    • (none)
  6. Brad-Edwards commented on Oct 29, 2026

    @Brad-Edwards
    CollaboratorAuthor

    gc_codex_review pre-push cycle 1 of 1 complete for issue #219 on branch '219-behavior-model-retired-classification-refs'. Posted by the MCP server to enforce the pre-push hard-cap-1 contract (issues #796, #804, #906). Do not edit or delete — used by the next gc_codex_review (uncommitted) invocation to count cycles.

  7. Brad-Edwards commented on Oct 29, 2026

    @Brad-Edwards
    CollaboratorAuthor

    Review decision record — codex cycle 1 (issue #219)

    Reviewer: codex
    Cycle: 1
    Verdict: ship

    Architectural read:

    The review covered all 29 files in two slices. The matrix reuses existing authorities, distinguishes bounded tests from stronger claims, and records gap owners and acceptance cases. No blocking architecture, code-quality, or exploitable security finding was identified.

    Blocking findings: 0 (clean run)

  8. Brad-Edwards commented on Oct 29, 2026

    @Brad-Edwards
    CollaboratorAuthor

    Pre-PR base synchronization

    • Source: refs/remotes/origin/dev at 0ab5bf575d7d178df43022d80a009da0a073c0f0
    • Outcome: already_current
    • Published feature head: 41ed0555d50688eba8b70eff26b22692c8b0cb3b
    • Synchronized tree: 20a908eb5e55ccd722cc178df02bc0901ccbdf71
  9. Brad-Edwards commented on Oct 29, 2026

    @Brad-Edwards
    CollaboratorAuthor

    Design complete

    Issue #219; branch 219-behavior-model-retired-classification-refs; pickup 6487849182.

    Design digest: e9f54d8fc339a6dce87b69f79bd1d244732804f705678ca364d52c8a9cf9704f.

    • docs/decisions/issue-219-participant-semantic-consistency-design.md (0ab2183c7ffc451965f65c8fb28b4d65a2d102808f2c903c5e366a96423c5f89)

    Research and coverage

    • specs/formal/participant-semantics/semantic-coverage.md: Extend the existing detailed clause/evidence index linked by the ADR-016 shared coverage summary; keep their status meanings distinct.
    • specs/formal/participant-behavior-model/README.md: Correct ACT-606/609/610 native field claims under existing external binding authority.
    • specs/concept-authority/external-concept-bindings.md: Preserve exact subject, offline scheme resolution and non-authorizing classification semantics.
    • docs/explain/reference/revised-control-semantics.md: Distinguish accepted design publications from current installed runtime support and unsupported combinations.
    • implementations/python/tests/test_issue_219_participant_semantic_coverage.py: Reuse source parity, exact field inventory, path/test resolution and evidence-class checks; add live ADR crosswalk checks.
    • https://docs.pydantic.dev/latest/concepts/models/ (2.12.5, Extra data and model fields): Closed native field inventory parity and rejection of obsolete classifications.
    • https://csrc.nist.gov/pubs/sp/800/160/v1/r1/final (Volume 1 Revision 1, November 2022, Security architecture and assurance): Explicit assets, threats, ownership, trust boundaries and verification limits.
    • https://www.asd-ste100.org/assets/files/ASD-STE100_ISSUE9.pdf (Issue 9, January 2025; official local copy /tmp/rae3-ste100-issue9.txt, Writing rules 1, 4, 5, 6 and 9): Manual terminology, sentence length, brevity and purpose review.
    • architecture: Design: Architecture and ownership retains SDL, contract, compiler, runtime and evidence incumbents; map extends existing reference.
    • systems_security: Design: Systems security maps scenario authority, hidden truth, historical evidence and assurance integrity threats to existing controls and tests.
    • data_flows: Design: Data flow and trust boundaries names author and participant entities, admission processes, policy/episode/evidence stores and projections.
    • diagrams: Design: Data-flow text diagram supplies components and flows; existing runtime specifications retain deployment/state models.
    • policy_as_code: Design: Existing file-local, requirement, ADR-pin, authority and documentation checks apply; no enforcement layer or schema changes.
    • architecture_as_code: Design: Existing field, clause and focused-specification parity tests expose three drift failures. Extend the same guard for live ADR status and transitive test-helper evidence, without new runtime enforcement.
    • adr_changes: Design: ADR-067/083 stay proposed; accepted ADR-095 and ADR-108–114 remain unchanged; ADR-059 governs any future accepted edits.
    • document_review: Design: Manual review against local official ASD-STE100 Issue 9, consistent technical names, short sentences, one topic and document purpose.
  10. Brad-Edwards commented on Oct 29, 2026

    @Brad-Edwards
    CollaboratorAuthor

    Document consistency before push

    Issue #219; branch 219-behavior-model-retired-classification-refs; pickup 6487849182.

    Design digest: e9f54d8fc339a6dce87b69f79bd1d244732804f705678ca364d52c8a9cf9704f.

    • docs/decisions/issue-219-participant-semantic-consistency-design.md (0ab2183c7ffc451965f65c8fb28b4d65a2d102808f2c903c5e366a96423c5f89)

    CI's exact source-bound runtime mapping regression was reproduced locally before repair. The incumbent collector freshly executed 25 public runtime cases and produced the content-addressed dd0ba4d8 capture: 8 matches, 15 incompatibilities and 2 observation gaps. Equivalence, full runtime realization and backend conformance remain not-established. Historical captures were preserved. The existing export regression and complete issue guard module pass against the new capture; exact ASR-506 scope assignments and traceability cover its two files. The design now explains test-source pinning and immutable regeneration. No source/model, schema, accepted ADR or runtime behavior changed. Reviewed document purpose, short prose, technical terms and evidence limits; run trusted document checks for this candidate.

    Candidate tree: 0064988b0be0396a0660cd5ae5b5f30778687c23.
    Document check: vale: server-owned baseline (Vale.Repetition)
    Checker identity: a9749df8f46a9b49cf48ed4d14b737dd480f2c3a1a933959433a535c894408b7.

  11. Brad-Edwards commented on Oct 29, 2026

    @Brad-Edwards
    CollaboratorAuthor

    Pre-PR base synchronization

    • Source: refs/remotes/origin/dev at 0ab5bf575d7d178df43022d80a009da0a073c0f0
    • Outcome: already_current
    • Published feature head: 02a5a2da8c1ef568b18796e32ca01135833ae92d
    • Synchronized tree: 0064988b0be0396a0660cd5ae5b5f30778687c23
  12. Brad-Edwards commented on Oct 29, 2026

    @Brad-Edwards
    CollaboratorAuthor

    Ready for review — issue #219

    PR: #1471
    Plan: #219 (comment)

    Outcome

    Maintainers can trace participant meaning to current clauses, contracts, implementation and tests. The map identifies remaining guarantees and their acceptance cases, while current classification and decision-surface guidance matches the governed contracts.

    In-scope requirements

    Proposed state in this PR — authoritative only after merge.

    • ASR-506 (Participant Semantic Artifacts) — DRAFT (proposed) — The consistency map records 90 rows with 25 partial obligations, each with concrete ownership and acceptance tests.

    Files changed

    Added:

    • docs/decisions/issue-219-asr-506-participant-semantic-consistency-preflight.md
    • docs/decisions/issue-219-participant-semantic-consistency-design.md
    • docs/governance/requirement-scopes/219.json
    • docs/research/formal-semantic-validation/capture-records/capture-07d8a3564e4c657749a8d5403312543c7253c75b36a130286b434361ccd4ad3e.json
    • docs/research/formal-semantic-validation/captures/capture-07d8a3564e4c657749a8d5403312543c7253c75b36a130286b434361ccd4ad3e/analysis.json
    • docs/research/formal-semantic-validation/captures/capture-07d8a3564e4c657749a8d5403312543c7253c75b36a130286b434361ccd4ad3e/manifest.json
    • docs/research/formal-semantic-validation/captures/capture-07d8a3564e4c657749a8d5403312543c7253c75b36a130286b434361ccd4ad3e/snapshot.json
    • docs/research/specification-coverage/capture-records/capture-5d13883d4d64630b4495667dc0b85db2c87987421371d16e883741383d0c3118.json
    • docs/research/specification-coverage/captures/capture-5d13883d4d64630b4495667dc0b85db2c87987421371d16e883741383d0c3118/analysis.json
    • docs/research/specification-coverage/captures/capture-5d13883d4d64630b4495667dc0b85db2c87987421371d16e883741383d0c3118/manifest.json
    • docs/research/specification-coverage/captures/capture-5d13883d4d64630b4495667dc0b85db2c87987421371d16e883741383d0c3118/snapshot.json
    • implementations/python/tests/test_issue_219_participant_semantic_coverage.py
    • specs/formal/participant-semantics/runtime-mapping/capture-dd0ba4d888b2cbb4dce76715df8ea780b4f6554b910da57901acc7ab2f0c5d17/cases.json
    • specs/formal/participant-semantics/runtime-mapping/capture-dd0ba4d888b2cbb4dce76715df8ea780b4f6554b910da57901acc7ab2f0c5d17/manifest.json
    • specs/formal/participant-semantics/semantic-coverage.md
    • specs/formal/participant-semantics/semantic-coverage/behavior-model-and-runtime.md
    • specs/formal/participant-semantics/semantic-coverage/design-commitments-sem-208-to-211.md
    • specs/formal/participant-semantics/semantic-coverage/design-commitments-sem-212-to-215.md
    • specs/formal/participant-semantics/semantic-coverage/family-rows.md
    • specs/formal/participant-semantics/semantic-coverage/invariants-i1-to-i18.md

    Modified:

    • docs/decisions/package-artifacts/operations.md
    • docs/explain/reference/participant-decision-surface-v2-migration.md
    • docs/explain/reference/shared-semantic-integrity.md
    • docs/requirements/ACT-609/requirement.md
    • docs/requirements/ACT-610/requirement.md
    • docs/requirements/ASR-506/requirement.md
    • specs/formal/assurance-fulfillment.yaml
    • specs/formal/participant-behavior-model/README.md
    • specs/formal/participant-semantics/README.md
    • specs/formal/participant-semantics/reusable-mixed-control.md
    • tools/policy/requirement_order.yaml

    Reviews

    • Codex: Core and security review covered 29 files without findings. The subsequent CI repair adds freshly executed source-bound evidence and passes its existing regression checks.

    Traceability reconciliation

    Proposed in this PR — verified against the merged tree in Phase E.

    • IMPLEMENTS / TESTS / DOCUMENTS added: 0
    • Links updated: 2
    • Stale links removed: 0

    Status

    • CI: ✅ green
    • SonarCloud: ✅ passed
    • PR ready for user review and merge. Phase E validates the merged requirement state, posts the final report, and closes the issue automatically once this PR merges.
  13. Brad-Edwards commented on Oct 29, 2026

    @Brad-Edwards
    CollaboratorAuthor

    Delivery readiness recorded — Phase E finalizes issue #219 automatically when PR #1471 merges.

  14. github-actions commented on Oct 29, 2026

    @github-actions
    Contributor

    Final report — issue #219 complete

    PR: #1471
    Plan: #219 (comment)

    Outcome

    Maintainers can trace participant meaning to current clauses, contracts, implementation and tests. The map identifies remaining guarantees and their acceptance cases, while current classification and decision-surface guidance matches the governed contracts.

    In-scope requirements

    Verified at merge revision 84cd21bffba8.

    • ASR-506 (Participant Semantic Artifacts) — DRAFT — The consistency map records 90 rows with 25 partial obligations, each with concrete ownership and acceptance tests.

    Files changed

    Added:

    • docs/decisions/issue-219-asr-506-participant-semantic-consistency-preflight.md
    • docs/decisions/issue-219-participant-semantic-consistency-design.md
    • docs/governance/requirement-scopes/219.json
    • docs/research/formal-semantic-validation/capture-records/capture-07d8a3564e4c657749a8d5403312543c7253c75b36a130286b434361ccd4ad3e.json
    • docs/research/formal-semantic-validation/captures/capture-07d8a3564e4c657749a8d5403312543c7253c75b36a130286b434361ccd4ad3e/analysis.json
    • docs/research/formal-semantic-validation/captures/capture-07d8a3564e4c657749a8d5403312543c7253c75b36a130286b434361ccd4ad3e/manifest.json
    • docs/research/formal-semantic-validation/captures/capture-07d8a3564e4c657749a8d5403312543c7253c75b36a130286b434361ccd4ad3e/snapshot.json
    • docs/research/specification-coverage/capture-records/capture-5d13883d4d64630b4495667dc0b85db2c87987421371d16e883741383d0c3118.json
    • docs/research/specification-coverage/captures/capture-5d13883d4d64630b4495667dc0b85db2c87987421371d16e883741383d0c3118/analysis.json
    • docs/research/specification-coverage/captures/capture-5d13883d4d64630b4495667dc0b85db2c87987421371d16e883741383d0c3118/manifest.json
    • docs/research/specification-coverage/captures/capture-5d13883d4d64630b4495667dc0b85db2c87987421371d16e883741383d0c3118/snapshot.json
    • implementations/python/tests/test_issue_219_participant_semantic_coverage.py
    • specs/formal/participant-semantics/runtime-mapping/capture-dd0ba4d888b2cbb4dce76715df8ea780b4f6554b910da57901acc7ab2f0c5d17/cases.json
    • specs/formal/participant-semantics/runtime-mapping/capture-dd0ba4d888b2cbb4dce76715df8ea780b4f6554b910da57901acc7ab2f0c5d17/manifest.json
    • specs/formal/participant-semantics/semantic-coverage.md
    • specs/formal/participant-semantics/semantic-coverage/behavior-model-and-runtime.md
    • specs/formal/participant-semantics/semantic-coverage/design-commitments-sem-208-to-211.md
    • specs/formal/participant-semantics/semantic-coverage/design-commitments-sem-212-to-215.md
    • specs/formal/participant-semantics/semantic-coverage/family-rows.md
    • specs/formal/participant-semantics/semantic-coverage/invariants-i1-to-i18.md

    Modified:

    • docs/decisions/package-artifacts/operations.md
    • docs/explain/reference/participant-decision-surface-v2-migration.md
    • docs/explain/reference/shared-semantic-integrity.md
    • docs/requirements/ACT-609/requirement.md
    • docs/requirements/ACT-610/requirement.md
    • docs/requirements/ASR-506/requirement.md
    • specs/formal/assurance-fulfillment.yaml
    • specs/formal/participant-behavior-model/README.md
    • specs/formal/participant-semantics/README.md
    • specs/formal/participant-semantics/reusable-mixed-control.md
    • tools/policy/requirement_order.yaml

    Reviews

    • Codex: Core and security review covered 29 files without findings. The subsequent CI repair adds freshly executed source-bound evidence and passes its existing regression checks.

    Traceability reconciliation

    • IMPLEMENTS / TESTS / DOCUMENTS added: 0
    • Links updated: 2
    • Stale links removed: 0

    DRAFT lifecycle preserved; source specifications, versioned contracts, executable evidence and unresolved guarantees remain distinct.

    Status

    • CI: ✅ green
    • SonarCloud: ✅ passed
    • PR ready for user review and merge.
  15. removed
    in-progressAn agent is actively working this issue via /implement
    on Oct 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    requirementTracks a Ground Control requirementwave-2Wave 2 requirement

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions