coulomb/informed-decision
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Connect lifecycle revisions to protected human review

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a10780-6d41-7952-9718-dfbc1f41236f
This commit is contained in:
tegwick 2026-10-04 20:33:24 +02:00
parent 0e79d69e27
commit f3b71b1521
16 changed files with 649 additions and 23 deletions
Download patch file Download diff file Expand all files Collapse all files

11
SCOPE.md
View file

@ -17,15 +17,20 @@ creation, research, discussion, publication, refinement, revision comparison and
packet downloads. Runtime configuration requires a separate lifecycle policy
package. The bearer API adapter remains unmounted pending workload identity and
listener admission. Lifecycle records remain outside the legacy approver overview;
the human binding handoff is not implemented.
a durable revision-specific request now connects supported records to intake
and the existing human-only review path. Outcomes retain exact source revision
and distinguish prepared/unresolved submissions from confirmed entries. See
`docs/specs/LifecycleReviewHandoff.md`; production forwarding is still outstanding.
Opt-in delivery commits lifecycle evidence through the existing Audit Core
outbox, with receipt-based settlement, retries and reconciliation. Current delivery
is platform-tenant-only. Pending evidence closes runtime readiness. The deployment
renderer supports separately pinned lifecycle policy and exact network proposals;
no live configuration was changed. Cross-repository validation: 623 passed,
no live configuration was changed. Cross-repository validation: 634 passed,
5 skipped, including two agent-created decisions and human collaboration with
unchanged runtime configuration and actual Audit Core delivery. Identity and PDP
unchanged runtime configuration, actual Approval Engine acceptance of a linked
source revision, and Audit Core delivery. Schema 5 prevents older code without
source-revision guards from opening the database. Identity and PDP
responses in that scenario are synthetic; this is not live acceptance evidence.
Contracts: `docs/specs/DecisionLifecycleService.md`, `LifecycleFoundationContract.md`,