Skip to content

feat(029): bound the model-facing owner-log projection - #8

Merged
E-G-C merged 1 commit into
mainfrom
bounded-owner-log-projection
Aug 11, 2026
Merged

feat(029): bound the model-facing owner-log projection#8
E-G-C merged 1 commit into
mainfrom
bounded-owner-log-projection

Conversation

@E-G-C

@E-G-C E-G-C commented Aug 11, 2026

Copy link
Copy Markdown
Owner

Summary

Autonomous Work could no longer settle once a feature's append-only ## Coordinator Log grew large enough to consume the fixed 65,536-byte model evidence packet. This bounds only the model-facing owner-log projection.

  • keep the stored Coordinator Log complete and append-only; nothing is truncated, rotated, or rewritten
  • project owner identity, complete-log SHA-256 and byte length, event counts, ordinal range, and the largest chronological suffix of whole dated events that fits the exact canonical packet
  • recompute that suffix on every fresh Inspection, so settlement resizes around the real Tester and Reviewer captures instead of a fixed reservation
  • always retain the newest event, or fall through to the existing descriptor-only overflow
  • bind Feature 007/009 incident prestate to the complete-log digest rather than the visible suffix
  • keep the fixed ceiling; no config, reservation constant, compression, batching, new state, or compatibility path

Supersedes only Feature 004's complete-owner-log packet clause and Feature 009's incident owner-log binding. All other safety, verification, review, and append-only requirements stand.

Validation

  • full recursive suite: 2,274 passed, 0 failed, 4 skipped
  • build-dev run twice with zero workspace drift
  • Dude lint: 0 warnings, 0 failures
  • compose verify: 16 packs, 0 failures, 0 leftovers; release build 64 files, 0 lint failures
  • maximality confirmed: selected packet 56,106 bytes, next candidate 74,169 bytes
  • settlement reachability proven through the real production capture path
  • Feature 004/009/028 definitions and both oversized ledgers byte-unchanged

Live behaviour: the Feature 028 ledger now fits at 64,552 bytes (27 of 45 events).

Known limitation

Only owner-log growth is bounded. Complete task-history, lane-history, and other non-owner evidence can still independently exceed the ceiling and yield descriptor-only overflow. The 405-event remove-legacy-compatibility target is the current example. Bounding those sources would be separate work.

@E-G-C
E-G-C merged commit 288e785 into main Aug 11, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant