Skip to content

docs: rescope userlevel plugin dispatch around SSOT #25 (PR 1/5)#3

Open
shaun0927 wants to merge 2 commits into
Q00:release/bootstrapfrom
shaun0927:docs/userlevel-plugin-dispatch
Open

docs: rescope userlevel plugin dispatch around SSOT #25 (PR 1/5)#3
shaun0927 wants to merge 2 commits into
Q00:release/bootstrapfrom
shaun0927:docs/userlevel-plugin-dispatch

Conversation

@shaun0927
Copy link
Copy Markdown

@shaun0927 shaun0927 commented May 23, 2026

Summary

PR 1 of the five-PR plan that delivers ooo <plugin> <command> ... dispatch under SSOT #25.

This is a docs-only rescope. It updates docs/userlevel-plugin-dispatch.md so that:

No runtime code changed.

Five-PR plan summary

PR Closes Scope
PR 1 (this) #4 #6 #12 #13 #14 Docs + issue hygiene
PR 2 #5 #8 #9 #18 #27 #29 Ourocode.Plugin.UserLevel.{Capability, Discovery, Registry} + OuroborosCLI adapter + Command.Registry plugin source wiring
PR 3 #16 #23 Ourocode.Plugin.UserLevel.{PreflightResult, Resolver} + router :user_level_plugin route
PR 4 #15 #17 (minimal) #20 #21 Ourocode.Runtime.UserLevelPluginInvocation + preflight panel + Superpowers E2E
PR 5 #7 #10 #11 #26 #28 ArtifactWatcher + Continuation policy + DecisionJournal

Umbrella restatement issues #4, #6, #12, #13, and #14 share the same vision as #25 and are auto-closed on merge of this PR. Vision issues #19, #22, #24 are intentionally deferred with trigger conditions; see the updated document for details.

Closes #4
Closes #6
Closes #12
Closes #13
Closes #14

Why

Five teammates picking up the work need one shared framing. Without this rescope, each later PR has to repeat "which umbrella am I closing" and the umbrella issues stay open even though they say nothing the SSOT doesn't already say.

Testing

  • Docs-only change. No code paths touched.
  • Local Elixir toolchain unavailable in the authoring environment; CI is the source of truth for any later code PRs.

🤖 Generated with Claude Code

shaun0927 and others added 2 commits May 25, 2026 16:53
Constraint: Ourocode v0.1.8 has core ooo routing but not generic UserLevel plugin dispatch.
Rejected: Treat superpowers as a one-off shell command | would bypass the Ouroboros plugin firewall and not generalize.
Confidence: high
Scope-risk: narrow
Directive: Keep plugin execution routed through Ouroboros trust and firewall boundaries; do not auto-grant plugin scopes.
Tested: git status; documentation-only change reviewed locally.
Not-tested: Elixir test suite not run because this PR only adds design documentation.
Re-anchor the userlevel plugin dispatch document on the orchestration
SSOT (Q00#25) and docs/product-vision.md, replacing the implementation
phasing section with the five-PR breakdown that this document drives.

Notes the existing read-only slash-command CapabilityPreflight as the
sibling layer that already handles /<plugin> input, and scopes this
document to the ooo-prefixed dispatch path that is still missing.

Records the deferred vision issues (Q00#19, Q00#22, Q00#24) with their trigger
conditions so they stay open without blocking implementation work.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment