Re-pin Informed Decision and seal knowledge 0.2.3
The pushed workplan note records the unadmitted 0.2.2 route and does not change intake code or authority. All 24 owner files verify again. The unsigned draft binds the new digest and is not submitted. EMERGENT-WP-0002 stays blocked. Assistant: grok Assistant-Session: 01a10286-9185-7bb2-b411-89cf6ab4c0c6
This commit is contained in:
parent
ebc7c61ee3
commit
681144e5d4
14 changed files with 168 additions and 42 deletions
33
docs/evidence/2026-10-03-023-source-check.json
Normal file
33
docs/evidence/2026-10-03-023-source-check.json
Normal file
|
|
@ -0,0 +1,33 @@
|
|||
{
|
||||
"schema": "emergent.knowledge-check.v1",
|
||||
"version": "0.2.3",
|
||||
"package_digest": "60f8811c6b94b30d357a0d9e5022f2a8ea52e69b47138d3a536755f3295310b5",
|
||||
"sources": {
|
||||
"net-kingdom": "verified-files",
|
||||
"gate-house": "verified-files",
|
||||
"ops-warden": "verified-files",
|
||||
"ops-mason": "verified-files",
|
||||
"access-engine": "verified-files",
|
||||
"security-canon": "verified-files",
|
||||
"user-engine": "verified-files",
|
||||
"tenant-engine": "verified-files",
|
||||
"zone-engine": "verified-files",
|
||||
"whitehat-security": "verified-files",
|
||||
"kings-guard": "verified-files",
|
||||
"secrets-engine": "verified-files",
|
||||
"key-cape": "verified-files",
|
||||
"approval-engine": "verified-files",
|
||||
"informed-decision": "verified-files",
|
||||
"audit-core": "verified-files",
|
||||
"risk-nexus": "verified-files",
|
||||
"info-tech-canon": "verified-files",
|
||||
"ops-bridge": "verified-files",
|
||||
"railiance-master": "verified-files",
|
||||
"glas-harness": "verified-files",
|
||||
"the-custodian": "verified-files",
|
||||
"emergent-security": "verified-files",
|
||||
"runbook-tutorials": "verified-files"
|
||||
},
|
||||
"live_state_verified": false,
|
||||
"ok": true
|
||||
}
|
||||
44
docs/evidence/2026-10-03-023-source-repin.md
Normal file
44
docs/evidence/2026-10-03-023-source-repin.md
Normal file
|
|
@ -0,0 +1,44 @@
|
|||
# Informed Decision source re-pin — knowledge 0.2.3
|
||||
|
||||
Live pilot: **0.2.3**, manifest digest
|
||||
`60f8811c6b94b30d357a0d9e5022f2a8ea52e69b47138d3a536755f3295310b5`.
|
||||
Release 0.2.2, digest
|
||||
`19de26540c693b94ac8c19d7ed2ddd901acbc828c9b8a78b44c1a43ca468222c`,
|
||||
stays the historical seal for its owner reviews and provider reports. This
|
||||
release does not relabel those results.
|
||||
|
||||
## What changed
|
||||
|
||||
The 0.2.2 source check withheld startup because Informed Decision's inventoried
|
||||
workplan differed from pin `b4be6ec7073bfe09fc0e0d639caffb91511725a4`. Compared
|
||||
with that pin, pushed `f0c60637e3fe592a23cc31ace8e4d386ff04b710` changes only
|
||||
`workplans/INFD-WP-0005-frictionless-decision-intake.md`. The other six
|
||||
inventoried files are byte-identical. The added section records the attended
|
||||
admission route for the unsigned 0.2.2 draft, `submitter_unknown` without a
|
||||
grant, and that no submission, provisioning, or human answer occurred. Intake
|
||||
code, schema, and authority are unchanged. Uncommitted `WORK-RECORDS.md` is not
|
||||
an inventoried source and was not pinned.
|
||||
|
||||
`knowledge/sources.yaml` now pins that pushed revision. The workplan digest is
|
||||
`f1f731b62cf93a2837c86efcd56d5937a7b6c7c8f52159e4849f0bfd34704849`. Cards were
|
||||
not rewritten. The integration-map links for this owner follow the new revision.
|
||||
The unsigned adoption draft was regenerated for this digest and was not submitted.
|
||||
Decision `d20a9750-2b29-534e-8227-fb866581a6ca` remains open.
|
||||
|
||||
## Checks
|
||||
|
||||
[Source check](2026-10-03-023-source-check.json): 24 owners `verified-files`,
|
||||
`ok: true`, `live_state_verified: false`. Startup retrieval for the Grok audience
|
||||
is `verified-files` again. `python3 tools/seal_knowledge.py --check` and
|
||||
`python3 tools/build_adoption_draft.py --check` pass. Portable tests: 332 passed,
|
||||
9 skipped. With `EMERGENT_OWNER_ROOT=/home/worsch`, the 9 owner-contract tests
|
||||
passed. File agreement is not deployment, permission, provider readiness, or
|
||||
adoption.
|
||||
|
||||
## Still open
|
||||
|
||||
0.2.2 Codex and Claude reports do not certify 0.2.3. No new provider,
|
||||
compaction, governed-session, or wider-pilot run is included. Whitehat
|
||||
close-out stays platform-blocked. Human exact-packet adoption still requires
|
||||
the attended Informed Decision route. Fleet publication and reach are not
|
||||
started. EMERGENT-WP-0002 stays blocked on T02, T05, T07, T08, T09, and T10.
|
||||
|
|
@ -1,6 +1,10 @@
|
|||
# Owner reviews and loaded-package consistency fixes — 2026-10-03
|
||||
|
||||
Current pilot: **0.2.2**, manifest digest
|
||||
The live seal is now 0.2.3. See
|
||||
`docs/evidence/2026-10-03-023-source-repin.md`. The 0.2.2 findings and receipts
|
||||
below remain historical and do not certify 0.2.3.
|
||||
|
||||
Historical pilot at sealing: **0.2.2**, manifest digest
|
||||
`19de26540c693b94ac8c19d7ed2ddd901acbc828c9b8a78b44c1a43ca468222c`.
|
||||
At sealing, all 24 inventoried source owners verified as files; startup remains
|
||||
5,091 bytes. The final post-worker source check below supersedes that receipt.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue