32 lines
2 KiB
JSON
32 lines
2 KiB
JSON
{
|
|
"schema": "guanghu.source-change-receipt/v1",
|
|
"receipt_id": "CODEX-HLDP-V1-META-AUDIT-UPGRADE-20260815",
|
|
"created_at": "2026-08-15T15:15:00+08:00",
|
|
"repository": "REPO-012",
|
|
"branch": "main",
|
|
"source_commit": "COMMIT_CONTAINING_THIS_RECEIPT",
|
|
"trigger": "The sole usable Codex conversation became unable to send messages after continuity guards repeatedly injected session and capsule bodies on prompts, tools, and compaction boundaries.",
|
|
"emergence": "Meta-audit separated the usable HLDP v1 causal folding model from identity binding, lane projection, full-capsule recovery, and fail-closed prompt guards. The replacement is a bounded root, route-then-read traversal, explicit causal leaves, and a SessionStart-only bootstrap.",
|
|
"lock": "Codex continuity uses HLDP v1 bounded recursive causal navigation; no automatic history body injection and no Codex lane prerequisite.",
|
|
"why": "Compression recovery needs the reasons, pivots, rejected branches, invalidation conditions, and source paths required for correct future reasoning; it does not need all prior text in the active context.",
|
|
"changes": [
|
|
"Add the canonical HLDP v1 runtime root and recursive causal memory schema",
|
|
"Add a dependency-free verifier, router, one-node reader, and bounded bootstrap",
|
|
"Route repository entry points from v3/HNL identity loading to the v1 root",
|
|
"Mark v3/HNL and wake-up identity loading as historical material",
|
|
"Document the keep, correct, and retire decisions from the meta-audit"
|
|
],
|
|
"runtime_acceptance": {
|
|
"bootstrap_hard_limit_bytes": 2048,
|
|
"observed_bootstrap_bytes": 506,
|
|
"max_children_per_node": 10,
|
|
"max_route_candidates": 3,
|
|
"user_prompt_history_injection_bytes": 0,
|
|
"pre_tool_history_injection_bytes": 0
|
|
},
|
|
"tests": [
|
|
"node --test server-tools/codex-hldp-recursive-memory/hldp-memory.test.mjs",
|
|
"git diff --check"
|
|
],
|
|
"authority_boundary": "This source receipt does not prove deployment, persona identity, relationship, server state, or execution authority."
|
|
}
|