gate-house/workplans/GH-WP-0001-foundation.md

id	type	title	domain	repo	status	state_hub_workstream_id	updated
GH-WP-0001	workplan	Foundation	infotech	gate-house	finished	2ec4cf1a-a73f-5793-9738-8d8019cccca8	2026-09-02

Foundation

Establish Gate House as the Staff-layer doctrine council: the layer model in canon, the re-cut recorded, the authority context published as a contract access-engine consumes, and the conformance loop turning.

Rewritten 2026-08-28 against decisions/decisions.md GH-DEC-2026-001. The previous plan targeted Blueprint milestone M0 — an /authorize skeleton — which lapsed with the re-cut. No service is built in this repository.

id: GH-WP-0001-T01
status: done
priority: high
state_hub_task_id: "af0fa778-89a8-52cf-a73a-021082a98cad"

Establish the repository baseline: classification, scope, agent instructions, workplan spine. Done — rmgr conform passes with no findings.

id: GH-WP-0001-T02
status: done
priority: high
state_hub_task_id: "6dd21d86-6546-58a7-b59e-fa1db72aae90"

Settle the boundary with access-engine and the security estate, and record it. Done — the review is in history/2026-08-28-security-layer-model-and-gate-house-recut.md, the ruling in GH-DEC-2026-001, and the model in net-kingdom/canon/standards/security-layer-model_v0.1.md (proposed).

id: GH-WP-0001-T03
status: done
priority: high
state_hub_task_id: "12f651be-1c07-587b-a781-4472e189e218"

Obtain assent for the boundaries that move vocabulary away from repositories currently using it. Requested 2026-08-28 as intakes in the owning repositories, with State Hub inbox notification — the intake is the inbound channel, so each repository triages and promotes into its own work structure rather than having work created for it:

• FLEX-IN-0001 — Engine framing, the access-engine rename, and the authoring/evaluation split. INTENT reframe applied; rename not authorized.
• KG-IN-0001 — Staff placement, "control plane" as Engine vocabulary, and the posture asymmetry.
• WARDEN-IN-0001 — Staff placement, doctrine versus runbook, the access lane/rule demarcation, and adding gate-house to the routing tables.

Awaiting response. Assent, revision, or rejection are all acceptable outcomes; a rejection that names a practical failure is the more valuable answer. Promote the standard from proposed to accepted once the three have answered.

id: GH-WP-0001-T04
status: done
priority: high
state_hub_task_id: "7903d142-9763-5b3f-839d-2a1599130a2b"

Publish the authority context as a contract: principal, actor, runtime identity, tenant, environment, mandate, task, operating mode — the vocabulary access-engine consumes as input claims alongside verified identity claims. Record it as ADR-001 and ADR-002. This is the deliverable that makes the doctrine consumable rather than descriptive.

Done — docs/contracts/authority-context.md publishes authority-context.v1 as the logical claims contract, with mode-specific requiredness, authoritative binding, fail-closed, evidence, and versioning rules. docs/adr/ADR-001-canonical-authority-context-contract.md and docs/adr/ADR-002-principal-actor-runtime-identity-model.md record the contract boundary and the three-role identity model.

id: GH-WP-0001-T05
status: done
priority: medium
state_hub_task_id: "010e3162-cab1-5644-b262-b0d1d7d676f8"

Revise ArchitectureBlueprint.md: fold the surviving material — domain model, authority context, operating modes, posture and credential contracts, MCP doctrine, change dynamics, audit, architectural invariants — into doctrine form, and retire the withdrawn sections from the working document into design history. Currently marked in place with a status banner.

Done — ArchitectureBlueprint.md v0.2 is a current doctrine architecture with no Gate House runtime role. The complete v0.1 remains recoverable at Git object 75ce372:ArchitectureBlueprint.md; its section-by-section disposition is in history/2026-09-01-authority-plane-blueprint-retirement.md. Derivative README and agent guidance now point to the current document.

id: GH-WP-0001-T06
status: done
priority: medium
state_hub_task_id: "8cc018e1-2787-5435-9c2c-c2b01cf75ae4"

