Proof path visual
One compact visual map of the supplied requirement-to-decision flow. It explains the current state; it never executes a graph action.
Factory Studio / Graph Ops
A bounded control plane for Product, Mission, Proof, Gate, Trace, semantic lineage, and verified counterfactual repair. Follow the failure, compare every candidate, and understand the winning proof without executing it.
Connecting to the local workspace.
Current stage, elapsed time, completed stages, and measured telemetry will appear here. Unknown token, cost, and productivity values stay unknown.
See what changed, why it affects evidence, the smallest next step, and who local Git history observed on the selected work. It is explanatory and read-only: it does not run a proof, recall memory bodies, or authorize a person.
Loading bounded local Git history.
Brief refreshes no more than once every five seconds. Live assembly telemetry refreshes separately.
Nodes
—Edges
—Evidenced
—Lineage runs
—Forensic findings
—Repair candidates
—Graph status
LoadingOne compact visual map of the supplied requirement-to-decision flow. It explains the current state; it never executes a graph action.
Deterministic ratios from this bounded graph result, not estimated productivity or a quality score.
See the structural critical path, safe parallel waves, shared-proof candidates, and blocker chains before selecting a separate, approved harness.
Blocks propagate visibly; every runnable item still requires independent verification.
These are proposal-only groups. They do not start work or authorize proof reuse.
No sealed admission packet has been projected from this workspace.
Locked: export and re-verify a time-bounded packet with a separate harness. Graph Ops cannot execute a wave, approve, repair, merge, publish, deploy, sign, message, access credentials, or grant a connector.
Every candidate is hash-bound, scope-checked, independently proven, mutation-tested, and ranked by one deterministic ordering.
No evaluation loaded.
Inspect, export, and validate the decision here. Applying code, merging, publishing, and deploying require separate authority.
Locked: ProofSearch has no workspace-mutation, approval, merge, publication, or deployment authority.
Rank supplied, non-executing experiments by exactly how many viable repair pairs they separate. Predictions are hypotheses, never proof or execution authority.
No sealed Evidence Frontier loaded.
Copy, export, and validate the plan. A separate approved runner is required before any experiment may run.
Locked: Graph Ops ranks evidence only; it cannot execute a command, mutate a workspace, or grant approval.
Only independently promoted, exact-scope, purpose-bound, non-expired references can influence a future decision. This panel redacts memory references and summaries by design.
No local continuity records loaded.
Graph Ops can inspect local metadata. It cannot store memory content, promote a lesson, sign evidence, or grant an agent access to a record.
Locked: promotion requires a separate identity, exact purpose, evidence references, and an explicit local CLI action.
Each declared agent earns a local, expiring tier from governed run evidence. A severe hollow-test, hollow-validator, or scope-escape result demotes it automatically. Identity remains declared unless an external harness proves it.
No governed agent evidence has been projected.
Inspect and verify local evidence here. This screen cannot issue a license, raise autonomy, start a candidate, or grant execution authority.
Locked: licenses are derived from independently verified governed events. Use the explicit local CLI after recording evidence; Graph Ops does not promote an agent.
Compare sealed state lineage, isolate the first semantic divergence, and preview the smallest recovery branch.
No deterministic concurrency or state anomalies detected.
Prepare and validate the recovery locally. Workspace mutation stays locked until a separate signed approval is supplied.
Locked: no named, expiring, signed approval is bound. Graph Ops cannot grant one.
Loading the authenticated local graph result.
Graph data is read from /api/graph-ops. A separate token-bound local request can record one named authorization or consume one Reality Check authorization. Labels are rendered as text nodes.