Seeded repo with initial and secondary research

This commit is contained in:
2026-06-05 13:12:48 +02:00
parent 9067e75693
commit 6dc1f8311c
14 changed files with 1418 additions and 1 deletions

View File

@@ -0,0 +1,71 @@
---
id: IDENTITY-WP-0001
type: workplan
title: "Bootstrap State Hub integration"
domain: canon
repo: identity-canon
status: finished
owner: codex
topic_slug: canon
created: "2026-06-05"
updated: "2026-06-05"
state_hub_workstream_id: "b7346171-35f6-45bf-b82f-c3703b79b426"
---
# Bootstrap State Hub integration
Orthogonal vocabulary and canonical model for identity-related concepts.
## Review Generated Integration Files
```task
id: IDENTITY-WP-0001-T01
status: done
priority: high
state_hub_task_id: "3d373474-4258-40f0-9d44-7e26f7ccfc69"
```
Review `INTENT.md`, `SCOPE.md`, `AGENTS.md`, and `.custodian-brief.md`.
Replace generated placeholders with repo-specific facts where needed.
Completed by reviewing the generated integration files, preserving
`.custodian-brief.md` as generated output, refining `SCOPE.md` to the actual
research-only repository boundary, and correcting `AGENTS.md` repo identity.
## Verify Local Developer Workflow
```task
id: IDENTITY-WP-0001-T02
status: done
priority: high
state_hub_task_id: "c465b751-5799-47a2-b1e0-93017b39b9a7"
```
Identify the repo's install, test, lint, build, and run commands. Add or refine
those commands in the agent instructions so future coding sessions can verify
changes confidently.
Completed by adding the local developer workflow to `AGENTS.md`. The repository
is documentation-only: no install, build, runtime service, package manifest, or
configured test runner exists. Current verification is `rg --files`, `git diff
--check`, and State Hub ADR-001 consistency sync after workplan changes.
## Seed First Real Workplan
```task
id: IDENTITY-WP-0001-T03
status: done
priority: medium
state_hub_task_id: "2baf0a58-ad4e-4888-a02a-0935bd329c43"
```
Create the first implementation workplan for the repository's most important
next change. After workplan file updates, run from `~/state-hub`:
```bash
make fix-consistency REPO=identity-canon
```
Completed by `IDENTITY-WP-0002`, which follows up on `ResearchProposal.md` by
seeding the first terminology, canon, model, scenario, open-question, and
downstream recommendation artifacts.

View File

@@ -0,0 +1,86 @@
---
id: IDENTITY-WP-0002
type: workplan
title: "Research proposal follow-up: initial canon scaffold"
domain: canon
repo: identity-canon
status: finished
owner: codex
topic_slug: canon
created: "2026-06-05"
updated: "2026-06-05"
state_hub_workstream_id: "ddb6ca2b-2b35-4dd7-a1fb-f31a51de44f5"
---
# Research proposal follow-up: initial canon scaffold
This workplan follows up on `ResearchProposal.md`, especially Immediate Next
Steps 5 through 9. The goal is to turn the seeded proposal and corpus outline
into the first repository-native terminology, canon, model, and scenario
artifacts without pretending that the source-note research pass is complete.
## Seed Terminology Inventory
```task
id: IDENTITY-WP-0002-T01
status: done
priority: high
state_hub_task_id: "2c66f05d-a19f-4f29-a24d-8cb43c0e7da1"
```
Create the first `terminology/TerminologyInventory.md` from the proposal,
intent, and seeded corpus topics. The inventory must mark mappings as
candidate mappings until the individual source notes are backfilled.
## Seed Terminology Conflict Map
```task
id: IDENTITY-WP-0002-T02
status: done
priority: high
state_hub_task_id: "eeca8178-76ec-485c-bace-70ed13d4a418"
```
Create the first `terminology/TerminologyConflictMap.md` for overloaded terms
that are central to the proposal: `user`, `identity`, `account`, `subject`,
`principal`, `tenant`, `organization`, `group`, `role`, `member`, `profile`,
`persona`, `identifier`, `credential`, and synonymity terms.
## Draft Canonical Principles And Glossary
```task
id: IDENTITY-WP-0002-T03
status: done
priority: high
state_hub_task_id: "44fb593e-1118-412f-a3d8-3976958ad175"
```
Create `canon/DesignPrinciples.md` and `canon/CanonicalGlossary.md` as the
first explicit canonical layer. These files should stay implementation-neutral
and keep external product mappings separate from canonical definitions.
## Add Model And Scenario Tests
```task
id: IDENTITY-WP-0002-T04
status: done
priority: medium
state_hub_task_id: "9a922e09-0609-4dcb-9828-00d12009c9eb"
```
Create `model/ConceptualModel.md` and `scenarios/ScenarioTests.md` so the
initial canon can be tested against the representative scenarios listed in the
research proposal.
## Record Follow-Up Boundaries
```task
id: IDENTITY-WP-0002-T05
status: done
priority: medium
state_hub_task_id: "3231c998-2e1a-4d35-a9c2-c7ff6888394f"
```
Create lightweight follow-up surfaces for open questions and downstream
recommendations. These notes should keep implementation ideas visible without
moving implementation work into this repository.