Skip to content

docs: add control tower ecosystem references #18

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
pramodbn27 merged 2 commits into from
Aug 15, 2026
+14 −4
Merged

docs: add control tower ecosystem references #18

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
cfc3fee
docs: add control tower ecosystem references
pramodbn27 Aug 15, 2026
ecb55e9
docs: use portable org profile references
pramodbn27 Aug 15, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 7 additions & 3 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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`

Expand Down Expand Up @@ -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`.

Expand All @@ -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`
3 changes: 2 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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`
Expand Down
5 changes: 5 additions & 0 deletions ROADMAP.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:

Expand Down