Platform layer

GitHub knows the code. Foundariq knows why the code exists.

Foundariq reaches your code through a GitHub App installation you grant per repository, and the scopes it asks for are contents, pull requests and checks — never administration. Agents hold no credentials of their own: each task draws a short-lived installation token scoped to the single repository it works in, and opens one branch and one pull request through it. The installation has no merge permission, no administration scope and no way to alter a protection rule, so there is no setting anywhere that would let an agent widen its own access. Foundariq posts its certification as a status check your rules may require or ignore, and writes the Blueprint version, the change set, the capability and the policy verdict into the description. Revoking the installation removes the writer, not the work.

Start building

Every change arrives as a pull request

An agent's work reaches you as a branch and a pull request with the diff, the commits and the history GitHub always gives you. If you would send it back from a colleague, you send it back the same way, with the same review tools your team already uses.

Your merge rules are not bypassed

Branch protection, required checks and CODEOWNERS apply to agent pull requests exactly as they apply to human ones, and Foundariq has no exception path around them. The agent that wrote the change is not the reviewer on it, and neither the author nor the reviewer can merge past a rule your repository enforces.

The pull request body is assembled from the change set

Foundariq composes the pull request body from the change set the control plane acted on: the Blueprint version, the operations inside it, the capability version each one resolved to, and the policy verdict with the rule that produced it. The agent that wrote the code does not author that section and cannot edit it afterwards, so a reviewer reads the record rather than the author's account of the record. What the agent wants to say sits in its commits and its comments, where it is visibly the agent talking.

Code in git, meaning in Foundariq

Foundariq holds Blueprints, capabilities, policies, decisions and provenance. It holds no second copy of your source: repositories, branches, commits, pull requests, reviews, CI and releases stay in GitHub, where your tooling and your auditors already look.

What this layer does

Creates branches and opens pull requests in your repositories, through an installation you grant and can revoke.
Honours branch protection, required checks and CODEOWNERS with no exception path.
Links each pull request to the Blueprint version, change set and capability behind it.
Records the merged commit and the built artifact in the release's provenance.
Leaves every repository fully usable without Foundariq — no proprietary format in the way.

What it does not do

Foundariq does not host your code, does not mirror it, and does not become a second place your team has to look for it. It does not merge on your behalf around a rule you set, and it does not replace your CI: your checks run in GitHub, and a failing check is a failing check.

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 works

Composition Engine

Before anything is created, Foundariq checks what the portfolio already has. The reuse ratio is what it reports back.

How it works

Policy 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 works

GitHub

Foundariq opens pull requests in your own repositories. Nothing is mirrored, hidden or locked away from your team.

How it works

Multi-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 works

API

Everything the interface does, the API does: Blueprints, capabilities, change sets, builds, decisions and audit records.

How it works

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.

Start building See how it works

Read-only to start · Your code stays in your GitHub · [email protected]