Search the portfolio first, design only what is missing.
Composition asks the question a prompt never asks: does this already exist? Capabilities are matched by what they mean — the entities, workflows and policies they implement — rather than by the name someone gave the folder. What an existing capability can satisfy is composed from it; what it cannot is proposed as a new capability, and once approved it joins the portfolio for the next product to use. Every composition reports its reuse ratio, because that number tells you whether the portfolio is compounding or sprawling.
Duplication is the default failure
Left alone, every team builds its own notifications, its own audit trail, its own export. Composition makes the search for an existing capability a required step, so the second product inherits what the first one proved.
Matched by meaning, not by name
Because capabilities are indexed by the entities, workflows and policies they implement, the consent capability built for one product is found when the survey product needs consent. Naming drift and repository boundaries do not hide it.
Reuse ratio is a number on every composition
Each composition shows what was reused, what was extended and what was newly designed. A falling ratio is a signal to look at the portfolio, and it appears while the work is still a proposal.
In this capability
- Meaning-based capability search
- Reuse, extend or create
- Reuse ratio per composition
- New capability design
Autonomous Builds
The rest of Autonomous Builds
Strategy Analysis
The instruction is read against your portfolio first: what already exists, what extends, what has to be new.
Engineering Plan
The work becomes ordered tasks with explicit dependencies, written down and approved before any file changes.
Implementation
Coding agents work the plan in your repositories and open pull requests; independent review and policy checks decide what merges.
Deterministic Generation
Every build names the Blueprint version, generator, capability versions, policy profile and pinned dependencies behind it.
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]