coulomb/glas-harness
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: record delivered production dependency handoffs
Some checks failed
ci / validate (push) Has been cancelled
Details

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0726e-5232-73f2-aaca-2c05ceb62efb
This commit is contained in:
tegwick 2026-09-06 20:23:56 +02:00
parent 8366b43c66
commit 93be6b4da5
4 changed files with 92 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

13
docs/production-dependency-handoffs.md
View file

@ -1,7 +1,9 @@
# Production dependency handoffs
Prepared 2026-09-06 from GLAS-WP-0012 and the deployed policy-service evidence.
These are reviewable owner requests, not delivered messages or authority grants.
Sent to the seven owners on 2026-09-06 after explicit user authorization.
Receipt IDs are in [production-handoff-receipts.json](production-handoff-receipts.json).
Delivery does not establish owner acceptance or an authority grant.
Glas coordinates acceptance; each owner retains implementation and authorization.
No credential values belong in responses.
@ -122,3 +124,12 @@ consumer tuple, declared egress and denial/cleanup evidence. GLAS-WP-0012 then
reviews version 1.1.0, executes its real artifact proof and promotes only the
proven candidate. Provider workspace scope and spend limit remain operator
inputs; model budget_tokens does not establish a provider spend limit.
## Repository access for owner sessions
Primary owner workspaces: key-cape, railiance-platform, audit-core,
approval-engine, secrets-engine, flex-auth and sand-boxer. Give each owner
read access to glas-harness for this packet and the acceptance contract.
Sand-boxer also needs rein-aharness as a sibling for runtime packaging/startup.
KeyCape/custody/audit preparation and approval-image/runtime preparation can
proceed in parallel; final native activation follows the verified prerequisites.