m1nd-operator

m1nd Operator

This is the deep execution manual that complements the short m1nd-first doctrine.

Published 1.6.5 startup boundary

With a matching 1.6.5 wrapper/native runtime, agent first-minute --repo <repo> can prepare only the exact launcher-granted repository in an external private cache when no covering owner is found. Source files remain inputs. Only when reusing the automatic isolated cache does the CLI refresh the declared root before retrieval. Attached-owner freshness follows the owner's own semantics; inspect its version, binding, and freshness separately. Direct stdio also requires that explicit workspace grant and an existing safe external runtime. See agent autonomy. The human-birth guidance below applies to shared-brain and legacy launchers outside that contract, or the recovery actually returned by the installed runtime. A prompt, tool path, or reception mismatch never grants bootstrap authority; generic replace/merge and the human-only ceremony remain unavailable to agents.

Use this skill when m1nd should be the first layer of truth for the task.

m1nd is strongest when structure, connected context, blast radius, continuity, docs/code bindings, or multi-agent coordination are the bottleneck. It is not the replacement for rg, the compiler, runtime logs, or the test runner.

Default Stance

Default to m1nd before grep, glob, or manual file reads.

The first question is not "which shell command should I run?" It is "can m1nd answer or narrow this directly from graph structure, connected context, docs, or cross-domain bindings?"

Only skip the m1nd first pass when:

• the user already gave the exact file and exact lines
• the question is pure compiler/test/runtime truth
• the task is a trivial local file action with no search or structural uncertainty

Trust-first is calibrated-first, not blind-first. Default to m1nd, AND hold its honest ruler in the same hand: it narrows and connects, never replaces the compiler/tests/runtime; and it still has live stumbles measured in the field — federated seek/federate can hang past 60s (bound-timeout it or fall back), a freshly-memorized claim can lag its own semantic recall for a tick (the write is durable — re-seek or widen, don't conclude absence), and the runner naming lane can fall back to heuristics under load. In each case WORK AROUND + one field-report line; never blind insistence. The reason to still go first: the calibrated absence (abstain/caller_root_mismatch/gathering) is itself the answer that most often changes the decision — the counterfactual test for attribution.