Read the Issuegraph frontmatter block out of an issue body and derive the graph it declares — ready set, effective priority, serialize and together components, duplicate resolution, cycles. Parsing and pure derivation only; no network, no tracker, no writ

Derive the selection order from an Issuegraph model — ranked slots, held slots with their reasons, together units, excluded duplicates, priority promotions — plus the pre-write cycle refusal. Pure; no network, no tracker, no writes.

Write the Issuegraph frontmatter block into an issue body — render a fresh block, splice generated edges in place without disturbing anything else, and re-delimit a block a fence left inert. Pure string work; no network, no tracker, no reads.

One command over the Issuegraph packages: read the block out of an issue body, derive the selection order from bodies you supply, and edit the block in place. Composes the reader, derive and writer packages; parses nothing itself, fetches nothing, and tak

The Issuegraph format's shared vocabulary as frozen constants and derived types — field names, cardinality, defaults and value sets. No parsing, no I/O. The reader, the writer and the viewer all read the format through this.

Everything that mutates an Issuegraph document: edit affordances drawn as overlays on a viewer, dispatching through a store. Composes the viewer and the store through their public surfaces and performs no write itself.

Render an Issuegraph document as a work order — the ordered spine with readiness stations, the five edge treatments, and three projections. Rendering only: no fetching, no mutation, no auth, and every value themeable through CSS custom properties.

A framework-free client store for an Issuegraph document, plus the data-source port a host plugs its tracker into. Renders edits optimistically, dispatches every mutation outward, and never re-evaluates the selection order until the write lands.