Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
8 changes: 8 additions & 0 deletions ROADMAP.md
Original file line number Diff line number Diff line change
Expand Up @@ -285,3 +285,11 @@ explicit output/evaluation/publication requirements, before general graph execut
[Static Wave F graph policy](docs/WAVE_F_STATIC_GRAPH_POLICY.md) adds declared branch
activation, conditional joins, explicit subgraph terminal decisions and a durable
program-dispatch ceiling. The subsequent [attempt-accounting slice](docs/WAVE_F_GRAPH_ATTEMPT_ACCOUNTING.md) separates reservations, consumption and release and adds explicitly authorized retry after a sealed pre-admission refusal. The subsequent [sourced-resource slice](docs/WAVE_F_RESOURCE_ACCOUNTING.md) adds distinct Eval reservations/consumption, exact runtime and provider-usage evidence, and bounded active-path reservation plans. Nested/conditional groups and general retries remain deferred.

### Operator-readiness stop condition

The [Wave F operator rehearsal](docs/WAVE_F_OPERATOR_REHEARSAL.md) moves the existing
static local control model through installed setup, inspection, review, budget
exhaustion and retained recovery. Once its operator and canonical gates pass,
freeze further local Wave F architecture expansion and return to product/release
work. This does not promote experimental graph/control contracts to stable APIs.
11 changes: 11 additions & 0 deletions docs/NEXT_PHASE_ARCHITECTURE.md
Original file line number Diff line number Diff line change
Expand Up @@ -556,3 +556,14 @@ an explicitly authorized second child run for the same node with exact original
Consumed or uncertain work cannot use that path. Nested/conditional groups and general
retries remain deferred. The subsequent [resource-accounting slice](WAVE_F_RESOURCE_ACCOUNTING.md) adds bounded Eval dispatch budgets, active-path reservation plans and exact runtime/SDK measurement references. Observed, provider-reported, estimated and unknown values remain distinct. Hard token/time/currency ceilings remain deferred; dynamic topology is not implied.
Remote trust and machine migration remain separate boundaries.

## Operator-readiness rehearsal and architecture freeze

The [operator-readiness exercise](WAVE_F_OPERATOR_REHEARSAL.md) uses the implemented
static graph architecture through one installed batch-summary host. Dispatch owns
the CLI integration; Kujo runtime, Workcell and Eval ownership do not change.
Concrete installation and explanation gaps are fixed without another scheduler,
protocol or lifecycle. After the operator proof and canonical gates pass, freeze
this local architecture lane and prioritize product/release usability. Remote
trust, machine migration and further graph/resource constructs require separate
adoption evidence and prioritization.
34 changes: 34 additions & 0 deletions docs/WAVE_F_OPERATOR_REHEARSAL.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,34 @@
# Wave F operator-readiness rehearsal

Dispatch's next step is an operator exercise, not another execution architecture
tranche. The bounded installed batch-summary host uses existing graph, review,
resource, effect, finalization and retained-recovery APIs. It adds no Kujo syntax,
participant protocol or scheduler.

The workflow is source JSON → typed producer summary → exact human review → Eval
→ pass/publication or fail/repair consumer → explicit graph terminal decision.
Program and Eval dispatch budgets remain distinct. A local OS-user decision is
revision-bound; output existence, approval and budget availability grant no effect
authority. Unknown provider usage/cost remain unknown.

The Dispatch [operator walkthrough](https://github.com/kujolang/dispatch/blob/5c8da03b59cf40ba9bd8fe5055813e8fb3caacb6/docs/operator-rehearsal.md)
and [first-hour findings](https://github.com/kujolang/dispatch/blob/5c8da03b59cf40ba9bd8fe5055813e8fb3caacb6/docs/OPERATOR_FIRST_HOUR.md)
record installation prerequisites and the tested interface. The black-box rehearsal
uses an installed package in a fresh HOME, real Workcell Git retention, a SQLite
receipt sink, a separate Eval process and actual SIGKILL timing. It exercises
wrong/stale approvals, quality failure, budget exhaustion and retained reservation
reconciliation without manually editing state. Full gate evidence remains required
before claiming the tranche verified.

The intended stop condition is explicit: after the operator proof and canonical
gates pass, freeze further local Wave F architecture expansion and return to
product/release work. General workflow authoring/usability can follow actual user
feedback. Dynamic graphs, arbitrary retries, hard token/time/currency ceilings,
remote trust, machine migration, public SDK stabilization and new node types remain
separately prioritized work, not automatic follow-on tranches.

This is experimental trusted-host static composition with surviving local evidence,
not universal production readiness. Existing one-use/consumed-work guarantees,
independent finalization and historical canonical bytes remain unchanged. No
runtime files or unrelated concurrent Kujo edits are part of this documentation
change.
Loading