Repository
Project Graph
Files, symbols, routes, components, dependencies, tests, and project structure become a navigable working model.
SourceCoder / System interface
SourceCoder turns a project into an inspectable mission: understand the repository, shape the change, authorize bounded writes, run the app, validate it, and leave a receipt.
Capability matrix
Repository
Files, symbols, routes, components, dependencies, tests, and project structure become a navigable working model.
Context
Retrieves only the code and history required for the current mission instead of flattening the entire repo into a prompt.
Mission
Inspection, planning, approval, execution, validation, acceptance, rollback, and receipts share one lifecycle.
Visual creation
Canvas, prompt-driven UI generation, component inspection, and live preview enter the same governed code pipeline.
Mutation
Every code write is represented as a bounded proposal with affected files and expected changes before execution.
Execution
Approved changes are applied inside the project boundary with file and mission identity preserved.
Proof
Typecheck, tests, build, preview health, browser inspection, and visual confirmation verify the actual result.
Evidence
The final delta, validation outcome, provider path, and acceptance state remain inspectable after the mission ends.
Execution path
The interface follows the same boundaries as the underlying system. A visual transition never implies authorization that the runtime has not actually granted.