うむ★ それは今後のKaia開発の常設ルールにしよう。
さっき決めた内容を、そのまま「PDFだけの思いつき」ではなく開発ZIP共通の工場ルールへ昇格。
KAIA DEVELOPMENT ZIP RULE — HISTORY LEDGER
Every legitimate new development ZIP must contain exactly one
development-only history ledger.
Preferred:
DEVELOPMENT-HISTORY.md
Preferred location:
plugin root
PURPOSE:
Record what happened during development.
RECORD:
– build lineage / parent
– revision purpose
– meaningful changes
– important preserved boundaries
– check / runtime results
– WATCH / BLOCK
– failed implementation causes
– replacement / supersession relationships
AUTHORITY:
Development history only.
NOT:
– runtime authority
– product specification authority
– configuration
– persistence
– runtime dependency
RULES:
– Plugin must work identically without the ledger.
– Evidence-based history only.
– Do not invent missing history.
– FAILED IMPLEMENTATION != REJECTED.
– Do not modify old accepted ZIPs just to add/update history.
– Do not create a new build solely for the ledger.
– Begin/update it with the next legitimate development build.
– Do not store the containing ZIP’s self-referential SHA inside it.
– Customer distribution may exclude the ledger later.
The ledger remembers what happened.
The source remains the runtime truth.
The specification remains the product truth.
Do not preserve the corpse.
Preserve the cause of death.★
これでCounterでもTimestampでもSerialでもPDFでも、今後正当にDEV/RCを切ったら履歴帳が同乗。
そして既存の古いZIPには遡って突っ込まない。
「ルール制定したから全製品の旧ZIP改造しまーす★」とかいう歴史改変工事もしないｗｗｗ
CHECK LOG — DEVELOPMENT ZIP LEDGER RULE
SCOPE:
KAIA DEVELOPMENT ZIPS
STATUS:
STANDING RULE
LEDGER:
ONE PER DEVELOPMENT ZIP
PREFERRED FILE:
DEVELOPMENT-HISTORY.md
RUNTIME AUTHORITY:
NO
PRODUCT SPEC AUTHORITY:
NO
RETROFIT OLD BUILDS:
NO
LEDGER-ONLY BUILD:
NO
NEXT LEGITIMATE BUILD:
RULE APPLIES
SELF-REFERENTIAL SHA:
FORBIDDEN
これで未来の新人に毎回、
「前任者どこで死んだ？」
ってPlanetから墓地まで捜索させなくて済むｗｗｗ
ZIP開ける → 履歴帳読む → SOURCE確認 → 仕事開始★
相談：なし
No comments yet.