-
Notifications
You must be signed in to change notification settings - Fork 0
Home
github-actions[bot] edited this page Apr 23, 2026
·
41 revisions
Dogfood documentation for the harness repo itself. Every page is written for a single reader intent — learning, doing, looking up, or understanding — per the Diátaxis convention (ADR 0004).
Note
This wiki documents agentic-harness for contributors to the harness repo. It is never installed into target projects — target projects get templates/wiki/ instead. See ADR 0002 for why.
- Tutorial 1 — Your first harness install — fresh clone to a healthy installed scratch project in ~5 minutes.
- How to install the harness into a project — add the scaffold to an existing repo.
- How to refresh an installed harness — pull a newer harness version into a project that already has one.
-
How to cut a release — tag, changelog, GitHub release via the
ship-releaseskill.
-
Installer CLI reference — flags, prerequisites, ownership table for
install.sh/install.ps1. - CI gates reference — what each CI workflow proves and the script behind it.
- Repo layout reference — top-level directory map and four-adapter parity table.
- Completed features — reverse-chronological log of shipped work.
- Product intent — what problem the harness solves and for whom.
- How the pieces fit — narrative of how phases, adapters, templates, and scripts interact.
- GitHub Projects integration — why and how the harness writes to ProjectsV2.
- ADR 0001 — Phase-gated workflow
- ADR 0002 — Documentation convention
- ADR 0003 — ProjectsV2 ownership and linking
- ADR 0004 — Diátaxis documentation spec
Page templates, filename rules, and the Diátaxis four-mode split are described in templates/wiki/README.md — the same conventions this wiki follows.
🔧 How-to
- Your first install
- Install into a project
- Configure a new project
- Update an installed harness
- Cut a release
- Use auto-context in phases
- Use per-project install
- Audit the vault
- Find missing note links
- Use AgentMemory in any agent
- Tune auto-orchestration
- Run without a vault
- Choose a storage backend
- Stand up the memory MCP server
- Installer CLI
- Detection rules
- Project config
- Migration tool
- CI gates
- Repo layout
- Vault lint checks
- Note relatedness signals
- AgentMemory context payload
- Process seam
- Storage seam
- Orchestration bridge
- Vault write protocol
- Queue status lite
- Auto-orchestration config
- Capability resolver
- Persona tier schema
- Compatibility
- Completed features
- Memory MCP tools
🏛️ Architecture
- AgentMemory
- Device-Wide Substrate
- Phases
- Orchestration and Auto-Detection
- Host adapters
- Toolkit interface ↔ crickets