ACT-605 — Reconcile baseline behavior profiles with autonomous participants

[Brad-Edwards]

ACT-605 | FUNCTIONAL | SHOULD | Wave 2 | DRAFT

Requirements

• ACT-605 — Declarative Baseline Behavior Profiles

Requirement Statement

The ecosystem shall support declarative baseline behavior profiles for non-adversarial participants, including ordinary user, automation, and ambient scenario activity.

Objective

Reconcile ACT-605 with the accepted autonomous-participant architecture and its existing end-to-end implementation.

Baseline activity is ordinary participant behavior authored through ParticipantBehaviorSpecification.autonomous_execution. Non-evaluated activity uses green participants, shared time, governed action and observation contracts, backend admission, runtime execution, and typed evidence. It must not introduce a separate background-actor, scheduler, clock, or activity ontology.

Authority

• ADR-092: Autonomous Benign Participants Under Shared Time
• Autonomous Participant Execution formal specification
• Participant behavior specification model
• Autonomous execution policy models

Scope

• Explicitly identify ACT-605 as covered by ADR-092 and the autonomous-execution formal specification.
• Verify that the existing v2/v3 policy surface covers work and pause windows, bounded timing, weighted action selection, dependencies, retries, cooldowns, bursts, execution limits, evaluation-authority separation, and runtime evidence.
• Update SDL documentation that still lists user behavior profiles as an expressiveness gap.
• Reconcile Ground Control DOCUMENTS, IMPLEMENTS, and TESTS links to the current ADR, specification, code, and tests.
• Transition ACT-605 to ACTIVE once coverage and traceability are verified.

Acceptance Criteria

• ADR-092 and the formal specification explicitly cover ACT-605.
• Baseline user, automation, and ambient activity is represented through autonomous green participants without a parallel actor model.
• Existing parser, semantic-validation, compiler, runtime, backend-admission, persistence, conformance, and negative-test coverage is verified.
• The stale “User behavior profiles” limitation is removed or rewritten to describe only a demonstrable remaining gap.
• Ground Control contains current DOCUMENTS, IMPLEMENTS, and TESTS links for ACT-605.
• ACT-605 is transitioned from DRAFT to ACTIVE.

[Brad-Edwards]

🛠️ Picked up by /implement - driver Codex, branch 213-act-605-reconciliation, 2026-08-01T17:13:24.206Z.

[Brad-Edwards]

gc workflow phase recorded: preflight (issue #213). 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.

[Brad-Edwards]

gc workflow phase recorded: plan (issue #213). 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.

Implementation Plan

Scope

• Keep the existing autonomous-participant model as the sole ACT-605 implementation surface; add no SDL field, schema, runtime service, backend protocol, or parallel background-actor abstraction.
• Amend ADR-092 and its formal autonomous-execution specification to identify ACT-605 explicitly as the requirement covered by the existing v1/v2/v3 policies and invariants.
• Record the accepted-ADR amendment in adr-index.yaml, update its canonical-content pin, and keep the ADR's in-file amendment table synchronized.
• Remove the stale “User behavior profiles” row from the SDL limitations table.
• Retain the architecture-preflight note as the durable boundary and traceability guide.

Existing Coverage And Remaining Gap

Existing parser, semantic-validation, compiler, capability-admission, scheduler/native-execution, persistence, control-plane, conformance, and negative-test paths already implement ordinary user, automation, and ambient activity through ParticipantBehaviorSpecification.autonomous_execution. The remaining repository diff is documentation and accepted-ADR governance; Ground Control status and links reconcile only after merge.

Requirement And Acceptance Coverage

• ACT-605 declarative profiles: bind the requirement to the existing behavior specification and v1/v2/v3 autonomous policy models in ADR-092 and the formal specification.
• Non-adversarial participants: retain the fail-closed evaluation_authority.mode: none → green invariant.
• User and ambient activity patterns: cite existing work/pause windows, bounded timing, weighted actions, dependencies, retries, cooldowns, bursts, finite limits, shared time, native execution, and typed evidence.
• No parallel actor model: preserve ADR-092's rejection of background actors, private schedulers, and private clocks.
• Documentation accuracy: remove the obsolete expressiveness-gap entry.
• Traceability/status: after merge, add current DOCUMENTS, IMPLEMENTS, and TESTS links and transition ACT-605 to ACTIVE.

TDD And Verification

The documentation-only carve-out is not taken because adr-index.yaml is executable policy data consumed by the ADR pin gate. Use the existing ADR-059 structural gate as the red-green driver: amend ADR-092 while retaining the old index pin to observe the expected pin/amendment failure, then add the matching #213 index amendment and canonical-content pin and rerun the gate green. No substring/snapshot prose test will be added.

Run focused existing coverage for DSL-437 behavior, evaluation authority, snapshot durability/conformance, issue #898 lifecycle/control, and issue #899 v3 resource budgets. Re-run the previously timed-out authenticated control-plane case explicitly. Then run the repository-required policy, requirement-governance, verify_all.py, completion, review, CI, and SonarCloud gates.

Cross-Cutting Design

• Security: cross no new auth, secret, environment, subprocess, socket, or API boundary; document the existing parser, reference, admission, generation-fencing, typed-result, persistence, and redacted-error gates without weakening them.
• Maintainability: reuse ADR-092, the formal autonomous-execution specification, the v1/v2/v3 model union, canonical compiler/runtime/admission helpers, ADR-059 pin tooling, and existing tests.
• Extensibility: preserve versioned autonomous policy profiles and exact execution bindings as the extension seam; future timing or selection semantics require a new governed profile, not ACT-605-specific optional fields.
• Whole-repo view: update only the preflight note, ADR-092, ADR index/pin, formal specification, and SDL limitations; verify the canonical policy/nox surfaces and leave schemas, generated bundles, release files, and product versions unchanged.

[Brad-Edwards]

Execution obligation ISSUE-213-GOVERNED-DIGEST-SYNC — Opened

Category: workflow
Observed state: verify-completion reported specification-coverage-artifact-digest for docs/explain/sdl/limitations.md and identity-cutover-historical-content for ADR-092/adr-index.
Impact: Repository-wide completion fails in unit and contract lanes until the specification-coverage and identity-cutover manifests match the intended content.
Current obligation: Synchronize all governed content digests affected by the ACT-605 ADR and limitations updates.

Evidence

• RAES_REQUIREMENT_UID=ACT-605 uv tool run --from nox[uv]==2026.4.10 nox -f noxfile.py -s verify-completion
• implementations/python/tests/test_specification_coverage.py::test_current_bundle_is_clean
• implementations/python/tests/test_identity_cutover_policy.py::test_current_repository_satisfies_identity_cutover

[Brad-Edwards]

Execution obligation ISSUE-213-GOVERNED-DIGEST-SYNC — Resolved

Category: workflow
Observed state: Specification-coverage snapshots/analyses/bundle manifests and historical-identity records now carry exact hashes for the changed artifacts.
Impact: Repository-wide completion had failed in unit and contract lanes until the governed manifests matched the intended content.
Current obligation: Synchronize all governed content digests affected by the ACT-605 ADR and limitations updates.

Evidence

• implementations/python/tests/test_specification_coverage.py
• implementations/python/tests/test_identity_cutover_policy.py

Disposition: fix
Corrective action: Updated both specification-coverage bundle revisions and the historical-identity manifest through their complete digest chains.

Verification

• 59 focused policy tests passed
• ACT-605 focused runtime suite previously passed 113 tests

[Brad-Edwards]

gc_codex_review — cycle 1 of 1 (pre-push) on issue #213 (branch 213-act-605-reconciliation)
Diff mode: inline — the complete diff was supplied in one prompt

Core review

Verdict: ship

This is shaped correctly as a reconciliation-only change: it makes ACT-605 trace explicitly to the existing autonomous-participant policy, shared-time, execution, and evidence path, while preserving the boundary against a parallel actor, scheduler, schema, or runtime plane. The ADR amendment, formal-specification clarification, removal of the stale SDL limitation, and corresponding immutable-record hash updates move together; the design seam remains the versioned autonomous execution profile, leaving future behavior variants to evolve through the incumbent contract rather than ACT-605-specific vocabulary.

No blocking findings.

Security review

Verdict: ship

This is a documentation and integrity-metadata reconciliation: it maps ACT-605 onto the existing autonomous-participant policy, updates the associated ADR amendment and content pins, and removes a now-stale SDL limitation. It touches published documentation and hash-linked research records but introduces no executable request path, authorization decision, secret handling, parser behavior, persistence operation, or network/OS boundary. The design seam remains the existing versioned autonomous-execution policy, and the change does not foreclose an obvious future variation.

No blocking findings.

[Brad-Edwards]

gc_codex_review pre-push cycle 1 of 1 complete for issue #213 on branch '213-act-605-reconciliation'. 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.