Skip to content

docs: add implementation map for layers in architecture docs #13

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
wayseer00 merged 1 commit into from
May 1, 2026
Merged

docs: add implementation map for layers in architecture docs #13

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
14 changes: 14 additions & 0 deletions docs/architecture.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,6 +39,20 @@ human request
- `DEPLOYMENT.md` — deployment notes.
- `interdependent_way.md` — philosophical/source doctrine for project behavior and voice.

## Where things live

A short implementation map for the working component layers in this repo:

- `a0 agent interface` → `client/` for the browser UI, `server/` for the Express proxy, and `python/routes/` for backend API endpoints.
- `context / memory layer` → `python/engine/pcna.py` (PCNA engine and memory inference), with persisted state modeled in `python/models.py` and `python/storage/domain.py`.
- `planner / policy layer` → `python/services/inference.py` for orchestration and `python/config/policy_loader.py` for policy config.
- `provider routing layer` → `python/services/energy_registry.py` and `python/services/providers/` (including `python/services/providers/_resolver.py`).
- `model call(s)` → `python/services/inference.py` plus provider implementations under `python/services/providers/`.
- `tool execution layer` → `python/services/tool_executor.py` and tool handlers in `python/services/tools/`.
- `audit / logging layer` → `python/logger.py` for log streams and audit plumbing in services such as `python/services/spawn_executor.py`.
- `gating / access control` → `python/services/gating.py` (with explicit allowlist rules in `python/services/gating_allowlist.py`).
- `agent runtime` → `python/main.py` for FastAPI startup, PCNA lifecycle, and route registration.

## AIMMH boundary

AIMMH is expected to provide, or eventually provide, the multimodel/multimodal hub layer. The clean boundary still needs confirmation.
Expand Down
Loading