Skip to content

[v0.1.3][Stage 1] Consolidate initial results and propose the optimization backlog #35

Closed

Description

@yifanxuaaa

Separate fast-iteration verification profile (2026-09-04)

The user requested roughly ten times faster development verification after fixed-background tiny checks took about three minutes each. The committed profile contract keeps fast_iteration_verified distinct from fully_verified; fast checks cannot satisfy the existing exhaustive Phase 1/release gates.

The exhaustive campaign is paused after a completed check: 37 new full proofs plus two retained full proofs remain available, with 343 further full checks required under the unchanged acceptance scope. All 373 active performance samples are retained. Implementation now removes repeated verifier work and adds certificate-bound changed-data checks plus explicit untouched FUSE witnesses. Qualification will use one small negative-check campaign and one representative fast tiny case before broader rollout. The 18–20-second target is not yet measured. No case definitions or historical failures are deleted, and this issue remains open.

Latest Phase 1 scope amendment (2026-09-04)

The user authorized permanent Phase 1 scheduling suppressions under the committed 15-second policy. This supersedes the original full-inventory execution wording below. Keep every case implementation and historical outcome for Phase 2 testing/optimization; suppression is not deletion or a passing result.

The original 130 new timed definitions remain intact. The initial 14 suppressed scenario IDs remove 42 performance samples and their 42 associated verifiers from required Phase 1 scheduling, leaving 116 active new cases / 348 performance samples, plus 25 capped inherited samples. All 29 standalone proof recipes remain required. Any additional single performance sample exceeding 15 seconds of cumulative declared product time permanently suppresses that exact scenario across all seeds/repetitions and future Phase 1 sources. Preparation, standalone proofs and external cleanup are exempt. Still-active correctness, resource, custody and cleanup gates remain unchanged; #21 stays open.

Phase 1 completion amendment (2026-09-04)

The user requires functional failures to be repaired in Phase 1. The committed amendment supersedes earlier baseline-only closure and deferral wording below. Required functional, correctness, integrity, resource, safety-deadline and cleanup gates must pass before PHASE1_TERMINAL_PASS. Optional latency/storage optimization of correct operations remains Phase 2.

Preserve all original baseline failures and producing identities; record corrected candidate evidence separately. Fix shared causes and recollect only genuinely invalidated coverage. Do not shrink fixtures, omit cases, weaken oracles, raise budgets/timeouts or add benchmark-only bypasses. Keep affected family issues and #35 open until corrected execution and independent verification pass; #21 stays open for later phases/release.

Parent: #21
Depends on the shared infrastructure and all twelve Stage 1 family sub-issues listed on the parent.

Problem statement

Separate family results need one source-aware inventory before we select product work. A collection of green timings is insufficient if required cases, proofs, preparation costs or failed outcomes are missing.

Goal

Publish the complete initial-baseline report and propose the Stage 2 backlog. This issue does not implement optimizations, change targets to fit observed results, or release v0.1.3.

Work and acceptance criteria

  • Verify all 130 unique new timed definitions, 390 prescribed initial sample slots, the CDC boundary proof, and all 28 reliability subcases. Count shared controls once and inherited evidence separately.
  • Require implemented/executed coverage: retain explicit failure/timeout/capability results rather than fabricate latency rows or silently omit cases. Unimplemented cases and missing mandatory observations keep Stage 1 incomplete.
  • Bind every result to the pinned product baseline and actual harness/fixture/oracle/environment identity. Seal one terminal Stage 1 collection; reuse only already-collected rows whose exact required identities still match, and recollect stale affected rows.
  • Report per-case distributions for eligible results; whole-Workspace size/dirty-frontier curves; preparation/cache-hit command wall; CPU/RSS/spool; actual Store and payload/metadata growth; and history/dedup evidence with correct denominators.
  • Publish a correctness/resource/cleanup findings table alongside performance. Baseline collection completeness is distinct from passing product or release gates.
  • Group findings by shared root cause, affected public operations, severity and confidence. Separate product problems from harness defects, environment limits and unsupported guarantees.
  • Propose Stage 2 optimization/correctness issues and numerical targets only from retained evidence. Do not assign one speculative optimization task to every family.
  • Record inherited regression and capped-replacement disposition, missing follow-up decisions, and the next-stage plan on the central issue; keep the central release issue open.

