Assistant: codex Assistant-Model: gpt-6.1-sol Assistant-Session: 01a126e1-76f8-7643-8cf3-e93336539ade
1.6 KiB
| type | derived | derived_from | derived_source_sha256 | updated |
|---|---|---|---|---|
| conformance-record | true | net-kingdom/canon/standards/security-layer-model_v0.8.md | 3d8298560069ef471fba28d2b1245fb2309328f231dad1a667cdf0ce5a5a7c8b | 2026-10-11 |
user-engine accepted v0.8 checker migration
This owner applies GH-WP-0004-T11's post-flip migration to the confirmed accepted NetKingdom v0.8 cut, immutable accepted-1 artifact SHA256 3d8298560069ef471fba28d2b1245fb2309328f231dad1a667cdf0ce5a5a7c8b. The checker names that artifact and its local scope in every run. INTENT frontmatter remains authoritative and the sidecar remains derived; a contradiction is a finding, never hidden by choosing one form. No declaration acquires a standard version.
The pin detector follows OpsWarden's A12 r3 reference semantics: standard and companion identity values (including nested lists), version-bearing paths and standard/companion version keys are pins; unrelated intent/schema/spec versions and bare prose provenance are not. Existing local Tooling/contact and capability detectors remain in place. Historical version strings in negative fixtures are retained. This source migration grants no native capability or runtime authority.
Validation includes the existing local declaration/contact suite and the same 12-case pin/provenance corpus across all four assigned owners, with exact accepted-artifact and scope assertions. The local test counts and staged source digests are retained in the coordinating Custodian evidence receipt. Standalone checker runs continue to inspect only this repository; no estate-wide compliance claim or novel declaration is produced.