Agent work arrives as a pull request your team can reject.
Foundariq does not replace GitHub or hide it behind an interface of its own. Work arrives as a branch and a pull request in your repository, your reviewers review it there, your CI runs there, and releases are cut there. What Foundariq adds sits above that: which Blueprint version a pull request implements, which capabilities it touches, which policy checks cleared it and which agent proposed it. An engineer who ignores Foundariq entirely still sees an ordinary pull request they can read, question and close.
Your repositories, your permissions
Code lives in your GitHub organisation, under your branch protection and your merge permissions. Foundariq opens pull requests; people with GitHub access decide what merges. Remove the installation and every branch, commit and pull request stays exactly as it stands.
Each pull request carries its reason
A pull request links back to the proposal it came from, the Blueprint version it implements, the capabilities it affects and the policy checks it cleared. A reviewer stops having to infer intent from a diff. Months later, the reason the code exists is still attached to the code.
Review stays where review belongs
An independent reviewer reviews the pull request, and no agent approves its own work. Review comments, required checks and CI results behave exactly as they do on every other pull request in the repository. Foundariq records the outcome; it does not overrule it.
In this capability
- Pull requests in your repositories
- Your branch protection rules
- Blueprint version on each PR
- CI and releases unchanged
Releases
The rest of Releases
Build Certification
Nine steps in fixed order: Blueprint validation, policy, dependency resolution, target resolution, generation, unit tests, integration tests, artifact verification, pull request.
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.
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]