Create and Adopt
How projects enter Workspace Intelligence through native, official, or existing project paths.
Workspace Intelligence is not limited to frameworks Workspai can scaffold. The project-entry capability contract states the rule in plain language:
Any readable project can enter Workspace Intelligence through adopt/import.
There are two separate capabilities:
| Capability | Meaning |
|---|---|
| Workspace Intelligence | Model, context, impact, doctor, verify, graph, evidence, and agent grounding around a project |
| Native Create | Workspai-owned project generation for supported kits |
Existing projects can enter through adopt/import even when Workspai does not own their scaffold path. Registration still depends on a readable project path and enough observable metadata to create valid workspace records. Only specific kits can be created natively.
The runtime signals in the create planner are examples for detection, not a closed allowlist. Existing projects in other languages or frameworks can still enter Workspace Intelligence through adopt/import when they are readable and can be registered.
Create planner lanes
| Lane | Use when | Result |
|---|---|---|
native | Workspai owns the scaffold contract | First-class generated project |
official | Official ecosystem generator exists | Run an available official generator and register it, or use adopt/import for planned handoffs |
existing | The project already exists or native create is not supported | Register, model, verify, and govern without scaffolding |
official contains both shipped and planned entries. Frontend generators such
as Next.js and Vite are available official paths: Workspai runs the ecosystem
generator, then registers the project in Workspace Intelligence. WordPress,
Laravel, Symfony, and Rails are planned official handoffs and should not be
presented as shipped automated workflows yet.
Native create kits
Current native create coverage includes:
fastapi.standardfastapi.dddnestjs.standardspringboot.standardgofiber.standardgogin.standarddotnet.webapi.clean
Available official generator paths
Current official generator coverage includes:
frontend.nextjsfrontend.remixfrontend.vite-reactfrontend.vite-vuefrontend.vite-sveltefrontend.vite-solidfrontend.vite-vanillafrontend.nuxtfrontend.angularfrontend.astrofrontend.sveltekit
Planned official handoffs include:
wordpress-sitewordpress-blocklaravelsymfonyrails
Adopt/import examples
npx workspai adopt /path/to/project --json
npx workspai import ../existing-service
npx workspai workspace model --json --writeUse adopt/import for existing repositories, unsupported scaffold paths, or systems that should enter Workspace Intelligence without being moved.
Do not read the create planner's existing runtime signals as the only supported adopt/import technologies. They are planner hints; the architecture boundary is the readable project and its observable workspace evidence.
Claim boundary
It is correct to say:
Existing projects can enter Workspace Intelligence through adopt/import.
It is not correct to say:
Workspai natively scaffolds every language and framework.
The first claim is architecture. The second claim would exceed the create planner contract.