Argus docs¶
Argus is an observable, self-hosted control plane + universal memory hub.
This site is generated from the plain Markdown in docs/ -- that Markdown
stays the single source of truth (agents and the hub's context assembler
read it raw; Forgejo renders it inline). This site is the human-facing view
on top of the same files.
The layout follows Diataxis: four kinds of documentation, organized by what the reader is trying to do.
Runbook -- how to operate it¶
Step-by-step, task-oriented. What to run, in what order, when something needs operating or recovering.
Reference -- what it guarantees¶
Dry, factual, lookup-oriented. Contracts: endpoints, event kinds, hook surfaces -- what you can rely on, not why it's shaped that way.
Explanation -- why it's built this way¶
Understanding-oriented. The PRD, the roadmap, and every spec/plan/research doc that recorded a design decision as it was made.
Decisions -- the record of what was ruled and why¶
Numbered ADRs, one ruling per file, never edited after acceptance -- a superseding decision gets a new number and links back.
- ADR template
- 0001: Task verification runs only on satisfied-at-land evidence
- 0002: Approval-gated tasks never auto-promote to dispatch
- 0003: Docs-as-code, Diataxis-structured, strict-CI-checked
Diataxis at a glance¶
flowchart LR
A[Runbook: how to operate] --> D[Docs site]
B[Reference: what it guarantees] --> D
C[Explanation: why it's built this way] --> D
E[ADR: what was ruled] --> D