🚀 The open-source, multi-tenant platform for self-building knowledge graphs and simulation
Agent
Arc close is the required final control pass before submitting a branch that closes a work arc. Load the arc-close skill and run this protocol; do not rely on remembering its constituent checks. It complements, rather than replaces, the legibility protocol's close-out rendering for arcs with significant…
Agent
This protocol assigns one authority to each kind of durable knowledge. It complements issue-tracker.md, which governs issue facts. docs/agents/ remains the operating-guidance set, and docs/INDEX.md remains the registry described below.
Agent
How engineering skills consume Brunch domain documentation inside the HASH monorepo.
Agent
Consult this at design moments — when you notice yourself about to add state, a layer, a loop, a route, or a test harness — before writing the new thing. Each row routes an indication to the affordance to rely on, the divergence it exists to prevent, and the point where canon stops and a human or an owning ticket…
Agent
Branches are managed with Graphite (gt), matching HASH's repository-wide use of Graphite (its CI runs the Graphite optimizer). The standalone repository's late gh stack convention does not carry over. The unit of branching is the Linear issue: every stacked branch answers to at least one issue, created when work on…
Agent
Issues for this repo live in Linear, worked through the linear CLI (see the tool-linear-cli skill). Long-form artifacts — specs, research write-ups, notes — stay in this repo in the role-based topology defined by documentation.md; Linear issues link to them by repo path (and to Notion/Google docs by URL). The issue is…
Agent
How to write Linear issues and GitHub pull requests for this repo. Adapted from the dogsled ds-writing-issues skill (the "issue contract"); motivated by team feedback that agent-authored records read as jargon and are not readable by non-engineers. Apply whenever creating or editing an issue title or body or a…
Agent
How work arcs with significant agent-generated output close: produce legibility artifacts that aid review and re-establish shared understanding between the humans and the agents carrying the work. Companion to documentation.md (which governs where documents live; this file governs how understanding is checked and…
Agent
posture: prototype.
Agent
Use this protocol to keep Brunch aimed at a current, falsifiable proof rather than at whatever issue happens to be available. The arc driver owns trigger evaluation. Current truth lives in STEERING, which references governing STRATEGY-LOG IDs; this document owns only the control loop.
Agent
The skills speak in terms of five canonical triage roles. This file maps those roles onto Linear (team FE) — using workflow states where a state is the natural fit, and labels only where no state expresses the role.