Document repository intent and bootstrap Statehub registration

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a101af-e240-7882-a1e3-e37720cbdbea

.custodian-brief.md

@@ -0,0 +1,27 @@
+<!-- custodian-brief: generated by statehub register; fix-consistency may replace this file -->
+# Custodian Brief - emergent-security
+
+**Project:** emergent-security
+**Domain:** communication
+**State Hub:** http://127.0.0.1:8000
+**Topic ID:** `a6c6e745-bf54-4465-9340-1534a2be493e`
+
+## Open Workplans
+
+### Bootstrap State Hub integration
+
+Workplan file: `workplans/EMERGENT-WP-0001-statehub-bootstrap.md`
+
+Open tasks:
+- T01 - Review generated integration files
+- T02 - Verify local developer workflow
+- T03 - Seed first real workplan
+
+## Session Start
+
+1. Read `INTENT.md`, `SCOPE.md`, and `AGENTS.md`.
+2. Check inbox: `GET /messages/?to_agent=emergent-security&unread_only=true`.
+3. Scan `workplans/`.
+4. Update task statuses in workplan files as work progresses.
+
+Last generated: 2026-10-03

.gitignore

@@ -1,3 +1,9 @@
 __pycache__/
 .pytest_cache/
 *.egg-info/
+
+# state-hub: track .claude/rules
+# Claude Code local state (track shared rules; ignore machine-specific files)
+.claude/*
+!.claude/rules/
+!.claude/rules/*.md

AGENTS.md

@@ -0,0 +1,210 @@
+# emergent-security — Agent Instructions
+
+## Repo Identity
+
+**Purpose:** Security governance canon, policy envelopes, and deterministic reference decisions for bounded agent autonomy.
+
+**Domain:** communication
+**Repo slug:** emergent-security
+**Topic ID:** `a6c6e745-bf54-4465-9340-1534a2be493e`
+**Workplan prefix:** `EMERGENT-WP-`
+
+---
+
+## State Hub Integration
+
+The Custodian State Hub tracks work across all domains. Codex uses HTTP REST and
+the `statehub` CLI by default. MCP is opt-in because the current Codex MCP bridge
+adds severe call latency; the full administrative MCP surface remains available
+to clients that need it.
+
+| Context | URL |
+|---------|-----|
+| Local workstation | `http://127.0.0.1:8000` |
+| Remote via tunnel | `http://127.0.0.1:18000` |
+| Optional local edge relay | http://127.0.0.1:18080 |
+
+When an operator has enabled the edge relay, set API_BASE to the relay URL.
+Queueable writes return an explicit queued receipt if the central hub is
+unreachable. Treat that as pending local evidence, then ask the operator to run
+statehub outbox status/replay after connectivity returns.
+
+Codex workspace-write sandboxes need network access enabled to reach the host's
+loopback listener. Bootstrap this once with `make -C ~/state-hub configure-codex`
+and restart Codex. The canonical REST health endpoint is `/state/health`, not
+`/health`. If a sandboxed loopback probe fails, retry it with escalated execution
+before declaring State Hub unavailable; a managed Codex permission profile may
+still enforce isolated networking. Experimental MCP can be enabled explicitly
+with `make -C ~/state-hub configure-codex WITH_MCP=1`.
+
+### Orient at session start
+
+```bash
+# Offline brief — works without hub connection
+cat .custodian-brief.md
+
+# Active workplans for this domain
+curl -s "http://127.0.0.1:8000/workplans/?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=emergent-security&unread_only=true" \
+  | python3 -m json.tool
+```
+
+Mark a message read:
+```bash
+curl -s -X PATCH "http://127.0.0.1:8000/messages/<id>/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",
+    "workplan_id": "<uuid>",
+    "task_id": "<uuid>"
+  }'
+```
+
+Omit `workplan_id` / `task_id` when not applicable.
+
+### Update task status
+
+```bash
+curl -s -X PATCH "http://127.0.0.1:8000/tasks/<task_id>" \
+  -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/<task_id>" \
+  -H "Content-Type: application/json" \
+  -d '{"needs_human": true, "intervention_note": "reason"}'
+```
+
+---
+
+## Session Protocol
+
+**Start:**
+1. `cat .custodian-brief.md` — domain goal and open workplans (offline-safe)
+2. Check inbox: `GET /messages/?to_agent=emergent-security&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. If finishing a workplan: hand off **residuals** as live work records first
+   (intake with `origin: residual` + `origin_ref: <WP-id>`, or a next workplan /
+   decision / engagement). Do not park leftovers only in prose or `SCOPE.md`.
+   Canon: `the-custodian/canon/standards/work-record-types_v0.1.md` § Residuals.
+3. Log: `POST /progress/` with a summary of what changed (name handoff ids)
+4. After workplan file changes, run:
+   ```bash
+   uv run --project ~/repo-manager rmgr sync --path . --push
+   ```
+   This assigns only missing deterministic identifiers, verifies the pushed
+   Forgejo commit and `primary/railliance01`, then requests one central
+   reconciliation. A queued receipt is pending evidence; rerun after
+   connectivity returns. Use `statehub fix-consistency` for a separate deep audit.
+
+---
+
+<!-- REPO-AGENTS-EXTENSIONS -->
+<!-- Append repo-specific agent instructions below this marker.
+     The state-hub template sync preserves content after this line. -->
+
+## Local Verification
+
+Requires Python 3.11 or newer. Install with `pip install -e '.[test]'` and run
+`python3 -m pytest -q`. Policy changes start with a failing decision fixture;
+keep the canon, agent extract, YAML envelopes, and A6 class coverage aligned.
+There is currently no dedicated lint command or running service in this repo.
+
+---
+
+## 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/EMERGENT-WP-NNNN-<slug>.md`
+
+**Archived location:** finished workplans may move to
+`workplans/archived/YYMMDD-EMERGENT-WP-NNNN-<slug>.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`, workplan id
+`EMERGENT-WP-ADHOC-YYYY-MM-DD`, and task ids
+`EMERGENT-WP-ADHOC-YYYY-MM-DD-T01`, etc. `EMERGENT-WP` includes its final `-WP`
+token. Unqualified historic `ADHOC-*` ids are grandfathered and must not be
+copied into new records. 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: EMERGENT-WP-NNNN
+type: workplan
+title: "..."
+domain: communication
+repo: emergent-security
+status: proposed | ready | active | blocked | backlog | finished | archived
+owner: codex
+topic_slug: ...
+created: "YYYY-MM-DD"
+updated: "YYYY-MM-DD"
+state_hub_workstream_id: "<uuid>"   # deterministic UUIDv5; managed by Repo Manager
+---
+```
+
+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.
+
+**Terminology:** workplan is the fleet term; `workstream` appears only in legacy
+API/MCP/frontmatter bridges until `STATE-WP-0069` retires them — see
+`the-custodian/canon/standards/workplan-terminology-fleet_v0.1.md`.
+
+**Task block format** (one per `##` section):
+
+```
+## Task Title
+
+` ` `task
+id: EMERGENT-WP-NNNN-T01
+status: wait | todo | progress | done | cancel
+priority: high | medium | low
+state_hub_task_id: "<uuid>"         # deterministic UUIDv5; managed by Repo Manager
+` ` `
+
+Task description text.
+```
+
+Status progression: `todo` → `progress` → `done`; use `wait` for waiting/blocked work and `cancel` for stopped work.
+
+**Residuals when finishing:** actionable leftovers become live work records
+before `status: finished` — usually an intake (`origin: residual`,
+`origin_ref: EMERGENT-WP-NNNN`) or a spawned workplan. Residual is a *role*,
+not a kind. Fleet list lives on State Hub, not in `SCOPE.md`.
+
+To create a new workplan:
+1. Write the file following the format above
+2. Run `uv run --project ~/repo-manager rmgr sync --path . --push`.
+3. Run `statehub fix-consistency` only when a separate deep audit is needed.

INTENT.md

@@ -0,0 +1,75 @@
+# Emergent Security — Intent
+
+Coordination domain: `netkingdom`.
+Statehub placement: domain `communication`, topic `netkingdom`.
+
+Enable maximum local autonomy consistent with the guarantees actually owed.
+Delegate understood decisions into explicit, testable risk envelopes; escalate
+unresolved decisions without expanding privilege; keep platform-root under human
+control. As evidence and decision maturity grow, routine work should need fewer
+manual approvals without weakening security or tenant guarantees.
+
+## Purpose and audience
+
+Provide the security governance canon and executable policy reference for coding
+agents, repository and domain maintainers, and platform and tenant governance
+owners. Make it clear who may decide which effects, within what scope and risk,
+with which evidence, and where an unresolved decision must go.
+
+## Repository scope
+
+- Maintain the versioned architectural canon in `specs/emergent-security-0.8.md`
+  and its self-contained agent extract in `emergent-security-agent.md`.
+- Express the default delegation envelope, ordinal risk scales, and illustrative
+  platform and tenant governance envelopes as reviewable YAML policy data.
+- Provide a small, pure Python reference decision function that evaluates scope,
+  prohibitions, root requirements, delegations, tenant bounds, negative memory,
+  evidence, risk, and reserved human decisions in a defined order.
+- Preserve executable fixtures for autonomous decisions, obligations, denials,
+  escalations, root authorization requirements, and tenant governance validation.
+
+The current implementation is a reference library and policy fixture suite. The
+canon also describes future integration seams for intent storage, delegation
+registries, credential brokering, enforcement, observation, and audit; this
+repository does not currently implement those operational services.
+
+## Constraints to preserve
+
+- Identity, available credentials, readable context, and successful precedent do
+  not confer authority. Agents cannot authorize their own privilege expansion.
+- Deterministic systems decide and enforce effects. Models may reason and
+  propose, but are not security boundaries. The reference decision function stays
+  deterministic, free of side effects, and independent of model calls.
+- Applicable prohibitions prevail over grants. Platform-root produces
+  `ROOT_AUTHORIZATION_REQUIRED`; it is never autonomously granted or activated.
+- The default autonomous envelope applies only to L0 agents on explicit human
+  tasks in a HOT build estate outside tenants. Other scopes require explicit
+  delegation; constitutional restrictions continue to apply everywhere.
+- Tenant governance may only narrow the platform tenant envelope. Exceeding the
+  platform envelope routes to the platform; tenant-reserved human decisions
+  cannot be silently approved by automation or timeout.
+- Missing scope, delegation, evidence, or acceptable risk produces an explained
+  escalation. Unclassified or unknown risk values fail safe. Applicable negative
+  memory blocks routine autonomy until resolved.
+- Privilege is scoped and leased, decisions remain attributable, and evidence of
+  authority use must survive that authority. Learning proposes policy changes;
+  it does not grant permissions.
+
+## Evolution and success
+
+Keep policy, canon, agent guidance, and fixtures aligned. Start policy changes
+with a failing decision fixture, change policy data where possible, and change
+the evaluator when the intended semantics require it. Preserve deterministic
+results, unmodified inputs, registry-order independence, and tenant narrowing
+invariants.
+
+Harden a zone when real consumers, data, contracts, or recovery costs require
+guarantees. Revisit structure through explicit, bounded governance when it
+creates needless friction; temperature changes never relax the constitution or
+parent guarantees.
+
+Success means more routine decisions resolved safely at the lowest sufficient
+scope, fewer repeated escalations and root interventions, less standing
+privilege, and clear evidence for every decision. This intent describes the
+repository's purpose; it does not itself grant operational authority or replace
+the canon and applicable delegation envelopes.

SCOPE.md

@@ -0,0 +1,32 @@
+# SCOPE
+
+> This file was generated by `statehub register`. Refine it as the repository
+> boundaries become clearer.
+
+## One-liner
+
+Security governance canon, policy envelopes, and deterministic reference decisions for bounded agent autonomy.
+
+## Core Idea
+
+emergent-security exists to provide the capability described in INTENT.md.
+
+## In Scope
+
+- Maintain the repository's primary implementation.
+- Keep docs, tests, and operational metadata current.
+
+## Out of Scope
+
+- Own unrelated adjacent systems.
+- Make irreversible operational decisions without human approval.
+
+## Current State
+
+- Status: active; implementation and stability should be verified by the repo agent.
+
+## Getting Oriented
+
+- Start with: INTENT.md
+- Agent instructions: AGENTS.md
+- Workplans: workplans/

workplans/EMERGENT-WP-0001-statehub-bootstrap.md

@@ -0,0 +1,55 @@
+---
+id: EMERGENT-WP-0001
+type: workplan
+title: "Bootstrap State Hub integration"
+domain: communication
+repo: emergent-security
+status: ready
+owner: codex
+topic_slug: netkingdom
+created: "2026-10-03"
+updated: "2026-10-03"
+---
+
+# Bootstrap State Hub integration
+
+Security governance canon, policy envelopes, and deterministic reference decisions for bounded agent autonomy.
+
+## Review Generated Integration Files
+
+```task
+id: EMERGENT-WP-0001-T01
+status: todo
+priority: high
+```
+
+Review `INTENT.md`, `SCOPE.md`, `AGENTS.md`, and `.custodian-brief.md`.
+Replace generated placeholders with repo-specific facts where needed.
+
+## Verify Local Developer Workflow
+
+```task
+id: EMERGENT-WP-0001-T02
+status: todo
+priority: high
+```
+
+Identify the repo's install, test, lint, build, and run commands. Add or refine
+those commands in the agent instructions so future coding sessions can verify
+changes confidently.
+
+## Seed First Real Workplan
+
+```task
+id: EMERGENT-WP-0001-T03
+status: todo
+priority: medium
+```
+
+Create the first implementation workplan for the repository's most important
+next change. After workplan file updates, run the sync locally from this repo
+checkout:
+
+```bash
+statehub fix-consistency
+```