Sharing has a price, and the graph names it before the promotion.
Every capability is scoped either to one product or shared across several, and the graph records which. Promotion to shared changes who may modify it, how breaking changes are handled, and who has to be told before one lands. Foundariq shows that trade before the promotion: the products that would adopt it, the freedom the originating team gives up, and the review a shared capability attracts from then on. Keeping a capability local is a recorded decision, not an omission.
Sharing too early costs more than duplicating
A capability shared across three products has to serve three sets of requirements. Generalising before the third use produces configuration switches nobody asked for and a review burden the original team never agreed to carry.
Promotion to shared scope is its own change
Moving a capability from product scope to shared scope is an explicit change with an owner, a version and a policy profile attached. Nothing becomes shared because a second product started importing it.
Local capabilities stay local on purpose
A capability that should not be shared keeps its product scope, and the graph records why. Reuse analysis can raise the question again later, and whoever revisits it reads the reasoning from the first time instead of restarting the argument.
In this capability
- Product and shared scope
- Recorded promotion step
- Cost and benefit shown
- Modification rights per scope
Capability Graph
The rest of Capability Graph
Capability Registry
One key per capability, held steady while the code behind it is regenerated, plus version, owner, status, dependencies and consumers.
Consumers & Impact
Which products depend on which version, direct and indirect, read while a change is still a proposal.
Reuse Opportunities
Analysis that finds two products solving the same problem separately, and proposes the shared capability that replaces both.
Deprecation & Migration
A published capability cannot simply vanish. Removal without a migration path is blocked by the policy engine.
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]