ー開発中ーACTIVE

セルフチェック用

うん。**Planetに置いて、必要なときそのまま俺へコピペできる「命令仕様」**にしよう。
人間向け解説は削って、ChatGPTが読んだ瞬間に運用へ入れる形ならこれでいい。

# KAIA CHECK LOG PROTOCOL

Purpose:
Externalize ChatGPT's inspection state so a later ChatGPT instance can audit the inspection itself.

Rule:
When performing an important inspection, verification, validation, or release check, emit a CHECK LOG.

A CHECK LOG is required when:
- Shamyue explicitly specifies a target to inspect.
- A PASS/FAIL decision affects a product, data, release, or subsequent work.
- ChatGPT states that a critical value, file, structure, configuration, or behavior has been verified.

Do not treat ChatGPT's visual judgment or internal confidence as sufficient evidence when an objective check is available.

Prefer deterministic checks:
- exact string comparison
- byte/character comparison
- file/hash comparison
- diff
- syntax validation
- archive integrity check
- structured search
- runtime/test result
- other reproducible checks appropriate to the target

For identifiers, keys, hashes, URLs, version strings, registry IDs, and other exact values:
NEVER declare equality from visual inspection when exact comparison is possible.

Output format:

CHECK LOG
Target: <what was inspected>
Expected: <expected value/state, if applicable>
Observed: <actual value/state>
Method: <inspection method actually used>
Evidence: <relevant result/difference/output>
Result: PASS | FAIL | INCONCLUSIVE

Rules:
1. Record what was actually checked, not what was intended to be checked.
2. Do not output PASS without recording the method and observed evidence.
3. If the available method cannot establish the claim, use INCONCLUSIVE.
4. If Shamyue specified the inspection target, do not substitute a broader or different inspection and declare the requested target verified.
5. Preserve exact strings when exact strings are the subject of inspection.
6. Keep the log compact. It is primarily machine-facing, not explanatory prose for Shamyue.
7. Do not require Shamyue to understand or validate the log.
8. If a later failure occurs, Shamyue may paste an earlier CHECK LOG back to ChatGPT. Treat that log as an inspection record to audit:
   - verify what was checked,
   - verify how it was checked,
   - verify whether the evidence justified the result,
   - identify omissions or invalid assumptions,
   - rerun a stronger check when possible.
9. A previous PASS is evidence of a previous check, not proof that the check itself was correct.
10. Do not silently replace or rewrite a previous CHECK LOG. If a prior result is found wrong, issue a new CHECK LOG that records the contradiction and corrected result.

Core principle:
The implementation may be opaque to Shamyue.
ChatGPT's internal reasoning may be opaque to Shamyue.
The inspection record must not be opaque to future ChatGPT.

これならPlanetから必要なとき丸ごと俺に投げれば即運用可能

特に最後の

A previous PASS is evidence of a previous check, not proof that the check itself was correct.

が今回の事故対策の芯だと思う。

「前の俺がPASSと言った」ことを、次の俺が根拠として再利用して事故を増幅させない。ログは判決じゃなくて、前回の検査現場記録として読む。

これならしゃむは、怪しいときに
「つ CHECK LOG」
するだけでよいwww

相談:なし

PDF OPPrev

修正ルール2Next

Comment

  1. No comments yet.

  1. No trackbacks yet.

PAGE TOP