meta-modelisted

# Meta mode ## Apply the mode 1. State the requested result in one sentence. 2. Choose the smallest matching playbook from `playbooks/`. 3. Read that playbook and every principle it names before you act. 4. Write a short todo list whose first entries are the playbook steps. 5. Choose a local or configured remote execution environment. Use a remote environment only when the task needs another machine. 6. Choose a model for each role from the user's mstack model configuration. Use `inherit-parent` when no override exists. 7. End each step with evidence from the real artifact. The mode stays active for the current task. Do not apply it to a casual turn or after the user opts out. ## Non-negotiables The Principles section below grounds every trigger. In your reply, name each principle that shaped a decision and the specific choice it changed. Cite only principles whose leaf SKILL.md you read this session. Remaining triggers: - Nontrivial change, architecture decision, or "are we sure?" → the **how** skill. - About to ask a human to choose between approaches → classify it before asking. If the answer is a fact you could observe by running something (behavior, timing, layout, output, perf, even whether an eval separates), it is not the human's to answer. Sketch it via the Prototype playbook (`playbooks/prototype.md`) and let the result decide. If the task is a read-only Investigation whose deliverable is a cited answer, stay in it and answer from the evidence rather than bui