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/first-session.md b/.claude/rules/first-session.md new file mode 100644 index 0000000..0763ae3 --- /dev/null +++ b/.claude/rules/first-session.md @@ -0,0 +1,38 @@ +## First Session Protocol + +Triggered when `get_domain_summary("consumer")` shows **no workstreams**. +The project is registered but work has not yet been structured. + +**Step 1 — Read, don't write** +- `~/the-custodian/canon/projects/consumer/project_charter_v0.1.md` — purpose, scope +- `~/the-custodian/canon/projects/consumer/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/SHARD-WP-NNNN-.md ← write this first +``` +Then register in the hub: +``` +create_workstream(topic_id="4c2e5315-2cb9-447c-9d16-a39bdb0aabd0", title="...", owner="...", description="...") +create_task(workstream_id="", title="...", priority="high|medium|low") +``` + +**Step 5 — Record the setup** +``` +add_progress_event( + summary="First session: structured consumer into N workstreams, M tasks", + event_type="milestone", + topic_id="4c2e5315-2cb9-447c-9d16-a39bdb0aabd0", + 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..3ea5992 --- /dev/null +++ b/.claude/rules/repo-boundary.md @@ -0,0 +1,8 @@ +## Repo boundary + +This repo owns **shard-wiki** 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..fdbf9ff --- /dev/null +++ b/.claude/rules/repo-identity.md @@ -0,0 +1,5 @@ +**Purpose:** Git-based Markdown wiki orchestrator and federation layer. Python (src/ layout, hatchling, pytest). Early-stage: scaffold + INTENT.md defined, domain model not yet implemented. See INTENT.md for authoritative scope. + +**Domain:** consumer +**Repo slug:** shard-wiki +**Topic ID:** 4c2e5315-2cb9-447c-9d16-a39bdb0aabd0 diff --git a/.claude/rules/session-protocol.md b/.claude/rules/session-protocol.md new file mode 100644 index 0000000..fd3e771 --- /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("consumer") +``` +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="shard-wiki", 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=shard-wiki&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 `consumer` — title, task counts, blocking decisions +2. **Pending tasks** from `workplans/` + any `[repo:shard-wiki]` 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="4c2e5315-2cb9-447c-9d16-a39bdb0aabd0", 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":"4c2e5315-2cb9-447c-9d16-a39bdb0aabd0","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=shard-wiki +``` +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=shard-wiki +``` +**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..adb9d4e --- /dev/null +++ b/.claude/rules/workplan-convention.md @@ -0,0 +1,40 @@ +## Workplan Convention (ADR-001) + +File location: `workplans/SHARD-WP-NNNN-.md` +ID prefix: `SHARD-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-SHARD-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:shard-wiki]` 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: SHARD-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 index 05dec03..a1f55be 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -1,65 +1,104 @@ -# AGENTS.md +# shard-wiki — Agent Instructions -Guidance for agents working in `shard-wiki`. +## Repo Identity -## Read First +**Purpose:** Git-based Markdown wiki orchestrator and federation layer. Python (src/ layout, hatchling, pytest). Early-stage: scaffold + INTENT.md defined, domain model not yet implemented. See INTENT.md for authoritative scope. -1. `INTENT.md` — aspiration and boundaries (stable; architectural changes are rare). -2. `SCOPE.md` — what we are achieving now and current maturity. -3. `.custodian-brief.md` — State Hub snapshot (generated; do not edit manually). +**Domain:** consumer +**Repo slug:** shard-wiki +**Topic ID:** `4c2e5315-2cb9-447c-9d16-a39bdb0aabd0` +**Workplan prefix:** `SHARD-WP-` -## Documentation Layout +--- -This repo follows the CoulombSocial / HelixForge / MarkiTect documentation -layout (recommendation, not strict law). Efficient retrieval by purpose: +## State Hub Integration -| Path | Purpose | -|------|---------| -| `INTENT.md` | Aspiration and boundaries | -| `SCOPE.md` | Top-level view of current achievement; closes gap to INTENT | -| `research/` | Exploration results (`yymmdd-` prefix on files or subdirs) | -| `demand/` | Inbound requests not yet reviewed into spec or workplans | -| `spec/` | Implementation guardrails (PRD, TSD, use cases, architecture) | -| `workplans/` | State Hub–registered implementation tasks | -| `docs/` | Stakeholder documentation (users, developers, humans, agents) | -| `wiki/` | Perspective-free interconnected knowledge (wiki UI when connected) | -| `issues/` | Mirror of relevant open tickets when ticket systems are in use | -| `history/` | Archived material (`yymmdd-` prefix); out of scope for daily work | +The Custodian State Hub tracks work across all domains. Interact via HTTP REST — +there is no MCP server for Codex agents. -**Mode of operation:** close SCOPE → INTENT while learning; refine both as needed. +| Context | URL | +|---------|-----| +| Local workstation | `http://127.0.0.1:8000` | +| Remote via tunnel | `http://127.0.0.1:18000` | -## Domain Vocabulary - -Honor terms from `INTENT.md`: shard, root entity, adapter contract, projection, -overlay, coordination journal, shard modes. Do not invent parallel vocabulary. - -## Build And Test +### Orient at session start ```bash -pip install -e ".[dev]" -pytest -ruff check -ruff format +# 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=4c2e5315-2cb9-447c-9d16-a39bdb0aabd0&status=active" \ + | python3 -m json.tool + +# Check inbox +curl -s "http://127.0.0.1:8000/messages/?to_agent=shard-wiki&unread_only=true" \ + | python3 -m json.tool ``` -## State Hub +Mark a message read: +```bash +curl -s -X PATCH "http://127.0.0.1:8000/messages//read" \ + -H "Content-Type: application/json" -d '{}' +``` -Workplans register with State Hub. After workplan changes: +### Log progress (required at session close) ```bash -cd ~/state-hub && make fix-consistency REPO=shard-wiki +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": "" + }' ``` -Finished or canceled workplans move to `history/` with a `yymmdd-` archive prefix. +Omit `workstream_id` / `task_id` when not applicable. -## Where To Put New Material +### 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=shard-wiki&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=shard-wiki + ``` + This syncs task status from files into the hub DB. -- Exploratory analysis → `research/yymmdd-/` -- Raw feature ask or external requirement → `demand/` -- Reviewed design ready to guide code → `spec/` -- Implementation tasks → `workplans/` -- User/dev/agent how-to → `docs/` -- Collaborative unstructured notes → `wiki/` --- ## Credential and access routing @@ -112,3 +151,69 @@ 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` + + + + +--- + +## 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/SHARD-WP-NNNN-.md` + +**Archived location:** finished workplans may move to +`workplans/archived/YYMMDD-SHARD-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: SHARD-WP-NNNN +type: workplan +title: "..." +domain: consumer +repo: shard-wiki +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: SHARD-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=shard-wiki` + (or send a message to the hub agent via `POST /messages/`) diff --git a/CLAUDE.md b/CLAUDE.md index 94f9fee..ecfac84 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -1,54 +1,12 @@ -# CLAUDE.md +# shard-wiki — Claude Code Instructions -This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository. - -## Repository status - -This is an **early-stage Python repository**. The package scaffold (`src/shard_wiki/`, `tests/`, `pyproject.toml`) exists with only smoke tests — the domain model is not yet implemented. Read `INTENT.md` (aspiration), `SCOPE.md` (current achievement), and `AGENTS.md` (layout and conventions) before designing anything. Close the gap from SCOPE to INTENT via `research/`, `spec/`, and `workplans/`. - -## What this project is - -`shard-wiki` is a **Git-based Markdown wiki orchestrator and federation layer**, not a wiki engine. It lets multiple heterogeneous wiki-shaped page stores (**shards**) attach to a shared root entity and be presented as a **union of pages**, while preserving each shard's separate storage, provenance, capabilities, and history. - -The core job is orchestration across backends — Git repos, repo subdirectories (`wiki/`), Gitea wikis, local folders, Obsidian vaults, WebDAV/Nextcloud directories, Coulomb spaces — never replacing or homogenizing them. - -## Core domain model (the concepts code must honor) - -These abstractions come from `INTENT.md` and define the architecture. New code should map onto them rather than inventing parallel vocabulary: - -- **Shard** — an independently meaningful page store attached to a root entity. Shards have *sovereignty*: their own backend, capabilities, limits, history, and identity model. Not all shards are Git-native. -- **Root entity / information space** — the joined space that shards attach to. Each information space should have a **Git-addressable coordination layer** (history, patches, review, backup, reconciliation) even when individual shards are not Git-native. -- **Shard adapter contract** — the versioned interface a backend implements to participate. Adapters are **capability-aware**: the core must model explicitly which operations a shard supports (read, write, diff, merge, lock, version, publish, accept patches) rather than assuming uniformity. -- **Wiki page model** — a stable, versioned, Markdown-first but backend-neutral representation of pages, paths, links, metadata, revisions. -- **Projection** — a lazy, cache-like local view of remote/external shard content. Prefer lazy projection over eager copying. -- **Overlay** — a non-destructive local edit against a remote, read-only, or capability-limited shard, representable as drafts/patches/commits/merge requests *before* destructive application ("overlay before mutation"). -- **Coordination journal** — the Git-backed record of change flows for an information space. -- **Shard modes** — read-only, write-through, mirrored, projected, cached, canonical. - -## Design constraints to enforce in code - -These are hard boundaries from `INTENT.md`; treat violations as design bugs: - -- **Mechanism over policy.** Provide primitives for federation, sync, overlays, patching, conflict detection, projection, reconciliation. Do *not* hard-code one editorial/sync/conflict/canonical-source policy — keep those configurable. -- **Union without erasure.** Always preserve provenance: which shard a page came from, its freshness, whether it is cached, whether it has overlays, whether it diverges from an equivalent page elsewhere. Never hide authorship, conflicts, freshness, or backend limitations. -- **No silent remote mutation.** Do not mutate remote systems without explicit adapter support and user intent. -- **Graceful degradation.** Limited backends must still be usable as read-only/cache/projection/backup/patch targets. -- **Not a file-sync daemon.** Synchronization is wiki-page-semantic, not generic file mirroring. - -`INTENT.md` has a "Stability Note": changes that redefine what a shard is, Git's role, how root entities are modeled, or whether this is an orchestrator vs. an engine are **architectural changes** and should be rare and deliberate. - -## Build, test, run - -Python with a `src/` layout, built via hatchling, tested with pytest. Tests run against the source tree directly (`pythonpath = ["src"]` in `pyproject.toml`), so no install/editable step is required to run them. - -```bash -pip install -e ".[dev]" # one-time: install dev tooling (pytest, pytest-cov, ruff) -pytest # run the full test suite -pytest tests/test_package.py::test_version_is_exposed # run a single test -pytest --cov # run with coverage -ruff check # lint -ruff format # format -``` - -Note: the system `pytest` is 7.4.x; `minversion` in `pyproject.toml` is pinned to `7.0` to match. Bump it if a newer pytest is installed into the dev environment. +@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/SHARD-WP-0001-yawex-requirements.md b/workplans/SHARD-WP-0001-yawex-requirements.md index 83c6b77..668313f 100644 --- a/workplans/SHARD-WP-0001-yawex-requirements.md +++ b/workplans/SHARD-WP-0001-yawex-requirements.md @@ -2,7 +2,7 @@ id: SHARD-WP-0001 type: workplan title: "shard-wiki requirements from yawex prior art" -domain: whynot +domain: consumer repo: shard-wiki status: done owner: tegwick diff --git a/workplans/SHARD-WP-0002-federation-architecture.md b/workplans/SHARD-WP-0002-federation-architecture.md index 83306b3..4241e5e 100644 --- a/workplans/SHARD-WP-0002-federation-architecture.md +++ b/workplans/SHARD-WP-0002-federation-architecture.md @@ -2,7 +2,7 @@ id: SHARD-WP-0002 type: workplan title: "federation architecture design" -domain: whynot +domain: consumer repo: shard-wiki status: done owner: tegwick diff --git a/workplans/SHARD-WP-0003-engine-dives-batch.md b/workplans/SHARD-WP-0003-engine-dives-batch.md index de6498c..68769e1 100644 --- a/workplans/SHARD-WP-0003-engine-dives-batch.md +++ b/workplans/SHARD-WP-0003-engine-dives-batch.md @@ -2,7 +2,7 @@ id: SHARD-WP-0003 type: workplan title: "wiki-engine deep-dive batch (new-insight + git-forge + classic engines)" -domain: whynot +domain: consumer repo: shard-wiki status: done owner: tegwick diff --git a/workplans/SHARD-WP-0004-computational-knowledge-systems.md b/workplans/SHARD-WP-0004-computational-knowledge-systems.md index e983c1c..971aee7 100644 --- a/workplans/SHARD-WP-0004-computational-knowledge-systems.md +++ b/workplans/SHARD-WP-0004-computational-knowledge-systems.md @@ -2,7 +2,7 @@ id: SHARD-WP-0004 type: workplan title: "computational / interactive-knowledge systems research" -domain: whynot +domain: consumer repo: shard-wiki status: done owner: tegwick diff --git a/workplans/SHARD-WP-0005-architecture-hardening.md b/workplans/SHARD-WP-0005-architecture-hardening.md index 62a0a11..4521ab9 100644 --- a/workplans/SHARD-WP-0005-architecture-hardening.md +++ b/workplans/SHARD-WP-0005-architecture-hardening.md @@ -2,7 +2,7 @@ id: SHARD-WP-0005 type: workplan title: "core architecture hardening (blueprint review fixes)" -domain: whynot +domain: consumer repo: shard-wiki status: done owner: tegwick diff --git a/workplans/SHARD-WP-0006-architecture-hardening-2.md b/workplans/SHARD-WP-0006-architecture-hardening-2.md index 45cf50a..2724804 100644 --- a/workplans/SHARD-WP-0006-architecture-hardening-2.md +++ b/workplans/SHARD-WP-0006-architecture-hardening-2.md @@ -2,7 +2,7 @@ id: SHARD-WP-0006 type: workplan title: "core architecture hardening II (round-2 review fixes)" -domain: whynot +domain: consumer repo: shard-wiki status: done owner: tegwick diff --git a/workplans/SHARD-WP-0007-foundation-implementation.md b/workplans/SHARD-WP-0007-foundation-implementation.md index e8cd0fa..b9f7db4 100644 --- a/workplans/SHARD-WP-0007-foundation-implementation.md +++ b/workplans/SHARD-WP-0007-foundation-implementation.md @@ -2,7 +2,7 @@ id: SHARD-WP-0007 type: workplan title: "foundation implementation — model, contract, decision log, union read" -domain: whynot +domain: consumer repo: shard-wiki status: done owner: tegwick diff --git a/workplans/SHARD-WP-0008-write-path.md b/workplans/SHARD-WP-0008-write-path.md index 87431d5..96825f7 100644 --- a/workplans/SHARD-WP-0008-write-path.md +++ b/workplans/SHARD-WP-0008-write-path.md @@ -2,7 +2,7 @@ id: SHARD-WP-0008 type: workplan title: "write path — overlay engine, writable adapter, apply-under-drift" -domain: whynot +domain: consumer repo: shard-wiki status: done owner: tegwick diff --git a/workplans/SHARD-WP-0009-git-decision-log.md b/workplans/SHARD-WP-0009-git-decision-log.md index b1424c1..92f5bad 100644 --- a/workplans/SHARD-WP-0009-git-decision-log.md +++ b/workplans/SHARD-WP-0009-git-decision-log.md @@ -2,7 +2,7 @@ id: SHARD-WP-0009 type: workplan title: "git-backed DecisionLog + per-space append authority" -domain: whynot +domain: consumer repo: shard-wiki status: done owner: tegwick diff --git a/workplans/SHARD-WP-0010-derived-views.md b/workplans/SHARD-WP-0010-derived-views.md index d2f6f20..c768a07 100644 --- a/workplans/SHARD-WP-0010-derived-views.md +++ b/workplans/SHARD-WP-0010-derived-views.md @@ -2,7 +2,7 @@ id: SHARD-WP-0010 type: workplan title: "derived views — wikilinks, BackLinks, RecentChanges, AllPages/SiteMap" -domain: whynot +domain: consumer repo: shard-wiki status: done owner: tegwick diff --git a/workplans/SHARD-WP-0011-incremental-union.md b/workplans/SHARD-WP-0011-incremental-union.md index fc07a45..da2e121 100644 --- a/workplans/SHARD-WP-0011-incremental-union.md +++ b/workplans/SHARD-WP-0011-incremental-union.md @@ -2,7 +2,7 @@ id: SHARD-WP-0011 type: workplan title: "incremental union maintenance + equivalence index + I-2 verification" -domain: whynot +domain: consumer repo: shard-wiki status: done owner: tegwick diff --git a/workplans/SHARD-WP-0012-git-shard-adapter.md b/workplans/SHARD-WP-0012-git-shard-adapter.md index fb5d568..ecf6e50 100644 --- a/workplans/SHARD-WP-0012-git-shard-adapter.md +++ b/workplans/SHARD-WP-0012-git-shard-adapter.md @@ -2,7 +2,7 @@ id: SHARD-WP-0012 type: workplan title: "second adapter — git-IS-store shard (contract validation on a new substrate)" -domain: whynot +domain: consumer repo: shard-wiki status: done owner: tegwick diff --git a/workplans/SHARD-WP-0013-wiki-engine-prep.md b/workplans/SHARD-WP-0013-wiki-engine-prep.md index e63fe4b..9716b56 100644 --- a/workplans/SHARD-WP-0013-wiki-engine-prep.md +++ b/workplans/SHARD-WP-0013-wiki-engine-prep.md @@ -2,7 +2,7 @@ id: SHARD-WP-0013 type: workplan title: "wiki-engine prep — reuse-surface registration, UC-catalog systematization, WikiEngineCoreArchitecture" -domain: whynot +domain: consumer repo: shard-wiki status: done owner: tegwick diff --git a/workplans/SHARD-WP-0014-engine-implementation.md b/workplans/SHARD-WP-0014-engine-implementation.md index d354f96..19aa0c4 100644 --- a/workplans/SHARD-WP-0014-engine-implementation.md +++ b/workplans/SHARD-WP-0014-engine-implementation.md @@ -2,7 +2,7 @@ id: SHARD-WP-0014 type: workplan title: "wiki-engine implementation — kernel + typed-extension runtime + activation" -domain: whynot +domain: consumer repo: shard-wiki status: done owner: tegwick