docs: add the three README images - #18
Merged
Merged
Conversation
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The images
docs/images/README.mdhas specified since the Astra release now exist.constellation.pngflow.pngrefusal.pngEach 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:
orrery-sol-researcher.tomlorrery-sol-reviewer.tomlorrery-terra-ops.tomlorrery-terra-implementer.toml$ fw installPublishing that would have put a claim on the front page that the shipped files contradict — the exact failure
verify.shexists 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: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 validatelink-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 cigreen:VERIFY PASSEDthree-role · 82 tests across 6 files, 0 fail · validate · sbomorrery-0.7.0.cdx.json(18 packaged files, 0 runtime dependencies) · release-check.Risk
Documentation and image assets only. No code, no behaviour change.