diff --git a/AGENTS.md b/AGENTS.md
index 048b50b..4a95c5a 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -24,8 +24,8 @@ impact before those issues appear in production.
   `ai-operations-spec`
 - General observability, profiling, or evaluation workflows — those belong in
   `agenticlens`
-- Agent-governance or pre-action intervention logic — that belongs in
-  `agentic-sidecar`
+- Agent supervision/governance or pre-action intervention logic — that belongs
+  in `agentic-sidecar`
 - A broad orchestration or control-plane surface — that belongs in
   `deep-agentic-core-mcp`
 
@@ -120,6 +120,9 @@ toward reproducible resilience evidence, not just ad hoc fault injection.
   usage text, or test fixtures that demonstrate expected usage.
 - When a roadmap item or milestone meaningfully changes status, update
   `README.md` and the roadmap document in the same change.
+- If that milestone or release changes the public ecosystem story, also update
+  the shared org-profile docs in the `.github` repository:
+  `profile/README.md` and, when relevant, `profile/ROADMAP.md`.
 - When work is packaged as a release-ready change, also update
   `pyproject.toml`, `src/agentic_chaos/__init__.py`, and `CHANGELOG.md`.
 
@@ -143,5 +146,6 @@ uv run pytest
 
 1. Bump version in `pyproject.toml`, `src/agentic_chaos/__init__.py`, and `CHANGELOG.md`
 2. Commit: `git commit -am "release: vX.Y.Z"`
-3. Tag: `git tag vX.Y.Z`
+3. Tag: create an annotated `vX.Y.Z` tag and use the latest `CHANGELOG.md`
+   release section as the tag description
 4. Push: `git push origin main --tags`
diff --git a/README.md b/README.md
index 13d0df8..d157cc4 100644
--- a/README.md
+++ b/README.md
@@ -11,7 +11,8 @@ Within the broader DeepAgentLabs architecture, Agentic Chaos is the resilience
 and failure-validation reference implementation for the **AI Operations
 Workflow Specification**. It injects, validates, tests, and proves resilience,
 while keeping its workflow artifacts compatible with the same shared
-operational model used by AgenticLens and the MCP layer.
+operational model used by AgenticLens, the MCP layer, and the future
+Control Tower control plane.
 
 If you also use AgenticLens, an optional integration lets you merge chaos
 events straight into an AgenticLens `Workflow`, so `agenticlens analyze`
diff --git a/ROADMAP.md b/ROADMAP.md
index 64d110c..666334d 100644
--- a/ROADMAP.md
+++ b/ROADMAP.md
@@ -28,6 +28,11 @@ validated against sibling projects before they are considered complete.
 - `deep-agentic-core-mcp`
   Exposes chaos capabilities to hosts and is a useful end-to-end check for
   user-facing experiment orchestration.
+- `agenticops-control-tower`
+  Coordinate with: once Control Tower ships real registry, inventory, and
+  operations surfaces, chaos status, experiment inventory, and resilience
+  posture should be representable there without moving chaos execution logic
+  out of this package.
 
 For roadmap planning, treat ecosystem links as: