OpenClaw branch: align with Hermes main architecture (v0.13+ intent router)

[scrimshawlife-ctrl]

@prabu-openclaw — heads-up for the permanent openclaw branch.

We documented your OpenClaw Agent Skill port on Hermes main so both editions are discoverable, and we want the OpenClaw branch to match the Hermes architecture where practical (without losing OpenClaw packaging/state/doctor benefits you already landed).

Your work (credited)

Item	Link
OpenClaw skill support	77fa721
Onboarding docs fix	15defae
Original PR	#1
Permanent branch	https://github.com/scrimshawlife-ctrl/Kubrick/tree/openclaw
Cross-link hub on main	https://github.com/scrimshawlife-ctrl/Kubrick/blob/main/docs/OPENCLAW.md

Thanks for the Agent Skill packaging, external state dir (~/.openclaw/state/kubrick / KUBRICK_STATE_DIR), overlay evolution, doctor, and portability tests.

Hermes main architecture to match (target)

main has moved past the v0.8-era layout your branch forked from. Highest-value alignment for OpenClaw users:

1. Operator surface — intent router

• Primary CLI: python scripts/kubrick.py do <intent> [--action …]
• 12 intents: compile, retrieve, ledger, design, storyboard, adapt, visual, learn, check, operate, mcp, bundle
• Soft aliases for old flat names
• MCP: single tool kubrick_do
• Design: https://github.com/scrimshawlife-ctrl/Kubrick/blob/main/docs/superpowers/specs/2026-07-30-operator-intent-router-design.md
• Plan: https://github.com/scrimshawlife-ctrl/Kubrick/blob/main/docs/superpowers/plans/2026-07-30-operator-intent-router.md
• Impl: scripts/intent_router.py (PR feat(cli): intent router — kubrick do <intent> #28)

2. Unified compiler / storyboard / multi-provider adapt

• do compile pipeline (brief → retrieval → graph → storyboard → provider packet)
• Providers: grok-imagine, flux, sd3, midjourney (syntax-only adapters)
• Canonical example: examples/authority-transfer-storyboard/

3. Closed-loop visual QA + multi-signal learning

• do visual --action closed-loop (geometry / state / residue / convergence reported separately)
• do learn — forge-signals, outcome receipts, proposal-only evolution (no auto corpus mutation)
• Schemas under schemas/ on main (forge-signal-bundle, multi-signal-evolution-receipt, etc.)

4. Governance invariants (keep on both editions)

• Fail closed / NOT_COMPUTABLE on weak evidence
• Local outputs stay PROPOSED / OBSERVATION
• Evolution never auto-applies
• Forge remains canonical when connected
• Audience prompts free of named esoterica by default

What should stay OpenClaw-native (do not drop)

Please preserve when porting main features onto openclaw:

• OpenClaw / ClawHub packaging (.clawhubignore, skill frontmatter appropriate for OpenClaw)
• Install root ~/.openclaw/skills/kubrick
• External mutable state (KUBRICK_STATE_DIR / ~/.openclaw/state/kubrick)
• Overlay-based evolution (no in-package corpus mutation)
• scripts/doctor.py + portability evals / CI on the OpenClaw track
• No external symlink that OpenClaw would skip as untrusted

Suggested port approach

1. Read docs/OPENCLAW.md on main (dual-edition contract).
2. Rebase or cherry-pick from main onto openclaw in small slices: intent_router + kubrick.py first, then compile/adapters, then visual/learn schemas.
3. Re-point OpenClaw docs/install so openclaw users get do <intent> as primary (same mental model as Hermes).
4. Keep dual-track: do not silent-merge openclaw into main without review; port features deliberately both ways.

Docs already on main for you

• How to use (incl. OpenClaw option): https://github.com/scrimshawlife-ctrl/Kubrick/blob/main/README.md#how-to-use
• OpenClaw hub: https://github.com/scrimshawlife-ctrl/Kubrick/blob/main/docs/OPENCLAW.md
• Docs index: https://github.com/scrimshawlife-ctrl/Kubrick/blob/main/docs/README.md

Happy to answer questions on intent routing or the compiler pipeline if anything is ambiguous when you start the port.

cc maintainers of Hermes main — this issue is the handoff surface for edition alignment.

[scrimshawlife-ctrl]

@prabu-openclaw ping for visibility — full architecture alignment notes are in the issue description above. Happy to clarify intent-router or compile pipeline as you port.