Venture Workspace

3/8/2026 seed

Preamble

Venture Workspace is where a validated wedge becomes a real product effort. It gives each venture local truth so product work does not dissolve into global DB state, chat memory, or a folder of disconnected artifacts.


One Venture Needs One Body

The Factory wants to run many ventures, but parallelism only works when each venture has its own body. Polsia points at the runtime primitive: one company instance with its own app, database, email, payments, state, tasks, and dashboard.

Factory needs the local version of that before it can safely scale. One wedge should become one bounded workspace with work, evidence, docs, code, analytics, decisions, launch state, and postmortem. Without that boundary, a validated idea becomes a global note and product truth gets spread across prompts, databases, and memory fragments.

The workspace is where the founder-decision handoff becomes physical. A choice becomes files, tasks, tests, deployments, expenses, and users. Once the loop can change those objects, accountability has to live beside the work, not in the conversation that started it.

The Passport Before The Product

Each venture needs a passport. The minimum local shape is _work for tasks, cycles, issues, and decisions; _evidence for raw evidence, claims, packs, tests, and outcomes; docs for vision, positioning, PRD, design, validation, and launch; src and tests for implementation; analytics for product behavior; and an archive path for pause, kill, or postmortem.

The workspace should make ownership visible. What is being built, what evidence allowed it, what changed, what shipped, what failed, and what future runs should reuse.

Code Has To Prove A Decision

The build harness has to resist code-shaped progress. A product workspace needs PRD/spec gates, architecture, tests, analytics, deployment state, rollback, support capture, and market instrumentation. An agent can generate code before the venture knows what it must learn. That speed is useful only when the workspace can show which decision the code is meant to test. The public proof is a venture workspace that can build, ship, measure, and preserve decisions locally. This is where Factory contrasts most sharply with the rest of the garden. A writing or audit artifact can be corrected after publication. A product can collect users, money, support pain, and operational debt. The harness has to treat build as a liability until the evidence earns it.

The First Real Proof

Venture Workspace lands when one validated wedge becomes a product workspace with local evidence, decisions, build state, launch state, analytics, and postmortem path. The branch succeeds when a future agent can enter the workspace and know what is true without asking the chat history to remember the company.