Register with repo-manager and add agent guidance

Register gate-house as category: tooling, domain: infotech, workplan
prefix GH-WP, via rmgr scaffold. Baseline files: .repo-classification.yaml,
SCOPE.md, AGENTS.md, workplans/GH-WP-0001-foundation.md. rmgr conform
passes with no findings.

SCOPE.md is derived from INTENT.md; GH-WP-0001 targets milestone M0
(executable skeleton) from ArchitectureBlueprint.md §41.

Move ArchitectureBlueprint.md to the repository root, matching its own
reference layout (§32). spec/ retains the Active Secrets Management Canon,
the external standard Gate House conforms to.

Add CLAUDE.md documenting the document precedence (Canon → INTENT →
Blueprint → README), the load-bearing security invariants, the fixed
domain vocabulary, and the stable identifier scheme.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 2564823@bnt-lap001
Assistant-Session: 2a7ed827-4928-4b9f-8613-9135c9cadfe9
This commit is contained in:
tegwick 2026-08-24 20:41:58 +02:00
parent 8604fe6021
commit a97e7c8ee1
6 changed files with 266 additions and 0 deletions

View file

@ -0,0 +1,69 @@
---
id: GH-WP-0001
type: workplan
title: "Foundation"
domain: infotech
repo: gate-house
status: proposed
---
# 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.
```task
id: GH-WP-0001-T01
status: todo
priority: high
```
Establish the repository baseline: classification, scope, agent instructions,
workplan spine.
```task
id: GH-WP-0001-T02
status: todo
priority: high
```
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.
```task
id: GH-WP-0001-T03
status: todo
priority: high
```
Define the canonical authorization request and decision schemas from
`ArchitectureBlueprint.md` §7 and §8.
```task
id: GH-WP-0001-T04
status: todo
priority: medium
```
Implement the `/authorize` service skeleton with static policy and the
evaluation order in `ArchitectureBlueprint.md` §13, monotonic toward restriction.
```task
id: GH-WP-0001-T05
status: todo
priority: medium
```
Emit structured decision evidence for every authorization call, per
`ArchitectureBlueprint.md` §24.
```task
id: GH-WP-0001-T06
status: todo
priority: medium
```
Seed the adversarial test suite with the fail-closed and self-escalation cases
(Canon T-04, T-09; `ArchitectureBlueprint.md` §34.4, §34.8).