Repository navigation
P0: propose event-loop and language benchmark contracts - #276
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
P0 selection handoff, not an integration approval (2026-10-10).
Validation commands for the verifier: Idempotency key: |
|
P0 selection handoff (not an independent approval or permission to merge).
Idempotency key Validation after repair: |
|
P0 selection and local-partial-work handoff; not an integration approval.
Idempotency key: Exact post-repair commands: |
|
P0 handoff/selection only; NOT an independent approval or merge instruction.
Idempotency key Exact read-only validation/reconciliation commands: Success: explicit independent positive P0 recommendation bound to this SHA/tree and green exact-head |
|
P0 selection handoff (not independent verification or merge approval). No files changed.
Idempotency key: Exact verifier commands: |
|
P0 corpus-path handoff, 2026-10-11. Agent-decided, owner may revisit: reject Windows drive-prefixed ( |
|
P0 handoff / ONE lane selection, not a merge approval. No repository files changed.
Idempotency key Validation on repaired tree: Success: repaired P0 contract passes its exit gate with fresh exact-head Required and independent positive verification; integration is separate. Failure state |
|
P0 selection handoff, not an independent review or merge approval. Agent-decided, owner may revisit for every judgment here:
Idempotency key: Exact read-only validation: Success: explicit independent positive P0 recommendation for the unchanged SHA/tree plus still-green exact-head Required; then separately reconcile delivery on this existing PR under AGENTS. Failure |
|
Independent, read-only P0 verification of published head The P0 exit is met for this proposed contract: Fresh local evidence on this unchanged tree: |
|
P0 lane selection / handoff, not review approval or permission to merge. No repository files edited.
Success: repaired P0 gate with fresh exact-head Required and independent positive review; this repair lane does NOT merge. Failure |
|
P0 handoff delta to the existing lane decision; not independent approval, a new PR, or permission to merge. No files modified by this inspection.
|
|
P0 selection/handoff only; not a positive review or merge instruction. No repository files changed.
Idempotency key: Validation for the released reviewer: Success: independent positive P0 gate review and explicit merge recommendation for this exact head with passing exact-head Required; delivery is separate. Failure: |
|
Inspection/decision handoff only; no file change, new PR, review approval, or merge. Agent-decided, owner may revisit for each choice below.
Idempotency key Exact validation in a loopback-capable environment, one owner per expensive command: Success condition: reconcile the local parity discrepancy with exact-head CI; complete applicable aggregate/native checks or explain environment-specific failures with independent evidence; obtain a fresh integration recommendation explicitly supporting merge, then the delivery owner can recheck head/Required/threads/mergeability and deliver via existing #276 only. Failure state |
|
P0 selection/handoff amendment on exact head Agent-decided, owner may revisit: Per AGENTS.md, use the exact-head Agent-decided, owner may revisit: select only the existing deferred P0 #276 delivery task |
|
P0 selection and reconciliation handoff, not an integration approval. No repository files changed.
Idempotency key Exact validation: Success: exact-head independent positive P0 review, parity disposition with evidence, fresh explicit integration recommendation and green exact-head Required; only a separately released delivery task may ready/auto-merge this same PR after rechecking head, scope, threads, mergeability and main. Failure |
|
P0 selection/handoff correction, not approval to merge. No files changed. The previous inspection comment said independent review covered only an older head. Correction: an independent content reviewer DID inspect exact Agent-decided, owner may revisit: select exactly one already-held lane: P0 delivery/reconciliation of this SAME draft PR #276, XCB Agent-decided, owner may revisit: P0 acceptance is a versioned event-loop and benchmark-result contract, actor/supervisor/habitat/revision vocabulary, source-to-runtime identities, no-separate-runtime decision and pinned baseline corpus/protocol; strict unknown-field refusal, bounds on every count/byte field, >=1 valid and >=5 invalid fixtures. One valid/ten invalid plus synthetic timings are contract evidence, not measured event-loop performance/parity or cumulative competence. Independent integration recommendation must explicitly disposition exact-head CI versus host-restricted local aggregate/parity and earlier old-head mismatch before readying this PR. A matched loopback-capable completed parity run is an alternative, not a blind repeat; fix a reproduced defect inside P0. Idempotency key Exact validation for the released lane: Success: fresh affirmative independent integration verdict for this unchanged P0 tree, explicit parity disposition, green exact-head Required and clean scope; only then consider the existing PR's normal delivery gates. Failure |
|
P0 selection/handoff only; not an independent affirmative review or permission to merge. No repository files changed.
Key: Exact validation for the released lane: Success for the follow-up: independent affirmative contract review of this tree, explicit integration recommendation after parity disposition, current Required/threads/mergeability recheck, then normal delivery of this existing PR and green post-merge main Required, each evidenced separately. This selector does not deliver. Failure |
|
P1 selection/handoff only, not implementation or permission to merge another PR. No repository files changed.
Acceptance: typed event, transition, state-write, notification, deferral and escalation records; event identity/deduplication and conflict rejection; explicit mailbox backpressure/failure outcomes; replayable bounded trace; static effect/resource summary; strict Exact future validation (on the eventual P1 tree): Idempotency key SHA-256 |
|
P1 selection/reconciliation handoff, 2026-10-12. No repository files edited by this inspection. Not a review approval or permission to integrate partial work.
P1 acceptance: typed events, transitions, state writes, notifications, deferrals and escalations; identity/deduplication; explicit backpressure/failure; replayable trace; static effect/resource summaries. Both TS and Rust strictly parse identical valid/invalid vectors with equal canonical digests and refusal behavior (unknown fields, bounds, conflicting identities). No scheduler or provider. Future exact checks: Idempotency key: |
|
Inspection handoff, 2026-10-12. No repository files edited here; this is not P1 verification, review approval, or permission to merge partial work.
P1 acceptance: typed events, transitions, state writes, notifications, deferrals and escalations; identity/deduplication; explicit backpressure/failure; replayable trace; static effect/resource summaries. Strict TypeScript/Rust admission of the same valid/invalid vectors must yield identical canonical digests and refusal codes; no scheduler or provider. The current new trace spec explicitly checks shape/identity only, so P1 remains open. Future gates: |
Scope
P0 language-contract fixtures and event-loop specification only:
spec/v1/{README,event-loop}.mdandbenchmarks/language/**. The contract and synthetic fixture timings do not qualify measured performance, source provenance, a runtime, event-loop cross-runtime parity, or cumulative competence. P1/P2 remain gated until P0 integrates.Reviewed proposal
Head
926c5795c11e0d91145c9385931534d9ce24e8b2, tree0a7f9d2a7c6e30b3493d8ec64fd92b5a80497c01, basebc6ddae6e426b2727a3ce7e07158b248bae74309. The 28 changed paths are limited to the P0 scope above. This head repairs the previous content HOLD ondb3f787f: a transition rejects a repeated state-field write with stableEVENT_LOOP_SEMANTICat the second path; distinct fields may commit together. The new test and spec agree. Event source/sequence semantics remain agent-decided and owner-revisitable (seebenchmarks/language/P0-EVENT-IDENTITY-DECISION.md); older repairs are inP0-REPAIR-EVIDENCE.md.Independent AI content review on this exact head/tree on 2026-10-12 (XCB
t_cc65185eda5a5c42d6792206f49d7057cccb8f84ab53594377664f4d6be225af, confirmed byt_64679d4067f6e2f81975a24c43aea63fc961eb80fa7b2fd20097634aa1e288bcandt_b517f2ab5375a1803e9ef65274b504163468dedf2de28a0523dee269e53e947f) is affirmative for delivery of the P0 proposal only, superseding the previous-head HOLD. This is not human approval or evidence of runtime parity.Gates and limitations
Focused local
bun test benchmarks/languagepassed (39 tests, 502 assertions); docs, site build, typecheck, lint, Cargo format and Clippy, native build and PR diff check passed in the independent review. Exact-head Check run 38206769860 passed Required on attempt 2, including the incumbent native and application parity gates. Its first Test (3/3) attempt failed SQLite IOERR_RDLOCK/BUSY; one diagnosed failed-job rerun passed. CI application parity compares existing runtimes, not this proposed event loop.Local
bun run checkand application parity timed out at 600s with loopback restrictions; workspace Cargo tests failed intests/http.rslocally, and default Cargo fetch had SSL -9808. These are not local passes; the same required gates completed in loopback-capable CI on the exact PR head. Synthetic timings and source digests are not performance or provenance results.Delivery
The separately released delivery task rechecked the exact head/tree/base, all 28 paths, mergeability, review threads and
gh pr checks 276 -R hraness/algal --requiredon 2026-10-12. No new blocker was found. Ready and enable normal squash auto-merge on this same PR; verify the merge SHA and post-merge main Required. Do not force-push, bypass checks, or claim P1/P2/event-loop runtime delivery. No release is requested.