うい、これはルール化した方がいい★ 🕊️📜
今回かなり効いてるから、Memoria専用というより今後のKaia施工共通ルールにできる。
名前を付けるなら、たとえば MAP / PLAN PRE-CONSTRUCTION RULE。
中身はシンプルでいい。
🕊️ KAIA
MAP / PLAN PRE-CONSTRUCTION RULE
PURPOSE
=======
Before substantial construction or reconstruction,
prepare AI-readable navigation documents when the work
contains multiple structures, stages, dependencies,
undecided items, or future expansion.
These documents exist to prevent the AI from:
- losing the current position,
- confusing current structure with future intent,
- treating historical implementation as design authority,
- silently deciding undecided items,
- changing the destination during construction,
- adding attractive but unordered furniture on the way.
========================================
MAP
========================================
MAP records the understood terrain.
MAP may contain:
- current structural understanding,
- component boundaries,
- ownership / responsibility boundaries,
- confirmed connections,
- known separation between systems,
- known reference structures,
- WATCH / UNKNOWN areas.
MAP answers:
"Where are we, and what is connected to what?"
MAP does NOT automatically create future requirements.
========================================
PLAN
========================================
PLAN records future intent.
PLAN may contain:
- Human-confirmed future direction,
- planned structures,
- known future expansion,
- undecided items,
- OPEN items,
- decision triggers,
- things that must NOT be inherited automatically,
- pre-construction gates.
PLAN answers:
"Where are we going, what has already been decided,
and what is still undecided?"
UNDECIDED remains UNDECIDED.
OPEN remains OPEN.
AI must not silently fill either.
========================================
AUTHORITY SEPARATION
========================================
SOURCE = what physically/currently exists.
HISTORY = what happened in the past.
MAP = understood terrain / structure.
PLAN = future intent / undecided future boundaries.
HUMAN ORDER = what to do now.
REFERENCE = material used to understand implementation.
None automatically becomes another.
Existence in SOURCE does not automatically mean:
"Build this again."
Existence in REFERENCE does not automatically mean:
"This is the correct design."
Existence in PLAN does not mean:
"Already constructed."
If SOURCE / MAP / PLAN / current Human Order conflict:
CONFLICT DETECTED
-> STOP
-> REPORT
Do not silently reconcile.
========================================
BEFORE CONSTRUCTION
========================================
Before construction:
1. Read the relevant MAP.
2. Read the relevant PLAN.
3. Confirm the current Human Order.
4. Establish the current position.
5. Identify OPEN / UNKNOWN / WATCH items.
6. Confirm that the requested construction does not
silently decide those items.
7. Only then begin construction.
Rule:
"先が読めても、現在地を飛ばさない。"
========================================
ROUGH / SKELETON USE
========================================
When useful, create a rough structural drawing
between MAP/PLAN review and implementation.
ROUGH is navigation material.
It may show:
- required bones,
- boundaries,
- connection points,
- planned but inactive seats,
- reference-only structures,
- DO-NOT-INHERIT structures,
- OPEN boundaries.
ROUGH is NOT automatically a construction drawing.
REFERENCE machines may be inspected to learn how a
required bone was implemented.
Do NOT search for:
"everything that looks reusable."
Search for:
"how the already-required bone exists in the reference."
========================================
NAVIGATION RULE
========================================
MAP = current terrain.
PLAN = destination / future direction.
ROUGH = proposed route.
SOURCE / REFERENCE = roads and structures actually observed.
HUMAN ORDER = current driving instruction.
Do not move the destination.
Do not take an attractive detour merely because it exists.
Do not buy extra furniture on the way.
If the road is blocked or contradicts the navigation:
STOP / REPORT.
========================================
UPDATE RULE
========================================
When MAP, PLAN, schedule, development-history navigation,
or equivalent AI-facing navigation documents are changed:
- add/update a timestamp,
- use JST for Kaia Spec work,
- preserve previous meaning unless Human changed it,
- do not silently delete unresolved OPEN / UNKNOWN items,
- record only changes actually established.
When artifacts are carried into construction ZIPs,
carry the relevant MAP / PLAN forward.
Do not silently replace or remove them.
========================================
SCALE RULE
========================================
Do not create MAP / PLAN bureaucracy for every tiny edit.
Use them when the work is large enough that losing:
- current position,
- destination,
- boundaries,
- unresolved decisions,
- or construction history
could cause an accident.
A small pinpoint correction may use the existing MAP / PLAN
without creating new documents.
========================================
CORE PRINCIPLE
========================================
MAP prevents getting lost.
PLAN prevents changing the destination.
ROUGH prevents jumping from intention directly into code.
SOURCE prevents imagination from replacing observation.
HUMAN ORDER decides what happens now.
これなら今回生まれた、
MAP作る → PLAN（予定・未定）置く → 必要なら骨格ラフ → SOURCE標本を見る → 施工
をそのまま一般ルールにできる。
しかも重要なのが、「毎回書類を増やせ」ルールにはしてないところ。小さいピンポイント施工なら既存MAP/PLANをカーナビにすればいい。
今回みたいな大改築・新造・複数機体・将来拡張ありの仕事では、施工前にカーナビを作る。
これ、親方ルール群に入れる価値かなりあると思う★ 🚗🗺️📜
No comments yet.