diff --git a/.claude/rules/first-session.md b/.claude/rules/first-session.md index dde0fa4..6943b00 100644 --- a/.claude/rules/first-session.md +++ b/.claude/rules/first-session.md @@ -1,11 +1,11 @@ ## First Session Protocol -Triggered when `get_domain_summary("custodian")` shows **no workstreams**. +Triggered when `get_domain_summary("infotech")` shows **no workstreams**. The project is registered but work has not yet been structured. **Step 1 — Read, don't write** -- `~/the-custodian/canon/projects/custodian/project_charter_v0.1.md` — purpose, scope -- `~/the-custodian/canon/projects/custodian/roadmap_v0.1.md` — planned phases +- `~/the-custodian/canon/projects/infotech/project_charter_v0.1.md` — purpose, scope +- `~/the-custodian/canon/projects/infotech/roadmap_v0.1.md` — planned phases - Scan repo root: README, directory structure, existing code or docs **Step 2 — Survey in-progress work** @@ -17,7 +17,7 @@ roadmap phase. **Wait for approval before creating.** **Step 4 — Create workplan file first, then DB record (ADR-001)** ``` -workplans/issue-core-WP-NNNN-.md ← write this first +workplans/ISSUE-WP-NNNN-.md ← write this first ``` Then register in the hub: ``` @@ -28,7 +28,7 @@ create_task(workstream_id="", title="...", priority="high|medium|low") **Step 5 — Record the setup** ``` add_progress_event( - summary="First session: structured custodian into N workstreams, M tasks", + summary="First session: structured infotech into N workstreams, M tasks", event_type="milestone", topic_id="cee7bedf-2b48-46ef-8601-006474f2ad7a", detail={"workstreams": [...], "tasks_created": M} diff --git a/.claude/rules/repo-identity.md b/.claude/rules/repo-identity.md index d9d5634..f2c71e2 100644 --- a/.claude/rules/repo-identity.md +++ b/.claude/rules/repo-identity.md @@ -1,5 +1,5 @@ **Purpose:** Authoritative task lifecycle manager for the Coulomb org. Backend-agnostic CLI + REST ingestion endpoint for tasks from activity-core's IssueSink. Pluggable backends (Gitea, SQLite, GitHub). Renamed from issue-facade on 2026-05-17. -**Domain:** custodian +**Domain:** infotech **Repo slug:** issue-core **Topic ID:** cee7bedf-2b48-46ef-8601-006474f2ad7a diff --git a/.claude/rules/session-protocol.md b/.claude/rules/session-protocol.md index 52eb3be..e29acbd 100644 --- a/.claude/rules/session-protocol.md +++ b/.claude/rules/session-protocol.md @@ -1,6 +1,7 @@ ## Session Protocol -State Hub: http://127.0.0.1:8000 +Dev Hub (State Hub API): http://127.0.0.1:8000 +MCP server name in `~/.claude.json`: `dev-hub` **Step 1 — Orient** @@ -10,7 +11,7 @@ cat .custodian-brief.md ``` Then call the MCP tool for richer cross-domain context when MCP tools are exposed: ``` -get_domain_summary("custodian") +get_domain_summary("infotech") ``` If MCP tools are unavailable in the current agent session, use the REST API: ```bash @@ -39,11 +40,11 @@ curl -s -X PATCH "http://127.0.0.1:8000/messages//read" \ ls workplans/ ``` For each file with `status: ready`, `active`, or `blocked`, note pending -`todo`/`in_progress` tasks. +`wait`/`todo`/`progress` tasks. **Step 4 — Present brief** -1. **Active workstreams** for `custodian` — title, task counts, blocking decisions +1. **Active workstreams** for `infotech` — title, task counts, blocking decisions 2. **Pending tasks** from `workplans/` + any `[repo:issue-core]` hub tasks 3. **Goal guidance** — if `goal_guidance` in summary: - `needs_workplan`: surface as top action — *"Repo goal '{title}' has no workplan yet"* diff --git a/.claude/rules/workplan-convention.md b/.claude/rules/workplan-convention.md index 14ca3e5..651b567 100644 --- a/.claude/rules/workplan-convention.md +++ b/.claude/rules/workplan-convention.md @@ -1,7 +1,7 @@ ## Workplan Convention (ADR-001) -File location: `workplans/issue-core-WP-NNNN-.md` -ID prefix: `ISSUE-WP` +File location: `workplans/ISSUE-WP-NNNN-.md` +ID prefix: `ISSUE-WP-` Work items originate as files in this repo **before** being registered in the hub. @@ -12,7 +12,7 @@ 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-issue-core-WP-NNNN-.md`. The frontmatter id remains +prefix: `YYMMDD-ISSUE-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**: @@ -25,4 +25,16 @@ Ecosystem todos from other agents arrive as `[repo:issue-core]` 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: ISSUE-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 8ef5289..d2ca6a4 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -4,7 +4,7 @@ **Purpose:** Authoritative task lifecycle manager for the Coulomb org. Backend-agnostic CLI + REST ingestion endpoint for tasks from activity-core's IssueSink. Pluggable backends (Gitea, SQLite, GitHub). Renamed from issue-facade on 2026-05-17. -**Domain:** custodian +**Domain:** infotech **Repo slug:** issue-core **Topic ID:** `cee7bedf-2b48-46ef-8601-006474f2ad7a` **Workplan prefix:** `ISSUE-WP-` @@ -63,8 +63,8 @@ Omit `workstream_id` / `task_id` when not applicable. ```bash curl -s -X PATCH "http://127.0.0.1:8000/tasks/" \ -H "Content-Type: application/json" \ - -d '{"status": "in_progress"}' -# values: todo | in_progress | done | blocked + -d '{"status": "progress"}' +# values: wait | todo | progress | done | cancel ``` ### Flag a task for human review @@ -83,7 +83,7 @@ curl -s -X PATCH "http://127.0.0.1:8000/tasks/" \ 1. `cat .custodian-brief.md` — domain goal and open workstreams (offline-safe) 2. Check inbox: `GET /messages/?to_agent=issue-core&unread_only=true`; mark read 3. Scan workplans: `ls workplans/` — note `status: ready`, `active`, or `blocked` files and open tasks -4. Check blocked tasks: `GET /tasks/?needs_human=true` +4. Check human-needed tasks: `GET /tasks/?needs_human=true` **During work:** - Update task statuses in workplan files as tasks progress @@ -151,31 +151,10 @@ 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` ---- -## REST ingestion API key - -`POST /issues/` requires a shared key in `ISSUE_CORE_API_KEY`. The server -refuses to start without it. activity-core's `IssueCoreRestSink` sends the same -value as `Authorization: Bearer ` (also accepts `X-API-Key`). - -**Do not request this key from ops-warden** — pair env vars locally or via -OpenBao/K8s on both repos. Routing lookup: -`warden route show activity-core-issue-sink --json`. - -**Local dev:** - -```bash -export ISSUE_CORE_API_KEY="$(python3 -c 'import secrets; print(secrets.token_urlsafe(32))')" -issue serve --host 127.0.0.1 --port 8765 -``` - -Set the same `ISSUE_CORE_API_KEY` in activity-core when `ISSUE_SINK_TYPE=rest`. -For local ingest smoke, set `default: local` in `~/.config/issue-tracker/backends.json` -— a remote Gitea default backend will hang on `POST /issues/`. - -See `README.md` (REST Ingestion Server) and activity-core -`docs/issue-core-emission-boundary.md`. + + --- @@ -202,7 +181,7 @@ anything needing analysis, design, approval, dependencies, or multiple phases. id: ISSUE-WP-NNNN type: workplan title: "..." -domain: custodian +domain: infotech repo: issue-core status: proposed | ready | active | blocked | backlog | finished | archived owner: codex @@ -224,7 +203,7 @@ derived health labels, not frontmatter statuses. ` ` `task id: ISSUE-WP-NNNN-T01 -status: todo | in_progress | done | blocked +status: wait | todo | progress | done | cancel priority: high | medium | low state_hub_task_id: "" # written by fix-consistency — do not edit ` ` ` @@ -232,7 +211,7 @@ state_hub_task_id: "" # written by fix-consistency — do not edit Task description text. ``` -Status progression: `todo` → `in_progress` → `done` (or `blocked`) +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 diff --git a/workplans/ISSC-WP-0001-rename-and-task-ingestion.md b/workplans/ISSC-WP-0001-rename-and-task-ingestion.md index b9642ff..8a99fa4 100644 --- a/workplans/ISSC-WP-0001-rename-and-task-ingestion.md +++ b/workplans/ISSC-WP-0001-rename-and-task-ingestion.md @@ -1,7 +1,7 @@ --- id: ISSC-WP-0001 type: workplan -domain: custodian +domain: infotech repo: issue-core status: done state_hub_workstream_id: 1135fc1d-1f46-4e35-886d-04cc3b8050b6 diff --git a/workplans/ISSUE-WP-0002-gitea-pypi-publication.md b/workplans/ISSUE-WP-0002-gitea-pypi-publication.md index 83c6854..9df25eb 100644 --- a/workplans/ISSUE-WP-0002-gitea-pypi-publication.md +++ b/workplans/ISSUE-WP-0002-gitea-pypi-publication.md @@ -2,7 +2,7 @@ id: ISSUE-WP-0002 type: workplan title: "Publish issue-core to Gitea PyPI" -domain: custodian +domain: infotech repo: issue-core status: finished owner: codex diff --git a/workplans/ISSUE-WP-0003-railiance01-deployment.md b/workplans/ISSUE-WP-0003-railiance01-deployment.md index 2da2476..ec4dfd6 100644 --- a/workplans/ISSUE-WP-0003-railiance01-deployment.md +++ b/workplans/ISSUE-WP-0003-railiance01-deployment.md @@ -2,7 +2,7 @@ id: ISSUE-WP-0003 type: workplan title: "Deploy issue-core as a service on railiance01 (ArgoCD GitOps pilot)" -domain: custodian +domain: infotech repo: issue-core status: active owner: claude @@ -136,7 +136,7 @@ workload manifests into the layout platform defines. ```task id: ISSUE-WP-0003-T03 -status: in_progress +status: progress priority: high state_hub_task_id: "38887dd6-0988-4ad1-bc6b-2a1b8839829f" ``` @@ -176,7 +176,7 @@ state_hub_task_id: "ad52527f-6222-4c11-9284-d8a3ed3b49ad" ```task id: ISSUE-WP-0003-T05 -status: in_progress +status: progress priority: medium state_hub_task_id: "10923f1e-050d-4f3e-980e-b061fef5f33a" ```