Skip to content

docs: add the three README images - #18

Merged
DivyamTalwar merged 1 commit into
mainfrom
docs/readme-images
Sep 5, 2026
Merged

DivyamTalwar merged 1 commit into
mainfrom
docs/readme-images

Conversation

@DivyamTalwar

Copy link
Copy Markdown
Owner

The images docs/images/README.md has specified since the Astra release now exist.

File Where What it argues
constellation.png end of The four bodies four bodies, four pins, and that Astra and Terra are alternatives — exactly one chosen per delegation
flow.png top of The flow one delegation end to end, including the four points where it can stop
refusal.png end of What it will not do the same command accepted and refused, with the filesystem untouched

Each was checked against the repository, not accepted on sight

An earlier pass carried a FABLEWRIGHT wordmark and, in the proof image, two role filenames and an install command that do not exist here:

Earlier pass showed Actually shipped
orrery-sol-researcher.toml orrery-sol-reviewer.toml
orrery-terra-ops.toml orrery-terra-implementer.toml
$ fw install no such command

Publishing that would have put a claim on the front page that the shipped files contradict — the exact failure verify.sh exists to catch — and it would have done so under the words "LAUNCH PROOF".

What is committed

The real command, sh plugins/orrery/scripts/install-agents.sh --target-dir ~/.codex/agents, the three real role filenames, and output whose load-bearing lines are verbatim from an actual run:

INSTALL PASSED: Astra, Sol, and Terra exactly match ./agents; no legacy Luna file remains.
ERROR: Astra destination is conflict and will not be replaced: ~/.codex/agents/orrery-astra-implementer.toml
[exit 1]

One thing stated plainly: the narrower progress lines between those are a readable dramatization of steps the installer genuinely performs — destination classification, the legacy-Luna check, the post-install exactness re-check — rather than literal stdout. Every load-bearing line is real.

Alt text describes content rather than naming files, so all three claims survive for anyone reading without images: which model is pinned to which lane, that exactly one implementer runs per delegation, and that a refusal leaves the filesystem untouched.

Verification

bun run validate link-checks image paths, so the embeds and the files are proven to agree — this is why the images could not be committed before the files existed.

bun run ci green: VERIFY PASSED three-role · 82 tests across 6 files, 0 fail · validate · sbom orrery-0.7.0.cdx.json (18 packaged files, 0 runtime dependencies) · release-check.

Risk

Documentation and image assets only. No code, no behaviour change.

The images `docs/images/README.md` has specified since the Astra release finally
exist: the constellation under "The four bodies", the delegation flow at the top of
"The flow", and the refusal proof closing "What it will not do".

Each was checked against the shipped repository rather than accepted on sight. An
earlier pass carried a FABLEWRIGHT wordmark and, in the proof image, two role
filenames and an install command that do not exist here — `orrery-sol-researcher.toml`,
`orrery-terra-ops.toml`, and `fw install`. Publishing that would have put a claim on
the front page that the shipped files contradict, which is precisely the failure
verify.sh exists to catch, and it would have done so under the words "LAUNCH PROOF".

The version committed here uses the real command,
`sh plugins/orrery/scripts/install-agents.sh --target-dir ~/.codex/agents`, the
three real role filenames, and terminal output whose load-bearing lines were taken
verbatim from an actual run: the INSTALL PASSED line, the ERROR line naming the
Astra conflict, and exit 1. The narrower progress lines between them are a
readable dramatization of steps the installer genuinely performs — destination
classification, the legacy-Luna check, and the post-install exactness re-check —
rather than literal stdout.

Alt text describes the content rather than naming the file, so the three claims
survive for anyone reading without images: which model is pinned to which lane,
that exactly one implementer runs per delegation, and that a refusal leaves the
filesystem untouched.

Verification
`bun run validate` passes, which link-checks image paths, so the embeds and the
files agree. `bun run ci` green: 82 tests across 6 files, sbom orrery-0.7.0.
@DivyamTalwar
DivyamTalwar merged commit 310df75 into main Sep 5, 2026
4 checks passed
@DivyamTalwar
DivyamTalwar deleted the docs/readme-images branch September 5, 2026 09:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant