whitehat-security/docs/evidence/2026-10-11-layer-declaration-migration.md
tegwick 5587a8f6ac Keep layer declaration separate from dated observer evidence
Assistant: codex
Assistant-Model: gpt-6.1-sol
Assistant-Session: 01a126e1-76f8-7643-8cf3-e93336539ade
2026-10-11 02:22:08 +02:00

32 lines
1.6 KiB
Markdown

---
type: evidence
date: "2026-10-11"
repository: whitehat-security
conformance_state: blocked-clean
source: INTENT.md
ruling: GH-DEC-2026-021
validated_against: net-kingdom/canon/standards/security-layer-model_v0.8.md
scope: "Declaration frontmatter only; relocation of existing state, no live probing or full conformance determination"
---
# Declaration-state relocation
GH-DEC-2026-021 §5 assigns conformance_state to run/evidence records rather
than the standing layer declaration. Accepted v0.8 source enables this
post-flip GH-WP-0004-T11 migration. The existing blocked-clean value is
preserved here, not upgraded to conformant. Historical workplans and scope
assessments remain unchanged. INTENT's governing statute citation now names
accepted v0.8; declaration keys retain no standard or companion version.
This migration changes no probe, authorization gate, live target, capability,
or evidence axis. The declared Staff role and offensive-validation remit
remain the repository's own voice. A passing declaration test establishes
this limited structural property; no target isolation is established.
Verification: all 117 offline tests passed against merged staged source,
with explicit existing SecretsEngine source and Railiance custody schema
paths. Three declaration tests also pass in the narrow staging directory.
The first full copied-tree run failed 19 tests because sibling source/schema
lookup cannot resolve from /tmp; supplying the documented environment
overrides restores the same source dependencies as the authoritative tree.
This was a verification-location failure, not a probe or capability change.