` is the half of the loop that can\n see a wrong animation — AUTHORING.md §9.\n- 🧭 **No reference pictures, because the rig is your own?** Then make them:\n `rigc render` the first build you are happy with and keep those frames. Every\n later build is checked against them, and the first such check — the same build\n against frames of itself — is the floor the rest are read against, because\n `check` grades nothing and has no pass mark. It is the same instrument and the\n same commands; what changes is that the reference is a build of yours you have\n already looked at, so what it measures is **what your edit did**. Every drift\n the report prints carries the bound its own match gives it on the line under\n it, so a figure is read against that rather than against a number from a page;\n AUTHORING.md §9.2 says what the two halves of that bound are and why the floor\n is not zero.\n- [docs/LADDER.md](https://github.com/firejune/rigc/blob/main/docs/LADDER.md) is the benchmark: the same job, from a brief\n and rendered frames, scored. [docs/PILOT.md](https://github.com/firejune/rigc/blob/main/docs/PILOT.md) is how to run an\n agent through it and score what comes back.\n- 🤖 **Handing the authoring to an AI agent?**\n [docs/PROMPTING.md](docs/PROMPTING.md) is the operator's page — the six prompt\n clauses a measured pilot run paid for, and what you can leave unsaid.\n\n## See what you built, and let someone choose\n\nSteps 6 and 7 above are the three commands that need nothing but a compiled rig — no\nreference frames, no second package, no server. **`render`** writes every frame as a\nPNG plus one contact-sheet grid of the whole shot; **`preview`** writes one\nself-contained `.html` that plays it in Spine's own web player; **`vote`** puts two to\nfour candidates in one page and takes a human's answer back. Reach for them the moment\na rig compiles green, because green says nothing at all about the picture.\n\n\n ![\"Two](\"https://raw.githubusercontent.com/firejune/rigc/main/assets/rigc-keypose.gif\")
\n
\n\nThe whole loop on one character: two key poses are the given\nconditions, rigc pose reads where every part sits in each picture, two\ncandidate in-betweenings are compiled from the same pair — and a real\nrigc vote ballot picks the winner, because the movement between the poses\nis the one thing no instrument here will grade.
\n\nThree properties of `vote` are worth stating, because they are what make its ledger\nusable by the next agent rather than by a reader: **a tie is a recorded outcome, not a\nmissing one** — `both-unacceptable` is the tie that means *propose again*, and it is\nunreachable if ties are not recordable; **the winner is a digest, not a label**, since\n`B` means nothing outside one ballot while a digest identifies the same pixels\nanywhere; and **every line carries a reason code** from a closed enumeration that is\nenforced, so *\"tie, because this one is better\"* is refused.\n\n🎞️ **Authoring the movement those pages show you** — key poses, in-betweening, and how\nto spread candidates so a ballot informs — is [docs/MOTION.md](docs/MOTION.md).\n\n📐 **`rigc pose --images parts/ --frame poseA.png` runs the other way.** Every command\nabove takes something you authored and tells you about it; this one takes a **picture\nthe user already has** — one key pose — and reports where each loose part PNG sits in\nit, so those coordinates go into the rig and the motion **by construction** and the\neffort goes into the part no instrument can measure: the movement between two poses.\nA part that matches nowhere is refused by name, two near-equal placements are reported\nas both, and nothing it prints is a score. Fields, the coordinate contract and the\nlimits: [AUTHORING.md §11](docs/AUTHORING.md). The parts it refuses because\nsomething is drawn over them are `rigc chainfit`'s, once a candidate exists —\n[§12](docs/AUTHORING.md).\n\n## The gallery — seven complete rigs over art that ships with them\n\nEach directory in [`gallery/`](https://github.com/firejune/rigc/tree/main/gallery) is\none rig spec, one motion spec and the PNGs they name, small enough to read in one\nsitting. Each stars a single feature, so *how do I do X* has a working answer rather\nthan a field table, and each README carries the frame rate it was authored at, what\nwas verified, and what writing it cost. Repository material: a clone and\n`bun install` runs them.\n\n| Example | Stars | What it is |\n| --- | --- | --- |\n| [`gallery/walk`](https://github.com/firejune/rigc/tree/main/gallery/walk) | `ik` constraints + **`ik` timelines** | Two two-bone leg chains solved to foot targets — the planted leg nailed down, the swinging one let go at the top of its lift |\n| [`gallery/squash`](https://github.com/firejune/rigc/tree/main/gallery/squash) | **`deform` timelines** | A ball squashed about its contact point and stretched along its travel, from two affine transforms the keys state rather than tabulate |\n| [`gallery/flex`](https://github.com/firejune/rigc/tree/main/gallery/flex) | **`contour` meshes** | A swallow-tailed banner and a serrated leaf: four meshes traced off their own alpha, waved by bone timelines and rippled by a `deform` |\n| [`gallery/ride`](https://github.com/firejune/rigc/tree/main/gallery/ride) | `path` attachments + **path constraints** | A trolley coasting down a drawn rail and rolling back, driven by a `position` timeline, with `groups` + `stagger` keying the wheels and the ears |\n| [`gallery/portrait`](https://github.com/firejune/rigc/tree/main/gallery/portrait) | **deform `transform`** + `derive` group tracks | A 2.5D head turn: two meshes and six feature bones all keyed from one stated expression, `dx = x(cos t − 1) − z·sin t`, with the depths in the spec rather than a README |\n| [`gallery/nod`](https://github.com/firejune/rigc/tree/main/gallery/nod) | the **`pitch`** and **`wave`** transform kinds | A head bowing and two lop ears rippling, on three meshes each laid out for the closed form that moves it — a fold angle solved for before authoring, and a shear whose winding no amplitude can reverse |\n| [`gallery/look`](https://github.com/firejune/rigc/tree/main/gallery/look) | **`slider` constraints** | A head that turns because a **value** says so: two dials drive two sliders, and the rendered animation moves the needles rather than the face — with a depth map under the face mesh, a soft mask on the cowlick, and a slider range derived from the turn ceiling `build` reports rather than picked by eye |\n\n\n ![\"A](\"https://raw.githubusercontent.com/firejune/rigc/main/assets/rigc-scene.gif\")
\n
\n\nThe portrait rig playing its three animations in one take — the turn is\nthe shot: both silhouette edges move apart, which a flat slide cannot do, because every\nfeature carries its own depth. The rig guarantees the seams — idle loops\nwhile gaze and turn return to rest, so the hand-offs meet at 0\ndiffering pixels — and the composing is the consumer's. Authorable on plain Spine 4.3, no\nplugin, no runtime patch; what the turn costs is authoring rather than runtime capability,\nand that cost is one stated expression per key. Compiled and rendered entirely by the\npublished package.
\n\n🎞️ **How the three films on this page were made** is kept with them, one directory per\nfilm in [`films/`](https://github.com/firejune/rigc/tree/main/films) — a `run.sh` that\nnames every step, the assembler that cuts the shots and draws the type, and a README\nsaying what the film claims and which tool printed each figure on screen. Repository\nmaterial, like the gallery: a clone runs them.\n\n## Commands\n\nEvery command takes its paths explicitly. `rigc --help` prints its flags, and\n[AUTHORING.md §0](docs/AUTHORING.md) is the same list with what each flag means, which\ncommands take it and what its default is.\n\n| Command | Does |\n| --- | --- |\n| `build --rig … --motion … --out …` | compiles, gates, and **writes only if the gate is green**. `--images ` says where the rig spec's `image` names resolve, `--manifest` adds measured art, and `--copy-images` copies every page PNG into `--out` so the directory is self-contained, with `skeleton.images` pointing at it so the editor's import finds the parts |\n| `build … --pack` | the same build with every part arranged onto **shared** atlas pages, written into `--out` — losslessly, and gated a second time as the pair that ships. `--page-size` and `--padding` tune it |\n| `build … --atlas-in ` | the same build with every part resolved to a **region of an existing pack** instead of a loose PNG; a name the atlas lacks, a size the spec disagrees with or a rectangle off its page is refused by name |\n| `validate ` | re-gates artifacts already on disk |\n| `ingest --out ` | `build` run backwards: reads a Spine 4.3 skeleton and writes the rig spec and motion spec that **rebuild it**, plus a findings report naming everything it could not carry. a skeleton that declares no stage is carried as declaring none, `--stage x,y,w,h` adds a box to one — and is refused, rather than ignored, beside one that declares a box — and `--images ` writes the spec's own images directory — the opposite direction from `build --images`, which overrides it — so the rebuild carries no flag at all |\n| `explain --rig … --motion …` | the compiled rig as a table — every bone with its resolved parent, the slots in draw order, every timeline key by key. Writes nothing. What to reach for when a rig compiles and still looks wrong |\n| `render --candidate ` | PNG frames plus a contact sheet, in `render/`. `--hide ` or `--slot ` draws part of the rig on the **same grid** as the whole, so the two frames overlay and the difference is the part; `frames.json` records the subset and `check` refuses such a set as a reference |\n| `preview --candidate ` | one self-contained `.html` that plays it, headed by the line `validate ` prints for it and the rigc version — a refused candidate is still previewed, and its header says so in the gate's words. Repeat `--candidate` for one page with a pane per candidate, in the order given; a green `build` ends by naming this command for its own `--out` |\n| `vote --candidate a --candidate b` | one `.html` that asks a human which; `vote --record ` checks the answer into `votes.jsonl` |\n| `pose --images --frame ` | reads part placements **out of** a picture |\n| `chainfit --candidate --images --frame ` | reads the parts `pose` refuses, through the candidate's own draw order and hierarchy: masked residuals over **visible** pixels, one hinge per child instead of four degrees of freedom, and the `rotate` key value each answer implies. A bone with two or more anchored descendants is **determined** rather than searched, and the residual that over-determination leaves is reported |\n| `diff ` | structural comparison of two skeletons, one ratio per measure and deliberately no combined score |\n| `bonedist --candidate … --reference … --bones …` | per-frame, per-bone world-transform distance against another skeleton — the ladder's stage 3, run on its own. `--bones ` is required rather than defaulted: a candidate is entitled to its own bone names, so the pairing is stated |\n| `check --candidate --frames [--out ]` | the candidate against reference pictures — the only instrument here that can see a *wrong animation*. `--out` also writes, for every frame the table lists, the picture its figures came from: reference, candidate, difference and overlay at native size |\n| `bench --candidate ` | one rung of the benchmark ladder |\n| `skills install [--dir …] [--copy]` | links every agent skill the package ships into `.agents/skills` (or `--dir`) as relative symlinks, or copies them with `--copy` — where Codex, Gemini CLI and Antigravity look. A second run has nothing to do; an entry already there that is not this command's is refused by name and nothing is written |\n\n`diff`, `bonedist`, `check` and `bench` measure against something you were given; the\nfirst three work on any reference you have, and `bench` is a repository workflow that needs a clone\nand `bun run fetch-examples`. The reasoning behind them is in\n[the benchmark dossier](https://github.com/firejune/rigc/blob/main/docs/BENCHMARK.md).\n\n`build` and `validate` both default to `--profile spine` — the 34 validity rules, which\nask *is this valid Spine 4.3 that any runtime plays correctly?* `--profile spine-html`\nadds all 49: the other 15 are one renderer's policy and one canvas budget's, and they\nfire on perfectly correct editor-produced Spine data, which is why they are opt-in.\n⇒ **That reason is about foreign data and does not carry to a rig you are authoring\nyourself: author under `--profile spine-html` and read the extra 15 as findings, and\ngate the release under `--profile spine`.** A `deform` key that folds a mesh inside\nout is written out under the default and refused by name under `spine-html`, which\nis the shape of what that split buys you. A report always names\nthe profile it ran and lists what that profile left out.\n\nSeveral cuts can also be registered in a `cuts.json` and built by name\n(`build --cut my_cut --cuts path/to/cuts.json`); every path in that table resolves\nrelative to the `cuts.json` file itself, so the table lives with the project that owns\nthe art. Its shape is under\n[Usage](https://github.com/firejune/rigc/blob/main/docs/BENCHMARK.md#usage).\n\n### Starting from a skeleton you already have\n\n`rigc ingest` reads a Spine 4.3 `skeleton.json` and writes the two spec files that\nrebuild it. It is the only command that runs against `build`'s direction, and the\nonly one whose contract is an equality rather than a rulebook:\n\n```bash\nrigc ingest hero.json --out specs/ --images parts/\nrigc build --rig specs/rig.json --motion specs/motion.json --out build/\nrigc diff build/skeleton.json hero.json\n```\n\n`--images parts/` is what makes the second line carry no flag: it writes the spec's\nown `images` directory, spelled from `--out`, so the specs are self-contained from\nthere on. Leave it off and the `image` names resolve against `specs/` itself, which\nholds no art — every rebuild then has to repeat `build --images parts/`.\n\n**`build(ingest(x))` is `x`.** Over the eleven rigs this repository builds — the seven\ngallery examples, the three generated probes and a coverage probe written for the\npurpose — the rebuilt `skeleton.json` is byte for byte the file the decompiler read.\nThe atlas is held to a weaker\nclaim on purpose, and the weakening is measured rather than assumed: it comes back\nequal as a **multiset of region blocks**, because the order the pages are collected in\nis in no field of the skeleton.\n\n**And over twelve skeletons nobody here wrote.** Every editor export in the fetched\nexample corpus, ingested, rebuilt through the pack beside it and `diff`ed against the\nsource, comes back **12 of 12, no blockers, 1.000 on every measure the report\ncarries** — and each rebuild is its export's own text in canonical form, apart from\nthe header's `hash` and `spine`: the editor's project hash and the runtime version\nrigc stamps, the two keys the rig spec has no field for by design (12 of 12).\n[INGEST.md §2.3](docs/INGEST.md) states that pass line and why those two are the\nexceptions.\n\n**What it reads is skeleton JSON and nothing else** — no `.spine` project, no binary\n`.skel`, no atlas, no art. So it never invents, and the things it cannot get out of\nthe file are **findings** with codes rather than plausible values: a construct the\nspec format cannot hold (`point`, a `sequence` block, an unknown field\non a bone, slot or constraint) is a blocker, the command exits non-zero, and both\nspecs are still written — a spec plus a list of what is missing from it beats no spec.\n\n⚠️ **Two values are not in a skeleton at all.**\n\n- **The stage.** `skeleton.width`/`height`. A skeleton that declares none is carried as\n declaring none — the rig spec states `\"width\": null, \"height\": null` and the rebuild\n carries no box either, byte for byte — and `--stage x,y,w,h` is how a\n caller *adds* one, recorded as a judgement. It is not derivable — posing the rig gives\n the *animated* extent, which is a different number from the setup box. ⛔ **And `--stage` beside a box the file already states is refused\n too**, for the opposite reason: two sources for one value, where the file is the record\n of what was measured. **All twelve exports in the example corpus carry a stage** and\n none of them needs the flag. It is the value that costs least to get wrong, because\n `diff` reports the box and gates nothing on it.\n- **An animation's duration.** The format has no such field. The largest key time is\n the only derivable answer and it is what a runtime plays to; it is wrong for an\n animation that holds its last pose past its last key, so it is recorded as a finding\n on every animation rather than chosen quietly.\n\nBoth specs carry a `note` that `ingest` writes itself, saying the file is decompiled\nand naming the skeleton it came from — because a decompiled spec is indistinguishable\nfrom an authored one by inspection, every gate here calls it green (it *is* green),\nand no gate can catch a missing note.\n\n[docs/INGEST.md](docs/INGEST.md) is the whole page on working from a file you were\nhanded; [docs/AUTHORING.md](docs/AUTHORING.md) §0.3 is the loop.\n\n### The editor round trip — for a licence holder, never in CI\n\n`tools/editor_roundtrip.ts` drives the loop the output's whole premise rests on:\nbuild → **import into the Spine editor** → export back to JSON → gate, `diff`,\n`render` and `check` the export against the build it came from.\n\n```\nbun cli.ts build --rig … --motion … --out build/ --copy-images\nbun tools/editor_roundtrip.ts --build build/ --editor /Applications/Spine.app/Contents/MacOS/Spine\n```\n\nIt prints the import and export exit codes, the validator's verdict on the\nexport, every `diff` measure that moved, `check`'s mean MAE and worst drift per\nanimation **for each skin the build and the export both declare** — one\nrender-and-check block per skin, with a per-skin roll-up under them, because a\nrig's contested art lives in its named skins and a single un-skinned check draws\nnone of it; a skin only one side declares is a FAIL naming it as **lost** (or\n**added**) **by the export**, with `diff`'s `attachments.skins` beside it, and is\nrendered on neither side — and a\nfield-by-field list of what the editor rewrote. Every step quotes what its child\nsaid when that child did not do what it was for, the renderers included; a skin\n**neither** side can draw — a hit-box rig, say — is a **SKIP** naming that, not a\nred, because `check` had nothing to compare and `diff` and `validate` have\nalready measured the rig. One side drawing where the other does not is the\ndivergence the trip exists to find and stays a failure. A human edit made in the\neditor survives the trip back.\n\n🔒 **It requires a licensed Spine editor on the machine, by construction**, and\ndrives only the [documented command line](https://esotericsoftware.com/spine-command-line-interface)\n— never the UI, and it produces nothing the editor did not produce. With no\neditor present it refuses by name and exits non-zero, and so does the **trial**:\nthe trial cannot save projects or export animation data, so the refusal names\nwhat it found — the executable, the bundle, the `CFBundleName` that bundle\ndeclares, or the banner the binary prints about itself — rather than starting it\nand failing downstream. Both refusals point at `--exported `, which\nmeasures an export the editor already made and is the half of this tool that\nneeds no editor at all.\n\n⛔ **Run the round trip by hand, on a machine that has the editor.** CI has no\neditor, so no automated check runs it.\n\n⚠️ Build with `--copy-images`. An ordinary build's atlas names its pages by a\nrelative path back to the art directory, and the round trip copies that atlas to\na directory at another depth — the tool refuses such a build by name rather than\nletting `A17` blame the editor for the harness's own doing.\n\n## Documentation\n\n| Document | For |\n| --- | --- |\n| 📘 **[docs/AUTHORING.md](docs/AUTHORING.md)** | **the format guide, and the one to read before writing a spec.** Both input files field by field with a complete minimal example each, every field with its Spine meaning, the rules that decide what is emitted, the build → read the report → fix → repeat loop, the map from every named failure to the file that has to change, and the features rigc refuses by name so you do not spend a loop discovering them. It travels **inside the npm package**, at `node_modules/spine-rigc/docs/AUTHORING.md` |\n| 🦴 **[docs/RIGGING.md](docs/RIGGING.md)** | **authoring the hierarchy.** Where a bone goes and why the art is pushed out on an offset, why a pivot in the wrong place looks like a search failure and what identifies one, moving a pivot and the child row that gets forgotten, gauges, siblings-not-a-chain, what a chain can reach and how many links it needs, why a local key is not a world key, duplicate art at mirrored pivots, and constraints as structure. Every section is a stumble the run records hold more than once, ranked by how often. Ships in the package too |\n| 🎞️ **[docs/MOTION.md](docs/MOTION.md)** | **the key-pose recipe.** How to get two poses, what a pair of poses does and does not fix, the in-betweening rules and where each comes from, and how to spread candidates so a ballot informs. Ships in the package too |\n| 🙂 **[docs/FACE.md](docs/FACE.md)** | **authoring a face.** A blink, a gaze and a 2.5D head turn on plain Spine data: the one line of yaw arithmetic every number in a turn comes from, depth as the parameter you are actually authoring, where to put a grid's columns and the angle at which any grid folds, what foreshortens and what does not, channel allocation before the first key, and the three cliffs with their angles. Also the deform audit gap, demonstrated — a folded mesh gates green — and the differential check that works today |\n| 📥 **[docs/INGEST.md](docs/INGEST.md)** | **working with a skeleton you did not author.** What every command can and cannot do with a foreign `skeleton.json`, reading it with the toolchain, transcription as the route that makes it yours, what each validator complaint means on an export, and the re-pivot/rename/extend recipes. Ships in the package too |\n| 🤖 **[docs/PROMPTING.md](docs/PROMPTING.md)** | **handing the authoring to an AI agent** — the prompt clauses a measured pilot run paid for, and what you can leave unsaid. Ships in the package too |\n| 🔬 **[docs/SPEC_COVERAGE.md](docs/SPEC_COVERAGE.md)** | **the Spine 4.3 format, field by field.** Every key the 4.3 JSON parser and atlas reader take, what each defaults to, and the parser line it comes from — the rows rigc's refusals cite by part number. Ships in the package too |\n| 🎓 **[the benchmark dossier](https://github.com/firejune/rigc/blob/main/docs/BENCHMARK.md)** | **why you can trust the output.** The yardstick, `diff` and `check` and what neither can see, the eight-rung ladder and the spineboy graduation exam, the run viewer, the 49 named assertions with their profiles, and the selftest that has watched every one of them fire. Repository material — it is not in the npm package |\n| 📋 [LADDER.md](https://github.com/firejune/rigc/blob/main/docs/LADDER.md) · [GATE.md](https://github.com/firejune/rigc/blob/main/docs/GATE.md) · [PILOT.md](https://github.com/firejune/rigc/blob/main/docs/PILOT.md) | the live rung ledger, the clause statements a candidate is graded against, and how to run an agent through the ladder and score what comes back |\n| 🔬 [SURVEY_2026-08-22.md](https://github.com/firejune/rigc/blob/main/docs/SURVEY_2026-08-22.md) | the survey the ladder was climbed by: rigc and the official examples as measured on 2026-08-22, and the gap list ordered by rung. A dated record, not kept current. Repository material |\n| 🧬 [GENERATIONS.md](https://github.com/firejune/rigc/blob/main/docs/GENERATIONS.md) | **Spine data from another generation.** Why a 3.8–4.2 file read as 4.3 fails in silence, the policy that follows (detect from `skeleton.spine`, never guess, play on the matching runtime), what `A16` and `ingest` do with such a file, and the editor as the migration path. Repository material |\n| 🗺️ [ROADMAP.md](https://github.com/firejune/rigc/blob/main/ROADMAP.md) | where this is going, and where it has been. What 1.0 had to mean before the number was claimed, and what it was claimed on — conditions rather than a feature list, because direction here comes from what users hit |\n| 📐 [CLAUDE.md](https://github.com/firejune/rigc/blob/main/CLAUDE.md) | **the doctrine** — why the validator's messages are the product, why nothing reaches disk before green, why no number is ever invented, and what a change has to keep. [CONTRIBUTING.md](https://github.com/firejune/rigc/blob/main/CONTRIBUTING.md) calls it worth ten minutes before a first patch. Repository material |\n\n## Why you can trust the output\n\nrigc is measured against **Spine's own official example projects** — the\n`1-weight-and-mass` … `8-follow-through` series as a difficulty ladder, with spineboy\nas the graduation exam.\n\n🎓 **The ladder is complete.** All eight numbered rungs and the\nspineboy graduation exam are cleared and hold under the current gate, **v2.4**, every clause PASS or SKIP:\nworst attributable slot drift **5.5550 px** against a 6.0 px bar — a **1.0801×**\nmargin, the thinnest of the ladder's **G2** figures, and **G5**'s 1.0376× is thinner\nstill — and **0 of 124** frame-change disagreements. Recompiling the same spec in a\ndifferent session reproduced every field of the measurement record **to the digit**.\nThe rungs stay in place as regression gates.\n\n**Rung 7 clears on a read-down.** One of its three slots draws in every set and is\nattributable in none; a read-down names the framing of its evidence, and a slot whose\nattributability is **measured** to be capped below the bar reads down when everything\nobservable about it is independently verified strict. Every other rung and the\ngraduation exam pass on the clause itself. Recompiling a stored candidate reproduces its\nrecord **to the digit within one gate**; across an instrument change the digits move,\nand [docs/LADDER.md](https://github.com/firejune/rigc/blob/main/docs/LADDER.md) records\nwhere. The standing figures quoted above are from its *gate-v2.4 re-inspection*, which\nis the current sweep.\n\n⚠️ **What that certifies, stated exactly.** That **the tool, the guide and the\nprotocol reach the bar across a bounded series of honest attempts, each residual\ndiagnosed and fixed** — spineboy took five, and the last inherited its\npredecessor's specs under the run protocol's inheritance clause. It is **not**\nthat an agent authors a spineboy-scale rig from the brief alone in one run: the\nladder has not demonstrated that, and each row records which of the two it is.\n\n🧪 **A separate series measures that harder question, and it has not been kind.**\nFrom-zero attempts at spineboy — no inherited specs — have landed at **18.2, 18.8,\n19.57, 7.86, 9.33 and 18.98 px** worst drift against the 6.0 px bar, a spread with no\nmonotone trend and every figure above the bar. They move no rung and reopen nothing —\na from-zero run is a tooling-progress measurement rather than a re-climb, which is\nwhy the certification above is scoped to tool + guide + protocol. One of those\nattempts states the residual in its own words: *\"in motion it is not at editor\nquality.\"* All six, with their verdicts, are in\n[docs/LADDER.md](https://github.com/firejune/rigc/blob/main/docs/LADDER.md).\n\nThe whole dossier — the yardstick, `diff` and `check` and what neither of them can\nsee, every rung, the run viewer, the 49 assertions and the selftest behind them — is\n[docs/BENCHMARK.md](https://github.com/firejune/rigc/blob/main/docs/BENCHMARK.md).\nLive rung status is\n[docs/LADDER.md](https://github.com/firejune/rigc/blob/main/docs/LADDER.md).\n\n## Contributing\n\nIssues are the ledger; see [CONTRIBUTING.md](https://github.com/firejune/rigc/blob/main/CONTRIBUTING.md) for what a change\nhas to clear before it lands. Releases are cut by release-please —\n[RELEASING.md](https://github.com/firejune/rigc/blob/main/RELEASING.md).\n\n## Licence\n\nMIT — see [LICENSE](LICENSE). Third-party terms, including the Spine editor licence\nrequirement that this project inherits, are in [NOTICE.md](NOTICE.md).\n","readmeFilename":"README.md"}![\"rigc](\"https://raw.githubusercontent.com/firejune/rigc/main/assets/banner.svg\")
\n![\"npm](\"https://img.shields.io/npm/v/spine-rigc.svg?style=flat-square&color=FF6B4A\")
\n ![\"npm](\"https://img.shields.io/npm/dm/spine-rigc.svg?style=flat-square&color=A855F7\")
\n ![\"license\"](\"https://img.shields.io/badge/license-MIT-38BDF8.svg?style=flat-square\"){kind=icon}
\n![\"Loose](\"https://raw.githubusercontent.com/firejune/rigc/main/assets/rigc-demo.gif\")
\n