Sensitivity belongs to the field, not to a wiki page.
A field is marked in the Blueprint — personal, financial, health, internal, public — and the marking is part of the field's definition rather than a note kept somewhere else. Generators read the marking and the policy engine reads it too, so it shapes both the code that gets produced and the route a change to that field has to take. Because products compose the same capabilities instead of copying them, one marking governs every product that uses the field. Change it once and those products are regenerated against the new marking.
Documentation is not a control
A sensitivity register in a document depends on every engineer finding it at the right moment, and on the document still being true. A marking carried in the Blueprint is read by machinery that cannot skip the step.
It travels into generated code
Logging, redaction and retention behaviour follow from the marking at generation time. The same marked field produces the same handling in every product that reuses it, whichever technology each of them targets.
It raises the bar on changes
An edit to a field marked personal is classified higher than the identical edit on a public one, so it takes the route with a human on it. Where an obligation demands it, the policy profile refuses the change outright.
In this capability
- Field-level sensitivity marking
- Classification in generated handling
- Policy that reads the marking
- Portfolio-wide propagation
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.
Policy Engine
Rules you can read out loud: deleting a published capability is blocked, reshaping a high-risk entity needs a named approval.
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.
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]