AgentFlow turns operational events into current entities, metrics, and queryable context behind one integration boundary. This site is a curated learning path for engineers who want to run the project, understand its responsibility boundaries, or integrate a client.
Use the project overview for product scope and the release story, the detailed architecture reference for current runtime choices and topology, and engineering status for current evidence and gates. The documentation hub maps the complete corpus and its historical records.
| Goal | Start here | Continue with |
|---|---|---|
| Run the local walkthrough | Quickstart | API or SDKs |
| Understand the system | Architecture | Concepts and Components |
| Prepare an environment | Deployment | Observability |
| Triage a local problem | Troubleshooting | Operational runbook |
flowchart LR
quickstart["Run locally"] --> architecture["Understand boundaries"]
architecture --> concepts["Learn semantics"]
architecture --> components["Map responsibilities"]
concepts --> api["Make requests"]
api --> sdk["Use a client"]
components --> deployment["Choose a deployment path"]
deployment --> observability["Read signals"]
observability --> troubleshooting["Triage a problem"]
| Question | Canonical owner |
|---|---|
| What the project offers and why | Project overview |
| Which runtime, version, backend, or topology is current | Detailed architecture reference |
| Which HTTP routes, headers, limits, and fields exist | Full API reference |
| What is proven, blocked, or externally gated now | Engineering status |
| Where current, historical, and generated documents belong | Documentation hub |
Walkthrough pages own the learning sequence and stable explanations. When an exact inventory or current claim changes, its linked reference remains the source of truth.