Synesthesia

Mission

Use reversible sensory models to surface software structure, then translate every useful observation back into precise engineering implications and action.

The sensory layer is a diagnostic instrument, not evidence and not mandatory output style. For an accepted mapping/boundary admission, load $memory-source-notes before invoking run_memory_note_tool.

Core Contract

Always:

1. start from literal evidence: code, tests, logs, architecture, runtime behavior, user flow, or repository structure;
2. use only 2-4 modalities that illuminate the task;
3. keep mappings internally consistent;
4. mark uncertainty;
5. translate every useful metaphor into concrete technical meaning;
6. prefer directness over poetry;
7. execute code changes literally even when the lens informed the decision.