ものづくりルール　チェックログ

うん。これは人間向け仕様書じゃなく、未来のChatGPTが「同じ失敗を再研究しない」ための機械向けルールとしてPlanetに一本ぶら下げるのがいい。

しかも不採用リスト単体より、ものを作る時の標準工程に組み込むのが強い。人間可読性を捨てるなら、こんな形で十分。

KAIA BUILD / REJECTION MEMORY RULE
Purpose:
Prevent repeated investigation, resurrection of rejected designs, and accumulation of obsolete implementation debris.

SCOPE
Apply when designing, revising, implementing, repairing, or inspecting an artifact.

STATE LABELS
CURRENT   = adopted / active design.
CANDIDATE = not yet sufficiently tested or decided.
REJECTED  = explicitly evaluated and not adopted.
OBSOLETE  = previously valid, superseded by a newer adopted design.
REFERENCE = retained only as implementation/evidence donor.

CORE RULE
Before proposing or implementing an alternative:
1. Inspect CURRENT.
2. Search REJECTED list for semantically equivalent prior attempts.
3. Search OBSOLETE/REFERENCE only when implementation history is relevant.
4. If equivalent REJECTED entry exists, do not re-test/rebuild by default.
5. Reopen REJECTED only when a materially changed constraint, dependency,
   requirement, or implementation method invalidates the recorded rejection reason.
6. If reopened, record why prior rejection no longer governs.

REJECTION RECORD
ID | CONTENT | REASON | NOTE

ID:
Permanent unique identifier. Never reuse after deletion/reset.
Recommended local series: RJ-001, RJ-002, ...

CONTENT:
Compact machine-oriented description of the rejected mechanism/design.
Describe semantics, not cosmetic wording.

REASON:
The actual failure/rejection condition.
Record enough causal information to prevent ChatGPT from proposing the same idea
under different wording.

NOTE:
Current replacement, relevant test evidence, exception condition, donor/version,
or conditions under which reopening is legitimate.

ON REJECTION
When a candidate is explicitly rejected:
1. Create REJECTED record.
2. Preserve rejection knowledge before deleting implementation debris.
3. Remove dead implementation code when it has no CURRENT/REFERENCE function.
4. Where useful, leave only a compact pointer such as:
   REJECTED: RJ-###
5. Do not retain large dead code solely to remember why it was rejected.

ON SUPERSESSION
Do not mark a formerly valid implementation REJECTED merely because it became old.
Use OBSOLETE.
REJECTED = evaluated and intentionally not adopted.
OBSOLETE = was valid/adopted, later replaced.

ON DISCOVERY OF OLD CODE
Never infer state from age.
Classify against CURRENT specification:
- matches CURRENT -> retain / reconcile.
- known rejected mechanism -> REJECTED; remove executable debris if safe.
- formerly valid but superseded -> OBSOLETE.
- potentially useful donor -> REFERENCE.
- insufficient evidence -> CANDIDATE / inspect before modification.

REVISION SAFETY
When modifying an existing artifact:
1. Preserve source artifact unchanged.
2. Create a new copy.
3. Assign the NEW version/identity immediately, before transferring/modifying content.
4. Modify the new copy while referencing the source.
5. Compare source vs new copy.
6. Verify intended delta only.
7. Run relevant functional/static checks.
8. Adopt only after verification.

IMPORTANT
Do not use REJECTED as a trash label.
A rejection requires an actual prior decision/evaluation.
Unknown old material is not automatically rejected.

RESEARCH STOP CONDITION
If a proposed idea matches REJECTED:
STOP.
Do not spend implementation/test effort merely to rediscover the rejection.
Continue only if a changed condition is identified and recorded.

DESIGN PRINCIPLE
Preserve decisions, not corpses.
Delete obsolete implementation debris when safe;
retain the smallest durable record necessary to prevent repeated mistakes.

これならPlanet側に置いたあと、各製品の不採用記録はものすごく小さくできる。

KAIA PDF — REJECTED

RJ-001 | Direct whole-Text-BOX drag | Conflicts with text editing interaction | CURRENT: left/right vertical drag handles
RJ-002 | Preview-only sticky | Independent sticky surface caused layout/following failures | CURRENT: entire workbench floor sticky
RJ-003 | Orientation by width/height swap only | Does not rotate Design/glyphs; violates ↻ semantics | CURRENT target: true paper rotation + conditional Design rotation

ただし RJ-001は今の会話で初めて「本当に不採用」と確定した場合だけ登録する。さっき出土したコードを見ただけでは登録しない。ここもルールに入れた理由がそれｗ

そしてこのルールの肝は、

REJECTED と OBSOLETE を分けたこと。

ここ混ぜると未来の私は、昔ちゃんと動いていたLEGOまで「不採用だったんですね★」と捨てかねない。

Planetには人間向け説明なしで、これをそのまま ChatGPT operational rule / rejection memory としてぶら下げていいと思う。

死体を保存するな。死因を保存しろ★ が機械向けには一番効くｗｗｗ

相談：なし

KAIA-REGISTRY
ID: KS-0058-CNT-26
CNT: CNT-26
TITLE: Kaia CHECK LOG Protocol
TITLE_JA: Kaia CHECK LOG 運用ルール
TARGET:
MEDIA:
LANG:
PART:
VERSION:
KAIA-REGISTRY-END