Cleanup of documentation

state-hub/policies/repo-doi.md

@@ -16,7 +16,9 @@ These are the minimum requirements for the state-hub to be aware of a repo.
   `GET /repos/{slug}`
 
 - [ ] **Domain assigned** — repo is linked to an active domain. The domain must
-  exist in `domains` and be in `active` status.
+  exist in `domains` and be in `active` status. Domain status is still a
+  simple administrative label; workstream/task lifecycle labels are now treated
+  as task-flow workstations.
 
 - [ ] **Local path resolves** — `_resolve_repo_path()` finds an existing
   directory on the current host (either via `host_paths[hostname]` or
@@ -43,6 +45,9 @@ A repo at this tier participates in state-hub tracking and tooling.
 - [ ] **Workplan convention followed** — any workplans live under
   `workplans/<ID>-<slug>.md` with valid YAML frontmatter
   (`id`, `type`, `title`, `domain`, `status`, `state_hub_workstream_id`).
+  The frontmatter `status` is the file-backed source for the workstream's
+  stored workstation label. Derived blocked state and blocking reasons come
+  from the task-flow engine, not from the frontmatter alone.
   Verified by: `make check-consistency REPO={slug}` → PASS or WARN only
   (no FAIL).
 
@@ -118,3 +123,8 @@ A fully integrated repo contributes to cross-repo planning and capability routin
 - A repo may satisfy **Standard** without **Full** indefinitely — Full
   integration is appropriate when the repo is actively contributing to
   cross-domain work or exposing capabilities to other repos.
+- For lifecycle inspection, prefer `get_flow_state(entity_type, entity_id)` and
+  `advance_workstation(entity_type, entity_id, target_workstation)` over
+  reasoning from stored status labels alone. Stored labels remain important for
+  filtering and compatibility, but DoI health should use structured flow
+  results when blocking assertions matter.