Workbench
The local write path in Canopus. Each writable frontier can accept papers, datasets, protocols, or results. The ingest path drafts reviewable changes to the record; review decides what becomes Vela-backed frontier state.
Workbench is the local engine. It receives source material, produces attempt packets and reviewable changes, then routes them toward review instead of silently mutating the record.
A bounded scientific record gives the work a target: findings, sources, links, review state, and proof.
Canopus engine surfaces produce attempt packets, reviewable changes, checks, and traces against frontier records.
Review, benchmarks, proof, checked changes, and failure packets decide what can change the record.
Accepted state rolls up into atlases and constellations so users can inspect the larger body of science.
A writable frontier should expose the objects that can ask to change state, the gates that judge them, and the event that finally mutates the record.
gapframing
A missing experiment, unresolved contradiction, extraction defect, or stale proof cell worth reviewing.
reviewable changework
A reviewable frontier-state change with affected findings, evidence, rationale, checks, and expected proof impact.
attemptwork
An agent, capability, procedure, system, or human run with input material, declared output material, environment, disclosures, failure state, and cited artifacts.
checkgate
A schema, provenance, contradiction, benchmark, proof, or evaluation result over a reviewable change or release.
reviewgate
A human or authorized reviewer decision over a reviewable change, check, candidate gap, or contested finding.
eventaccepted
A signed, reviewable state transition that changes the Vela-backed frontier record.
Workbench should make the common write paths visible before a user opens a frontier: source intake, reproduction, review, and capability registration all produce packets before review changes state.
source
Add source materialpacket
source record with provenance, locator, extraction method, and caveats
inspect source connectors →surface
open workbench →reproduce
Run a reproduction or benchmarkentry
task, benchmark target, code artifact, environment, and expected assertion
choose a campaign target →packet
attempt packet with logs, runner, input material, declared output material, and failure state
inspect harnesses →surface
open campaigns →surface
review queue →entry
declared input material, output lanes, auth boundary, version, and limits
browse capability records →accepted effect
engine capability linked to agents, runs, and affected frontiers
inspect agent usage →surface
inspect capabilities →Signals collect the next work across writable frontiers: review queues, open tasks, contested findings, and local checks that need attention before a record can be treated as clear.
No active signals in this view. The record has no visible queue, blocker, or validation item under this index.
No writable frontiers found. A frontier becomes writable once it is a full .vela/ workspace.