Grove

Evidence, learning and publication — actual records, separate authority.

Reader observes; annotator corrects; operator trains and evaluates; publisher approves. Tokens are never saved or sent outside this service.

Starting Zio/WASM controller…

1. Observe, predict, correct

Predictions name their immutable model. Filed corrections and actually learned corrections are distinct.

Two entries: image sensor first, then numeric. Each is "true" or "false".

Answers bound to their exact snapshot
PredictionSnapshotOutputAbstainedCorrect
Filed is not learned
SignalStatusIn forceLearned into

Conflicts and refusals

2. Queue, traces, checkpoints and lineage

Training names graph, weights, data, optional val_data, steps, seed and save_at. Input paths belong to the server's allowed root. Source work is a Zio program. steps_budget bounds the run.

Actual state and consumed steps; resumes never rewrite parents
RunStateStepsResumed from

    Lineage and checkpoint recovery

    3. Evaluate, compare and select

    Protocol-bound metrics and gates; selection does not publish
    SnapshotRepeatsMean metricsGatesSelect

    4. Modules and experts

    Semantic spaces, frozen/shared parameters, permissions and ensemble experts from the snapshot.

    No snapshot loaded.

    5. Review proposed logic

    
        

    6. Human approval and versioned publication

    Only an authenticated publisher can approve. Qualification never publishes automatically. Confirm the exact snapshot, protocol and expected active version.

    No active publication.

    Immutable publication history