Platform layer
Every screen here is an API call you can make yourself.
Foundariq's own screens are built on this API, so there is no second-class surface underneath them. You can read a Blueprint and its version history, query the capability graph, propose a change set, start a build, list decisions waiting on a person, and pull audit records. A proposal made over the API takes exactly the path a proposal made in the interface takes: schema validation, policy evaluation, then approval where a rule requires it. Tokens carry explicit scopes, so an integration that reads the capability graph cannot open a change set. Webhooks tell your systems when a change set is validated, a build finishes, or a decision is waiting.
Read the portfolio as data
Blueprints, capability versions, dependencies, consumers and reuse ratios come back as structured records. Portfolio reporting stops being a screenshot exercise, and your own dashboards can answer which products depend on a capability before someone changes it.
Proposals take the same path
A change set submitted over the API is validated, evaluated against policy and routed for approval exactly as one raised in the interface. No endpoint skips a gate, and none applies a change that has not passed one.
Tokens carry scopes and expiry
Each token is issued with explicit scopes and a lifetime, per integration rather than per person. A build integration that reads status holds nothing that could publish a Blueprint or approve a decision.
Events instead of polling
Webhooks fire when a change set validates, a build completes, a decision needs a human, or a release goes out. A chat channel, a ticket tracker or an internal dashboard reacts to the event rather than asking on a timer.
What this layer does
- Blueprints and their version history, readable by product or by version.
- Capability records: versions, dependencies, consumers and reuse ratios.
- Change sets: propose, inspect validation results, and see the approval route.
- Builds and releases, with the Blueprint version, generator and policy profile behind each one.
- Decisions and audit records, exportable for review.
What it does not do
The API exposes operations, not shortcuts: nothing in it applies a change without validation, approval and an audit record, and no request can widen its own token's scope. It is also not an API to your code — repositories, commits and pull requests are reached through GitHub, not through this.
The platform
Six layers between strategy and software.
Blueprint Engine
Blueprints hold what a product means: structured, versioned, validated, and readable long after the stack changes.
How it worksComposition Engine
Before anything is created, Foundariq checks what the portfolio already has. The reuse ratio is what it reports back.
How it worksPolicy Engine
Checks run before any model is consulted. The control plane evaluates policy; it never asks an AI whether an action is allowed.
How it worksGitHub
Foundariq opens pull requests in your own repositories. Nothing is mirrored, hidden or locked away from your team.
How it worksMulti-Model AI
Every job resolves to a provider, a model and a pinned version before the run starts, and a run the rules cannot staff does not start.
How it worksAPI
Everything the interface does, the API does: Blueprints, capabilities, change sets, builds, decisions and audit records.
How it worksStop 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]