Русская версия 中文版 Contributing guide Code of Conduct
A practical book and documentation site about secure, governable, production-grade AI agent architecture.
This project is for people who want to build not demo magic, but calm, controllable, and safe agent systems that can survive contact with real users, real tools, and real operations.
Most agent tutorials optimize for fast demos. Real systems need more than clever prompting or tool calling. They need:
- explicit trust boundaries
- policy enforcement and approvals
- memory discipline
- observability and evals
- rollout control and lifecycle management
This repository exists to document that full operating model.
- a multilingual book on secure AI agent architecture
- a GitHub Pages documentation site built with
MkDocsandMaterial for MkDocs - a runnable reference runtime in
agent_runtime_ref/ - practical schemas, checklists, and operational artifacts
- a modern Python-first tooling setup based on
uv
- Vendor-neutral architecture. The book focuses on principles and operating models that outlive any single framework or model provider.
- Production reality over agent theater. It emphasizes policy, approvals, observability, evals, and lifecycle discipline.
- A runnable reference layer. The repository includes executable reference assets, not just prose.
- Read the site: https://agent-axiom.github.io/agent-arch/
- Start with the book homepage: docs/index.en.md
- Open the guided entry page: docs/start-here.en.md
- Explore the reference runtime: docs/appendix/reference-package.en.md
uv sync --group docs --group dev
uv run mkdocs serveThe local site will be available at http://127.0.0.1:8000/.
uv run ruff check .
uv run ty check
uv run pytest --cov=agent_runtime_ref --cov-report=term-missing
uv run mkdocs build --strictThe repository includes a minimal runnable skeleton package:
.venv/bin/python -m agent_runtime_refIt gives you a compact reference runtime for the book:
- runtime and policy layer
- capability catalog and approved inventory
- memory path, telemetry, approvals, and rollout checks
- lifecycle-oriented artifacts for change records, artifact bundles, and retirement plans
- YAML-driven configs for the operational skeleton
Quick examples:
.venv/bin/python -m agent_runtime_ref simulate-run
.venv/bin/python -m agent_runtime_ref inspect-agent
.venv/bin/python -m agent_runtime_ref inspect-lifecycle
.venv/bin/python -m agent_runtime_ref inspect-session
.venv/bin/python -m agent_runtime_ref export-session --output artifacts/session-demo-001.json
.venv/bin/python -m agent_runtime_ref export-eval-dataset --output artifacts/eval-dataset.jsonThe canonical walkthrough, full CLI list, and config overview live on the docs page:
If you want notebooks or data analysis tooling:
uv sync --group researchThe research group already includes marimo and polars.
The repository includes a GitHub Actions workflow for GitHub Pages:
- build with
uv - strict
mkdocs build --strict - Pages deployment from the
docs-prodbranch
actions/configure-pages@v5 has an important limitation: if Pages have never been enabled in the repository before, the default GITHUB_TOKEN may not be able to bootstrap the Pages site automatically.
There are two correct ways to handle the first setup:
- Enable Pages once in
Settings -> Pagesand chooseGitHub Actions. - Add a
PAGES_PATsecret with sufficient permissions, and the workflow can enable Pages automatically.
If the github-pages environment has deployment branch restrictions, make sure it explicitly allows deployments from docs-prod.
PAGES_PAT should be a real token, not GITHUB_TOKEN:
- for a Personal Access Token:
repoor Pages write permission - for a GitHub App:
administration:writeandpages:write
mainis the source-of-truth development branchdocs-prodis the publication branch used for GitHub Pages deployment
uvfor environment and dependency managementrufffor lintingtyfor type checkingMkDocs + Material for MkDocsfor publishingMermaidandObservable Plotfor visual content
This repository is published under CC BY-SA 4.0.
