docs: realign WP-0029 and boundaries with canon and nexus owners

Review ACTIVITY-WP-0029 against info-tech-canon, policy-nexus, and
State Hub retirement: activity-core keeps schedule and ops_run;
repo-manager owns consistency; hub-core owns progress ports.
Mark WP-0026 finished. Refresh INTENT, SCOPE, and repo-boundary.

INTENT.md

@@ -1,7 +1,7 @@
 ---
 domain: capabilities
 repo: activity-core
-updated: "2026-07-21"
+updated: "2026-08-18"
 ---
 
 # INTENT
@@ -78,17 +78,28 @@ It is an event loop governed by declarative rules and LLM instructions:
 
 | Concern | Owner |
 |---|---|
-| Task lifecycle (create, assign, track, close) | issue-core / work-record connectors (not default for internal findings) |
-| Project and initiative management | project-core (future) |
+| Task / work-item *semantics* (Task, Commitment, TaskState) | info-tech-canon (Task Model) |
+| Who may act, who is responsible / accountable | info-tech-canon (Organization Model) |
+| Policy *content* (canon, ADRs) | Owning repo; local files are source of truth |
+| Policy *publication* (stable URLs, currency) | policy-nexus |
+| Regulatory intake / interpretation | risk-nexus |
+| Task lifecycle (assign, track, close) | issue-core / work-record connectors (not default for internal findings) |
+| Repo registry, file↔index consistency, work-record index | repo-manager |
+| Messages, progress projections, hub ports | hub-core (surviving runtime; core-hub absorbed via CORE-WP-0010) |
+| Mixed coordination read model (until retirement) | state-hub (STATE-WP-0079 strangler; not a permanent peer) |
+| Project and initiative management | `prj-*` repos + GOAL.md |
 | Repository capability profiling | repo-scoping |
-| Cross-domain coordination state | state hub |
-| Execution of automatable tasks | Temporal workers (per-repo) |
+| Execution of domain work | per-repo workers / rein-aharness claiming ops_runs |
 | Event broker infrastructure | NATS (org infrastructure) |
 
-activity-core does not compete with the state hub — it extends it. The state
-hub is a read model of what is and has been; activity-core is the automation
-layer that reacts to that state and creates new work. The state hub delegates
-maintenance automation to activity-core by publishing lifecycle events on NATS.
+activity-core does not compete with those owners. It **schedules and evaluates**;
+it reads org context and emits work or evidence into the owner that already has
+that responsibility. State Hub is a compatibility read model on the way out
+(`prj-state-hub-retirement`), not the permanent place coordination state lives.
+
+Layout orientation for this repo itself follows the InfoTechCanon Repository
+Layout recommendation (`INTENT` vs `SCOPE`, work in `workplans/`). Policy that
+governs other repos is not published from here.
 
 ---