Skip to content

docs: align value frontier after VALUE-02 software integration #150

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
daniele21 merged 3 commits into from
Sep 3, 2026
Merged

docs: align value frontier after VALUE-02 software integration #150

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
9fe4e49
docs: refresh value frontier after VALUE-02 integration
daniele21 Sep 3, 2026
061b24b
docs: align incremental delivery with integrated VALUE-02 software
daniele21 Sep 3, 2026
937c411
docs: preserve VALUE-01 acceptance detail
daniele21 Sep 3, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
43 changes: 30 additions & 13 deletions docs/current-state.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ Status: active
Document type: current-state
Owner: repository
Canonical scope: state.repository
Last reviewed: 2026-09-02
Last reviewed: 2026-09-03

Short operational ledger only. Durable behavior belongs in architecture/ADR/design docs; active detail belongs in workstreams; Git history owns implementation history.

Expand All @@ -16,10 +16,12 @@ Primary product question:

> For this use case on this device, which available model + quantization + configuration gives me the best evidence-backed trade-off, and why?

Work now advances through vertical VALUE slices that unlock end-to-end outcomes. M1-M9 remain the capability/maturity coverage map rather than the delivery sequence.
Work advances through vertical VALUE slices that unlock end-to-end outcomes. M1-M9 remain the capability/maturity coverage map rather than the delivery sequence.

## Integrated baseline

Current integration head: `dev@0b9c376f2dbcbb167f8df8488374c1b0c5d0ace2`.

`dev` contains Overview; Find best setup `Goal -> Models -> Optimization -> Review -> Campaign -> Results`; Test a model; Live Run recovery; Runs/Run Detail; Compare; Library/Settings; Benchmark Detail; Run -> Samples -> Sample Evidence; same-case comparison; browser-local Light/Dark/System appearance; and built/package lifecycle support.

Campaigns revalidate frozen plan digests, persist reconnectable lifecycle separately from immutable Runs and apply compatibility before explicit decision policy. Quality, Performance and Resources remain separate; missing, incompatible, unavailable and not-retained evidence remain explicit.
Expand All @@ -30,43 +32,58 @@ VALUE-01 software/readiness lanes are integrated:
- **VALUE-01B / #118 DONE** — retained evidence completeness/portability verifier;
- **VALUE-01C / #119 DONE** — exact-head PRE_REAL-gated real-run entry point and retained run manifest.

Their branch validation passed Repository Validation, Browser Acceptance, Built Product/PRE_REAL and Repository Health before integration. The merge commits moved `dev`, so the representative run still requires a **fresh exact-head PRE_REAL PASS** for the final `dev` revision.
VALUE-02 software lanes are also integrated through PR #141:

## Current value frontier
- **VALUE-02A / #129 software DONE** — configured-target multi-model discovery and per-candidate Local LLM Server identity/telemetry attribution;
- **VALUE-02B / #130 software DONE** — bounded real multi-model Campaign/browser harness;
- **VALUE-02C / #131 software DONE** — retained multi-model decision evidence verifier.

Current executable slice: **VALUE-01 — Real single-model evidence loop** in [`workstreams/incremental-value-delivery.md`](workstreams/incremental-value-delivery.md).
This software integration does not satisfy the representative real-device acceptance owned by VALUE-01D / #120 and VALUE-02D / #132.

## Current value frontier

Target loop:
The next convergence sequence is:

```text
real target/device -> discover one real model -> Test a model -> real inference
-> Run Detail -> sample evidence -> retained .plab.zip
fresh exact-head PRE_REAL on current dev
-> VALUE-01D / #120 single-model REAL_ENVIRONMENT PASS
-> VALUE-02D / #132 multi-model REAL_ENVIRONMENT PASS
-> integrate the prepared VALUE-03 / VALUE-04 / VALUE-08 lanes
```

VALUE-01 remains **ACTIVE**. Its only remaining acceptance gate is **VALUE-01D / #120**, now READY for one retained `REAL_ENVIRONMENT` execution after a fresh exact-head PRE_REAL/Built Product pass.
VALUE-01 remains **ACTIVE** until #120 passes. VALUE-02 software is integrated, but VALUE-02 acceptance remains **BLOCKED** by #120 and then #132.

The previous VALUE-01 PRE_REAL handoffs are historical only because PR #141 moved `dev`; a new exact-head PRE_REAL/Built Product PASS is required for the current `dev` revision before representative execution.

