warpline documentation
Everything published about warpline, in reading order. If you have never run a
plugin, start at the top and work down.
- first-plugin.md — start here: build, run and gate a plugin in ten minutes
- doctrine.md — the deterministic/LLM boundary
- runtime-spec.md — manifest fields, retry/timeout/abort semantics, run artifacts
- derive-dont-store.md — why there is no snapshot store, diff engine or resource cache, and what
ttl_hours plus one overwritten file does instead
- needs-llm-contract.md — the LLM handoff protocol
- plugin-authoring.md — writing and testing plugins
- scheduler-recipe.md — running
advance on a fifteen-minute tick under systemd, launchd or cron, with every scheduler fact cited to the page it came from
- upgrading.md — what to change when you move between published versions, starting with the 0.6.0 plugin-name rule
Background
Not needed to use warpline: the reasoning behind the gate, and the spec for a surface the package does not ship.
- board-spec.md
— the Board: objects, Ask lifecycle, places, form, file formats. The board is a repo-only surface,
so this spec is not shipped in the package and the link is absolute.
- why-the-gate-holds.md — the long argument: why the gate holds, and the objections it has to survive