coulomb/gate-house
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

repo.work.update_workplan GH-WP-0001 (update)

Browse source 
correlation_id: a1e9a76e-93d5-4bcb-a843-56e168041b26
reason: rmgr CLI
source: repo-manager

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 2564823@bnt-lap001
Assistant-Session: 2a7ed827-4928-4b9f-8613-9135c9cadfe9
This commit is contained in:
repo-manager 2026-08-28 21:24:07 +02:00
parent e9f29e6551
commit 81f9fce82b
1 changed files with 37 additions and 20 deletions
Download patch file Download diff file Expand all files Collapse all files

57
workplans/GH-WP-0001-foundation.md
View file

@ -4,56 +4,68 @@ type: workplan
title: "Foundation"
domain: infotech
repo: gate-house
status: proposed
status: active
state_hub_workstream_id: "2ec4cf1a-a73f-5793-9738-8d8019cccca8"
updated: "2026-08-28"
---
# Foundation
Establish the repository baseline and reach milestone **M0 — Executable Skeleton**
as defined in `ArchitectureBlueprint.md` §41: a request must produce a
deterministic `GRANT` / `DENY` with structured audit evidence.
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.
```task
id: GH-WP-0001-T01
status: todo
status: done
priority: high
state_hub_task_id: "af0fa778-89a8-52cf-a73a-021082a98cad"
```
Establish the repository baseline: classification, scope, agent instructions,
workplan spine.
workplan spine. Done — `rmgr conform` passes with no findings.
```task
id: GH-WP-0001-T02
status: todo
status: done
priority: high
state_hub_task_id: "6dd21d86-6546-58a7-b59e-fa1db72aae90"
```
Record the early ADRs that gate implementation choices — ADR-001 canonical
authority request schema, ADR-002 principal/actor/runtime identity model,
ADR-003 policy engine selection. Backlog in `ArchitectureBlueprint.md` §40.
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).
```task
id: GH-WP-0001-T03
status: todo
status: progress
priority: high
state_hub_task_id: "12f651be-1c07-587b-a781-4472e189e218"
```
Define the canonical authorization request and decision schemas from
`ArchitectureBlueprint.md` §7 and §8.
Obtain assent for the two boundaries that move vocabulary away from repositories
currently using it: flex-auth (Engine framing, rename, authoring/evaluation
split — INTENT reframed, rename outstanding) and kings-guard plus ops-warden
("control plane" and the security curriculum). Promote the standard from
`proposed` to `accepted` once assent lands.
```task
id: GH-WP-0001-T04
status: todo
priority: medium
priority: high
state_hub_task_id: "7903d142-9763-5b3f-839d-2a1599130a2b"
```
Implement the `/authorize` service skeleton with static policy and the
evaluation order in `ArchitectureBlueprint.md` §13, monotonic toward restriction.
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.
```task
id: GH-WP-0001-T05
@ -62,8 +74,11 @@ priority: medium
state_hub_task_id: "010e3162-cab1-5644-b262-b0d1d7d676f8"
```
Emit structured decision evidence for every authorization call, per
`ArchitectureBlueprint.md` §24.
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.
```task
id: GH-WP-0001-T06
@ -72,5 +87,7 @@ priority: medium
state_hub_task_id: "8cc018e1-2787-5435-9c2c-c2b01cf75ae4"
```
Seed the adversarial test suite with the fail-closed and self-escalation cases
(Canon T-04, T-09; `ArchitectureBlueprint.md` §34.4, §34.8).
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.