ui rules established

AGENTS.md

@@ -4,7 +4,7 @@
 
 **Purpose:** Durable task factory built on Temporal. Manages ActivityDefinitions, schedules recurring workflows via Temporal Schedules, routes events via NATS JetStream, and exposes a FastAPI CRUD surface for the custodian domain.
 
-**Domain:** custodian
+**Domain:** infotech
 **Repo slug:** activity-core
 **Topic ID:** `cee7bedf-2b48-46ef-8601-006474f2ad7a`
 **Workplan prefix:** `ACTIVITY-WP-`
@@ -83,7 +83,7 @@ curl -s -X PATCH "http://127.0.0.1:8000/tasks/<task_id>" \
 1. `cat .custodian-brief.md` — domain goal and open workstreams (offline-safe)
 2. Check inbox: `GET /messages/?to_agent=activity-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,27 +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`
----
 
-## Issue-core emission (`ISSUE_SINK_TYPE=rest`)
-
-activity-core emits tasks to issue-core via `IssueCoreRestSink` (`src/activity_core/issue_sink.py`).
-
-**Do not request `ISSUE_CORE_API_KEY` from ops-warden** — ops-warden issues SSH
-certs only. For routing: `warden route show activity-core-issue-sink --json`.
-
-| Env var | Purpose |
-| --- | --- |
-| `ISSUE_CORE_URL` | issue-core base URL (default `http://127.0.0.1:8765`) |
-| `ISSUE_CORE_API_KEY` | Shared ingestion key — sent as `Authorization: Bearer` |
-| `ISSUE_SINK_TYPE` | `rest` (live POST) or `null` (dry-run; Railiance default) |
-
-**Local dev:** generate one key, export on both activity-core and issue-core
-processes. See `docs/issue-core-emission-boundary.md` and issue-core `README.md`.
-Use `default: local` in issue-core `backends.json` for local smoke.
-
-**Production:** inject the same key on both sides via OpenBao/K8s (coordinate
-`railiance-platform` when the canonical path ships).
+<!-- REPO-AGENTS-EXTENSIONS -->
+<!-- Append repo-specific agent instructions below this marker.
+     The state-hub template sync preserves content after this line. -->
 
 ---
 
@@ -198,7 +181,7 @@ anything needing analysis, design, approval, dependencies, or multiple phases.
 id: ACTIVITY-WP-NNNN
 type: workplan
 title: "..."
-domain: custodian
+domain: infotech
 repo: activity-core
 status: proposed | ready | active | blocked | backlog | finished | archived
 owner: codex
@@ -228,10 +211,7 @@ state_hub_task_id: "<uuid>"         # written by fix-consistency — do not edit
 Task description text.
 ```
 
-Status progression: `todo` → `progress` → `done`; use `wait` for a task
-blocked on external input and `cancel` for intentionally abandoned work.
-Workstream/workplan lifecycle status is separate; frontmatter `blocked` remains
-valid there.
+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