agenthropic

agenthropic — documentation site (content root)

Tool-agnostic Markdown source for the public GitHub Pages docs site. The generator (VitePress / Docusaurus / MkDocs) is deferred — content here is plain CommonMark so it can be authored and reviewed before the generator is chosen (see ../DOCS-PLAN.md DOC-P1). Assembly (nav, theme, publish) happens later without touching page content.

The app binds 127.0.0.1 only. These docs are the sole public surface. Nothing here may instruct a reader to bind 0.0.0.0, expose the port, or add a spawner.

Update — 2026-07 (as built). This corpus was written before any application code existed. Implementation began 2026-07-11 (by explicit owner override of the CD-8 no-code-before-Phase-0 gate), so pages that describe agenthropic as “pre-code” or “bootstrap phase” are design history, not current truth. What runs today: the loopback-bound, token-gated Fastify server; the SQLite/WAL substrate with twenty migrations and a daily backup timer; JSONL corpus ingest with replay-on-startup and tail-follow polling that re-reads only new bytes; the persisted subagent DAG; the cost engine (compaction repricing + delegation savings); the hook receiver and its installer; the status watchdog that ages an unobserved agent to unknown; the SSE realtime hub; the read API; and all four dashboard views (live status, session tree, global DAG, cost/Sankey) plus a per-session cost-analysis panel. Retention is signed and wired as of 2026-09-10 — events rows older than 90 days and backup files older than 30 days (never below the newest 7) are pruned after each successful daily backup; token_usage is never pruned in v1.0, by decision.

Test figures, re-measured 2026-09-18 on the working tree: 131 test files / 2428 tests, with 100% statements, branches, functions and lines enforced in all five packages — (re-measured again 2026-09-23: 140 test files / 2621 tests; and 2026-09-26: 167 test files / 3060 tests, same 100% on all four axes in all five packages - a dated measurement, not a constant) — packages/test-fixtures is no longer an exclusion, it is inside the gate. Two things that figure does not mean: the thresholds block a contributor’s merge but not the sole maintainer’s push (branch protection on main requires the ci check as of 2026-08-25, with enforce_admins deliberately off), and coverage of the code is not accuracy of the output — the hierarchy-accuracy exit gate still reports NOT CERTIFIED at n = 0 because no session has been hand-labeled.

Three things are not true of the running system, and every affected page below now says so: there are only four real hooks (UserPromptSubmit, Stop, SubagentStop, PreCompact) rather than twelve, and SubagentStart does not exist; there is no separate Normalizer→Projection pipeline — JSONL parses straight into the projections in one transaction per session, and events_raw holds hook events only; and v2.0 alerting (Telegram) is not started and may never start — it is entered only via KC-5, and its operator-alerts API and UI (WP-A8/A9) were cut outright.

Two honesty caveats stand across the whole corpus: the Phase-0 spike numbers remain PROVISIONAL until ratified against a hand-labeled corpus, and the v1.0 “<30s to understand a session” usability claim is unmeasured — nobody has ever timed it. Kill checkpoints KC-0 and KC-1 both passed unmet — work continues by explicit owner override, not because the gates were satisfied. See guide/roadmap.md for the full checkpoint record.

Amendment convention (how pages are corrected without erasing the design record): STYLE-GUIDE.md § “As-built amendments”. This block is the single amendment blockquote that convention allows; its contents are refreshed in place as the tree moves, most recently on 2026-09-19.

On the generator. Still deferred (DOC-P1 / ADR-0013) — but the corpus is wired to publish: .github/workflows/pages.yml renders it with the stock GitHub Pages Jekyll builder, adding zero dependencies. Its source root is docs/, not docs/site/, because the site tree cross-links heavily into ../analysis/ and ../due-diligence/. Pages was enabled on 2026-08-25 and the site is live at https://ivanbbaev.github.io/agenthropic/. Before that, every run of the workflow failed at the Configure Pages step, and it could not be automated away: the workflow does pass enablement: true, but a workflow’s GITHUB_TOKEN may only deploy to a Pages site that already exists — creating one needs repository-administration rights the token deliberately never has. Two runs proved it with Create Pages site failed. Error: Resource not accessible by integration. Failing loudly there was the intended behaviour; a job that “succeeded” while deploying nowhere would have been worse. The same corpus remains readable in the repository.

Site map

Section Page File
Guide What is agenthropic guide/what-is-agenthropic.md
Guide Running agenthropic guide/running.md
Guide The moat — why build guide/the-moat.md
Guide Comparison vs the field guide/comparison.md
Guide Roadmap guide/roadmap.md
Guide FAQ guide/faq.md
Architecture Overview architecture/overview.md
Architecture Data model architecture/data-model.md
Architecture Hook ingestion architecture/hooks.md
Architecture Ingest & reconciliation architecture/ingest-reconciliation.md
Architecture The DAG moat architecture/dag-moat.md
Architecture Cost model architecture/cost-model.md
Architecture Glossary & reference architecture/glossary.md
Security Security model security/model.md
Security Threat model security/threat-model.md
Security Remote access security/remote-access.md
Operations Backup & restore operations/backup-restore.md
Operations Troubleshooting operations/troubleshooting.md
Contributing Overview contributing/index.md
Contributing Testing & quality contributing/testing.md
Contributing Licensing & provenance contributing/licensing.md
Contributing Decisions (ADRs) contributing/decisions/README.md
Contributing Governance contributing/governance.md
Usage (written pre-code; amended as-built) Getting started usage/getting-started.md
Usage Hooks installer usage/hooks-installer.md
Usage Configuration usage/configuration.md
Usage Using the dashboard usage/dashboard.md
Usage API reference usage/api.md
Usage (not built — v2.0, entered only via KC-5) Telegram alerts usage/telegram.md

Authoring conventions: STYLE-GUIDE.md. Decomposition & per-page scope: ../DOCS-PLAN.md. Design basis: docs/ai/DESIGN.md (internal, kept local-only — not published in this repo).