From 9c6ad74f6bfbf2fbbea1cea037d887663aa7ca08 Mon Sep 17 00:00:00 2001 From: tegwick Date: Mon, 22 Jun 2026 23:16:28 +0200 Subject: [PATCH] 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 --- .claude/rules/agents.md | 20 ++ .claude/rules/architecture.md | 8 + .claude/rules/credential-routing.md | 50 ++++ .claude/rules/first-session.md | 38 +++ .claude/rules/repo-boundary.md | 8 + .claude/rules/repo-identity.md | 5 + .claude/rules/session-protocol.md | 85 +++++++ .claude/rules/stack-and-commands.md | 19 ++ .claude/rules/workplan-convention.md | 40 ++++ AGENTS.md | 219 ++++++++++++++++++ CLAUDE.md | 12 + ...0001-preparation-and-interface-adoption.md | 2 +- workplans/USER-WP-0002-isolated-mvp.md | 2 +- workplans/USER-WP-0003-multi-tenancy.md | 2 +- ...USER-WP-0004-multi-application-catalogs.md | 2 +- .../USER-WP-0005-integrated-test-scenarios.md | 2 +- workplans/USER-WP-0006-finalization-polish.md | 2 +- ...WP-0007-identity-domain-canon-alignment.md | 2 +- ...SER-WP-0008-family-dataspace-onboarding.md | 2 +- ...009-postgres-durable-store-requirements.md | 2 +- ...-registration-identity-and-factor-model.md | 2 +- ...repared-accounts-and-entitlement-claims.md | 2 +- ...-realms-services-assets-access-profiles.md | 2 +- ...boarding-journeys-and-welcome-protocols.md | 2 +- ...4-registration-and-access-management-ui.md | 2 +- ...ation-scenario-and-security-conformance.md | 2 +- ...store-migration-and-conformance-harness.md | 2 +- ...0017-durable-store-record-serialization.md | 2 +- .../USER-WP-0018-postgres-store-adapter.md | 2 +- ...19-provider-backed-postgres-conformance.md | 2 +- 30 files changed, 523 insertions(+), 19 deletions(-) create mode 100644 .claude/rules/agents.md create mode 100644 .claude/rules/architecture.md create mode 100644 .claude/rules/credential-routing.md create mode 100644 .claude/rules/first-session.md create mode 100644 .claude/rules/repo-boundary.md create mode 100644 .claude/rules/repo-identity.md create mode 100644 .claude/rules/session-protocol.md create mode 100644 .claude/rules/stack-and-commands.md create mode 100644 .claude/rules/workplan-convention.md create mode 100644 AGENTS.md create mode 100644 CLAUDE.md diff --git a/.claude/rules/agents.md b/.claude/rules/agents.md new file mode 100644 index 0000000..0e8a5d9 --- /dev/null +++ b/.claude/rules/agents.md @@ -0,0 +1,20 @@ +## Kaizen Agents + +Specialized agent personas available on demand via the state-hub MCP. + +**Discover:** `list_kaizen_agents()` — returns all agents with name, description, category +**Load:** `get_kaizen_agent("tdd-workflow")` — returns full instructions; read and follow them + +Common agents: + +| Agent | Category | When to use | +|-------|----------|-------------| +| `tdd-workflow` | testing | Step-by-step TDD8 workflow for any feature | +| `code-refactoring` | quality | Code quality analysis and safe refactoring | +| `test-maintenance` | testing | Diagnose and fix failing tests | +| `requirements-engineering` | process | Prevent interface/mock mismatches upfront | +| `keepaTodofile` | process | Maintain TODO.md during work | +| `project-management` | process | Track status, determine next steps | +| `datamodel-optimization` | quality | Optimize dataclasses and data structures | + +All 17 agents: call `list_kaizen_agents()` for the full list. diff --git a/.claude/rules/architecture.md b/.claude/rules/architecture.md new file mode 100644 index 0000000..7c2a645 --- /dev/null +++ b/.claude/rules/architecture.md @@ -0,0 +1,8 @@ +## Architecture + + + +## Quick Reference + +`~/state-hub/mcp_server/TOOLS.md` — MCP tool reference diff --git a/.claude/rules/credential-routing.md b/.claude/rules/credential-routing.md new file mode 100644 index 0000000..590e0c0 --- /dev/null +++ b/.claude/rules/credential-routing.md @@ -0,0 +1,50 @@ +# Credential and access routing + +**Audience:** Codex, Claude Code, Grok, and custodian agents that call **llm-connect** +for inference. Run this check **before** requesting secrets, API keys, SSH access, +login tokens, or database passwords — in any repo, not only `ops-warden`. + +ops-warden **issues SSH certificates only** (`warden sign`, `cert_command`). Every +other credential need belongs to another subsystem. **Do not** message +`ops-warden` on State Hub expecting a secret value; the reply is a pointer, not a key. + +### Lookup (do this first) + +```bash +warden route find "" --json +warden route show --json +``` + +Requires the `warden` CLI from `~/ops-warden` (`uv tool install .` or `uv run warden`). + +| Agent runtime | How to orient | +| --- | --- | +| **Codex / Grok** (shell, HTTP State Hub) | `warden route` commands above; inbox `to_agent=user-engine` is for coordination, not secret vending | +| **Claude Code** (MCP when available) | `get_domain_summary("custodian")` for workstreams; **still** use `warden route` for credential ownership | +| **llm-connect** (inference service) | Never put secret retrieval in prompts; route custody to OpenBao/operator paths surfaced by `warden route` | + +### Quick routing table + +| I need… | Owner | ops-warden executes? | +| --- | --- | --- | +| SSH cert (`adm`/`agt`/`atm`) | ops-warden | **Yes** — `warden sign` | +| API key, DB password, provider token | OpenBao (`railiance-platform`) | No — route only | +| Login / OIDC / MFA | key-cape / Keycloak | No — route only | +| Authorization decision | flex-auth | No — route only | +| activity-core → issue-core emission | activity-core + issue-core | No — `warden route show activity-core-issue-sink` | +| SSH tunnel | ops-bridge (+ `cert_command` from warden) | No — route only | + +### Anti-patterns (do not do these) + +- `POST /messages/` to `ops-warden` asking for `ISSUE_CORE_API_KEY`, `OPENROUTER_API_KEY`, etc. +- Inventing `warden secret`, `warden login`, `warden bao`, `warden tunnel` — they do not exist +- Pasting secrets into Git, State Hub, workplans, logs, or chat + +### Other capabilities (reuse-surface) + +Non-credential capabilities are usually discovered through **reuse-surface** federation +(`reuse-surface` registry / `capability.*` indexes). Credential routing is inlined in +every repo's agent instructions because it is high-frequency, high-risk, and easy to +get wrong. + +**Canon:** `~/ops-warden/wiki/CredentialRouting.md` · catalog `~/ops-warden/registry/routing/catalog.yaml` \ No newline at end of file diff --git a/.claude/rules/first-session.md b/.claude/rules/first-session.md new file mode 100644 index 0000000..b1dc769 --- /dev/null +++ b/.claude/rules/first-session.md @@ -0,0 +1,38 @@ +## First Session Protocol + +Triggered when `get_domain_summary("communication")` shows **no workstreams**. +The project is registered but work has not yet been structured. + +**Step 1 — Read, don't write** +- `~/the-custodian/canon/projects/communication/project_charter_v0.1.md` — purpose, scope +- `~/the-custodian/canon/projects/communication/roadmap_v0.1.md` — planned phases +- Scan repo root: README, directory structure, existing code or docs + +**Step 2 — Survey in-progress work** +Look for TODOs, open branches, half-finished files. Note done vs. started but incomplete. + +**Step 3 — Propose workstreams to Bernd** +Propose 1–3 workstreams — each a coherent strand, weeks to months, anchored to a +roadmap phase. **Wait for approval before creating.** + +**Step 4 — Create workplan file first, then DB record (ADR-001)** +``` +workplans/USER-WP-NNNN-.md ← write this first +``` +Then register in the hub: +``` +create_workstream(topic_id="a6c6e745-bf54-4465-9340-1534a2be493e", title="...", owner="...", description="...") +create_task(workstream_id="", title="...", priority="high|medium|low") +``` + +**Step 5 — Record the setup** +``` +add_progress_event( + summary="First session: structured communication into N workstreams, M tasks", + event_type="milestone", + topic_id="a6c6e745-bf54-4465-9340-1534a2be493e", + detail={"workstreams": [...], "tasks_created": M} +) +``` + + diff --git a/.claude/rules/repo-boundary.md b/.claude/rules/repo-boundary.md new file mode 100644 index 0000000..1361e9a --- /dev/null +++ b/.claude/rules/repo-boundary.md @@ -0,0 +1,8 @@ +## Repo boundary + +This repo owns **user-engine** only. It does not own: + + diff --git a/.claude/rules/repo-identity.md b/.claude/rules/repo-identity.md new file mode 100644 index 0000000..bf40147 --- /dev/null +++ b/.claude/rules/repo-identity.md @@ -0,0 +1,5 @@ +**Purpose:** Headless user-domain/profile service for accounts, preferences, memberships, catalogs, projections, audit, and events. + +**Domain:** communication +**Repo slug:** user-engine +**Topic ID:** a6c6e745-bf54-4465-9340-1534a2be493e diff --git a/.claude/rules/session-protocol.md b/.claude/rules/session-protocol.md new file mode 100644 index 0000000..d892675 --- /dev/null +++ b/.claude/rules/session-protocol.md @@ -0,0 +1,85 @@ +## Session Protocol + +Dev Hub (State Hub API): http://127.0.0.1:8000 +MCP server name in `~/.claude.json`: `dev-hub` + +**Step 1 — Orient** + +Read the offline-safe brief first — it works without a live hub connection: +```bash +cat .custodian-brief.md +``` +Then call the MCP tool for richer cross-domain context when MCP tools are exposed: +``` +get_domain_summary("communication") +``` +If MCP tools are unavailable in the current agent session, use the REST API: +```bash +curl -s "http://127.0.0.1:8000/state/summary" | python3 -m json.tool +``` +If the hub is offline: `cd ~/state-hub && make api` + +**Step 2 — Check inbox** +With MCP tools: +``` +get_messages(to_agent="user-engine", unread_only=True) +``` +Mark read with `mark_message_read(message_id)`. Reply or act on coordination +requests before proceeding. + +Without MCP tools: +```bash +curl -s "http://127.0.0.1:8000/messages/?to_agent=user-engine&unread_only=true" \ + | python3 -m json.tool +curl -s -X PATCH "http://127.0.0.1:8000/messages//read" \ + -H "Content-Type: application/json" -d '{}' +``` + +**Step 3 — Scan workplans** +```bash +ls workplans/ +``` +For each file with `status: ready`, `active`, or `blocked`, note pending +`wait`/`todo`/`progress` tasks. + +**Step 4 — Present brief** + +1. **Active workstreams** for `communication` — title, task counts, blocking decisions +2. **Pending tasks** from `workplans/` + any `[repo:user-engine]` hub tasks +3. **Goal guidance** — if `goal_guidance` in summary: + - `needs_workplan`: surface as top action — *"Repo goal '{title}' has no workplan yet"* + - `alignment_warnings`: flag if active work is not aligned with current goal +4. **Suggested next action** — highest-priority open item +5. **SBOM status** — flag if `last_sbom_at` is unset for this repo + +If no workstreams: follow First Session Protocol (`first-session.md`). + +**During work:** `record_decision()` · `add_progress_event()` · `resolve_decision()` + +> State Hub is a *read model*. Bootstrap tools (`create_workstream`, `create_task`) +> are First Session Protocol only. Work structure belongs in repo files (ADR-001). + +**Session close:** +With MCP tools: +``` +add_progress_event(summary="...", topic_id="a6c6e745-bf54-4465-9340-1534a2be493e", workstream_id="") +``` +Without MCP tools: +```bash +curl -s -X POST http://127.0.0.1:8000/progress/ \ + -H "Content-Type: application/json" \ + -d '{"topic_id":"a6c6e745-bf54-4465-9340-1534a2be493e","workstream_id":"","event_type":"note","summary":"what changed","author":"codex"}' +``` +If workplan files were modified, ensure the local copy is up to date first: +```bash +git -C pull --ff-only +cd ~/state-hub && make fix-consistency REPO=user-engine +``` +For repos where implementation runs on a remote machine (e.g. CoulombCore), +use the combined target which pulls before fixing: +```bash +cd ~/state-hub && make fix-consistency-remote REPO=user-engine +``` +**C-15** (DB task ahead of file) is normal in multi-machine workflows — writeback +will sync the file to match DB. **C-16** (repo behind remote) blocks all writes +until you pull — intentional to prevent clobbering remote progress. diff --git a/.claude/rules/stack-and-commands.md b/.claude/rules/stack-and-commands.md new file mode 100644 index 0000000..dc53ac6 --- /dev/null +++ b/.claude/rules/stack-and-commands.md @@ -0,0 +1,19 @@ +## Stack + + +- **Language:** +- **Key deps:** + +## Dev Commands + +```bash +# TODO: Fill in the standard commands for this repo + +# Install dependencies + +# Run tests + +# Lint / type check + +# Build / package (if applicable) +``` diff --git a/.claude/rules/workplan-convention.md b/.claude/rules/workplan-convention.md new file mode 100644 index 0000000..910f5c7 --- /dev/null +++ b/.claude/rules/workplan-convention.md @@ -0,0 +1,40 @@ +## Workplan Convention (ADR-001) + +File location: `workplans/USER-WP-NNNN-.md` +ID prefix: `USER-WP-` + +Work items originate as files in this repo **before** being registered in the hub. + +Canonical workplan/workstream frontmatter statuses are: +`proposed`, `ready`, `active`, `blocked`, `backlog`, `finished`, `archived`. +Use `proposed` for a newly drafted plan, `ready` after review against current +repo state, and `finished` when implementation is complete. `stalled` and +`needs_review` are derived health labels, not stored statuses. + +Closed workplans may be moved to `workplans/archived/` with a completion-date +prefix: `YYMMDD-USER-WP-NNNN-.md`. The frontmatter id remains +unchanged; the prefix is only for quick visual reference. + +Small opportunistic tasks discovered during another session use **Ad Hoc Tasks**: +`workplans/ADHOC-YYYY-MM-DD.md`, workstream slug `adhoc-YYYY-MM-DD`, and task ids +`ADHOC-YYYY-MM-DD-T01`, `T02`, etc. Use adhocs only for low-risk work completed +directly. Promote anything requiring analysis, design, approval, dependencies, or +multiple planned phases into a normal workplan. + +Ecosystem todos from other agents arrive as `[repo:user-engine]` hub tasks — +visible at session start. Pick one up by creating the workplan file, then registering +the workstream. + +Task blocks use this shape: + +```task +id: USER-WP-NNNN-T01 +status: wait | todo | progress | done | cancel +priority: high | medium | low +state_hub_task_id: "" # written by fix-consistency — do not edit +``` + +Status progression is `todo` → `progress` → `done`; use `wait` for waiting or +blocked work and `cancel` for stopped work. + + diff --git a/AGENTS.md b/AGENTS.md new file mode 100644 index 0000000..566aab1 --- /dev/null +++ b/AGENTS.md @@ -0,0 +1,219 @@ +# user-engine — Agent Instructions + +## Repo Identity + +**Purpose:** Headless user-domain/profile service for accounts, preferences, memberships, catalogs, projections, audit, and events. + +**Domain:** communication +**Repo slug:** user-engine +**Topic ID:** `a6c6e745-bf54-4465-9340-1534a2be493e` +**Workplan prefix:** `USER-WP-` + +--- + +## State Hub Integration + +The Custodian State Hub tracks work across all domains. Interact via HTTP REST — +there is no MCP server for Codex agents. + +| Context | URL | +|---------|-----| +| Local workstation | `http://127.0.0.1:8000` | +| Remote via tunnel | `http://127.0.0.1:18000` | + +### Orient at session start + +```bash +# Offline brief — works without hub connection +cat .custodian-brief.md + +# Active workstreams for this domain +curl -s "http://127.0.0.1:8000/workstreams/?topic_id=a6c6e745-bf54-4465-9340-1534a2be493e&status=active" \ + | python3 -m json.tool + +# Check inbox +curl -s "http://127.0.0.1:8000/messages/?to_agent=user-engine&unread_only=true" \ + | python3 -m json.tool +``` + +Mark a message read: +```bash +curl -s -X PATCH "http://127.0.0.1:8000/messages//read" \ + -H "Content-Type: application/json" -d '{}' +``` + +### Log progress (required at session close) + +```bash +curl -s -X POST http://127.0.0.1:8000/progress/ \ + -H "Content-Type: application/json" \ + -d '{ + "summary": "what was done", + "event_type": "note", + "author": "codex", + "workstream_id": "", + "task_id": "" + }' +``` + +Omit `workstream_id` / `task_id` when not applicable. + +### Update task status + +```bash +curl -s -X PATCH "http://127.0.0.1:8000/tasks/" \ + -H "Content-Type: application/json" \ + -d '{"status": "progress"}' +# values: wait | todo | progress | done | cancel +``` + +### Flag a task for human review + +```bash +curl -s -X PATCH "http://127.0.0.1:8000/tasks/" \ + -H "Content-Type: application/json" \ + -d '{"needs_human": true, "intervention_note": "reason"}' +``` + +--- + +## Session Protocol + +**Start:** +1. `cat .custodian-brief.md` — domain goal and open workstreams (offline-safe) +2. Check inbox: `GET /messages/?to_agent=user-engine&unread_only=true`; mark read +3. Scan workplans: `ls workplans/` — note `status: ready`, `active`, or `blocked` files and open tasks +4. Check human-needed tasks: `GET /tasks/?needs_human=true` + +**During work:** +- Update task statuses in workplan files as tasks progress +- Record significant decisions via `POST /decisions/` + +**Close:** +1. Update workplan file task statuses to reflect progress +2. Log: `POST /progress/` with a summary of what changed +3. Note for the custodian operator: after workplan file changes, run from + `~/state-hub`: + ```bash + make fix-consistency REPO=user-engine + ``` + This syncs task status from files into the hub DB. + +--- + +## Credential and access routing + +**Audience:** Codex, Claude Code, Grok, and custodian agents that call **llm-connect** +for inference. Run this check **before** requesting secrets, API keys, SSH access, +login tokens, or database passwords — in any repo, not only `ops-warden`. + +ops-warden **issues SSH certificates only** (`warden sign`, `cert_command`). Every +other credential need belongs to another subsystem. **Do not** message +`ops-warden` on State Hub expecting a secret value; the reply is a pointer, not a key. + +### Lookup (do this first) + +```bash +warden route find "" --json +warden route show --json +``` + +Requires the `warden` CLI from `~/ops-warden` (`uv tool install .` or `uv run warden`). + +| Agent runtime | How to orient | +| --- | --- | +| **Codex / Grok** (shell, HTTP State Hub) | `warden route` commands above; inbox `to_agent=user-engine` is for coordination, not secret vending | +| **Claude Code** (MCP when available) | `get_domain_summary("custodian")` for workstreams; **still** use `warden route` for credential ownership | +| **llm-connect** (inference service) | Never put secret retrieval in prompts; route custody to OpenBao/operator paths surfaced by `warden route` | + +### Quick routing table + +| I need… | Owner | ops-warden executes? | +| --- | --- | --- | +| SSH cert (`adm`/`agt`/`atm`) | ops-warden | **Yes** — `warden sign` | +| API key, DB password, provider token | OpenBao (`railiance-platform`) | No — route only | +| Login / OIDC / MFA | key-cape / Keycloak | No — route only | +| Authorization decision | flex-auth | No — route only | +| activity-core → issue-core emission | activity-core + issue-core | No — `warden route show activity-core-issue-sink` | +| SSH tunnel | ops-bridge (+ `cert_command` from warden) | No — route only | + +### Anti-patterns (do not do these) + +- `POST /messages/` to `ops-warden` asking for `ISSUE_CORE_API_KEY`, `OPENROUTER_API_KEY`, etc. +- Inventing `warden secret`, `warden login`, `warden bao`, `warden tunnel` — they do not exist +- Pasting secrets into Git, State Hub, workplans, logs, or chat + +### Other capabilities (reuse-surface) + +Non-credential capabilities are usually discovered through **reuse-surface** federation +(`reuse-surface` registry / `capability.*` indexes). Credential routing is inlined in +every repo's agent instructions because it is high-frequency, high-risk, and easy to +get wrong. + +**Canon:** `~/ops-warden/wiki/CredentialRouting.md` · catalog `~/ops-warden/registry/routing/catalog.yaml` + + + + +--- + +## Workplan Convention (ADR-001) + +Work items originate as files in this repo — not in the hub. The hub is a +read/cache/index layer that rebuilds from files. + +**File location:** `workplans/USER-WP-NNNN-.md` + +**Archived location:** finished workplans may move to +`workplans/archived/YYMMDD-USER-WP-NNNN-.md`. The `YYMMDD` prefix is +the completion/archive date; the frontmatter `id` does not change. + +**Ad Hoc Tasks:** small opportunistic fixes discovered during a session use +`workplans/ADHOC-YYYY-MM-DD.md` with task ids `ADHOC-YYYY-MM-DD-T01`, etc. Use +this only for low-risk work completed directly; create a normal workplan for +anything needing analysis, design, approval, dependencies, or multiple phases. + +**Frontmatter:** + +```yaml +--- +id: USER-WP-NNNN +type: workplan +title: "..." +domain: communication +repo: user-engine +status: proposed | ready | active | blocked | backlog | finished | archived +owner: codex +topic_slug: ... +created: "YYYY-MM-DD" +updated: "YYYY-MM-DD" +state_hub_workstream_id: "" # written by fix-consistency — do not edit +--- +``` + +Use `proposed` for a new draft, `ready` after review against current repo +state, and `finished` after implementation. `stalled` and `needs_review` are +derived health labels, not frontmatter statuses. + +**Task block format** (one per `##` section): + +``` +## Task Title + +` ` `task +id: USER-WP-NNNN-T01 +status: wait | todo | progress | done | cancel +priority: high | medium | low +state_hub_task_id: "" # written by fix-consistency — do not edit +` ` ` + +Task description text. +``` + +Status progression: `todo` → `progress` → `done`; use `wait` for waiting/blocked work and `cancel` for stopped work. + +To create a new workplan: +1. Write the file following the format above +2. Notify the custodian operator to run `make fix-consistency REPO=user-engine` + (or send a message to the hub agent via `POST /messages/`) diff --git a/CLAUDE.md b/CLAUDE.md new file mode 100644 index 0000000..9137fe6 --- /dev/null +++ b/CLAUDE.md @@ -0,0 +1,12 @@ +# user-engine — Claude Code Instructions + +@SCOPE.md +@.claude/rules/repo-identity.md +@.claude/rules/session-protocol.md +@.claude/rules/first-session.md +@.claude/rules/workplan-convention.md +@.claude/rules/stack-and-commands.md +@.claude/rules/architecture.md +@.claude/rules/repo-boundary.md +@.claude/rules/credential-routing.md +@.claude/rules/agents.md diff --git a/workplans/USER-WP-0001-preparation-and-interface-adoption.md b/workplans/USER-WP-0001-preparation-and-interface-adoption.md index b10287a..d8f9b8d 100644 --- a/workplans/USER-WP-0001-preparation-and-interface-adoption.md +++ b/workplans/USER-WP-0001-preparation-and-interface-adoption.md @@ -2,7 +2,7 @@ id: USER-WP-0001 type: workplan title: "User Engine Preparation And Interface Adoption" -domain: netkingdom +domain: communication repo: user-engine status: finished owner: codex diff --git a/workplans/USER-WP-0002-isolated-mvp.md b/workplans/USER-WP-0002-isolated-mvp.md index 16258f5..e350e30 100644 --- a/workplans/USER-WP-0002-isolated-mvp.md +++ b/workplans/USER-WP-0002-isolated-mvp.md @@ -2,7 +2,7 @@ id: USER-WP-0002 type: workplan title: "User Engine Isolated MVP" -domain: netkingdom +domain: communication repo: user-engine status: finished owner: codex diff --git a/workplans/USER-WP-0003-multi-tenancy.md b/workplans/USER-WP-0003-multi-tenancy.md index 303affb..e8b177a 100644 --- a/workplans/USER-WP-0003-multi-tenancy.md +++ b/workplans/USER-WP-0003-multi-tenancy.md @@ -2,7 +2,7 @@ id: USER-WP-0003 type: workplan title: "User Engine Multi-Tenancy" -domain: netkingdom +domain: communication repo: user-engine status: finished owner: codex diff --git a/workplans/USER-WP-0004-multi-application-catalogs.md b/workplans/USER-WP-0004-multi-application-catalogs.md index 33376b4..72f8f71 100644 --- a/workplans/USER-WP-0004-multi-application-catalogs.md +++ b/workplans/USER-WP-0004-multi-application-catalogs.md @@ -2,7 +2,7 @@ id: USER-WP-0004 type: workplan title: "User Engine Multi-Application And Catalog Support" -domain: netkingdom +domain: communication repo: user-engine status: finished owner: codex diff --git a/workplans/USER-WP-0005-integrated-test-scenarios.md b/workplans/USER-WP-0005-integrated-test-scenarios.md index 26ba08c..5b4bea1 100644 --- a/workplans/USER-WP-0005-integrated-test-scenarios.md +++ b/workplans/USER-WP-0005-integrated-test-scenarios.md @@ -2,7 +2,7 @@ id: USER-WP-0005 type: workplan title: "User Engine Integrated Test Scenarios" -domain: netkingdom +domain: communication repo: user-engine status: finished owner: codex diff --git a/workplans/USER-WP-0006-finalization-polish.md b/workplans/USER-WP-0006-finalization-polish.md index 1f53b89..3706969 100644 --- a/workplans/USER-WP-0006-finalization-polish.md +++ b/workplans/USER-WP-0006-finalization-polish.md @@ -2,7 +2,7 @@ id: USER-WP-0006 type: workplan title: "User Engine Implementation Assessment And Polish" -domain: netkingdom +domain: communication repo: user-engine status: finished owner: codex diff --git a/workplans/USER-WP-0007-identity-domain-canon-alignment.md b/workplans/USER-WP-0007-identity-domain-canon-alignment.md index c7dfb71..649418a 100644 --- a/workplans/USER-WP-0007-identity-domain-canon-alignment.md +++ b/workplans/USER-WP-0007-identity-domain-canon-alignment.md @@ -2,7 +2,7 @@ id: USER-WP-0007 type: workplan title: "Identity Domain Canon Alignment" -domain: netkingdom +domain: communication repo: user-engine status: finished owner: codex diff --git a/workplans/USER-WP-0008-family-dataspace-onboarding.md b/workplans/USER-WP-0008-family-dataspace-onboarding.md index 17956df..fa0f96b 100644 --- a/workplans/USER-WP-0008-family-dataspace-onboarding.md +++ b/workplans/USER-WP-0008-family-dataspace-onboarding.md @@ -2,7 +2,7 @@ id: USER-WP-0008 type: workplan title: "Family Dataspace Onboarding" -domain: netkingdom +domain: communication repo: user-engine status: finished owner: codex diff --git a/workplans/USER-WP-0009-postgres-durable-store-requirements.md b/workplans/USER-WP-0009-postgres-durable-store-requirements.md index 5672175..794a17d 100644 --- a/workplans/USER-WP-0009-postgres-durable-store-requirements.md +++ b/workplans/USER-WP-0009-postgres-durable-store-requirements.md @@ -2,7 +2,7 @@ id: USER-WP-0009 type: workplan title: "Postgres Durable Store Consumer Requirements" -domain: netkingdom +domain: communication repo: user-engine status: finished owner: codex diff --git a/workplans/USER-WP-0010-registration-identity-and-factor-model.md b/workplans/USER-WP-0010-registration-identity-and-factor-model.md index 932828c..787afd1 100644 --- a/workplans/USER-WP-0010-registration-identity-and-factor-model.md +++ b/workplans/USER-WP-0010-registration-identity-and-factor-model.md @@ -2,7 +2,7 @@ id: USER-WP-0010 type: workplan title: "Registration Identity And Factor Model" -domain: netkingdom +domain: communication repo: user-engine status: finished owner: codex diff --git a/workplans/USER-WP-0011-prepared-accounts-and-entitlement-claims.md b/workplans/USER-WP-0011-prepared-accounts-and-entitlement-claims.md index 037fd23..186eb70 100644 --- a/workplans/USER-WP-0011-prepared-accounts-and-entitlement-claims.md +++ b/workplans/USER-WP-0011-prepared-accounts-and-entitlement-claims.md @@ -2,7 +2,7 @@ id: USER-WP-0011 type: workplan title: "Prepared Accounts And Entitlement Claims" -domain: netkingdom +domain: communication repo: user-engine status: finished owner: codex diff --git a/workplans/USER-WP-0012-hats-realms-services-assets-access-profiles.md b/workplans/USER-WP-0012-hats-realms-services-assets-access-profiles.md index 161fea4..fa278fe 100644 --- a/workplans/USER-WP-0012-hats-realms-services-assets-access-profiles.md +++ b/workplans/USER-WP-0012-hats-realms-services-assets-access-profiles.md @@ -2,7 +2,7 @@ id: USER-WP-0012 type: workplan title: "Hats, Realms, Services, Assets, And Access Profiles" -domain: netkingdom +domain: communication repo: user-engine status: finished owner: codex diff --git a/workplans/USER-WP-0013-onboarding-journeys-and-welcome-protocols.md b/workplans/USER-WP-0013-onboarding-journeys-and-welcome-protocols.md index 74ba7d6..dc9b4fd 100644 --- a/workplans/USER-WP-0013-onboarding-journeys-and-welcome-protocols.md +++ b/workplans/USER-WP-0013-onboarding-journeys-and-welcome-protocols.md @@ -2,7 +2,7 @@ id: USER-WP-0013 type: workplan title: "Onboarding Journeys And Welcome Protocols" -domain: netkingdom +domain: communication repo: user-engine status: finished owner: codex diff --git a/workplans/USER-WP-0014-registration-and-access-management-ui.md b/workplans/USER-WP-0014-registration-and-access-management-ui.md index 33b1513..3b991e6 100644 --- a/workplans/USER-WP-0014-registration-and-access-management-ui.md +++ b/workplans/USER-WP-0014-registration-and-access-management-ui.md @@ -2,7 +2,7 @@ id: USER-WP-0014 type: workplan title: "Registration And Access Management UI" -domain: netkingdom +domain: communication repo: user-engine status: finished owner: codex diff --git a/workplans/USER-WP-0015-registration-scenario-and-security-conformance.md b/workplans/USER-WP-0015-registration-scenario-and-security-conformance.md index f7ef30c..d734675 100644 --- a/workplans/USER-WP-0015-registration-scenario-and-security-conformance.md +++ b/workplans/USER-WP-0015-registration-scenario-and-security-conformance.md @@ -2,7 +2,7 @@ id: USER-WP-0015 type: workplan title: "Registration Scenario And Security Conformance" -domain: netkingdom +domain: communication repo: user-engine status: finished owner: codex diff --git a/workplans/USER-WP-0016-durable-store-migration-and-conformance-harness.md b/workplans/USER-WP-0016-durable-store-migration-and-conformance-harness.md index c1dc838..26d02d2 100644 --- a/workplans/USER-WP-0016-durable-store-migration-and-conformance-harness.md +++ b/workplans/USER-WP-0016-durable-store-migration-and-conformance-harness.md @@ -2,7 +2,7 @@ id: USER-WP-0016 type: workplan title: "Durable Store Migration And Conformance Harness" -domain: netkingdom +domain: communication repo: user-engine status: finished owner: codex diff --git a/workplans/USER-WP-0017-durable-store-record-serialization.md b/workplans/USER-WP-0017-durable-store-record-serialization.md index 184b103..592d041 100644 --- a/workplans/USER-WP-0017-durable-store-record-serialization.md +++ b/workplans/USER-WP-0017-durable-store-record-serialization.md @@ -2,7 +2,7 @@ id: USER-WP-0017 type: workplan title: "Durable Store Record Serialization" -domain: netkingdom +domain: communication repo: user-engine status: finished owner: codex diff --git a/workplans/USER-WP-0018-postgres-store-adapter.md b/workplans/USER-WP-0018-postgres-store-adapter.md index 213efe9..a7ef100 100644 --- a/workplans/USER-WP-0018-postgres-store-adapter.md +++ b/workplans/USER-WP-0018-postgres-store-adapter.md @@ -2,7 +2,7 @@ id: USER-WP-0018 type: workplan title: "Postgres Store Adapter" -domain: netkingdom +domain: communication repo: user-engine status: finished owner: codex diff --git a/workplans/USER-WP-0019-provider-backed-postgres-conformance.md b/workplans/USER-WP-0019-provider-backed-postgres-conformance.md index e57170e..0d0179e 100644 --- a/workplans/USER-WP-0019-provider-backed-postgres-conformance.md +++ b/workplans/USER-WP-0019-provider-backed-postgres-conformance.md @@ -2,7 +2,7 @@ id: USER-WP-0019 type: workplan title: "Provider Backed Postgres Conformance" -domain: netkingdom +domain: communication repo: user-engine status: finished owner: codex