A build is a sequence of checks, not a command that happens to succeed.
Certification begins with a proposed change to the Blueprint, not with a prompt, and it runs the same nine steps in the same order every time. The Blueprint is validated, policy is evaluated, dependencies and targets are resolved, code is generated, unit and integration tests run, the artifact is verified, and a pull request is opened in your GitHub repository. Each step records its result, so a build that stops names the step that stopped it and what it found. Nothing downstream begins while an earlier step is unresolved.
The order is not negotiable
Blueprint validation comes before policy, policy before resolution, resolution before generation. A change that cannot pass the rules never reaches a model, so no compute is spent writing code the control plane will refuse. The sequence is identical for a one-word label change and for a new workflow.
Tests are part of the build
Unit and integration tests run inside certification, not as a later stage that can be skipped under pressure. A failing test is a failed build, and the run stops there with the failing step named. The generated code and the tests that exercise it arrive in the same pull request.
Certification ends in a pull request
The last step lands where your engineers already work: an open pull request in GitHub, with the branch, the diff and the CI run in their usual place. Foundariq attaches the certification record to that pull request instead of replacing the review your team already does. Merging stays a GitHub action, taken by people with GitHub permissions.
In this capability
- Ordered nine-step sequence
- Blueprint and policy validation
- Unit and integration tests
- Pull request in GitHub
Releases
The rest of Releases
Provenance
Every artifact names what produced it: product, Blueprint version, generator, agents, policy profile and commit.
Release Gates
Blueprint validation, build, policy, code review, security, QA, provenance and rollback — each one explicit, with a stated risk level.
Rollback
A release you can ship is a release you can reverse. The previous verified artifact stays available, record intact.
GitHub Flow
Branches, pull requests, reviews, CI and releases stay in GitHub. Foundariq records why each one exists.
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]