Problem
Interface work slows down when the running product and code changes live in separate tools.
Story
A running app, preview state, and source changes sit in the same workspace.
Constraint
The public case shows the editor workflow without exposing private implementation details.
Approach
Import a real repo and run the app in the browser. Keep visual edits, local context, and source changes in one workspace. Show the code diff next to the decision to ship.
Outcome
The workflow connects the running product to editable source code.
Human stake
The next decision is easier when the running app and the code change are visible together.
Blocked person
A builder waiting for a preview to explain what changed.
Confusion
Preview, local context, and staged changes can be split across tools.
Made visible
The editor keeps preview and change state together.
Evidence
Browser workspace for previewing an imported app, editing the UI, and reviewing source changes.
Problem
The preview needs context.
The preview is useful when nearby context explains what changed.
Interface still / Owned captureOperate
The workflow is inspectable.
Local context and preview state stay visible in the same product view.
Interface still / Owned capture
Decision
The ship action has context.
Staged changes remain visible where the product asks for a decision.
Interface still / Owned capture
Receipt
Changes ready.
Preview, local context, ship action, and staged changes resolve into one reviewable workflow.
Interface still / Owned captureResult
What changed
- sim0 shows a running app, visual editing, and source changes in one browser workspace.
Claims
Public claims kept inside the available evidence.
- Browser app import and preview
- Visual editing tied to source changes
- Public site at sim0.com