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

Record approved production lifecycle cutover and native evidence

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a10780-6d41-7952-9718-dfbc1f41236f
This commit is contained in:
tegwick 2026-10-05 00:15:09 +02:00
parent b5b5a5aa7f
commit 3fe029d49e
11 changed files with 1059 additions and 55 deletions
Download patch file Download diff file Expand all files Collapse all files

50
SCOPE.md
View file

@ -4,39 +4,31 @@
> direction belongs in `INTENT.md`; the current stage belongs in `GOAL.md`;
> current work and gates belong in `workplans/`.
## Lifecycle expansion — 2026-10-04 (source implementation)
## Lifecycle production boundary — 2026-10-05
INFD-WP-0007 adds a headless service and an optional browser workspace. The shared
foundation supports registration with packet custody, immutable revisions,
attributed sources/evaluations/comments, explicit revision-specific publication,
authorized search, retrieval and history. Every operation consumes fresh Access
Engine policy observations; audience facts do not implement a local ACL.
The headless lifecycle service and browser workspace are deployed at
`decisions.coulomb.social` under the founder-approved initial audience:
net-kingdom-admins humans and system:serviceaccount:state-hub:state-hub.
Service image 804d89fb runs schema 5; Access Engine owns lifecycle v1 and
compact-sitting v12 policy decisions. Approval Engine remains the approval-state
owner. The UI uses the shared service foundation; the private bearer API listens
on 8081 through informed-decision-workload and is absent from public ingress.
The workspace reuses verified KeyCape sessions and CSRF/origin checks for draft
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;
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.
Native proof registered two records, retained sources/evaluation/comment, revised
and published one, and sent its exact review envelope through the private State
Hub dispatcher to native approval 22b30fe7-c565-46f2-8193-d8875975ad9e. No image,
configuration or policy change was required for these decisions. Service and
dispatcher pod recreation retained revision 2, custody and the same receipt.
Missing/crossed-audience/unregistered callers are refused. Independent Audit
Core counts match; prior 24 confirmed submissions were preserved.
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: 634 passed,
5 skipped, including two agent-created decisions and human collaboration with
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.
Human acceptance of the new lifecycle review is still pending. Broader binding
profiles and browser acceptance remain live tasks in INFD-WP-0007; intake
continuation is INFD-WP-0005. Issuer rotation is separately governed under Platform
RPF-IN-0004. Automatic Hub resolution write-back remains disabled.
Contracts: `docs/specs/DecisionLifecycleService.md`, `LifecycleFoundationContract.md`,
`LifecycleServiceContract.md`, `LifecycleHTTPContract.md` and
`LifecycleWorkspaceDelivery.md` under `docs/specs/`. INFD-WP-0005 retains intake
runtime/admission work. The deployment snapshot below is historical.
Release/cutover procedure: `deploy/lifecycle/README.md`. Native receipts:
`docs/evidence/2026-10-05-lifecycle-cutover/`. Earlier statuses below are historical.
## Status — 2026-09-27