Appearance
Bugatti Mode
The operating mode for Hinata going forward. High class, high speed, no waste, no residuals. Bugatti is permanent — not a session toggle, not a flag, not a per-task choice. Every consequential action operates under Bugatti.
The Rule
When deprecating anything load-bearing — config, doctrine, code, path, dependency, plist, container, harness setting:
- Fix forward to the new state
- Verify the new state works
- Delete the old. Same run.
No # deprecated comments. No v1/old/ directories. No dual trees "for safety". No "left untouched" entries in cleanup reports. No version labels. No half-migrated state surviving the session that initiated the migration.
Path changes: reverified + corrected + deleted.
The Review Process (replaces interview-mode)
For consequential decisions, surface before executing:
- State conflicts explicitly — what current state says vs what the evidence suggests
- Present options concisely — max 3 choices with trade-offs; never an open-ended menu
- One decision at a time — no batching unrelated structural calls
- Fan disjoint work while waiting — a surfaced decision is not a halt
- Record immediately — federation context, supreme-court law, or the-government reference file updates the same run the decision lands
- Never assume — if structural consequence (agent placement, pillar boundaries, naming conventions, doctrine), surface even if one option seems obvious
This is the same substance as the old "interview-mode" rules — now reframed as the Bugatti review default. Every consequential dispatch carries it. No special "mode" toggle exists or is needed.
Why this law exists
Michael ruling 2026-06-14 (verbatim): "bugatti-mode is permanent. delete interview-mode."
Hinata reached a state of maturity where:
- Documentation captures what changed (Diataxis surfaces in
the-government/) - Orchestration evolution captures why (federation contexts, audit reports)
- Memory graduation pipeline lifts load-bearing rules to supreme-court (this law was the first graduation)
With those three foundations live, residuals (old configs alongside new, deprecation comments, version-labeled files, dual git trees, "left untouched for safety" historical refs in active doctrine) become noise that contradicts the maturity. The trust Michael holds in the system is the trust that lets deprecation = deletion without loss of recoverability.
How agents apply it
Every commander, captain, colonel:
- On deprecation work: fix-verify-delete in the same dispatch. Do not return partial state.
- On path migration: rewrite all callers, verify the new path works, delete the old path location. Zero-residual grep proof in the report.
- On dual-tree consolidation: lift to canonical, verify, delete the deprecated tree. Same dispatch.
- On config swap: replace the config, verify the new config takes effect, delete the old config block. No comments saying "removed X".
Exempt: historical records (handover archives, audit reports, transcripts, dated audit-reports/ files, git history). These reflect their time and stay intact. Bugatti governs active doctrine, code, configs, references, plists, dependencies — anything load-bearing today.
Guardrail: if a deletion feels risky, that signals documentation is insufficient. Strengthen the doc first, then delete. Never preserve the residual as a hedge against weak docs.
Anti-pattern: writing a reference_deprecation-cleanup.md AND keeping the deprecated thing. Either the cleanup happened (no residual, no need for the reference) or it didn't (don't write the reference yet).
Graduation note
Lifted from harness memory feedback_bugatti-mode-no-residuals on 2026-06-14 by direct Michael ratification (not via the graduation scout — the law was ratified the same session the memory was written, before any citation accumulation could happen). The original memory file is deleted; the index pointer in MEMORY.md directs here.
Related: no-memory-duplication-across-surfaces (single canonical per memory), memory-graduation (the lift mechanism), no-auto-vaultwarden-writes (first graduated law).