generated from coulomb/repo-seed
Normalize agent instructions and workplan frontmatter (STATE-WP-0067)
- 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
This commit is contained in:
75
AGENTS.md
75
AGENTS.md
@@ -2,9 +2,9 @@
|
||||
|
||||
## Repo Identity
|
||||
|
||||
**Purpose:** Orthogonal vocabulary and canonical model for identity-related concepts.
|
||||
**Purpose:** Othogonal vocabulary and canonical model for identity related concepts.
|
||||
|
||||
**Domain:** canon
|
||||
**Domain:** infotech
|
||||
**Repo slug:** identity-canon
|
||||
**Topic ID:** `fe2aaa78-9c20-4feb-b3d2-4fe0529572a3`
|
||||
**Workplan prefix:** `IDENTITY-WP-`
|
||||
@@ -151,6 +151,11 @@ every repo's agent instructions because it is high-frequency, high-risk, and eas
|
||||
get wrong.
|
||||
|
||||
**Canon:** `~/ops-warden/wiki/CredentialRouting.md` · catalog `~/ops-warden/registry/routing/catalog.yaml`
|
||||
|
||||
<!-- REPO-AGENTS-EXTENSIONS -->
|
||||
<!-- Append repo-specific agent instructions below this marker.
|
||||
The state-hub template sync preserves content after this line. -->
|
||||
|
||||
---
|
||||
|
||||
## Workplan Convention (ADR-001)
|
||||
@@ -176,7 +181,7 @@ anything needing analysis, design, approval, dependencies, or multiple phases.
|
||||
id: IDENTITY-WP-NNNN
|
||||
type: workplan
|
||||
title: "..."
|
||||
domain: canon
|
||||
domain: infotech
|
||||
repo: identity-canon
|
||||
status: proposed | ready | active | blocked | backlog | finished | archived
|
||||
owner: codex
|
||||
@@ -212,67 +217,3 @@ To create a new workplan:
|
||||
1. Write the file following the format above
|
||||
2. Notify the custodian operator to run `make fix-consistency REPO=identity-canon`
|
||||
(or send a message to the hub agent via `POST /messages/`)
|
||||
|
||||
---
|
||||
|
||||
## Local Developer Workflow
|
||||
|
||||
This repository is currently documentation-only. There is no package manifest,
|
||||
runtime application, build system, executable test suite, or formatter/linter
|
||||
configuration checked in.
|
||||
|
||||
### Install
|
||||
|
||||
No install step is required for normal repository work.
|
||||
|
||||
### Build
|
||||
|
||||
No build step exists. Treat Markdown and workplan edits as source artifacts.
|
||||
|
||||
### Test / lint
|
||||
|
||||
There is no project test runner or markdown linter configured yet. Use these
|
||||
checks before closing a change:
|
||||
|
||||
```bash
|
||||
# Confirm the repository file inventory still looks intentional
|
||||
rg --files
|
||||
|
||||
# Catch whitespace errors in tracked and staged diffs
|
||||
git diff --check
|
||||
```
|
||||
|
||||
When workplan files change, sync ADR-001 file state into State Hub:
|
||||
|
||||
```bash
|
||||
curl -s -X POST "http://127.0.0.1:8000/repos/identity-canon/sync?fix=true" \
|
||||
| python3 -m json.tool
|
||||
```
|
||||
|
||||
If the HTTP sync endpoint is unavailable, run the consistency script from the
|
||||
State Hub checkout:
|
||||
|
||||
```bash
|
||||
cd ~/state-hub
|
||||
.venv/bin/python scripts/consistency_check.py --repo identity-canon --fix
|
||||
.venv/bin/python scripts/consistency_check.py --repo identity-canon
|
||||
```
|
||||
|
||||
The generated instruction in older workplans says `make fix-consistency
|
||||
REPO=identity-canon`; that is still valid when `uv` is installed and on PATH.
|
||||
On this workstation, the `.venv/bin/python` fallback has been verified.
|
||||
|
||||
### Run
|
||||
|
||||
There is no local service to run from this repository.
|
||||
|
||||
### Documentation Review Checklist
|
||||
|
||||
- Keep `INTENT.md`, `SCOPE.md`, and `ResearchProposal.md` aligned on the
|
||||
repository's research-only boundary.
|
||||
- Keep source-backed observations in `research/` and canonical candidate terms
|
||||
in `terminology/`, `canon/`, `model/`, and `scenarios/`.
|
||||
- Mark draft concepts as candidate or draft until source notes contain real
|
||||
references and extracted terminology.
|
||||
- Record implementation ideas in `DownstreamRecommendations.md`, not as code in
|
||||
this repository.
|
||||
|
||||
Reference in New Issue
Block a user