Rules decide, and the rules are readable.
A policy profile is a list of statements about what may happen to a portfolio, written to be read by the people accountable for it. Deleting a published capability is blocked, because other products compose it. A high-risk change to an entity requires a named human approval, a wording change applies on its own, and deletion of production data is refused outright. Common cases ship as defaults, so an ordinary portfolio is governed before a single rule is written; a team with an unusual obligation adds one without touching the engine.
Written for humans, evaluated by machine
Each rule reads as a sentence: who may change what, under which conditions, and what happens when the condition fails. The engine evaluates that same statement the same way every time, so the rule you read is the rule that ran.
Defaults cover the ordinary cases
Removing something other products depend on, reshaping an entity, touching production data — these arrive already governed. You write a rule only where your obligations differ from what ships, and the rest of the profile stays as it came.
Profiles differ per product
A product holding consent records and an internal admin tool should not be governed identically. A profile attaches per product and per environment, and every release records which profile was in force when it was cut.
In this capability
- Readable rule statements
- Default policy profiles
- Per-product and per-environment scope
- Automatic, approval or blocked outcomes
Governance
The rest of Governance
Deterministic Validation
Structure is checked first. A change that does not fit the Blueprint is rejected before any model reads it.
Risk & Approval
Each change carries a risk level, and the level decides: apply automatically, wait for a person, or refuse.
Audit Trail
Append-only record of who proposed, what validated, what review said, what policy returned and who approved.
Data Classification
Mark a field sensitive once in the Blueprint, and that marking follows it into generated code and policy.
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]