## Active work

| Workstream | State | Next gate |
| --- | --- | --- |
| [Incremental value delivery](workstreams/incremental-value-delivery.md) | VALUE-01 ACTIVE; A/B/C DONE; D READY | refresh exact-head PRE_REAL, then execute #120 on representative hardware |
| [Incremental value delivery](workstreams/incremental-value-delivery.md) | VALUE-01 ACTIVE; VALUE-02 software integrated / acceptance blocked | refresh exact-head PRE_REAL -> execute #120 -> execute #132 |
| [Product UX/UI convergence](workstreams/product-ux-ui-convergence.md) | automated product/visual acceptance PASS | representative human accessibility/usability acceptance; then finalize/delete |
| [Representative device evidence](workstreams/representative-device-evidence.md) | EVID-001 READY | #120 retained real run supplies the first representative artifact set |
| [Local LLM Server migration](workstreams/local-llm-migration.md) | MIG-001 DONE / MIG-002 evidence-blocked / MIG-003 blocked | EV-3 + real PL replacement evidence; consumed by VALUE-07 |

Prepared off `dev`, but intentionally not integrated until VALUE-02 real acceptance:

- **VALUE-03A / PR #149** — consume runtime/model-declared generation parameter domains;
- **VALUE-04A / PR #148** — classify decision-grade device/resource evidence separately from contextual telemetry;
- **VALUE-08A / PR #147** — artifact-owned launcher that removes repository-development setup from normal launch.

## Delivery model

- `dev` is the integration line; ordinary feature branches start from current green `dev` and target `dev`.
- `main` is stable/release-oriented and is promoted deliberately with `FULL` validation.
- VALUE slices are vertical user outcomes. After VALUE-02, configuration optimization, device-aware evidence and distribution may proceed in parallel when ownership does not conflict.
- VALUE slices are vertical user outcomes. After VALUE-02 real acceptance, configuration optimization, device-aware evidence and distribution may proceed in parallel when ownership does not conflict.
- Parallel work uses explicit non-conflicting owners and one convergence gate; it must not create competing implementations of the same contract.
- Do not build broad subsystems in anticipation of later slices.

## Evidence still required

- fresh exact-head PRE_REAL/Built Product readiness for the final integrated `dev` revision;
- fresh exact-head PRE_REAL/Built Product readiness for current `dev`;
- VALUE-01D retained real target/model/device execution with verifier PASS;
- later VALUE-02/04/05/06 real decision, telemetry/repeatability and regression evidence;
- VALUE-02D retained 2+ real-model decision with verifier PASS;
- later VALUE-04/05/06 real telemetry/repeatability and regression evidence;
- representative human accessibility/usability acceptance before a reference-grade human UX claim;
- LLS EV-3 + real PL replacement run + post-disable cross-repository smoke before VALUE-07 cutover;
- branch protection/admin work remains tracked separately in GitHub issue #61.
47 changes: 39 additions & 8 deletions docs/workstreams/incremental-value-delivery.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,28 +29,28 @@ M1-M9 in `docs/roadmap.md` remain the capability/maturity map. This workstream o
| ID | User value unlocked | Depends on | Parallel | State |
| --- | --- | --- | --- | --- |
| VALUE-01 | **Real single-model evidence loop** — discover, test, inspect and export one real target/model | fresh exact-head PRE_REAL + VALUE-01D | internal lanes complete | ACTIVE |
| VALUE-02 | **Real model decision** — compare 2+ real candidates and return an explainable recommendation/no-rank | VALUE-01 | no | BLOCKED |
| VALUE-03 | **Configuration decision** — choose a supported configuration, not only a model | VALUE-02 | VALUE-04/08 | BLOCKED |
| VALUE-04 | **Device-aware decision** — real performance/resource evidence affects the trade-off | VALUE-02 | VALUE-03/08 | BLOCKED |
| VALUE-02 | **Real model decision** — compare 2+ real candidates and return an explainable recommendation/no-rank | VALUE-01D + fresh PRE_REAL + VALUE-02D | software A/B/C integrated | BLOCKED |
| VALUE-03 | **Configuration decision** — choose a supported configuration, not only a model | VALUE-02 real acceptance | VALUE-04/08 | BLOCKED |
| VALUE-04 | **Device-aware decision** — real performance/resource evidence affects the trade-off | VALUE-02 real acceptance | VALUE-03/08 | BLOCKED |
| VALUE-05 | **Confidence / repeatability** — controlled variability supports the recommendation | VALUE-04 | late VALUE-03 | BLOCKED |
| VALUE-06 | **Regression workflow** — real baseline vs candidate produces a policy outcome | VALUE-02, VALUE-05 | no | BLOCKED |
| VALUE-07 | **LLS evaluation cutover** — PL owns new evaluation; LLS stays serving/runtime owner | VALUE-03 + LLS gates | no | BLOCKED |
| VALUE-08 | **Low-friction distribution** — launch/connect/evaluate without repo-development setup | VALUE-02 | VALUE-03..07 | BLOCKED |
| VALUE-08 | **Low-friction distribution** — launch/connect/evaluate without repo-development setup | VALUE-02 real acceptance | VALUE-03..07 | BLOCKED |

Allowed states: `READY`, `ACTIVE`, `BLOCKED`, `DONE`. After VALUE-02, VALUE-03/04/08 may proceed in parallel where ownership is independent.
Allowed states: `READY`, `ACTIVE`, `BLOCKED`, `DONE`. After VALUE-02 real acceptance, VALUE-03/04/08 may proceed in parallel where ownership is independent.

## VALUE-01 execution graph

The software/readiness lanes were developed independently and converged on `dev`. The representative-device run is now the only remaining acceptance gate.
The software/readiness lanes are integrated. The representative-device run remains the acceptance gate.

| ID | Work | Owns/writes | State |
| --- | --- | --- | --- |
| VALUE-01A / #117 | Real built-browser loop against Local LLM Server | target-environment Playwright + bounded browser launcher | DONE |
| VALUE-01B / #118 | Evidence completeness + portability verifier | real-runtime verifier + deterministic tests | DONE |
| VALUE-01C / #119 | Exact-head real-run operator entry point | real-runtime smoke/runbook + readiness tests | DONE |
| VALUE-01D / #120 | Retained representative device execution | RUNTIME-1 artifact set + state transition | READY |
| VALUE-01D / #120 | Retained representative device execution | RUNTIME-1 artifact set + state transition | READY after fresh PRE_REAL |

A/B/C passed their required repository gates before integration. Because integration changes the commit SHA, #120 must start only after a fresh PRE_REAL/Built Product PASS whose source revision matches the final integrated `dev` HEAD.
PR #141 intentionally moved `dev` to integrate the completed VALUE-02 software for end-to-end testing. Therefore older PRE_REAL handoffs are historical evidence only; #120 must use a fresh PRE_REAL/Built Product PASS for the current `dev` revision.

## Current acceptance — VALUE-01

Expand All @@ -69,6 +69,37 @@ Acceptance:

`representative-device-evidence.md` owns the detailed real-device protocol/artifact rules.

## VALUE-02 execution graph

The deterministic/software portions are already integrated on `dev`; only representative acceptance remains.

| ID | Work | State |
| --- | --- | --- |
| VALUE-02A / #129 | Configured-target multi-model discovery + candidate evidence attribution | SOFTWARE DONE |
| VALUE-02B / #130 | Real multi-model Campaign/browser harness | SOFTWARE DONE |
| VALUE-02C / #131 | Retained multi-model decision evidence verifier | SOFTWARE DONE |
| VALUE-02D / #132 | Representative 2+ real-model decision | BLOCKED by #120 + fresh PRE_REAL |

VALUE-02 is not `DONE` merely because A/B/C are integrated. Acceptance still requires #120 PASS first and then one retained REAL_ENVIRONMENT #132 run whose browser/backend/verifier evidence agrees.

## Current convergence sequence

```text
current dev
-> fresh exact-head PRE_REAL/Built Product PASS
-> #120 single-model REAL_ENVIRONMENT PASS
-> #132 multi-model REAL_ENVIRONMENT PASS
-> VALUE-02 DONE
-> integrate prepared VALUE-03A / VALUE-04A / VALUE-08A
-> continue VALUE-03 / VALUE-04 / VALUE-08 in parallel
```

Prepared isolated lanes already exist and remain intentionally unmerged until VALUE-02 acceptance:

- VALUE-03A / PR #149 — runtime/model-declared bounded generation domains;
- VALUE-04A / PR #148 — policy-eligible device evidence classification;
- VALUE-08A / PR #147 — artifact-owned launcher.

## Later slice acceptance

| Slice | Minimum acceptance |
Expand Down
Loading