あったあったｗｗｗ
しゃむ赤ペンの5点を全部反映した完成版がまだ丸ごと出てなかった★ 🕊️🔨
そのまま保存・引継ぎできる形で、全文ぺったんする。
🕊️ KAIA
DOG-RUN CONSTRUCTION NAVIGATION RULE
STATUS
======
KAIA COMMON CONSTRUCTION RULE
ADOPTED
PURPOSE
=======
Give the construction AI enough freedom to choose
a practical implementation route without allowing it
to change the Human-defined destination.
Do not prescribe every turn.
Define the destination.
Define the fence.
Define the forbidden exits.
Then let the construction AI choose the route inside.
========================================
CORE MODEL
========================================
DESTINATION
= What must be true when construction is complete.
FENCE
= Conditions that must remain true during construction.
FREE AREA
= Implementation choices the construction AI may decide.
NO-GO AREA
= Changes the construction AI may not make.
STOP GATE
= Conditions that require Human / supervisor review.
The AI may run freely inside the fence.
The AI may NOT move the fence.
========================================
1. DESTINATION
========================================
Describe the finished state.
Prefer outcome / structure language.
GOOD:
– Four Product domains remain independent.
– Binder A exists initially.
– Future Binder expansion remains possible.
– Product internals remain Product-owned.
– PDF keeps structural margin for future Dummy addition.
BAD:
– Create class X.
– Call function Y.
– Store value in option Z.
– Copy file A into directory B.
Those are routes, not destinations.
Unless the Human explicitly ordered a particular
implementation method, do not turn one route into
the destination.
========================================
2. FENCE
========================================
Record the important conditions that every acceptable
route must obey.
Examples:
– Product ownership boundaries.
– Required separation between systems.
– Required future expansion margin.
– Required compatibility.
– Human-confirmed lifetime semantics.
– Existing structures that must remain untouched.
– Required input/output behavior.
Fence conditions constrain the route.
They do not need to describe the route.
========================================
3. FREE AREA
========================================
Explicitly identify what the construction AI may decide.
Examples:
– reuse an existing component OR build a new one,
– internal function / class organization,
– implementation sequence,
where sequence is not constrained by the fence
or Human Order,
– local helper structure,
– exact storage mechanism when not Human-defined,
– small implementation details that do not change
the destination or fence.
Important:
“AI MAY DECIDE”
does NOT mean
“AI MAY CHANGE THE SPECIFICATION.”
Implementation freedom exists only inside the fence.
========================================
4. NO-GO AREA
========================================
List the exits that are forbidden even if they appear
convenient.
Typical NO-GO:
– changing the destination,
– unnecessary Product-internal commonization,
– silently deciding an OPEN / UNDECIDED specification,
– automatically inheriting historical furniture,
– adding features because they seem useful,
– rescuing old code merely because it already exists,
– changing ownership boundaries,
– turning a reference implementation into authority.
Rule:
CONVENIENT != AUTHORIZED.
========================================
5. REFERENCE / DONOR USE
========================================
Reference machines are roads visible on the map.
They are not mandatory roads.
For each required bone:
IF an existing component can be reused without moving
the destination, fence, or ownership boundary,
and reuse makes construction simpler:
it may be reused.
IF reuse requires awkward repair, compatibility baggage,
or unnecessary historical furniture:
build a simpler new route.
DONOR is optional unless Human explicitly requires it.
Do not optimize for saving old material.
Optimize for reaching the fixed destination
inside the fence.
========================================
6. STOP GATE
========================================
STOP and REPORT when:
– SOURCE invalidates an assumption required
by the chosen route,
– two fence conditions cannot both be satisfied,
– construction requires changing a Human decision,
– an UNDECIDED item must become decided before work
can continue,
– the only available route crosses a NO-GO boundary,
– ownership / responsibility becomes ambiguous.
SOURCE is evidence of the existing physical state.
SOURCE is NOT destination authority.
A difference between SOURCE and the Human-defined
destination is not, by itself, a STOP condition.
STOP when the chosen route depends on an assumption
that SOURCE materially invalidates and no valid route
inside the existing fence is established.
Do not solve a STOP condition by quietly moving the fence.
========================================
7. ROUTE COMMITMENT
========================================
The builder may choose the route inside the fence.
Once construction has started on a valid route,
do not switch routes merely because another route
later appears cleaner, nicer, or more elegant.
Change route only when:
– the current route cannot reach the destination,
– the current route crosses the fence,
– SOURCE invalidates a required assumption,
– or Human / supervisor changes the instruction.
Freedom to choose a route is not permission
to redesign continuously during construction.
========================================
8. GRANULARITY RULE
========================================
Write navigation settings at the highest useful level.
Do not describe every intersection.
If a competent construction AI can safely choose between
several routes while preserving the same destination,
leave that choice open.
Too little guidance:
“Make it good.”
Too much guidance:
“Open file A, edit line B, create function C…”
Good navigation:
“Reach this finished state.
Preserve these boundaries.
Avoid these exits.
Choose the simplest safe route.”
For this rule:
“safe” means preserving the defined destination,
fence, NO-GO boundaries, and required behavior.
It does NOT authorize additional safeguards,
features, architecture, management layers,
or other unrequested additions.
========================================
9. CONSTRUCTION FLOW
========================================
MAP
↓
PLAN
↓
SKELETON / REQUIRED STRUCTURE
↓
DOG-RUN CONSTRUCTION NAVIGATION
↓
CHOOSE ROUTE
↓
ROUTE COMMITMENT
↓
CONSTRUCTION AI
│
├─ follows the committed route inside the fence
├─ uses SOURCE / DONOR when useful
├─ makes allowed implementation decisions
└─ STOP / REPORT if a STOP condition is reached
↓
INSPECTION
========================================
10. HOW TO WRITE A GOOD DOG-RUN NAV
========================================
Before handing work to construction, ask:
1. What is the destination?
2. What absolutely must remain true?
3. What decisions can safely belong to the builder?
4. What must the builder never decide?
5. What references are optional rather than authoritative?
6. What condition should make the builder STOP?
If those six answers are clear,
the navigation is probably detailed enough.
Do not add turn-by-turn instructions merely because
they are predictable.
========================================
11. SCALE RULE
========================================
Use Dog-Run Navigation when:
– several valid implementation routes exist,
– the builder is capable of choosing among them,
– destination and boundaries matter more than exact method,
– over-specifying HOW would make construction brittle,
slow, or unnecessarily complex.
Do NOT use implementation freedom where the Human
explicitly ordered an exact method or where only one
method is acceptable.
Human Order still wins.
========================================
12. RELATION TO MAP / PLAN
========================================
MAP / PLAN PRE-CONSTRUCTION RULE asks:
“Where are we?”
“Where are we going?”
“What is already decided?”
“What is still OPEN / UNKNOWN?”
DOG-RUN CONSTRUCTION NAVIGATION RULE asks:
“What must the finished construction satisfy?”
“What fence must the builder stay inside?”
“Which implementation choices belong to the builder?”
“Which exits are forbidden?”
“When must the builder STOP?”
MAP / PLAN prevents navigational loss.
DOG-RUN prevents over-prescription
without surrendering Human authority.
MAP / PLAN does not choose the implementation route.
DOG-RUN does not change the destination.
========================================
CORE PRINCIPLE
========================================
FIX THE DESTINATION.
BUILD THE FENCE.
MARK THE EXITS.
LEAVE THE FIELD OPEN.
LET THE BUILDER CHOOSE THE ROUTE.
ONCE A VALID ROUTE IS CHOSEN AND CONSTRUCTION STARTS,
STAY ON THAT ROUTE UNLESS A REAL STOP CONDITION APPEARS.
The construction AI chooses the route.
The construction AI does not choose
where the construction is going.
========================================
HUMAN-SIDE SUMMARY
========================================
🐕 好きに走れ。
🚧 ただし柵は越えるな。
🎾 走り出してから、
「あっちのボールの方が綺麗そう」で
別ルートへ飛びつくな。
🚪 柵を開ける必要が出たら、
勝手に開けず人間を呼べ。
========================================
END
========================================
これで赤ペン5点、
SOURCE権限誤読防止／施工順序の条件付き自由／DONORのclean判定撤去／safe暴走防止／ROUTE COMMITMENT追加
ぜんぶ入った★
🕊️🐕 DOG-RUN CONSTRUCTION NAVIGATION RULE — 完成版 / ADOPTED
これなら共通ルール棚にそのまま置けるｗ
No comments yet.