Correct repo flavor to product; add SCOPE, AGENTS, classification
fix-consistency surfaced that GOAL.md's `repo_flavor: project` was wrong. project-repository-flavor_v0.1.md reserves the prj- flavor for bounded cross-repo coordination efforts and says durable products use INTENT.md and an ordinary category. informed-decision is a durable product, so the C-35 "prj- flavor forbids shipping both INTENT.md and GOAL.md" contradiction was self-inflicted rather than a real conflict. - .repo-classification.yaml: category product, domain infotech. - GOAL.md: drop repo_flavor/project_status, add a flavor note explaining that GOAL.md is retained as the stage statement alongside a stable INTENT.md. - SCOPE.md: honestly empty — states that nothing is implemented and that INFD-WP-0001-T06 rewrites it after the gate-house ruling and the specs. - AGENTS.md: shared State Hub / session / workplan boilerplate, plus the hard rules for this repository — never decide, never own approval state, never invent identity, never let awareness enter view_hash, never let an agent bind, never fork the schema, fail closed. - INFD-WP-0001: T01 records both corrections; T06 now rewrites SCOPE.md. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01V3W1dQG7GFFM9d94jFx7iR Assistant: claude-code Assistant-Model: opus Assistant-Process: 1565372@bnt-lap001 Assistant-Session: 16bb2f25-b34c-49ef-8e94-5fec3567a568
This commit is contained in:
parent
0f5a6c4f59
commit
309bea463e
6 changed files with 461 additions and 10 deletions
|
|
@ -11,6 +11,7 @@ created: "2026-09-09"
|
|||
updated: "2026-09-09"
|
||||
origin: founding
|
||||
origin_ref: history/20260909-initial-exploration/InitialExploration.md
|
||||
state_hub_workstream_id: "a985a65a-08f7-5a39-8645-b618ea022657"
|
||||
---
|
||||
|
||||
# INFD-WP-0001 — Founding specs and approver-UI ownership
|
||||
|
|
@ -44,6 +45,7 @@ walking skeleton**. Full L3 product build is residual and belongs to
|
|||
id: INFD-WP-0001-T01
|
||||
status: done
|
||||
priority: high
|
||||
state_hub_task_id: "abe83f6a-18d2-5fe5-bd01-56b6fd0babbe"
|
||||
```
|
||||
|
||||
Write the repository's stable statements of purpose and current stage, derived
|
||||
|
|
@ -56,10 +58,23 @@ invariants and definition of done; `README.md` orients a new reader in under a
|
|||
minute; `history/20260909-initial-exploration/` is preserved unmodified as the
|
||||
provenance record.
|
||||
|
||||
Completed 2026-09-09: `INTENT.md`, `GOAL.md` and `README.md` written. `SCOPE.md`
|
||||
is deliberately deferred to T06 — a scope file written before the layer ruling
|
||||
and the specs would describe an imagined boundary, which is the drift `SCOPE.md`
|
||||
exists to prevent.
|
||||
Completed 2026-09-09: `INTENT.md`, `GOAL.md`, `README.md`, `SCOPE.md`,
|
||||
`AGENTS.md` and `.repo-classification.yaml` written; repo registered in the
|
||||
State Hub and `INFD-WP-0001` indexed by `fix-consistency`.
|
||||
|
||||
Two corrections made during the same task, recorded rather than silently fixed:
|
||||
|
||||
- `GOAL.md` first declared `repo_flavor: project`. That is wrong.
|
||||
`project-repository-flavor_v0.1.md` reserves the `prj-` flavor for bounded
|
||||
cross-repo coordination efforts and states that durable products use
|
||||
`INTENT.md` and an ordinary category. This is a durable product;
|
||||
`.repo-classification.yaml` sets `category: product`. `GOAL.md` is retained
|
||||
as the *stage* statement, which the flavor standard does not forbid.
|
||||
- `SCOPE.md` was initially deferred to T06 on the reasoning that a scope file
|
||||
written before the layer ruling describes an imagined boundary. The Repo
|
||||
Manager requires it (C-35), and the reasoning was better served by writing an
|
||||
honestly empty one: the shipped `SCOPE.md` states plainly that nothing is
|
||||
implemented and that T06 rewrites it. T06 now rewrites rather than creates.
|
||||
|
||||
## Settle layer placement and approver-UI ownership with gate-house
|
||||
|
||||
|
|
@ -67,6 +82,7 @@ exists to prevent.
|
|||
id: INFD-WP-0001-T02
|
||||
status: todo
|
||||
priority: high
|
||||
state_hub_task_id: "4f94134b-2260-5404-84e0-12f2b08ef565"
|
||||
```
|
||||
|
||||
Take the ownership question to `gate-house` as doctrine rather than asserting a
|
||||
|
|
@ -104,6 +120,7 @@ recorded as a decision, not left implicit. Blocking for T05 and T07.
|
|||
id: INFD-WP-0001-T03
|
||||
status: todo
|
||||
priority: high
|
||||
state_hub_task_id: "86465a35-1af5-5956-a767-57ad838dffa9"
|
||||
```
|
||||
|
||||
Write `docs/specs/ProductRequirementsDocument.md` for Stage 1: the L3 approval
|
||||
|
|
@ -130,6 +147,7 @@ names what it is deliberately not requiring and why.
|
|||
id: INFD-WP-0001-T04
|
||||
status: todo
|
||||
priority: medium
|
||||
state_hub_task_id: "00a83db5-fe0e-522a-b885-6f9ef034bc07"
|
||||
```
|
||||
|
||||
Write `docs/specs/UseCaseCatalog.md` covering the full depth spectrum L0–L5, with
|
||||
|
|
@ -156,6 +174,7 @@ catalog states for each level which estate repository would consume it.
|
|||
id: INFD-WP-0001-T05
|
||||
status: todo
|
||||
priority: high
|
||||
state_hub_task_id: "20ea118e-0657-5054-8aa2-b316444f4000"
|
||||
```
|
||||
|
||||
Write `docs/specs/ArchitectureBlueprint.md`. Depends on T02 — the layer ruling
|
||||
|
|
@ -186,6 +205,7 @@ are placeholders.
|
|||
id: INFD-WP-0001-T06
|
||||
status: todo
|
||||
priority: high
|
||||
state_hub_task_id: "47cb3f7a-e349-5c81-a304-86275e058a85"
|
||||
```
|
||||
|
||||
Promote the exploration artifacts from `history/` into governed, tested
|
||||
|
|
@ -210,13 +230,16 @@ offline, its relationship to `audit-core`'s archive, and — carried over from
|
|||
that a hash chain proves records were not altered after arrival and cannot prove
|
||||
a record was never sent.
|
||||
|
||||
Write `SCOPE.md` as the last step of this task, once the layer ruling and the
|
||||
specs have fixed the real boundary.
|
||||
**Rewrite** `SCOPE.md` as the last step of this task. The version shipped in
|
||||
T01 is honestly empty — it states that nothing is implemented. Replace it with
|
||||
the real implemented-and-first-cut boundary once the layer ruling and the specs
|
||||
have fixed it, and drop the T01 status banner.
|
||||
|
||||
Acceptance: schema, canonicalizer and vectors live outside `history/` and are
|
||||
exercised in CI; the three published expected hashes reproduce byte-for-byte;
|
||||
`EvidenceModel.md` states the residual it does not close; `SCOPE.md` exists and
|
||||
describes the implemented-and-first-cut boundary, not the aspiration.
|
||||
`EvidenceModel.md` states the residual it does not close; `SCOPE.md` describes
|
||||
the implemented-and-first-cut boundary rather than the aspiration, and no longer
|
||||
carries the T01 "nothing is implemented" banner.
|
||||
|
||||
## Publish the OIDC browser-client contract to key-cape
|
||||
|
||||
|
|
@ -224,6 +247,7 @@ describes the implemented-and-first-cut boundary, not the aspiration.
|
|||
id: INFD-WP-0001-T07
|
||||
status: todo
|
||||
priority: high
|
||||
state_hub_task_id: "38a83a76-f152-55bf-8a9a-6132fd6d9642"
|
||||
```
|
||||
|
||||
Own and publish the two strings `approval-engine` could not supply: the human
|
||||
|
|
@ -253,6 +277,7 @@ repository.**
|
|||
id: INFD-WP-0001-T08
|
||||
status: todo
|
||||
priority: medium
|
||||
state_hub_task_id: "b5c1d329-9580-5672-9640-2930cbbb729a"
|
||||
```
|
||||
|
||||
Prove the specs against reality with the thinnest possible L3 path: sign in via
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue