Factory Studio / Graph Ops

Follow the proof path.

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.

Read-only inspection. Graph Ops cannot execute, approve, publish, deploy, sign, message, access credentials, or grant connectors until a named person creates a narrowly scoped, expiring local authorization. WebMCP is a progressive enhancement; checking browser support.
Start here · one question first

What do you need to prove today?

Choose the outcome that matches your work. Code Factory keeps the deeper machinery available without making you learn it before your first useful result.

Read-only guide
Individual developerCan this test actually fail?factory first-proof --root .
Engineering teamDid the agent build what we asked for?factory oracle status --root .
Enterprise evaluatorCan we govern agent work without trusting its story?factory graph ops --root . --json
Show specialized modules only when needed

Advanced proof, SaaS, mobile, multi-repository, and enterprise controls appear below. AppForge applies only when mobile delivery is explicitly in scope. Every consequential action remains separately reviewed.

This guide runs nothing. It does not approve intent, start an agent, change a repository, access credentials, or release work.

Live Factory telemetry

Connecting to the local workspace.

Loading

Current stage, elapsed time, completed stages, and measured telemetry will appear here. Unknown token, cost, and productivity values stay unknown.

Open specialized modules and their blockersFor teams already using sealed intent, agent evidence, SaaS, mobile delivery, or enterprise controls.
Mission Control · shared authority map

One truth for people and connected agents.

Humans decide intent and final approval. Agents receive the same sealed, local evidence but cannot alter the contract, threshold, scope, repair decision, Git state, or release. Unknowns stay visible instead of being inferred away.

Loading
Human controlReview state loading
Agent controlSupervised protocol loading
IntentOracle evidence loading
RepairRepair evidence loading
DecisionNext action loading

This panel is read-only. It never turns a green card into approval or a connected agent into an authorized actor.

Senior Engineering · runtime assurance

Six ways a green build can still fail users.

Challenge workflow invariants, tenant boundaries, retries and recovery, consumer contracts, database migrations, and performance or memory retention. Every lane shows what failed, why it matters, the evidence digest, and the smallest repair.

Not run
Stateful workflowsWaiting for signed evidence
Tenant isolationWaiting for signed evidence
Failure recoveryWaiting for signed evidence
Consumer compatibilityWaiting for signed evidence
Migration integrityWaiting for signed evidence
Performance + memoryWaiting for signed evidence

No self-hash-verified receipt yet. Run an externally signed six-lane plan; this screen cannot invent thresholds or execute tests.

Memory Spine · proof-aware briefing

Turn the diff into the next safe proof.

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 local facts
1 · What changedLoading local change facts.
2 · Evidence stateLoading proof state.
3 · Do this nextLoading next action.
4 · Team contributionLoading local Git attribution.

Observed project contributors

Loading bounded local Git history.

Brief refreshes no more than once every five seconds. Live assembly telemetry refreshes separately.

Proof Review · team inbox

Review the riskiest item first.

Current, stale, and invalid proof reviews stay separate. This queue never infers productivity and never approves work.

Loading
Current0
Stale0
Invalid0
Learned regressions0
No current review itemCreate a proof review from a confirmed intent contract.
Revenue · evidence before action

See exactly where purchase reality diverges.

Build the monetization lane, replay the observed lifecycle, challenge every failure path, and invalidate only conclusions touched by policy drift.

No bundle
Build contractNo hash-bound bundle
Purchase replayNo build-bound replay
Failure matrixNo negative-path evidence
Policy watchNo source comparison
TestFlight inboxNo authorized local export
Human decisionUnknowns and mismatches block green; provider writes remain locked.
No generated bundle yet. App Store writes, pricing, offers, experiments, and publication remain locked.
SaaS Reality · provider neutral

Did login, payment, and permission agree?

Trace an observed OAuth/OIDC identity through tenant authorization, checkout, verified webhook, entitlement, feature access, and revocation. Clerk, Auth0, Okta, Entra, Cognito, Supabase, Firebase, and other compliant providers use the same evidence contract.

No receipt
IdentityIssuer, audience, active token, and PKCE contract
AuthorizationSubject, tenant, and role binding
EntitlementPromise, SKU, webhook, and access order
RevocationCancel, refund, and expiry must remove access
No hash-valid receipt. Unknown evidence stays blocked; no provider is contacted or mutated.
AppForge + SaaS · mission control

Improve your app before Apple finds the gap.

