Skip to content

v1.0.0 docs: post-v1.0 staleness sweep (3 stragglers) #335

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
dep0we merged 1 commit into from
Jun 5, 2026
Merged

v1.0.0 docs: post-v1.0 staleness sweep (3 stragglers) #335

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 4 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,6 +49,10 @@ CHANGELOG entry.

## [Unreleased]

### Documentation

- Post-v1.0 staleness sweep: `ROADMAP.md`, `docs/deployment/programmatic.md`, and `docs/spec/31-llm-backend.md` updated to reflect the v1.0 release (twelfth backend protocol shipped, MCPServerRegistryBackend added to lists, status copy flipped from future-tense to PyPI-install present-tense, spec/31 status line refreshed from "v0.13 era" to "v1.0"). Closes the three stragglers an audit found after the PR #334 v1.0 release sweep.

## [1.0.0] - 2026-06-04

### Added
Expand Down
8 changes: 4 additions & 4 deletions ROADMAP.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,15 +6,15 @@ For shipped work, see [CHANGELOG.md](CHANGELOG.md). For the framework's design s

---

## v1.0 — remaining backend protocols
## v1.0 — backend protocols shipped

The framework's protocol-pattern scaling story closes at v1.0. **Eleven of twelve** backend protocols have shipped: `MemoryBackend`, `LLMBackend`, `JudgeBackend`, `LockBackend`, `LogBackend`, `AgentProfileBackend`, `ToolRegistryBackend`, `MandateBackend`, `PolicyBackend`, `PersonaBackend`, `CorpusBackend`. One remains.
The framework's protocol-pattern scaling story closed at v1.0 on 2026-06-05. **Twelve of twelve** backend protocols have shipped: `MemoryBackend`, `LLMBackend`, `JudgeBackend`, `LockBackend`, `LogBackend`, `AgentProfileBackend`, `ToolRegistryBackend`, `MandateBackend`, `PolicyBackend`, `PersonaBackend`, `CorpusBackend`, `MCPServerRegistryBackend`. All twelve have locked specs, reference implementations, and parametrized conformance suites.

| Issue | Backend | Status | What it unblocks |
|-------|---------|--------|------------------|
| [#201](https://github.com/dep0we/atomic-agents-stack/issues/201) | `MCPServerRegistryBackend` | Planned | Catalog + install/audit for MCP servers (the MCP equivalent of the ToolRegistry pattern) |
| [#201](https://github.com/dep0we/atomic-agents-stack/issues/201) | `MCPServerRegistryBackend` | Shipped (v1.0.0) | Catalog + install/audit for MCP servers (the MCP equivalent of the ToolRegistry pattern) |

**v1.0 ships when the remaining backend lands + its conformance suite pins the contract.** Same agent definitions, same `agent.call()` flow, same audit trail — different backends registered.
**v1.0.0 is live on PyPI:** `pip install atomic-agents-stack`. Same agent definitions, same `agent.call()` flow, same audit trail; different backends registered.

---

Expand Down
10 changes: 5 additions & 5 deletions docs/deployment/programmatic.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -724,15 +724,15 @@ public surface) is internal. Specifically:

The protocol pattern from
[`spec/20-memory-backend.md`](../spec/20-memory-backend.md) is the
template every backend follows. Eleven backend protocols have shipped
(`MemoryBackend`, `LLMBackend`, `JudgeBackend`, `LockBackend`,
template every backend follows. Twelve backend protocols have shipped
at v1.0 (`MemoryBackend`, `LLMBackend`, `JudgeBackend`, `LockBackend`,
`LogBackend`, `AgentProfileBackend`, `ToolRegistryBackend`,
`MandateBackend`, `PolicyBackend`, `PersonaBackend`, `CorpusBackend`);
one remains for v1.0 (`MCPServerRegistryBackend`). Each ships with a
`MandateBackend`, `PolicyBackend`, `PersonaBackend`, `CorpusBackend`,
`MCPServerRegistryBackend`). Each ships with a
filesystem reference impl, a conformance suite, an operator override
env var + constructor kwarg, a `doctor.check_<backend>` coherence
check, and a numbered spec doc (`spec/20`, `21`, `22`, `24`, `25`,
`28`, `29`, `31`, `32`, `33`, `34`). Future SaaS / Postgres / git adapters
`28`, `29`, `31`, `32`, `33`, `34`, `36`). Future SaaS / Postgres / git adapters
register via the matching `register_<backend>_backend()` entry point
without forking core.

Expand Down
2 changes: 1 addition & 1 deletion docs/spec/31-llm-backend.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# 31 — LLMBackend Protocol

**Status:** locked (spec matches implementation as of v0.13 era).
**Status:** locked (spec matches implementation as of v1.0).
**Origin:** [#87](https://github.com/dep0we/atomic-agents-stack/issues/87).
**Shipped across four PRs:** PR 1 (canonical types + Protocol contract + registry primitives), PR 2 (`AnthropicLLMBackend` + Claude dispatch routing), PR 2.5 (`agent.py` tool-dispatch refactor to canonical types), PR 3 (`OpenAICompatibleLLMBackend` + `MoonshotLLMBackend` + registry-only dispatch + `model.md` `provider:` parser).

Expand Down