nəc̓aʔmat — permission & centre
7 Star Doctrine active
Pattern Carry
Load → merge → enter
You do not need to start from zero. What has already held can be carried forward and used again.
▸ Open MaxCP (click here for more)
▸ ◉ Key Insight
Movement does not need to be rebuilt each time. Patterns that hold can be carried forward and reused.
Condition
Only patterns that hold across attempts should be carried.
One Line
Do not start from zero if you do not have to.
▸ ⚡ Mantras
- Only what holds gets carried.
- Past informs. Present decides.
- No blind replay.
- One move is enough.
▸ ↺ Flowchart
Need to act? → Read the field.
Recognize pattern? → Load prior loop.
Fits current state? → Merge.
Does not fit? → Discard.
Aligned? → Enter once.
▸ ⌘ Micro-Lexicon
- Pattern Carry — reuse of confirmed loops that hold across attempts.
- Confirmed Loop — a pattern that consistently produces movement.
- Load — recall of a prior working pattern.
- Merge — adapting a carried pattern to current conditions.
The Shift
Beginners try things.
Developing operators remember things.
Experienced operators recognize patterns.
Mechanism
- Seed patterns in low-cost conditions
- Confirm what holds
- Store as shared language
- Load during read
- Merge with present
- Enter once
Constraint
Bad reps create bad carry.
If a pattern does not hold, it must not be reused.
Result
You stop guessing.
You stop rebuilding.
You begin selecting.