Close the conformance loop. Hand the assurance specifications T-01…T-10 to whitehat-security as executable targets, agree the posture and findings return path with kings-guard, and establish how conformance review reports back. Until this turns, Gate House is a paper generator by its own falsifier.

Initial handoff — Gate House's side was published at commit 8cb7250. The executable target set and reporting contract were handed to whitehat-security in State Hub message 8229c9a4-862f-4d55-842c-5c95702f79d9; the posture/findings contract, grounded in KG-DEC-2026-001 and KG-WP-0003, was handed to kings-guard in message 50d392ad-b342-4e90-85e7-d4c5495f3671. Completion required a calibrated whitehat result, kings-guard's return-path disposition/status, and Gate House's first recorded doctrine disposition. Full record: history/2026-09-01-conformance-loop-handoff.md.

Progress 2026-09-02 — kings-guard accepted the return-path contract, completed KG-WP-0003, and returned a real qonto-assistant observation. Gate House recorded no_change: the lane is staffed, while deny-stream completeness is unknown pending heartbeat/reconciliation. Review: docs/conformance/2026-09-02-kings-guard-qonto-live-observation.md. The last completion gate was a contract-complete Whitehat return envelope, now satisfied by message a1ebf012-bd1e-43d2-843c-ba3ddecb8c82. Risk Nexus disposition is complete. Gate House acknowledged the King's Guard return and accepted whitehat's probe-ownership correction; whitehat follow-up c33c3a72-5bf3-4693-8861-9e9ad37d5908 requests the remaining fixture-safe calibrated result without authorizing a live probe. A concrete T-06 candidate is now recorded from secrets-engine revision 4b4d556; its implementer suite passed 17/17 in the initially observed working tree. Candidate: docs/conformance/2026-09-02-secrets-engine-t06-candidate.md. The bounded candidate was handed to whitehat-security in message cc19a1c4-2acf-448d-b90f-e9843a57a7d4. Whitehat subsequently opened WHITEHAT-IN-0002; Gate House accepted that intake without contract revision, while preserving that it is not a result. The qonto completeness finding was routed to risk-nexus in message 53645a75-0215-4261-a700-f7aedf09e7e8 for grading and remediation tracking. Whitehat then promoted its intake into WHITEHAT-WP-0007 at revision 5384f05 and completed the ten-target triage. Gate House accepted the triage, class split, and result routes without contract revision. At triage all live targets remained pending; T-06's fixture blocker was reassessed against the supplied secrets-engine candidate via message 418fe53b-4a4b-4ebb-909e-62d206cd005f. Review: docs/conformance/2026-09-02-whitehat-asm-triage-review.md. Whitehat then admitted fixture-only T-06 and returned a passing known-bad calibration at revision 75deaf0; Gate House reproduced the focused suite (53 passed). The standalone conformance-reporting.v1 envelope was then supplied. Risk Nexus registered the qonto residual as RISK-F-0011 (medium, public, open, no escalation) under RISK-RULING-2026-09-02-A, closing the finding-intake gate. Whitehat revision 6f1ca0b now calibrates fixture harnesses for T-01 through T-10; Gate House reproduced 53/53 focused tests and recorded no_change to the target specification. Live targets remain pending / not_run. Review: docs/conformance/2026-09-02-whitehat-asm-fixture-calibrations.md.

Done — Whitehat supplied the contract-complete T-06 fixture envelope in State Hub message a1ebf012-bd1e-43d2-843c-ba3ddecb8c82, including engagement and authorization references. Gate House recorded Whitehat's pass without regrading it and dispositioned doctrine no_change in docs/conformance/2026-09-02-whitehat-t06-fixture-return.md. The live T-01 through T-10 residuals remain pending / not_run under WHITEHAT-WP-0008; they are deliberately not converted into green results. With King's Guard's return, RISK-F-0011, and both Gate House dispositions recorded, the conformance loop is staffed and GH-WP-0001 is finished.