6cript is built around a single idea: most operational software can be described in a sentence. The product's job is to translate that sentence into structure that is real enough to run on, and to keep the structure honest as you change your mind.
The pipeline
Every project moves through this pipeline, in order:
- Prompt — what you describe in chat or in the homepage prompt box.
- Blueprint — the typed plan: app goal, pages, tables, roles, integrations, tasks.
- Build — the system materializes schema, forms, tables, and the first scene.
- Data — you (or your customers) add real records.
- Test — Launch Room scores readiness and lists blockers.
- Share — you publish a read-only preview, or download the JSON export package.
AI plus structured state
The AI never paints arbitrary UI. Every model response is parsed into a typed JSON shape with two fields: an action (what to do) and a UI config (what to render). The application then runs the action against your project state and hands the UI config to a schema-driven renderer.
That means the AI can change your data, but only through actions the application understands — table creation, column changes, record inserts, scene saves, and so on. Free-form HTML is not a valid response.
Objects you will see
- Project — one operation, one workspace, one database namespace.
- Blueprint — the plan-mode draft. Pages, tables, roles, integrations, tasks.
- Schema — the live table list and column types backing the project.
- Scene — a saved snapshot of a UI layout (a specific table, form, or chart).
- Checkpoint — a recoverable schema snapshot taken before risky AI moves.
- Preview — a read-only share token bound to one project.
- Export package — JSON + Markdown bundle covering everything except secrets.
Why six modes
Each builder mode focuses on one job: Plan structures, Build generates, Design brands, Data inspects, Test verifies, Deploy ships. The modes share the same project state — switching never resets your work — but each mode hides the controls that do not belong to its job.
See Builder modes for a tour, or jump to a specific mode.