A Pack too large for one bundle reads whole in parts

outcome

Execute the parts rules on a probe Pack whose members together exceed the budget while each fits a part alone.

assumptions

• The world writes a probe Pack of three story-altitude behavior Specs stating idea, each with an Intent outcome and a narrative of 6,000 letters, none related to a Spec outside the Pack. It runs the shipped context bundle file through sdp q --json with the Pack, the budget and part: 1, reads part.of, then asks for every other part in turn. It checks that each part's used is at most the budget, that no part's leftOut names a cut, that every part repeats the scope and the Pack, and that only part 1 carries a boundary.

Examples

Given a probe Pack of three members whose bundle exceeds the budget {budget: 10000} {sizes: "while each member fits a part alone"}
When each part of its context bundle is requested in turn
Then the bundle comes in {parts: 3} parts, each within the budget
Then the members of the parts, in part order, are the Pack's members in authored order, each once: {complete: true}

Verifier bindings

• test:protocol.context-bundle.parts-cover-the-pack · anchored · test anchor binding present · test/self-hosting-bundle-parts.test.ts:115

  External run evidence from test/self-hosting-bundle-parts.test.ts

  Test anchors: test:protocol.context-bundle.oversized-member-named, test:protocol.context-bundle.parts-cover-the-pack. Specs verified by those bindings: spec:consumers.context-bundle, spec:consumers.context-bundle.oversized-member-named, spec:consumers.context-bundle.parts-cover-the-pack.

  Run 1: external run evidence from vitest 4.1.10

  Build: CI 380 · Branch: feature/roadmap-and-slices-v0 · Commit: 34909918bf0be0e849959644401797191cae379f · Start: 2026-10-22T17:40:31.456Z · Stop: 2026-10-22T17:42:16.171Z

  Name	Suite	Result	Duration
  executes the bound example against a fresh world	A Pack too large for one bundle reads whole in parts (spec:consumers.context-bundle.parts-cover-the-pack)	passed	42.45 ms
  executes the bound example against a fresh world	A member larger than the budget is named, and no part is returned (spec:consumers.context-bundle.oversized-member-named)	passed	10.24 ms
  diagnoses invalid part 0	bundle part budgets	passed	4.27 ms
  diagnoses invalid part -1	bundle part budgets	passed	3.8 ms
  diagnoses invalid part 1.5	bundle part budgets	passed	5.68 ms
  diagnoses invalid part null	bundle part budgets	passed	2.44 ms
  diagnoses invalid part "1"	bundle part budgets	passed	5.6 ms
  diagnoses invalid part true	bundle part budgets	passed	2.24 ms
  diagnoses a part beyond the final count	bundle part budgets	passed	3.51 ms
  accepts an exact whole-part budget and cuts only when that item cannot fit	bundle part budgets	passed	13.29 ms
  measures two-digit part counts and takes the longest whole run at every boundary	bundle part budgets	passed	67.34 ms
  repartitions at the first common cut stage instead of mixing cut and whole members	bundle part budgets	passed	5.73 ms
  preserves pinned declarations until addresses are allowed, and never returns a partial part	bundle part budgets	passed	9.62 ms
  gives an empty scope one complete part when it fits	bundle part budgets	passed	3.68 ms
  names only the part header when the repeated Pack framing alone exceeds the budget	bundle part budgets	passed	8.47 ms
  names an oversized boundary when its outside neighbour ids exceed the budget after every cut	bundle part budgets	passed	34.08 ms

Requirement drawing

• Satisfying or referencing units: no recorded binding.

Decisions

No decision record named.

No implementation neighborhood recorded.

Runtime observation: not tracked.

Runtime observation: not tracked.

Build attestations: not tracked.

Deployments: not tracked.

Bills of materials: not tracked.