Start with one plain-English mission and one exact build. AppForge binds user design input, adaptive native-surface signals, an iPhone/iPad proof plan, truthful storefront story coverage, strict UI and accessibility evidence, SaaS reality, policy applicability, current-build media, supervised physical-device evidence, and a credential-free release rehearsal without placing secrets in Code Factory. A supervised agent may prepare evidence; only a named human can authorize the final Apple handoff.

Init + 9 evidence lanes
1 · MissionWho the app serves and what they need to accomplish.
2 · TensionWhich design, policy, or runtime gap could delay review.
3 · GuidanceThe smallest exact evidence needed to resolve it.
4 · AgencyYou choose human-controlled or supervised preparation.
5 · TransformationUnknowns become verified facts or visible blockers.
6 · Ready handoffA sealed receipt and named approval unlock one exact next step.
Use a keychain item or environment-variable name. Raw keys and passwords are refused.
Your review pathConnect references
Classify every policy
Import current-build evidence
Resolve every blocker
Review what changed
Authorize one exact handoff

Locked: App Review, Store media, SaaS lifecycle, strict quality-audit, adaptive native-surface preflight, and any required Device Reality receipt must match the same candidate before AppForge issues the final Markdown/PDF dossier. Native Surface binds confirmed user design input to local Swift sources, adaptive navigation signals, accessibility fallbacks, restrained custom glass, and the device-bound screenshot storyboard. It is static evidence—not a device or approval claim. Release Rehearsal seals a Fastlane lane, App Store Connect CLI app ID, Cider YAML-manifest hash, Swiftlane build/test/archive/export source sequence, or a Zealot-style artifact/channel/audience manifest. It keeps local readiness, archive, upload, processing, beta delivery, review submission, and Apple decision separate—and never invokes a provider. Device Reality seals the approved journey, forbidden outcome, design-input hash, and allowed capture transport before evidence collection. A separate named, expiring human authorization is still required for any Apple handoff.

Oracle Firewall · Shadow Oracle Loop

Prove the gate is still honest.

Freeze the exact original request before coding. Only human-confirmed or trusted-source rules can release work. A separate challenge lane targets the implementation and boundary cases; it cannot edit the contract, production code, or a test.

No sealed contract

Proof chain: source → obligation → forbidden behavior → gate → test → evidence → decision.

SourceNo immutable handoff
Approved obligationNo approved rule
Forbidden behaviorNo negative invariant
Gate + testNo independent challenge plan
Evidence → decisionHuman review remains required
0 current contractsAny threshold relaxation, removed negative case, new exception, or rewritten test emits E_ORACLE_WEAKENING, pauses autonomous work, and opens a demotion incident.

Locked: this screen reads local proof. It cannot approve a successor contract, raise autonomy, modify a test, run a challenge, or contact a provider. Use a separate named human approval to seal a successor.

Intent Authorization Plane · deterministic handoff

A message is not permission.

Before a worker can rely on a handoff, FactoryLine binds it to one sealed Oracle Contract, one versioned context, one declared receiver, a narrow action list, an exact scope, and an expiry. A green schema never proves intent; independent implementation evidence and a human decision still matter.

No sealed handoff
Sealed intentNo Oracle Contract binding
Shared contextNo versioned context
Typed handoffNo constrained message
Expiring leaseNo active least-privilege lease
Evidence → decisionA separate runner and human review remain required
0 current handoffsStatic validation protects the envelope, scope, context, action allowlist, expiry, and replay. It cannot certify an agent’s open-ended reasoning, so the Oracle challenge lane and execution evidence remain mandatory.

Locked: Graph Ops reads local receipts only. It cannot send a handoff, call a tool, create a lease, approve a decision, access credentials, or bypass a sandbox/runner boundary.

Enterprise admission reference · signed identity + policy

An admitted receipt is not an executed action.

Before a separate runner can rely on a task, FactoryLine can bind its declared workload, tenant policy, exact paths, action category, revocation state, and—when required—its live semantic lease. The receipt is replay-safe and visible; it never becomes a hidden permission grant.

No admission receipt
Workload identityNo signed local identity
Tenant policyNo signed policy binding
Lease + revocationNo verified bounded authority
Decision receiptNo replay-safe admission
Runner packetNo sealed runner input
Separate runnerProduction enforcement must prove its own topology.
0 local admission receiptsRead whether a runner input is bound to its exact receipt, action, scope, and argv digest. It does not claim OIDC federation, sidecar/eBPF control, tool execution, or enterprise approval.

Locked: this view reads local signed facts only. It cannot authenticate a cloud workload, grant a credential, invoke a tool, enforce a network boundary, execute a release, or bypass human review.

Atomic mechanics · independent proof bridge

Keep the workflow, verify the handoff.

Import a compact workflow export to inspect its typed stage DAG, capability-scoped handoffs, source-precondition hashes, and checkpoint continuity against the sealed intent contract. This display never starts Atomic, resumes a checkpoint, or turns a declared workflow into authority.

No imported run
Sealed intentNo Oracle Contract binding
Typed DAGNo declared stages
Scoped handoffsNo capability evidence
Checkpoint continuityNo imported checkpoint
Human decisionImported evidence never grants execution or release authority.

Locked: Graph Ops only reads hash-valid local receipt facts. A declared worktree, container, VM, or remote host is not proof of a sandbox. Inspect the exact Oracle Contract and receipt before authorizing separate work.

Agent Proof Bridge · provider-neutral handoff

Bring the agent’s evidence, not its authority.

Inspect a compact Eve, Junie, Grok Build, or generic export against the exact sealed intent. Code Factory binds the declared workflow, original source preconditions, and real local before/after artifacts. It never starts, resumes, approves, or deploys an agent run.

No imported proof
Sealed intentNo Oracle Contract binding
Declared workflowNo provider-neutral DAG
Source preconditionsNo source-byte binding
Before/after proofNo local artifact pair
Human decisionEvidence remains read-only; authority stays outside the bridge.

Locked: a provider export is not provider identity, sandbox, checkpoint, deployment, or agent-quality proof. It must remain tied to a current Oracle Contract and actual local evidence artifacts; a separate human still controls every real action.

Operations Control · preconditions before work

Make the work envelope reviewable before an agent starts.

Bind the base revision, branch isolation, failed reproduction, change budget, evidence tier, architecture zones, and local repository heads. A receipt says what was checked; it does not create a worktree, run a repair, or approve a merge.

No envelope
IsolateNo verified base or branch
ReproduceNo failure budget receipt
ConstrainNo change envelope
ProveNo declared evidence tier
CoordinateNo local repository head binding

Locked: operations controls observe local preconditions only. They do not execute a task, allocate a sandbox, invoke a model, create an approval, or change Git state.

Session Trace · explicit continuity

Trace the handoff without trusting a story.

Each recorded stage names the declared harness and session, binds input and output hashes to a sealed Oracle Contract, and points to the prior receipt. Session traces are local, hash-linked evidence—not identity, execution, or release authority.

No trace
Sealed intentNo Oracle Contract binding
SessionNo declared harness session
StageNo hash-bound lifecycle stage
EvidenceNo local evidence hash
Human reviewNo review-required state

Locked: this is an inspection-only trace. It cannot resume a session, contact a provider, alter intent, grant an agent permission, or mark work approved.

Repair Loop · consequence-aware

Fix the exact fault, then challenge the fix.

Turn a real failure into a bounded packet: affected obligation, explicit potential consequences, observed reproduction, candidate hash, positive and negative independent re-checks, and a named human reviewer. The loop cannot self-approve or keep guessing after evidence breaks.

No packet
IssueNo exact failure
ConsequencesNo reviewed consequence
ReproduceNo bound failure evidence
ChallengeNo positive and negative re-check
Human decisionNo named review

Locked: a packet is a review artifact, not a repair command. Any scope, oracle, evidence, or independent-check gap remains blocked.

Journey Proof · repair supervision

Choose who may attempt the repair—not who may approve it.

Human-controlled mode only verifies a prepared repair. Supervised-auto mode permits one bounded local agent command, then independently audits its identity, command, workspace delta, scope, positive proof, and negative mutation. Neither mode grants final approval.

Loading receipts
0 verified receiptsNo Journey Proof receipts are loaded. The controls create an inert template only; they never start an agent or approve a repair.

Final approval is always withheld. Run the copied manifest through factory journey heal-verify in a separately reviewed terminal.

Forge receipt · intent trace

Did the shipped work honor the sealed intent?

This is a local, read-only projection of the newest Forge ship receipt. It shows the intent hash and obligation result without treating a receipt as execution or approval authority.

Loading traceability
Fail-closed boundary. No local Forge ship receipt has been projected; intent traceability is unverified.

Nodes

—

Edges

—

Evidenced

—

Lineage runs

—

Forensic findings

—

Repair candidates

—

Graph status

Loading

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.

Local facts
Intent0 requirements
Verifier0 receipts
PolicyNo dossier
Human decisionReview required

Evidence health

Deterministic ratios from this bounded graph result, not estimated productivity or a quality score.

Loading
—evidenced
Requirements
—
Policy drift
—
Blocked gates
—

Graph lanes

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.