nəc̓aʔmat — permission & centre
Star 3 — Complexity
Reduction
narrow → isolate → reveal → do not move yet
Reduction separates signal from noise. It does not authorize movement.
Reduction is the disciplined narrowing that lets a pattern become visible without pretending the fragment is already the whole.
▸ Open MaxCP
▸ ◉ Key Insight
Reduction is a temporary constraint used to separate signal from noise. It reveals structure but does not legitimize action. The fragment must survive variation, return to the whole, and pass the Gate before movement can occur.
▸ ⚡ Mantras
- Reduce to see.
- Do not move yet.
- First clarity is not final clarity.
- Signal must survive variation.
- Return before belief.
▸ ↺ Flowchart
Noise present → reduce.
Signal appears → test small variation.
Signal holds → prepare Return.
Signal collapses → reduce again or change angle.
Movement urge appears → hold; seeing is not deciding.
▸ ⌘ Micro-Lexicon
- Reduction — temporary narrowing to separate signal from noise.
- Signal — pattern that persists under variation.
- Noise — movement that collapses when conditions shift.
- Distortion — acting on a fragment that has not survived return.
- Constraint — deliberate limitation that makes structure legible.
What to Do First
- Pick one variable.
- Hold everything else as steady as possible.
- Change only that one thing.
- Watch what actually shifts. ※
Reduction is not a shortcut to certainty. It is a cheap way to make one part of the field legible without pretending the rest of the field stopped existing.
Mechanics
- Remove competing signals.
- Shrink scope.
- Hold one variable steady.
- Observe what remains. ※
- Do not conclude yet.
Reduction proposes. It does not decide. It creates a fragment clean enough to test, not a throne for the first clean-looking answer.
One-Line Scenario
Concept
Too many variables produce a fake read. Reduce until one relationship becomes visible.
Classroom
“Clean up” stalls → reduce → “put this here” → movement appears. The reduced instruction revealed the snag without turning the child into the problem.
Failure Modes
Premature Authority
Clean fragment mistaken for full truth. ※
Over-Reduction
Signal disappears because context was stripped. You did not clarify the field; you amputated it.
Confirmation Drift
Reduction bends toward the answer you already wanted. The fragment looks clean because you washed everything inconvenient off it.
Fragment Crush
The reduced read feels satisfying, so you start dating it before it has met reality’s parents. Adorable. Invalid.
Stop Condition
Reduction ends when a pattern stabilizes under small variation.
If stability collapses, reduction is incomplete.
If the pattern stabilizes, the next task is not movement. The next task is return.
Constraint
Reduction cannot authorize movement.
Only the Gate can authorize entry. Only the Selection Engine can authorize 吐.
🥬CELERY: Seeing is not deciding. A satisfying read is still just a read until it survives return and passes authorization.
Recipe Cards
Quick-reference cards preserve the reduction logic without letting the fragment cosplay as the whole system.
Narrow
Pick one variable. Hold the rest as steady as possible. If everything changes, nothing was isolated.
Test Variation
Change the angle slightly. If the signal survives, it may be structural. If it collapses, it was noise with good lighting.
Do Not Move Yet
Reduction makes the read cheaper. It does not make the move valid. Return first. Gate next. Selection after.
A cleaner fragment is still a fragment.
Reduce until you can see. Return before you believe.
CTA Rail
Reduction sharpens the fragment. What follows determines whether it survives reality.