Files to read

docs/roadmap/0.1/0.1.3/README.md, docs/roadmap/0.1/0.1.3/testing-rules.md, each canonical family file, and the source-bound raw results produced by its child issue.

Stage 1 boundary

Build the benchmark and retain its initial outcomes. Product algorithm, storage-format and performance optimization are deferred to Stage 2. Improve benchmark preparation/reuse and correct harness defects now; do not silently change the measured product to make results pass. Pin the unoptimized product identity and distinguish harness changes from product changes.

A slow result, product failure or timeout is an initial finding, not permission to lower a gate, drop a case or start tuning. Keep outcome, harness validity, verification, resources, cleanup and coverage completeness separate. Failed/invalid cases cannot support performance claims. Unimplemented cases, missing mandatory observations and unexecuted slots remain incomplete.

Shared execution rules

  • Reuse fs-bench-pro, existing generators, runner helpers, custody, qualified pristine inputs, independent writable samples and reports. Add only needed family adapters.
  • Use 1/10/100/500 of the declared unit; no Cartesian size/count matrix. Each workload file is at most 500 MiB and aggregate logical content is strictly below 1 GiB at every intermediate state, including temporary files and Git internals. Physical Store/spool/cache budgets are separately reported.
  • Resolve the selected case/seed before preparation. Reuse compatible artifacts; prepare only required inputs. Measured creation/import/history must still execute all work.
  • Iterate one selected case and seed; ordinary warm-prepared 1–5 second command wall is a target to qualify, not a blanket guarantee. Required extended cases are explicitly selected and cannot be omitted from complete baseline coverage.
  • Separate performance and verification. Added benchmark hashes, full manifests, reopen and fault injection stay outside performance timing; intrinsic CAS/Git hashing remains measured.
  • Collect several metrics from one execution and regenerate reports from raw evidence without rerunning successful workloads. Retain all valid results and failures, with exact source, fixture, oracle, runtime and cache identities.

Activity

  1. self-assigned this
    on Sep 4, 2026
  2. yifanxuaaa commented on Sep 4, 2026

    @yifanxuaaa
    ContributorAuthor

    Progress toward Phase 1 terminal pass on the user-authorized8-CPU Docker VM:

    • Current implementation is published at 7948df2d. Benchmark containers still have the existing2-CPU/2-GiB caps; no deadline, fixture or correctness gate was relaxed.
    • The separate fast tiny-stat-1, seed1, check passed:6.916s runtime,13.895s complete sample,15.862s CLI invocation. The retained exhaustive reference was170.565s runtime/177.173s per sample. Observed sample time was12.75× lower; this is a different assurance profile, not a controlled product-performance comparison.
    • Fast scope: all101,144 current namespace/global-inode entries and all native names/types;60 selected regular paths/500,131bytes;209 native metadata paths. It explicitly skipped100,440 untouched bodies and100,935 native metadata checks. Independent validation found no issues or resource violations, and cleanup passed. fast_iteration_verified receives zero exhaustive verification credit.
    • The small qualification passed9 canonical/certificate and8 native negative checks after repairing and retaining the original canonical-envelope failure. The already-passing Python model was reused.
    • MatchingVM8 performance collection is in progress:78 current passes at this checkpoint, including all24 payload and51 active tiny-file samples. The original373 VM4 observations remain preserved, not relabelled asVM8 evidence.
      -37 compatible VM8 full proofs and the separately identified completed600-second proof are retained.344 further full checks remain for the matching cohort, including the small payload proof needing the current environment.
      -[v0.1.3][Stage 1][04] Build and baseline git workflow in a populated workspace #26 is closed under the explicit four-case Git runtime-suppression scope. It is not a claim that suppressed Git exhaustive checks passed. [v0.1.3] Benchmark-first Workspace and CAS/CDC roadmap #21 stays open.

    Contracts: verification profiles, VM8 admission cohort.

    Fast attempt tiny-stat-1-s1-fast-verify-4173c0ddecb8 and its independent validation are preserved locally under the campaign evidence directory; their artifact publication is queued for the next non-measurement checkpoint. This issue remains open until the applicable terminal evidence gates pass.

  3. yifanxuaaa commented on Sep 4, 2026

    @yifanxuaaa
    ContributorAuthor

    VM8 performance collection is complete: 373/373 active samples have raw PASS outcomes, with supervisor and mutable-sample cleanup PASS for every sample. The independent admission selection checkpoint passed; final report validation and 344 outstanding full checks remain. No terminal pass is claimed.

    Published checkpoint: 3753870bc, including source-bound raw evidence and selection receipt and qualified fast-profile results and limits.

    The 8-CPU VM retains 2-CPU/2-GiB per-container caps. Samples totaled 1,751.250 seconds including 1,062.159 seconds of preparation. All14 authorized exact-case suppressions remain explicit, never passing coverage. Both cache-cap preparation failures and selected successful retries are retained.

    The final campaign will reuse37 completed VM8 full proofs plus the original source/environment-bound600-second standalone proof. Fast verification has zero full-gate credit. A verifier-only direct authenticated inode traversal retains all full byte, metadata, alias, namespace and typed-census checks; its scoped build and small qualification are next. Product timings remain sourced to7948; no performance recollection is needed for that verifier-only change.

    Remaining children stay open until their mandatory checks pass. Central#21 stays open for later phases.

  4. yifanxuaaa commented on Sep 4, 2026

    @yifanxuaaa
    ContributorAuthor

    Capped inherited performance checkpoint: 25/25 samples independently validated PASS, across the five unchanged capped replacements (five prescribed repetitions each). Separate full verification remains scheduled; no legacy58-case release claim is made.

    Published complete report preserves source7948 and the VM8 environment with2CPU/2GiB container caps. The declared cumulative product time below is separate from preparation and complete sample wall; all frozen2second edit+Commit+End,10secondworker, preparation, resource and cleanup gates remain unchanged.

    Capped case n Median cumulative product ms Median preparation s Median complete sample s
    append-tail-4k-input-524283904b-result-500mib-ops-1-capped-v1 5 81.731 0.912 1.369
    insert-middle-4k-input-524283904b-result-500mib-ops-1-capped-v1 5 82.696 0.926 1.395
    prepend-head-4k-input-524283904b-result-500mib-ops-1-capped-v1 5 74.250 0.882 1.335
    replace-grow-middle-2k-to-4k-input-524285952b-result-500mib-ops-1-capped-v1 5 71.015 0.894 1.338
    zero-extend-tail-4k-input-524283904b-result-500mib-ops-1-capped-v1 5 80.156 0.900 1.342

    Result comments are now posted on every family ticket#23–#34. Shared infrastructure#22 and complete payload#23 are closed with published passing evidence;#26 remains closed under its explicit Git suppression scope. Central#21 stays open. All373 active VM8 performance samples are qualified,41full proofs are independently qualified and retained, and341remaining full checks are now executing on the qualified verifier-only successor. No fast profile receives full-proof credit.

  5. yifanxuaaa commented on Sep 4, 2026

    @yifanxuaaa
    ContributorAuthor

    The five versioned capped inherited replacements are complete for their Phase 1 scope: 25 VM8 performance samples and five full VM8 verification slots, with no missing, invalid or failed capped slots. The sealed capped completion receipt records every identity and performance-to-proof join.

    The five newly completed exhaustive proofs at source fb5b34f7a882e257cd3647591fbd6c7f6ac6c2ec were each validated once through the existing report.validate_attempt. All passed their full canonical/native byte and metadata checks, independent capped transcript checks, original 30-second verification deadline, resource/custody gates and supervisor/mutable-sample cleanup. Fast verification supplied no credit.

    The 25 already-qualified VM8 performance rows were reused from the exact published report at b1f6ff18fe3e16b89989a0d0b5b665e56980a984; they were not revalidated or rerun. All five repetitions of each case match its one full proof’s input and VM8 environment identity through the current explicit source-compatibility map. The checkpoint binds the published report Git blob and SHA-256, validator identity, current mapping, new proof seals and completed CLI invocations. No full report or product execution was rerun for this checkpoint.

    Replacement Exact input bytes Exact final bytes Repetitions / full proofs
    Insert middle 4 KiB 524,283,904 524,288,000 5 / 1
    Append tail 4 KiB 524,283,904 524,288,000 5 / 1
    Prepend head 4 KiB 524,283,904 524,288,000 5 / 1
    Replace middle 2 KiB with 4 KiB 524,285,952 524,288,000 5 / 1
    Zero-extend tail 4 KiB 524,283,904 524,288,000 5 / 1

    The new versioned IDs and frozen hashes remain distinct from the five oversized original definitions. Those originals are preserved without being executed under the incompatible result-size cap. The other 58 inherited definitions/results keep their historical release disposition; this update does not claim 58 fresh passes, full inherited release qualification, #35 completion or overall terminal pass.

    Evidence: capped specification; five validated full rows; checkpoint manifest. All original failures and source/environment observations remain retained. Other required full-proof work continues; #35 and #21 remain open.

  6. yifanxuaaa commented on Sep 4, 2026

    @yifanxuaaa
    ContributorAuthor

    The user has amended Phase 1 acceptance: qualified fast verification is sufficient for routine benchmark verification. The published amendment supersedes earlier comments requiring every routine exhaustive proof before closure. The reference qualification contract preserves independent expected states, affected-content/metadata/alias/absence checks, authenticated references and deterministic witnesses.

    The posted performance results remain valid at their original source/environment identities. Completed full proofs remain accepted and are reused. At the scope checkpoint,48 routine slots already had full proofs; the305 unrun routine exhaustive counterparts are now deferred to Phase2 while their qualified fast checks are implemented and collected. Fast evidence keeps its actual assurance and explicit skipped coverage; it will not be labelled fully_verified.

    Required targeted reliability checks, the CDC boundary proof, exact expected-error oracles, resource and cleanup gates still apply. Observed failures still require focused repair confirmation. The already-qualified600-second proof is retained rather than repeated. This amendment does not manufacture missing evidence or itself establish terminal pass.

    Remaining routine families will close after their accepted fast/full coverage and applicable gates pass. #21 remains open for later phases and release.

  7. yifanxuaaa commented on Sep 4, 2026

    @yifanxuaaa
    ContributorAuthor

    Phase 1 is closed under the user's explicit withdrawal of all remaining verification tests. This is a scope withdrawal, NOT a claim that the original verification terminal criteria passed.

    The assistant designed an excessively expensive verification suite and spent too long expanding it after the user requested a much faster finish. That design is withdrawn and must be reassessed in Phase 2. No more verification work is scheduled.

    Final performance results:370 independently qualified active observations, with actual source identities and unoptimized timings. All15 suppressed case definitions, original failures and incomplete attempts remain preserved. Completed29 targeted proofs,48 routine full proofs and qualified fast evidence remain historical evidence; unrun verification is withdrawn/deferred, never relabeled passing.

    Explicit withdrawal and accountability record. Separate Phase 2 backlog. Central#21 stays open for Phase 2/release. No release tag was created.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

new featureA new user-facing capabilityv0.1.3LayerFS v0.1.3 checkpoint and delivery

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions