generated from coulomb/repo-seed
tegwick
f5b851005d
- Align agent files with on-disk workplan prefixes (infer from workplan ids) - Set workplan domain to registered domain_slug; add topic_slug where applicable - Repair frontmatter delimiter formatting; migrate legacy task status literals - Regenerate AGENTS.md, CLAUDE.md, and .claude/rules from State Hub templates
87 lines
2.5 KiB
Markdown
87 lines
2.5 KiB
Markdown
---
|
|
id: IDENTITY-WP-0002
|
|
type: workplan
|
|
title: "Research proposal follow-up: initial canon scaffold"
|
|
domain: infotech
|
|
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.
|