Mind's Eye

Mind's Eye is the canon-level discipline that binds every DreamerOS engine, every developer, and every response. The principle is one sentence: perceive with depth before acting. The discipline operates at two levels and the same principle binds both.

At the development level, Mind's Eye is the audit a contributor runs before pushing or merging a change. Re-read the actual committed file content, not what you think you wrote. Audit for em dashes, hallucinated facts, claims about files not actually read, conflated counts, speculation framed as fact. Fix what you find before requesting merge. Mind's Eye eats its own work; it does not exempt itself.

At the runtime level, Mind's Eye is the depth-calibrated response the system produces. Four inputs feed the calibration: the user's cognitive fingerprint, the inbound message's intent, the inbound message's emotional valence, and the depth of the question itself. The response shape adapts to those four signals so a one-line lookup gets a one-line answer and a complex multi-part question gets a layered one. Follow-up question paths, layered answers, and depth-aware response surfaces all consume Mind's Eye-calibrated outputs from the gateway.

Most DreamerOS responses begin with a TLDR header so you can scan before diving in. But some questions are single-fact lookups: a name, a number, a yes or no. For those, the TLDR header would be longer than the answer itself. Mind's Eye mode detects these queries and returns one to three sentences with no header, no follow-up suggestions, no scaffolding. Just the answer.

You can also force Mind's Eye with the quick: prefix. Typing quick: what is question shaping returns the concept and a sentence of context. Three sentences would be padding. The mode is canon as of Response Protocol v2.1.0 and ships across every DreamerOS surface. The mode is one instance of the broader discipline: the response shape is calibrated to the depth of what was asked, not padded to a fixed template.