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

Make profile runtime readiness explicit
Some checks failed
ci / validate (push) Has been cancelled
Details

Browse source 
Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a0233b-178d-7162-b92f-31a31ea8ca9b
This commit is contained in:
tegwick 2026-08-23 11:32:23 +02:00
parent a224e71555
commit cac605abd7
19 changed files with 339 additions and 41 deletions
Download patch file Download diff file Expand all files Collapse all files

8
docs/intakes/residuals.md
View file

@ -147,7 +147,7 @@ id: GLAS-IN-0005
kind: intake
title: "Separate profile selection enablement from runtime readiness"
lane: red
status: todo
status: done
priority: high
owner: glas-harness
repo: glas-harness
@ -168,3 +168,9 @@ description: |
fallback or claim readiness from lifecycle-only proof.
state_hub_intake_id: "01a02dce-b761-75e6-861a-8abf8b8e0072"
```
Completed by `GLAS-WP-0008` on 2026-08-23. Catalog enablement is now separate
from typed operational readiness. Both local profiles are `blocked` by
`GLAS-IN-0002` and refuse before sandbox creation; the remote profile is
`unverified` and may be used only for a labeled bounded proof attempt. Catalog
and execution evidence expose the state, and no host fallback was added.