Product / Surfaces / Code workspace

Code workspaceEarly access

The Software Factory's front door.

The Code workspace is where requests become specs, specs become sandboxed runs, and runs become pull requests with their evidence attached.

Fig.1 · sample

request › Fix: routes trust workspace_id from the body (#142)

task spec
goalWorkspace id comes from the session, never the request body
scopesrc/routes/** · no schema changes
acceptforeign workspace → 403 · own workspace → 200
barfixed before code · each check must fail when broken
compiled plan
  1. 1.read routes that take workspace_id from body
  2. 2.add session guard, remove body field
  3. 3.write 403 / 200 tests
  4. 4.sabotage: drop guard, expect RED

How it works.

  1. 01 /

    Request

    Describe the change, or point at an issue.

  2. 02 /

    Spec and plan

    A task spec with acceptance checks and a bar, then a compiled plan.

  3. 03 /

    Run and deliver

    A sandboxed run, then a pull request through the Qvrone GitHub App.

What you get. Each point labelled with its real status.

1.1Early access

Repository browser

Browse the connected repository from the workspace.

1.2Early access

Evidence per run

Spec, plan, diff, test output and artifacts kept together.

1.3Early access

Review decisions

Reviews and comments recorded against the change.