Current capacity after approved full-cache cleanup — 2026-09-14
Complete cleanup observation and native qualification: audited Cargo/coverage/Bazel cache cleanup recovered 43,929,825,280 available bytes while preserving source work, Git history, environments, binaries and measurement evidence. Verification retains the explicit disposition of four regenerated compiler-probe metadata files; all preserved binary/evidence hashes matched.
Current S20/S22 planning decision: admit. Available capacity 777,694,818,304 B; projected demand 588,524,115,286 B; unchanged reserve 141,258,578,535 B; 47,912,124,483 B spare after reserve, zero planning deficit. This supersedes the earlier 3.98 GB margin below. Future builds or other writes can consume this point-in-time headroom.
Remaining close gate: actual final ladder/capacity evidence. No S24/S25/S26 was executed or authorized by this cleanup. The existing ladder’s adjacent admission and final S26 public lifecycle/count/resource requirements remain unchanged.
Current capacity after XYG cache cleanup — 2026-09-14
Verified cleanup and complete native qualification: XYG’s unused dev-profile build cache returned 2,674,348,032 available bytes, preserving both checkouts, dependencies and runtime assets. Native backend and all 647 ABI smoke checks pass.
Current S20/S22 planning decision: admit. Available capacity 733,767,651,328 B; projected demand 588,524,115,286 B; unchanged reserve 141,258,578,535 B; 3,984,957,507 B spare after reserve, zero planning deficit. This supersedes the earlier 1.31 GB margin below; filesystem availability remains point-in-time.
The only remaining close gate is actual final ladder/capacity evidence. No S24/S25/S26 ran; this projection does not authorize or replace their existing admission and execution requirements.
Current capacity after approved cache reclamation — 2026-09-14
The complete reclamation observation and native qualification supersede the earlier 30.10 GB planning deficit below. Audited cleanup recovered 31,305,781,248 available bytes, preserving original executable paths/hashes, frozen binaries, raw evidence and unrelated work.
The existing S20/S22 projection now returns admit: projected demand 588,524,115,286 B, actual available capacity 731,095,973,888 B, unchanged reserve 141,258,578,535 B; 1,313,280,067 B spare after reserve and zero current planning deficit. This is a small, point-in-time margin that subsequent builds/writes can consume.
Remaining acceptance: actual final ladder/capacity evidence. No S24/S25/S26 was executed or authorized by this cleanup. The existing ladder still requires its admitted S24/S25 observations and terminal S26 public lifecycle/count/resource evidence. Lower-rung projection alone does not close #1194/#900/#745. Earlier dated reports remain preserved as historical observations.
Verified capacity follow-up — 2026-09-14
The merged integrated report supersedes earlier capacity estimates as the current evidence ledger. #1269/#1268/#1272/#1274 are verified closed after their focused PRs passed exact-head CI Gate and squash-merged. #1276 records the integrated evidence merge 989579078cc7e71ca4deaa1464afbbed7d222222 and required CI.
On the same OVHC-AGENCY host, merged source 710c6c64f4718c0664d08bdd3aafe21de4a29eba and frozen executables completed only S18 → S19 → S20 → S22, with native admission before each successor and all ten ordinary lifecycle phases passing. Accepted rung workspaces were reclaimed before the next rung. S22 contains 4,194,304 nodes and 67,108,864 live edges. Compared with the preserved 24ca688c run, lifecycle peak falls 47,657,119,744 → 36,760,567,808 bytes. The report preserves storage owners without double-counting, logical and process I/O, CPU, process VmHWM, cgroup/page-cache observations and disjoint construction timings.
| Capacity acceptance |
Current outcome |
| Material implementation and deterministic representative budgets |
Merged consumed-root retirement, authenticated recovery cleanup and exact packed current-format records; measured storage and I/O improvements, CPU/RSS envelopes and public lifecycle/corruption/recovery tests retained. |
| Authorized lower-rung integration |
S18/S19/S20/S22 passed with unchanged input/host profiles and reserve; native receipts and historical evidence retained. |
| Product demand projection |
S26 projected peak 762,866,827,264 → 588,524,115,286 B; reduction 174,342,711,978 B. At the old available-capacity sample, deficit is 96,428,597,181 B. |
| Owned artifact reclamation |
Actual available-byte increase 75,087,810,560 B, separately measured after freezing. Unrelated work, measured executables and raw evidence preserved. |
| Current native capacity projection |
refuse: projected peak 588,524,115,286 B, actual available capacity 699,686,567,936 B, unchanged admission reserve 141,258,578,535 B. Deficit 30,096,125,885 B; spare after reserve 0 B. |
| Final capacity/S26 |
OPEN. No S24/S25/S26 was authorized or executed. The existing ladder still requires S24/S25 admission and actual terminal S26 lifecycle/count/resource evidence; a S20/S22 projection cannot replace it. |
All authorized implementation and lower-rung evidence work is complete. #1194/#900/#745 remain open only for the final named-host capacity/S26 outcome in their existing acceptance criteria. No larger-host substitution, reduced reserve, admission waiver or new certification workflow was used. Historical dated notes below remain preserved and are superseded where their capacity numbers differ.
Problem
Component tests and laptop observations cannot establish the final billion-edge outcome. The integrated tree needs one reproducible host-native proof of construction, recovery, queries, portable-v2 verification, clean import, reopen, and exact evidence across a progressive ladder.
Objective
Accept the terminal S26 result from the completed OVHC-AGENCY ladder in #900 as GraphForge's final billion-live-edge certification evidence.
Required ladder
S18 -> S19 -> S20 -> S22 -> S24 -> S25 -> S26
- Every rung uses the same frozen commit, generator identity, EF16, seed, public lifecycle, durability, queries, and evidence contracts on OVHC-AGENCY under
local-linux-cgroups-v2.
- Each rung generates its canonical deterministic dataset once and reuses those exact bytes throughout that rung. Smaller rungs are not derived by truncating or remapping larger-scale data.
- Developer laptops and overlay-rooted VMs are not the SUT and contribute no scale measurements.
- A failed rung authorizes no larger rung.
- S20 requires adjacent S18/S19 admission; S26 requires adjacent S24/S25 admission.
Certification requirements
- Identify the exact commit, host identity (
OVHC-AGENCY), BenchExec/profile versions, OS/tool versions, seed, and maximum-scale authorization.
- S26 must produce >=1,000,000,000 live persisted edges after rejects/duplicates/self-loops are reconciled.
- Complete generate, ordinary staged construction, atomic publication, reopen/recount, deterministic one-hop/two-hop ordered-LIMIT queries, portable-v2 export, full integrity/compatibility verification, clean import, imported reopen/recount, and matching post-import queries.
- Record per-phase BenchExec wall/CPU/process-tree RSS/physical I/O and GraphForge logical construction/storage/reader/publication evidence. Separate process anonymous RSS from page cache.
- Prove bounded or plateauing RSS across the ladder. Persistent graph size is expected to be disk-bound; material edge-proportional RSS growth is a failure.
- S20 must fit the four-hour and 4 GiB process-RSS envelope with reasonable headroom.
- Every rung must fit the four-hour runaway envelope. S26 must be admitted from adjacent rungs below this host’s free capacity with a 15% reserve.
- Peak RSS ≤128 GiB remains only an absolute M5 ceiling on this 125 GiB host, never a sizing target or default.
- Reconcile source/imported counts, query observations, semantic package digest, transport digest, source generation, imported generation, and canonical fingerprints.
- Preserve prior CURRENT under cancellation, corruption, resource failure, or interrupted finalization; run negative drills at representative bounded scale.
- Validate closed sanitized evidence independently and check it into a durable reviewable repository location without large data or secrets.
- Prove complete teardown of temporary datasets, projects, exports/imports, and work-root debris on OVHC-AGENCY.
Acceptance criteria
Non-goals
A benchmark leaderboard, laptop/overlay-VM certification, universal hardware-independent capacity claims, a 24-hour normal-usage story, uploading the billion-edge payload to a registry, or accepting a skipped/interrupted rung.
Relationships
Current capacity after approved full-cache cleanup — 2026-09-14
Complete cleanup observation and native qualification: audited Cargo/coverage/Bazel cache cleanup recovered 43,929,825,280 available bytes while preserving source work, Git history, environments, binaries and measurement evidence. Verification retains the explicit disposition of four regenerated compiler-probe metadata files; all preserved binary/evidence hashes matched.
Current S20/S22 planning decision: admit. Available capacity 777,694,818,304 B; projected demand 588,524,115,286 B; unchanged reserve 141,258,578,535 B; 47,912,124,483 B spare after reserve, zero planning deficit. This supersedes the earlier 3.98 GB margin below. Future builds or other writes can consume this point-in-time headroom.
Remaining close gate: actual final ladder/capacity evidence. No S24/S25/S26 was executed or authorized by this cleanup. The existing ladder’s adjacent admission and final S26 public lifecycle/count/resource requirements remain unchanged.
Current capacity after XYG cache cleanup — 2026-09-14
Verified cleanup and complete native qualification: XYG’s unused dev-profile build cache returned 2,674,348,032 available bytes, preserving both checkouts, dependencies and runtime assets. Native backend and all 647 ABI smoke checks pass.
Current S20/S22 planning decision: admit. Available capacity 733,767,651,328 B; projected demand 588,524,115,286 B; unchanged reserve 141,258,578,535 B; 3,984,957,507 B spare after reserve, zero planning deficit. This supersedes the earlier 1.31 GB margin below; filesystem availability remains point-in-time.
The only remaining close gate is actual final ladder/capacity evidence. No S24/S25/S26 ran; this projection does not authorize or replace their existing admission and execution requirements.
Current capacity after approved cache reclamation — 2026-09-14
The complete reclamation observation and native qualification supersede the earlier 30.10 GB planning deficit below. Audited cleanup recovered 31,305,781,248 available bytes, preserving original executable paths/hashes, frozen binaries, raw evidence and unrelated work.
The existing S20/S22 projection now returns admit: projected demand 588,524,115,286 B, actual available capacity 731,095,973,888 B, unchanged reserve 141,258,578,535 B; 1,313,280,067 B spare after reserve and zero current planning deficit. This is a small, point-in-time margin that subsequent builds/writes can consume.
Remaining acceptance: actual final ladder/capacity evidence. No S24/S25/S26 was executed or authorized by this cleanup. The existing ladder still requires its admitted S24/S25 observations and terminal S26 public lifecycle/count/resource evidence. Lower-rung projection alone does not close #1194/#900/#745. Earlier dated reports remain preserved as historical observations.
Verified capacity follow-up — 2026-09-14
The merged integrated report supersedes earlier capacity estimates as the current evidence ledger. #1269/#1268/#1272/#1274 are verified closed after their focused PRs passed exact-head CI Gate and squash-merged. #1276 records the integrated evidence merge
989579078cc7e71ca4deaa1464afbbed7d222222and required CI.On the same OVHC-AGENCY host, merged source
710c6c64f4718c0664d08bdd3aafe21de4a29ebaand frozen executables completed only S18 → S19 → S20 → S22, with native admission before each successor and all ten ordinary lifecycle phases passing. Accepted rung workspaces were reclaimed before the next rung. S22 contains 4,194,304 nodes and 67,108,864 live edges. Compared with the preserved24ca688crun, lifecycle peak falls 47,657,119,744 → 36,760,567,808 bytes. The report preserves storage owners without double-counting, logical and process I/O, CPU, process VmHWM, cgroup/page-cache observations and disjoint construction timings.All authorized implementation and lower-rung evidence work is complete. #1194/#900/#745 remain open only for the final named-host capacity/S26 outcome in their existing acceptance criteria. No larger-host substitution, reduced reserve, admission waiver or new certification workflow was used. Historical dated notes below remain preserved and are superseded where their capacity numbers differ.
Problem
Component tests and laptop observations cannot establish the final billion-edge outcome. The integrated tree needs one reproducible host-native proof of construction, recovery, queries, portable-v2 verification, clean import, reopen, and exact evidence across a progressive ladder.
Objective
Accept the terminal S26 result from the completed OVHC-AGENCY ladder in #900 as GraphForge's final billion-live-edge certification evidence.
Required ladder
S18 -> S19 -> S20 -> S22 -> S24 -> S25 -> S26local-linux-cgroups-v2.Certification requirements
OVHC-AGENCY), BenchExec/profile versions, OS/tool versions, seed, and maximum-scale authorization.Acceptance criteria
Non-goals
A benchmark leaderboard, laptop/overlay-VM certification, universal hardware-independent capacity claims, a 24-hour normal-usage story, uploading the billion-edge payload to a registry, or accepting a skipped/interrupted rung.
Relationships