Structured changes can be checked; rewrites cannot.
Ask for a rewrite of the customer model and what comes back is new text that something else has to read, interpret and hope about. A Blueprint change is recorded instead as a named operation: add a field to Customer, of type email address, classified as personal data. Deterministic validation evaluates that operation against the policies in force before any generation runs, because the operation states exactly what it does. Nothing proceeds on the strength of how convincing an explanation sounded.
Rewrites hide what actually changed
When a change arrives as replacement text, the only way to know what moved is to read both versions and infer. Inference is not something a policy engine can run, so review falls back on human attention at exactly the wrong moment.
The operation names its own effect
The stored record says add a field to Customer, of type email address, classified as personal data: a statement with fields, not prose. Checks read those fields directly, so a rule about personal data fires on the classification rather than on a guess at intent.
Proposals go through the same gate
A change proposed by an agent arrives as the same kind of operation a person would type, and meets the same checks. The Architect proposes, an independent Critic reviews, the policy engine decides against the policies in force, and a human approves wherever policy says a human must.
In this capability
- Named change operations
- Typed field definitions
- Data classifications
- Checkable proposals
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.
Blueprint Studio
One surface for entities, pages, actions, workflows, permissions, policies, capabilities, versions and history.
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]