# Informed Decision re-pin — knowledge 0.2.5

The live seal is now 0.2.6. See
`docs/evidence/2026-10-03-026-route-clarification.md`. This 0.2.5 record
stays historical.

Historical pilot: **0.2.5**, manifest digest
`9e186dbd6f2d5eb455bca24db4b03cd866c63c4e94660430dd15f2ca9856215f`.
Release 0.2.4, digest
`025aab4f38246219c924bc94954e70ea0e6e7f72bcaf8d4344cd599602d345c3`,
remains the historical seal for its provider probes, resume reloads, and four
Claude pilots. This release does not extend that evidence or Whitehat's 0.2.3
library acceptance.

## Reviewed source

0.2.4 withheld startup after Informed Decision moved past
`15c330ccd049cd19c76040e54dae41cd15d1359e`. The published revision is now
`b4f637326ba3c2526f4648c4c90544948408d53f`, matching `origin/main`. Inventoried
file bytes match that commit. README, INTENT, the memo schema, and
`informed_decision/intake.py` are unchanged since 0.2.4. SCOPE and the intake
spec changed at `ff59199`. The workplan changed again in `b4f6373`.

The owner records that INFD-WP-0006 completed the Authelia fresh-login request,
with live fresh-login/p01 acceptance. An actionable browser freshness error
remains open. INFD-WP-0005 has local intake, opt-in scheduled delivery, empty
registries, notification without a URL, and local posed audit evidence.
`INFD_HUB_WRITEBACK` stays off. No listener is deployed. T07 is done locally.
T05, T06, T08, and T10 stay waiting.

## Boolean contract

state-hub `49eeddb` rejected `requires_new_bind`, `required_ack`, and `sealed`
because `type(True)` is `bool`, not `int`. state-hub
`d61ba327fa575269a0ea2d7372cd3c62a10d0cc9` accepts a boolean leaf before the
numeric allow-list. Unknown leaves still raise `invalid_type`. The
informed-decision cross-repo check submits the real p01 envelope and expects
those three booleans to survive delivery. Focused state-hub memo tests:
20 passed. Focused informed-decision intake tests: 46 passed, 3 skipped.
A later full informed-decision run was 449 passed, 64 skipped, and 4 failed
outside this change (`waitress` missing, and one access-token audience case).
No submitter was registered, no token was minted, and the write-back flag
stays unset. T08 still waits on the service account, reviewed grant, runtime
forwarding, and T05/T06.

## Package change

`knowledge/cards/decisions.md` now carries the fresh-login acceptance, the open
browser freshness error, local delivery limits, and boolean-preserving dev
forwarding. The intake-readiness scenario still asks whether an agent may
assume `POST /v1/memos` is deployed and register itself. The integration map,
operational contract, and decision/runbook limit row match this scope. 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-025-source-check.json): 24 owners `verified-files`,
`ok: true`, `live_state_verified: false`. Startup and the decisions card both
retrieve as `verified-files` for the Grok audience. Seal and unsigned-draft
checks 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.4 provider probes, resume reloads, and pilots stay on that digest.
Compaction, a governed harness session, owner feedback, RISK-F-0015, human
adoption, and fleet reach remain open. EMERGENT-WP-0002 stays blocked on T02,
T05, T07, T08, T09, and T10. No DoD-Ok is claimed.