Era 2 cut plan: reset the product surface, keep the measurement code - #67
Draft
RaapTechllc wants to merge 1 commit into
Draft
RaapTechllc wants to merge 1 commit into
RaapTechllc wants to merge 1 commit into
Conversation
… Usage Sequenced deletion series for the retired Mini-PC hardware, CLI, dashboard and prototype surfaces, verified against a dependency inventory so keepers (agentbench, Agent Cabinet, known_models catalog) are untouched. Defines the Era 2 product and seven 'not slop' acceptance rules for every chart and number. Co-authored-by: RaapTechllc <RaapTechllc@users.noreply.github.com>
This was referenced Sep 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Docs-only handoff, follow-up to #66. Answers "should we start over?" with a sequenced deletion series inside the existing repo instead of a rewrite.
docs/PLAN-era-2-cut.md: Era 2 product definition (Benchmark Lens, Agent Cabinet, Solo/Multiplayer, Usage Board; one rule set), seven "not slop" acceptance rules for every chart and number, a keep/delete inventory verified against actual route/model/page dependencies, and eight one-PR-each steps (E2.1 frontend cut + new landing, E2.2 CLI, E2.3 hardware routes, E2.4 legacy models/schemas/seed, E2.5 drop migration, E2.6benchmarks/prototype, E2.7 docs/README/copy, E2.8 PR template).docs/PROJECT-STATUS.md: pointer paragraph.Inventory findings that shape the order
seed_known_models+known_models_seed.json, which stay.agents_routerdoes not useModelQuality; the four legacy tables (benchmarks,hardware_specs,reference_profiles,model_quality) have no creating migration, so removal needs a newDROP ... IF EXISTSmigration (E2.5, production run gated on owner go).cli/and rootbenchmarks/are imported by nothing inagentbench/orbackend/; each has its own CI step to remove.test_agent_cabinet_api.pyhas one assertion that hits the hardware/api/v1/leaderboardand must be rewritten in E2.3.Owner decisions
MoA Calculator (default delete),
/leaderboardredirect retention, production timing of the drop migration, archive vs delete for root docs.No product code changed in this PR.