From 9c2c7f15b9dc678c4966cf2e39b78f22d7a15f48 Mon Sep 17 00:00:00 2001 From: PRAMOD B N Date: Fri, 14 Aug 2026 23:27:39 -0500 Subject: [PATCH 1/2] docs: align sidecar ecosystem positioning --- AGENTS.md | 9 ++++++++- README.md | 1 + ROADMAP.md | 6 ++++++ 3 files changed, 15 insertions(+), 1 deletion(-) diff --git a/AGENTS.md b/AGENTS.md index 7ba977c..3f299ca 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -9,6 +9,9 @@ alongside an autonomous agent runtime and evaluates whether the next action is still aligned with user intent, policy, risk tolerance, and escalation rules before the action is allowed to proceed. +At the ecosystem-role level, the preferred keyword is **SUPERVISE**. In +practice, the package covers both supervision and governance. + ### Owns - Decision Gate behavior, policy/risk evaluation, and intent-preservation @@ -167,6 +170,9 @@ Full architecture and build order: [ROADMAP.md](ROADMAP.md). `examples/`. - When a roadmap item or milestone meaningfully changes status, update `README.md` and `ROADMAP.md` in the same change. +- If that milestone or release changes the public ecosystem story, also update + `/home/pramodbn27/PyPi Projects/.github/profile/README.md` and, when + relevant, `/home/pramodbn27/PyPi Projects/.github/profile/ROADMAP.md`. - When work is packaged as a release-ready change, also update `pyproject.toml`, `src/agentic_sidecar/__init__.py`, and `CHANGELOG.md`. @@ -178,7 +184,8 @@ Run `make check` before every push. It runs: lint → format-check → typecheck 1. Bump version in `pyproject.toml`, `src/agentic_sidecar/__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` The `release-pypi.yml` workflow triggers on the tag push and publishes to diff --git a/README.md b/README.md index fe305f7..165d65b 100644 --- a/README.md +++ b/README.md @@ -392,6 +392,7 @@ even though nothing consumes it across process boundaries yet. | [AgenticLens](https://github.com/DeepAgentLabs/agenticlens) | What did the agent do, and what happened? | | [Agentic Chaos](https://github.com/DeepAgentLabs/agentic-chaos) | How does the agent behave when things go wrong? | | [Agentic MCP](https://github.com/DeepAgentLabs/mcp-server) | How does the agent interact with tools and external capabilities? | +| [AgenticOps Control Tower](https://github.com/DeepAgentLabs/agenticops-control-tower) | What is deployed, what governance posture exists across agents, and how do operators manage it centrally? | | **Agentic Sidecar** | Should the agent continue with this decision, and is it still acting according to intent? | Each project is independently installable; none requires another as a hard diff --git a/ROADMAP.md b/ROADMAP.md index e413ce9..d495424 100644 --- a/ROADMAP.md +++ b/ROADMAP.md @@ -163,6 +163,12 @@ optional integration surface only, never a coordinated release). Validate in: MCP tool calls are a natural decision boundary ([`concept.md` §28](concept.md)). A useful end-to-end check once v0.1's Decision Gate exists is gating a real MCP tool call through it. +- `agenticops-control-tower` + Coordinate with: Control Tower is the future operator-facing layer above the + ecosystem. Once Sidecar emits stable runtime status and decision artifacts, + Control Tower should be able to summarize governance posture, intervention + counts, and escalation state centrally without taking ownership of the + Sidecar runtime. For roadmap planning, treat ecosystem links as: From ad2652faeba7b13bb8c700f032b1478e5aca2b32 Mon Sep 17 00:00:00 2001 From: PRAMOD B N Date: Fri, 14 Aug 2026 23:40:33 -0500 Subject: [PATCH 2/2] docs: use portable org profile references --- AGENTS.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 3f299ca..8b0e249 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -171,8 +171,8 @@ Full architecture and build order: [ROADMAP.md](ROADMAP.md). - When a roadmap item or milestone meaningfully changes status, update `README.md` and `ROADMAP.md` in the same change. - If that milestone or release changes the public ecosystem story, also update - `/home/pramodbn27/PyPi Projects/.github/profile/README.md` and, when - relevant, `/home/pramodbn27/PyPi Projects/.github/profile/ROADMAP.md`. + 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_sidecar/__init__.py`, and `CHANGELOG.md`.