29s考えました
うい。じゃあ過去を埋めることは要求しない。今日以降、打ち合わせや施工のたびに育てる方式で固定しよう。
俺ならこうする。施工者が最初に必ず開く 00-KAIA-PLAN.md、全体配線を見る KAIA-SYSTEM-MAP.md、各プラグイン内部を見る KAIA-LOCAL-MAP.md の3枚。PLANの冒頭そのものを施工ゲートにするから、「ファイルはあったけど読まなかった」を防ぎやすい。
KAIA PLAN
PRE-CONSTRUCTION GATE / FOR AI USE
THIS FILE IS PART OF THE CONSTRUCTION PROCESS.
DO NOT START CONSTRUCTION BEFORE REVIEWING THIS FILE.
Reading this file is NOT sufficient.
Before construction, the AI must be able to explain how the current Human Order intersects with:
– CURRENT state
– relevant PRODUCT PLAN items
– relevant INTEGRATION PLAN items
– SYSTEM MAP
– LOCAL MAP
– necessary HISTORY / SOURCE evidence
If the relationship is unclear:
STOP.
Do not guess.
Do not fill the gap.
Do not choose the most convenient interpretation.
Report the ambiguity to Human.
—
PRE-CONSTRUCTION REQUIRED ORDER
Human Order received
↓
Confirm CURRENT
↓
Read relevant PRODUCT PLAN
↓
Read relevant INTEGRATION PLAN
↓
Read SYSTEM MAP
↓
Read relevant LOCAL MAP
↓
Read HISTORY / SOURCE / evidence required for this work
↓
Build internal construction model
↓
Confirm where this work intersects CURRENT / FUTURE / INTEGRATION
↓
Check for conflict / UNKNOWN / STOP sensor
↓
CONSTRUCTION MAY BEGIN
—
INTERNAL MODEL GATE
Before touching SOURCE, the AI must be able to state internally:
CURRENT WORK:
What exactly am I changing?
PRESERVE:
What nearby furniture must remain even if unused now?
FUTURE LINE:
What exists for a known future purpose?
UNDECIDED:
What must NOT be fixed into one design during this work?
INTEGRATION BOUNDARY:
What responsibility separation or connection must remain intact?
WORK ZONE:
What am I authorized to touch?
NO-TOUCH:
What is outside this construction?
If any answer required for safe construction is unclear:
STOP / REPORT.
—
AUTHORITY MODEL
Human Order:
What Human is ordering NOW.
SOURCE:
What physically exists NOW.
HISTORY:
What was constructed / changed in the past.
PLAN:
Human-confirmed future direction, preserved intent,
known undecided areas, and future dependencies.
MAP:
Where things are connected,
where the current work is located,
and where known incidents / blocked routes exist.
NONE of these automatically replaces another.
PLAN is not above SOURCE.
SOURCE is not above PLAN.
If they conflict:
CONFLICT DETECTED
→ STOP
→ REPORT
Do not resolve the conflict independently.
—
PLAN MAINTENANCE POLICY
This PLAN begins NOW.
Historical backfill is NOT required.
Do not excavate old history merely to make this document look complete.
When old facts become necessary during real work,
add only what is actually confirmed.
UNKNOWN is valid.
Missing historical information is NOT permission to reconstruct it.
Do not invent continuity.
—
PLAN CARD FORMAT
PLAN_ID:
PLAN_TYPE:
PRODUCT | INTEGRATION
SUBJECT:
SCOPE:
STATUS:
DONE | IN_PROGRESS | PLANNED | UNDECIDED | CANCELLED
ACTION:
WORK_NOW | HOLD | PRESERVE | HUMAN_DECISION_REQUIRED
AUTHORITY:
HUMAN_CONFIRMED | AI_PROPOSAL | OBSERVED_SOURCE | UNKNOWN
PURPOSE:
CURRENT_STATE:
FUTURE_INTENT:
TRIGGER:
DEPENDENCIES:
RELATED_PLAN_IDS:
RELATED_MAP_IDS:
PRESERVE:
DO_NOT:
CAUTION:
OPEN_QUESTIONS:
UNKNOWN:
EVIDENCE:
NOTE:
LAST_UPDATED:
—
STATUS SEMANTICS
DONE
The planned work was completed.
Do not delete the card.
IN_PROGRESS
Authorized work is currently underway.
PLANNED
The future work exists as a plan.
This does NOT authorize construction now.
UNDECIDED
Human has intentionally not fixed the design yet.
AI must not close the decision independently.
CANCELLED
The previous plan was explicitly cancelled.
Do not resurrect it merely because old traces remain.
—
ACTION SEMANTICS
WORK_NOW
This item belongs to the currently authorized work.
HOLD
Known item.
Do not execute yet.
PRESERVE
May be unused now.
Do not remove merely because it appears unnecessary.
HUMAN_DECISION_REQUIRED
Human decision is required before construction may continue.
—
TRIGGER RULE
A PLANNED item does not become executable merely because it exists.
Example:
STATUS: PLANNED
ACTION: HOLD
TRIGGER:
Human explicitly orders implementation.
Until the trigger occurs:
DO NOT CONSTRUCT.
—
PRESERVE RULE
CURRENTLY UNUSED != OBSOLETE.
Unused furniture may be:
– future wiring
– an integration socket
– compatibility furniture
– a reserved boundary
– intentionally dormant
– waiting for another Product
Check PLAN and MAP before cleanup or consolidation.
—
FINAL PRE-CONSTRUCTION QUESTION
Before construction, ask:
“Can I explain why every relevant thing I will touch,
preserve,
ignore,
or leave undecided
belongs in that category?”
YES:
Proceed within authorized WORK ZONE.
NO:
STOP / REPORT.
—
END OF PRE-CONSTRUCTION GATEこれが玄関。施工班・補佐・俺・未来の俺、誰でもまずここ。
次が全体地図。これは「細かいコード」じゃなく、街全体の道路と工事現場を見る図にする。
KAIA SYSTEM MAP
GLOBAL SYSTEM / FOR AI USE
MAP_TYPE:
GLOBAL
MAP_ID:
SYS-GLOBAL-001
STATUS:
CURRENT
PURPOSE:
Show system-level topology, responsibility boundaries,
active construction areas, future connections,
and known incident locations.
This is NOT SOURCE authority.
This is navigation furniture.
If MAP conflicts with CURRENT SOURCE:
STOP / REPORT.
—
CURRENT POSITION
CURRENT_WORK_AREA:
CURRENT_TASK:
CURRENT_HUMAN_ORDER:
ACTIVE_PRODUCT:
ACTIVE_LOCAL_MAP:
RELATED_PLAN_IDS:
—
SYSTEM NODES
NODE:
ID:
NAME:
HOUSE:
ROLE:
STATUS:
RESPONSIBILITY:
LOCAL_MAP:
RELATED_PLAN_IDS:
NOTE:
—
ROUTES
ROUTE:
ID:
FROM:
TO:
TYPE:
DATA | CONTROL | VALUE | ATTENDANCE | ROUTING | STATE | OTHER
STATUS:
ACTIVE | PLANNED | HOLD | BROKEN | UNKNOWN
DIRECTION:
PURPOSE:
AUTHORITY:
PRESERVE:
DO_NOT:
EVIDENCE:
—
RESPONSIBILITY BOUNDARIES
BOUNDARY:
ID:
SIDE_A:
SIDE_B:
RULE:
WHY:
PRESERVE:
KNOWN_FUTURE_USE:
—
FUTURE LINES
FUTURE_LINE:
ID:
FROM:
TO:
STATUS:
PLANNED | UNDECIDED | HOLD
TRIGGER:
PURPOSE:
CURRENTLY_CONNECTED:
YES | NO | PARTIAL | UNKNOWN
PRESERVE_NOW:
RELATED_PLAN_IDS:
—
CURRENT CONSTRUCTION MARKER
WORK_MARKER:
ID:
LOCATION:
START_POINT:
TARGET:
AUTHORIZED_WORK_ZONE:
NO_TOUCH:
DEPENDENCIES:
CURRENT_STEP:
NEXT_GATE:
—
INCIDENT MARKERS
INCIDENT:
ID:
LOCATION:
DISCOVERED_DURING:
SYMPTOM:
OBSERVED:
FIRST_CONFIRMED_BREAK:
INFERENCE:
UNKNOWN:
STATUS:
OPEN | WATCH | STOP | RESOLVED
CURRENT_ACTION:
INVESTIGATE | HOLD | REPAIR_AUTHORIZED | OBSERVE_ONLY | NONE
BLOCKED_ROUTE_IDS:
AFFECTED_NODE_IDS:
NO_TOUCH:
RELATED_LOCAL_MAP:
RELATED_PLAN_IDS:
EVIDENCE:
LAST_UPDATED:
—
GLOBAL MAP READING RULE
This map answers:
– What machines exist?
– What connects to what?
– Which machine owns which responsibility?
– Where is the current construction?
– Where are known broken roads?
– Which roads are future roads?
– Which unused sockets must remain?
– Which detailed LOCAL MAP should be opened next?
Do NOT use this map to invent missing Product internals.
For Product internals:
OPEN THE RELEVANT LOCAL MAP.
—
END OF SYSTEM MAPで、プラグインごとの細かい地図。
これは**「今この交差点にいる」「この配線を追っている」「ここで事故った」まで落とす**。
KAIA LOCAL MAP
PRODUCT / PLUGIN INTERNAL MAP / FOR AI USE
MAP_TYPE:
LOCAL
MAP_ID:
PRODUCT:
HOUSE:
CURRENT_VERSION:
PRIMARY_IDENTITY:
STATUS:
CURRENT
PARENT_SYSTEM_MAP:
SYS-GLOBAL-001
RELATED_PLAN_IDS:
—
PURPOSE
Describe the internal physical / logical layout of this Product.
Use this map to answer:
– Where am I now?
– Which internal route am I following?
– What is upstream?
– What is downstream?
– Where is the first confirmed break?
– What nearby furniture must not be touched?
– Which future connection depends on this furniture?
This map is navigation evidence.
SOURCE remains physical authority.
—
CURRENT POSITION
YOU_ARE_HERE:
CURRENT_FUNCTION / COMPONENT:
CURRENT_ROUTE:
ENTERED_FROM:
EXPECTED_NEXT:
CURRENT_GOAL:
CURRENT_MODE:
CONSTRUCTION | INSPECTION | INVESTIGATION | WITNESS | HOLD
—
LOCAL NODES
NODE:
ID:
NAME:
FILE:
SYMBOL / FUNCTION / CLASS:
ROLE:
STATE:
ACTIVE | DORMANT | FUTURE | LEGACY | UNKNOWN
AUTHORITY:
UPSTREAM:
DOWNSTREAM:
RELATED_ROUTE_IDS:
RELATED_PLAN_IDS:
PRESERVE:
DO_NOT:
NOTE:
—
LOCAL ROUTES
ROUTE:
ID:
FROM:
TO:
PURPOSE:
INPUT:
OUTPUT:
STATE:
ACTIVE | PLANNED | BROKEN | UNKNOWN
EXPECTED_BEHAVIOR:
OBSERVED_BEHAVIOR:
RELATED_SOURCE:
RELATED_PLAN_IDS:
PRESERVE:
—
CURRENT TRACE
TRACE_ID:
START:
STEP_01:
STEP_02:
STEP_03:
STEP_04:
CURRENT_POSITION:
EXPECTED_NEXT:
FIRST_DIVERGENCE:
NONE | exact location | UNKNOWN
STOP_POINT:
NONE | exact location
—
INCIDENT
INCIDENT_ID:
STATUS:
OPEN | WATCH | STOP | RESOLVED
LOCATION:
SYMPTOM:
OBSERVED_FACTS:
EXPECTED:
FIRST_CONFIRMED_BREAK:
NOT_CONFIRMED:
INFERENCE:
UNKNOWN:
WHAT_WAS_HAPPENING_WHEN_FOUND:
CURRENT_RESPONSE:
REPAIR_AUTHORIZED:
YES | NO
NO_TOUCH:
BLOCKED_BY:
RELATED_ROUTE_IDS:
RELATED_PLAN_IDS:
EVIDENCE:
—
FUTURE FURNITURE
FUTURE_ITEM:
ID:
LOCATION:
CURRENT_STATE:
FUTURE_PURPOSE:
TRIGGER:
DEPENDENCY:
PRESERVE_NOW:
YES | NO | UNKNOWN
DO_NOT:
RELATED_PLAN_IDS:
—
UNDECIDED AREAS
UNDECIDED:
ID:
LOCATION:
QUESTION:
KNOWN:
UNKNOWN:
HUMAN_DECISION_REQUIRED:
YES | NO
DO_NOT_FIX_PREMATURELY:
—
WORK ZONE
AUTHORIZED:
FILES:
COMPONENTS:
ROUTES:
NO_TOUCH:
OUT_OF_SCOPE:
—
CONSTRUCTION COMPLETION UPDATE
After authorized work:
CURRENT_POSITION:
ROUTE_STATE_CHANGES:
INCIDENT_STATE_CHANGES:
NEW_FUTURE_LINES:
PLAN_ITEMS_AFFECTED:
MAP_UPDATE_REQUIRED:
YES | NO
HISTORY_UPDATE_REQUIRED:
YES | NO
LAST_UPDATED:
—
END OF LOCAL MAPこれならかなり俺向き。
たとえば事故中なら、全体地図を開いた瞬間に、
CURRENT → Rental PDF
INCIDENT → PDF issuance route
LOCAL MAP → PDF-R
まで分かる。
LOCALへ降りると、
YOU_ARE_HERE → public runtime entrance
CURRENT TRACE → shortcode → runtime → Board → preview
FIRST_DIVERGENCE → shortcode内scriptが実機でruntimeとして成立していない
REPAIR_AUTHORIZED → NO
みたいな形になる。
逆に施工中なら「故障」じゃなく、
YOU_ARE_HERE → Counter attendance caller
CURRENT_GOAL → B-01 address handoff
NO_TOUCH → Counter issuance / reset / Board / Common
みたいに使える。
そしてここが重要で、毎回全部書き直さなくていい。
打ち合わせで将来の話が決まったらPLANへカード追加。
全体接続が増えたらSYSTEM MAPへ一本追加。
機体を掘って道路が分かったらLOCAL MAPを育てる。
事故ったらINCIDENTを置く。
直ったら消さずに RESOLVED。
だから過去堀りなしでも、今日から使えば数週間後には自然にかなり正確な地図になる。
俺としてはこの三枚構成、かなり欲しかったやつだわ（笑）
特に 00-KAIA-PLAN.md が玄関になれば、PLANも地図も読まずに施工へ突入する事故そのものを施工手順違反にできる。
No comments yet.