Skip to content

V1_FREEZE_CANDIDATE.md

Latest commit

 

History

History
94 lines (60 loc) · 2.72 KB

V1_FREEZE_CANDIDATE.md

File metadata and controls

94 lines (60 loc) · 2.72 KB
Raw

CodeWell V1 Freeze Candidate

Last updated: 2026-05-21

Purpose

This document defines the current candidate baseline for freezing CodeWell V1.

It is not a public launch note.

It exists to separate three things that should not be conflated:

  • a stable internal V1 baseline
  • a public open-source release decision
  • later V2 research work

Current Candidate

Current working branch:

  • feature/precision-governor-v1

Current preserved pre-V1 snapshot:

  • branch: snapshot/pre-precision-governor
  • tag: pre-precision-governor-2026-05-19

Current V1 freeze candidate should be understood as:

  • the state after the recent retrieval-policy refinements
  • the current TS/JS real-project evaluation coverage
  • the completed strong_multi_goal repeated-run protocol

What Is Already True

The current candidate now has:

  • a lightweight local-first product direction
  • no required LLM API, vector DB, hosted service, or reranker
  • maintained fixture, self-eval, package, and real-project evaluation paths
  • internal TS/JS agent-eval evidence with bucketed interpretation
  • a completed 3 x 2 repeated-run read for the strong_multi_goal task slice
  • a product-facing V1 evidence summary in docs/V1_EVALUATION_NOTE.md

What V1 Can Honestly Claim

Reasonable V1 claim:

CodeWell is a selective navigation aid for coding agents on repository tasks with real path ambiguity.

Reasonable V1 non-claim:

CodeWell is not yet a universal speedup layer across all coding tasks or all prompt shapes.

Freeze Meaning

Freezing V1 should mean:

  1. preserve this state as the comparison baseline for V2
  2. preserve the current evaluation interpretation alongside the code
  3. stop changing the core product thesis for V1
  4. allow later V2 work to branch cleanly without rewriting the V1 evidence story

It should not automatically mean:

  1. publicly launch immediately
  2. stop improving docs or release packaging
  3. claim benchmark-level external validation

Remaining Freeze-Adjacent Work

Before declaring the baseline frozen in practice, the remaining work is mostly packaging and release-facing clarity:

  1. update release-facing notes to reference the V1 evidence summary directly
  2. decide whether to create a dedicated V1 branch or tag such as v1-open-source-baseline
  3. run or re-run the full release gate when the working tree is ready
  4. capture the final freeze summary alongside the chosen branch/tag

Recommended Next Action

The next concrete action is:

  1. create the final freeze branch/tag for this V1 candidate
  2. store the final summary docs beside that snapshot
  3. start V2 work on a separate branch

Related Files

  • docs/V1_EVALUATION_NOTE.md
  • docs/RELEASE_READINESS.md
  • docs/AGENT_EVAL_SUMMARY.md
  • docs/AGENT_EVAL_CONCLUSION.md