Skip to content

epic: Road to 0.0.1-stable #301

Description

@rickylabs

Program epic tracking everything between 0.0.1-alpha.19 and a credible 0.0.1-beta.x, then 0.0.1-stable. Supervised by the road-to-stable program session; the coordinator holds the merge gate.

Locked positioning

NetScript competes on AI-agent build-efficiency, not runtime throughput. Defensible falsifiable claim: one-primitive-per-concern + compile-time contract enforcement + explicit plugin composition let an AI agent ship production-grade backend code in fewer turns with less hand-rolled code than bare routers, and at production-readiness parity-or-better vs the batteries-included tier (Encore.ts). This sidesteps the RPS fight and plays where the evidence is winnable. Falsifiable via turns_to_green + production_rubric_pass_rate (t1/t2), low-variance test_pass_rate (t1), and a reactive Fresh-UI task (t3b) as a separate extended axis. We do not claim shipped AI-backend capability (in-flight #238), throughput leadership, or API stability yet. Credibility asset: fork Encore's exact weights, publish raw traces, disclose the alpha-corpus + Fresh-2-beta confounds openly. Source: validated netscript-bench-research.v2.md.

Locked acceptance criteria (bench numbers = post-Run-1 "match-or-beat peer median" placeholders)

0.0.1-beta.x — correctness floor + repo maturity

  • Self-bench exists; Run-1 t1+t2 test_pass_rate >= 0.90 median; t1 turns_to_green <= NestJS median; t1 production_rubric >= 0.50; zero harness-level NetScript failures.
  • e2e-cli-prod + scaffold.runtime green (hard gates); plugin-service type-soundness fixed (172a-2-SOUND); public surface doc-linted; zero machine-specific assumptions in shipped tooling; doctrine v2 ratified with fitness functions in arch:check; stale-elimination wave-1 complete; one-shot deterministic release:cut proven by cutting the beta itself.

0.0.1-stable — leadership + production-readiness

  • t2 turns_to_green strictly below all bare routers and <= Encore.ts; production_rubric >= 0.80 and test_pass_rate >= 0.95 on t1-t3; composite top-2 among core-5; reproduced across Sonnet 5 + Opus 4.8; t3b >= 0.90.
  • Full cross-framework batch published; continuous self-bench per release; API/semver policy + public-surface-diff CI gate; deprecation policy enforced; >=1 verified production deployment path + CI deployability gate; zero unowned arch-debt.

Children (sub-epics)

Tracked in-flight lanes (owned elsewhere — referenced, not stomped)

Operating rules

Focused reviewable PRs only, never a mega-PR. Every branch cuts from origin/main (the working checkout ran 380 commits behind during audit). Doctrine-first for packages//plugins/; contract-first; wrap-don't-reinvent. Implementer and evaluator are separate sessions; CI quality trio (fmt:check+lint+check, workspace check needs --unstable-kv) reproduced before every PR; scaffold-affecting changes run deno task e2e:cli run scaffold.runtime --cleanup --format pretty. e2e-cli-prod stays a hard release gate. Publishing stays in CI via OIDC. No backward-compat pre-beta: stale code is deleted, not shimmed.

Stale-elimination methodology note (S6/#307)

Deleting a .css/asset file requires a class-name-coupling check (does any shipped component apply the BEM/selectors it defines via cn(...)/class=?), not only an @import/<link>/registry-import grep. Wave-1 nearly dropped fresh-ui/src/presentation/data-grid.css, which styles the shipped exported DataGrid (#225) purely by ns-data-grid* class-name coupling — invisible to import-grep and to deno check (CSS is not type-checked). Restored before merge (PR #324).

User decisions pending (bench §12)

D1 VM provider · D2 framework list · D3 task count · D4 score weights · D5 model+cadence · D6 repo location · D7 license. Plus product escalations: beta/stable version-surface strategy; --legacy-aspire removal approval; packages/runtime-config roadmap-or-retire. From #313 (DB layer, coordinator-held): default-flip policy · Postgres-only-vs-all-engines matrix policy · validator-branch confirmation. NetScript self-bench proceeds without any of these.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions