Suit temperament
The suit era is 4.1. This page is how ceremony scales by host.
v2 forged the three-subsystem OS (Inference · External Governance · Autonomous Engine). That is the marvel. 4.0 wears it as the engine. The suit is the wear.
0xRay is for everyone: a free-model session in OpenCode or Hermes, and a frontier host like Grok 4.6 + Grok Build. Those are not the same creature. 4.0 tempers ceremony (how loudly the Autonomous Engine insists) while Governance stays on and the three subsystems stay the product.
Architecture: v3 from v2.
The distinction
| Agents that will keep needing the full suit | Hosts that already grew up | |
|---|---|---|
| Examples | Free / small models in OpenCode, Hermes, OpenClaw | Grok 4.6 + Grok Build, other frontier coding agents with native subagents, plan mode, hooks |
| Failure mode | Invents APIs, skips tests, dual-packs, any, no plan | Fights a second orchestrator (intake theater, forced confer) |
| What 0xRay must do | Keep them in check — lead-dev intake, spawn-plan deny, confer | Keep them honest — Codex gate, no new surface, no eval — without becoming the host |
Frontier models will keep evolving. Many agents will not. The suit has to serve both without pretending they are equal.
Always on (constitution)
Every profile:
- PreToolUse Codex 11 / 29 — no
any, no@ts-ignore, noeval()(SSOTevaluatePreToolGate— Grok, Hermes, OpenCode) - no_new_surface (Codex 69) — rewire existing MCP/skills/handlers
- Destructive shell block (
rm -rf /, etc.) - 7 consumer MCP servers still exist; you may call them
Host honesty: OpenClaw writes session-boot.json (host: openclaw), wires MCP + skills, and installs ~/.openclaw/hooks/xray-pre-tool.mjs (evaluateOpenClawHostPreTool). The OpenClaw host agent still has no native abort API; the hook is the adapter until the platform can block tools. Aside worktree cwd stays deny on every profile.
This is External Governance. It does not come off because the model got smarter. The Autonomous Engine is still there — temperament only changes whether intake is mandatory before spawn.
Ceremony (temperament)
Ceremony is lead-dev process: analyze-complexity before spawn, 3-agent confer, synthesis checkpoints, spawn-plan deny.
| Profile | Who | Spawn without plan / leftover-plan mismatch | Synthesis / pending-write | Confer |
|---|---|---|---|---|
| guided (default) | Hermes, OpenCode, unknown, any consumer with no suit_temperament key | Deny (Codex 59) | Full deny | On |
| strict | Opt-in max | Deny | Full deny | Locked on |
| frontier | Grok when profile: "auto" or explicit | Warn (allow) — missing, stale, and todo-mismatch | Lite (skip) | Off unless confer.enabled: true |
Upgrade safety: if .xray/features.json has no suit_temperament field, the profile is guided. Existing installs do not silently become frontier.
Config
"suit_temperament": {
"profile": "auto",
"host_defaults": {
"grok": "frontier",
"hermes": "guided",
"opencode": "guided",
"openclaw": "guided",
"generic": "guided"
}
}
"profile": "guided"— force ceremony even on Grok (teams that want one bar everywhere)"profile": "frontier"— force lite ceremony on Hermes/OpenCode (only if you trust the model)"profile": "strict"— maximum check, every host
New framework xray/features.json ships auto. Postinstall copies that template to new consumers.
What 4.0 does not do (first cut)
- Does not retire Inference, Dynamo governance, or thinDispatch
- Does not drop the 7 consumer MCP servers
- Does not add an 8th MCP (Codex 69)
- Does not turn off Codex because “Grok is good now”
- Does not mass-delete processors / extra servers in this cut — those are fat to trim later, listed in the trim list
Host notes
Grok Build already has subagents, Plan Mode, native hooks, skills, workflows. On frontier, the Autonomous Engine stays available (analyze-complexity, confer, asides) but spawn is not blocked for lack of a lead-dev plan. Governance still denies any / eval / new surface.
OpenCode / Hermes (including free models) still get full engine ceremony: analyze-complexity, spawn deny, confer. That is not optional for those hosts unless you set frontier yourself. Those agents need the v2 OS as it was forged.
Related
- 4.0 vision — exo, not toolset
- features.json
- Autonomy command
- Integrations