This table consolidates every capability described across this section's nine pages, with the status token, the primary evidence anchor, and any caveat. Status tokens follow the register's fixed vocabulary: verified, production-record, private-test-stage, target-contract, upstream, extension, retired, quarantined, unverified. Every path below exists at frontend pin 99f49dae6368414896bf2858cb848f5a7c7fcf98. Full machine-readable claims with falsifiable_check commands are in the frontend evidence bundle (frontend-evidence.json, evidence/frontend/).
Editor-first layout; draft vs. immutable revision distinguished by type
Authoring completions/diagnostics from backend
verified
src/strategy/authoring/registry.ts
Never hardcodes Nautilus symbol/diagnostic content
Revision-based backtest submission
verified
src/strategy/runs/run-config.tsx
One instrument per job; multi-instrument = client-side batch of jobs
Execution controls (capital/fee/fill/seed) on submit
target-contract
src/strategy/runs/run-config.tsx
Not in wire shape; shown inert with reason; see CR-026
Same controls on a finished job's execution block
verified
src/strategy/runs/backtests.tsx
Typed on the answer only
No progress/ETA on running jobs
verified
src/strategy/runs/backtests.tsx
Backend publishes no percentage/counter/ETA fact
Sandbox start/stop against a saved revision
verified
src/strategy/runs/sandbox-panel.tsx
Gated to private-operator deployments only; at the reviewed backend pin, sandbox_start/sandbox_stop/sandbox_status are deferred/unavailable server-side, so a submitted start/stop reaches a not-yet-implemented backend route, not a working sandbox lane
Real-money execution claim
quarantined
—
Not claimed anywhere at this pin; environment label is backend-verbatim, unverified beyond that
Only lightweight summaries persisted; details always re-fetched
One-shot memoized backend-fact reads
verified
src/datafeed/resolution-contract.ts
Failed reads are not memoized
Runtime ajv schema validation, compiled once per schema
verified
src/contracts/validate.ts
Ordered check sequence is itself part of the contract
Trading facts (orders/fills/positions/bars) persisted to browser storage
unverified
—
No such persistence was found anywhere at this pin (only UI preference, saved screens, and the lightweight backtest-job roster are persisted); this is an absence, not a documented deliberate removal, so it is not labeled retired
Rows marked private-test-stage describe consoles that exist and are reachable in the build but are explicitly treated by the project's own navigation as secondary, not the product surface. Rows marked target-contract name a gap the project has itself already filed as an open contract request against the backend (see the linked contract-request documents referenced on the corresponding page, under docs/contract-requests/ in the frontend repository). No row in this table claims real-money trade execution, completed multi-user identity, or resurrects a legacy trading-engine claim; where the code path was insufficient to fully resolve a question, the row is marked unverified and detailed in the frontend evidence bundle's open-questions log rather than asserted.
Evidence and source pins for this page
Verified. Current behaviour, confirmed in source at the pinned commit.
Verified on against the following immutable sources: