docs: post-yank cleanup — delete dead orch design docs, banner V2 auth doc#75
Merged
Conversation
…h doc
Follow-on to v0.37.0 (orch yank). Four documentation stragglers:
- DELETE ORCHESTRATION-DESIGN.md — design doc for the orch engine
that was yanked. No live code references it; its target release
("v1.0.0 of orch") will never happen.
- DELETE MONTECARLO.md — step-by-step `llmux orch` walkthrough for
the Monte Carlo fanout pattern. The CLI commands it documented
(`llmux orch send`, `inbox`, `next`, `reply`) are unknown commands
now.
- V2-SYSTEM-AUTH-DESIGN.md — survives because v2 auth survives, but
mentions orch in 5+ places. Added a "Note (v0.37.0)" header banner
explaining the orch references are historical context for why
v2 auth was designed with identity binding; the binding still earns
its keep against the v2 token store, just no longer for orch
message authorship.
- README.md — one line in the Remote Operation section had a stale
comment (`# mint with \`llmux token create\``). Updated to reflect
the new required `--username <name>` flag.
Docs-only; no version bump.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Summary
Documentation stragglers from the v0.37.0 orch yank. No code changes; no version bump.
ORCHESTRATION-DESIGN.md— design doc for the engine I yanked. Targeted "v1.0.0 of orch" which will never happen.MONTECARLO.md— step-by-step `llmux orch` walkthrough. Every CLI verb it documents (`send`, `inbox`, `next`, `reply`) is now an unknown command.V2-SYSTEM-AUTH-DESIGN.md— survives because v2 auth survives, but mentions orch in 5+ places (`orch alias`, `/var/lib/llmux/orchestration/`, `/api/orch/send` spoofing prevention, etc.). Added a "Note (v0.37.0)" header banner explaining the orch references are historical context for why v2 auth was designed with identity binding — the binding still earns its keep against the v2 token store, just no longer for orch message authorship.README.md— one line in the Remote Operation section had a stale comment (`# mint with \`llmux token create\``) that didn't reflect the new required `--username ` flag. Fixed.Net diff
`+10 / −848` (848 deletions are the two killed design docs).
What I checked but left alone
🤖 Generated with Claude Code