diff --git a/.claude/rules/first-session.md b/.claude/rules/first-session.md index 605d1f7..8880968 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("helix_forge")` 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/helix_forge/project_charter_v0.1.md` — purpose, scope -- `~/the-custodian/canon/projects/helix_forge/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/helix-forge-WP-NNNN-.md ← write this first +workplans/HF-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 helix_forge into N workstreams, M tasks", + summary="First session: structured infotech into N workstreams, M tasks", event_type="milestone", topic_id="f39fa2a3-c491-414c-a91b-b4c5fcc6139c", detail={"workstreams": [...], "tasks_created": M} diff --git a/.claude/rules/repo-identity.md b/.claude/rules/repo-identity.md index 4fa6442..c5af125 100644 --- a/.claude/rules/repo-identity.md +++ b/.claude/rules/repo-identity.md @@ -1,5 +1,5 @@ **Purpose:** Capability-first development ecosystem for evolving reusable software capabilities from natural-language intent through architecture-aware discovery, validation, implementation, feedback, and reuse. -**Domain:** helix_forge +**Domain:** infotech **Repo slug:** helix-forge **Topic ID:** f39fa2a3-c491-414c-a91b-b4c5fcc6139c diff --git a/.claude/rules/session-protocol.md b/.claude/rules/session-protocol.md index 3e46ebd..932eb2c 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("helix_forge") +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 `helix_forge` — title, task counts, blocking decisions +1. **Active workstreams** for `infotech` — title, task counts, blocking decisions 2. **Pending tasks** from `workplans/` + any `[repo:helix-forge]` 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 94d6958..62cd3eb 100644 --- a/.claude/rules/workplan-convention.md +++ b/.claude/rules/workplan-convention.md @@ -1,7 +1,7 @@ ## Workplan Convention (ADR-001) -File location: `workplans/helix-forge-WP-NNNN-.md` -ID prefix: `HELIX-WP` +File location: `workplans/HF-WP-NNNN-.md` +ID prefix: `HF-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-helix-forge-WP-NNNN-.md`. The frontmatter id remains +prefix: `YYMMDD-HF-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:helix-forge]` 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: HF-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 2e25202..142deed 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -4,10 +4,10 @@ **Purpose:** Capability-first development ecosystem for evolving reusable software capabilities from natural-language intent through architecture-aware discovery, validation, implementation, feedback, and reuse. -**Domain:** helix_forge +**Domain:** infotech **Repo slug:** helix-forge **Topic ID:** `f39fa2a3-c491-414c-a91b-b4c5fcc6139c` -**Workplan prefix:** `HELIX-WP-` +**Workplan prefix:** `HF-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` + + + + --- ## Workplan Convention (ADR-001) @@ -176,7 +181,7 @@ anything needing analysis, design, approval, dependencies, or multiple phases. id: HELIX-WP-NNNN type: workplan title: "..." -domain: helix_forge +domain: infotech repo: helix-forge status: proposed | ready | active | blocked | backlog | finished | archived owner: codex diff --git a/workplans/HF-WP-0001-establish-ops-hub-first-extension.md b/workplans/HF-WP-0001-establish-ops-hub-first-extension.md index 662c8fc..5c68185 100644 --- a/workplans/HF-WP-0001-establish-ops-hub-first-extension.md +++ b/workplans/HF-WP-0001-establish-ops-hub-first-extension.md @@ -2,7 +2,8 @@ id: HF-WP-0001 type: workplan title: "Establish ops-hub as the First VSM Inter-Hub Extension" -domain: helix_forge +domain: infotech +topic_slug: helix-forge repo: helix-forge status: finished owner: worsch diff --git a/workplans/HF-WP-0002-openbao-browser-ui-at-bao-coulomb-social.md b/workplans/HF-WP-0002-openbao-browser-ui-at-bao-coulomb-social.md index fa4fd34..8fbd157 100644 --- a/workplans/HF-WP-0002-openbao-browser-ui-at-bao-coulomb-social.md +++ b/workplans/HF-WP-0002-openbao-browser-ui-at-bao-coulomb-social.md @@ -2,11 +2,11 @@ id: HF-WP-0002 type: workplan title: "Expose OpenBao Browser UI at bao.coulomb.social" -domain: helix_forge +domain: infotech repo: helix-forge status: finished owner: codex -topic_slug: openbao-browser-ui +topic_slug: helix-forge created: "2026-06-15" updated: "2026-06-19" planning_priority: high diff --git a/workplans/HF-WP-0003-openbao-keycape-login-overlay.md b/workplans/HF-WP-0003-openbao-keycape-login-overlay.md index 9d17572..61b5bdc 100644 --- a/workplans/HF-WP-0003-openbao-keycape-login-overlay.md +++ b/workplans/HF-WP-0003-openbao-keycape-login-overlay.md @@ -2,11 +2,11 @@ id: HF-WP-0003 type: workplan title: "Streamline OpenBao login screen for KeyCape sign-in" -domain: helix_forge +domain: infotech repo: helix-forge status: finished owner: codex -topic_slug: openbao-keycape-login-overlay +topic_slug: helix-forge created: "2026-06-19" updated: "2026-06-19" planning_priority: medium