[CLAUDE] Docs: S130 anh chốt 3 mục S126 owner-gated — B3 tách mega-line (STATUS 261→686 + HANDOFF 13→317 dòng, separator ' · '→CRLF, round-trip PASS giữ-nguyên-chữ) + B4 memory-budget:74 relabel EN "upper-bound (heuristic-notice) headroom" + gỡ carry mark-S123 stale (RESOLVED @S130 ACTIVE-MARKS.md, mark RC-…17-23-10 đã tồn-tại+stamped)
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
@ -71,7 +71,7 @@
|
||||
"crystallized_backfill": {
|
||||
"_note": "Harness-20-era (S103, 2026-07-06) crystallized-backfill = 'measure-then-fill'. Read by scripts/crystallized-backfill.ps1 (deterministic NO-API DRY planner). Adapts AI_INFRA broadcast 2026-07-04 F4 + session-cmd-budget-display Upgrade-1. DISTINCT from CRYSTALLIZATION (engine §I distill = compress-TOWARD-source, keep time-invariant): backfill goes the OPPOSITE direction = FILL the empty hot-feed budget with already-crystallized cold-tier data so the cap is not wasted. PRECONDITION: expected_backfill opens ONLY when target>0 AND measured_headroom>0. Default target=0=OFF. NOT-for-sub (sub packs are lead-curated per-task; blind-pour dilutes relevance).",
|
||||
"target": 210000,
|
||||
"_target_note": "OWNER-AUTHORITY static number (mirror token_governor.role_boundary_note + mark RC-...21-06...01-58-01). Default 0 = OFF/disabled. Owner raises >0 ONLY after judging a POSITIVE real-token headroom exists on the stable hot-load floor. The AI (em-main) NEVER sets/auto-tunes this; the script is READ-ONLY on it. S115 (2026-07-13) OWNER-DIRECTED: target 0 -> 210000 (backfill ON). em-main executed per role_boundary_note (owner sets the number, em-main executes+reports, does NOT auto-tune down). HONEST CAVEAT surfaced to owner: measured_headroom ~253.7K tok is over the STABLE FILE-FLOOR only (UPPER BOUND); the real peak ALSO loads session-variable task-context approaching the ~368K read-set, so file-floor ~126K + 210K backfill = ~336K always-on leaves only ~44K for task-context => heavy sessions risk exceeding the 380K cap + higher context-rot (owner previously accepted near-full hot-feed, mark RC-pqhuy1987-29-06-2026-23-25-50 v4). Backfill stays DRY-PLANNER: target>0 makes crystallized-backfill.ps1 PRINT expected_backfill + source-order; it performs NO auto-pour -- actual hot-feed fill is em-main manual per-session from source_order (gist -> value-marked-archive -> curated-RAG, dedup vs hot-load).",
|
||||
"_target_note": "OWNER-AUTHORITY static number (mirror token_governor.role_boundary_note + mark RC-...21-06...01-58-01). Default 0 = OFF/disabled. Owner raises >0 ONLY after judging a POSITIVE upper-bound (heuristic-notice) headroom exists on the stable hot-load floor. The AI (em-main) NEVER sets/auto-tunes this; the script is READ-ONLY on it. S115 (2026-07-13) OWNER-DIRECTED: target 0 -> 210000 (backfill ON). em-main executed per role_boundary_note (owner sets the number, em-main executes+reports, does NOT auto-tune down). HONEST CAVEAT surfaced to owner: measured_headroom ~253.7K tok is over the STABLE FILE-FLOOR only (UPPER BOUND); the real peak ALSO loads session-variable task-context approaching the ~368K read-set, so file-floor ~126K + 210K backfill = ~336K always-on leaves only ~44K for task-context => heavy sessions risk exceeding the 380K cap + higher context-rot (owner previously accepted near-full hot-feed, mark RC-pqhuy1987-29-06-2026-23-25-50 v4). Backfill stays DRY-PLANNER: target>0 makes crystallized-backfill.ps1 PRINT expected_backfill + source-order; it performs NO auto-pour -- actual hot-feed fill is em-main manual per-session from source_order (gist -> value-marked-archive -> curated-RAG, dedup vs hot-load).",
|
||||
"hotload_sources": [
|
||||
"docs/STATUS.md",
|
||||
"docs/HANDOFF.md",
|
||||
|
||||
Reference in New Issue
Block a user