Read the Blueprint, compare two versions, hand one to build.
Blueprint Studio is where a Blueprint is read, argued over and changed. Its tabs run from the overview through capabilities, entities, pages, actions, workflows, permissions and policies, then into versions and history. Compare puts one version against another; build hands an approved version to generation. What appears here is the same record that validation, generation and release work from later.
Read it before you build it
The overview states what the product is for, which capabilities it reuses and which it introduces, before any tab of detail is opened. Build runs against a chosen published version, so nothing is generated from a half-finished draft.
Compare two versions side by side
Compare lists what changed between versions in the terms the Blueprint uses: entities, fields, actions, permissions, policies. A change to who may approve a refund shows up as exactly that, not as a line in a file.
Detail sits one click deeper
Each tab leads with plain statements — who may approve a refund, which pages a role can open — and keeps the underlying definition one level beneath. A founder can read the surface while an engineer still gets the exact record.
In this capability
- Entity and page editors
- Workflow and policy views
- Version compare
- Build from a version
Blueprints
The rest of Blueprints
The Blueprint Model
Entities and fields, pages and actions, workflows, permissions, policies and capability references, in one structured record.
Technology Neutral
Customers, invoices and approvals on one side. Framework, database and cloud on the other. A Blueprint holds the first.
Versions & History
Published versions are immutable. Every change opens a new version with a comparison against the one before it.
Typed Operations
A change is recorded as a structured operation: add a field, with a type and a classification. Never as a rewrite.
Stop managing prompts. Start managing software strategy.
Connect your repositories. Let Foundariq understand what you have already built. Then tell it what your portfolio should build next.
Read-only to start · Your code stays in your GitHub · [email protected]