Every capability has a key the whole portfolio agrees on.
Each capability is registered under a key that does not change when the implementation does. The record is the same six fields every time: the key, the version, the owner, the status, the capabilities it depends on and the products consuming it. Domains keep the graph readable as it grows: identity sits with identity, billing with billing, analytics with analytics. A Blueprint references the key, so the same reference resolves after the code behind it has been regenerated.
Keys outlive their implementations
A capability key is stable; the code behind it is not. Regenerate that code onto a different framework, a different database or a different cloud and every Blueprint reference still resolves, so a technology move is not a portfolio rewrite.
Versions make change explicit
Consumers depend on a named version, never on whatever is newest. Behaviour that changes becomes a new version with its own consumer list, instead of a silent edit that reaches every product at once.
Every capability names an owner and a status
Every capability names an owner and carries a status. A question routes to a person rather than a channel, and a capability still in draft cannot quietly become load-bearing for a product that has already shipped.
In this capability
- Stable capability keys
- Version history
- Named owners
- Domain grouping
Capability Graph
The rest of Capability Graph
Consumers & Impact
Which products depend on which version, direct and indirect, read while a change is still a proposal.
Shared and Product-Specific
Promotion from one product to shared is an explicit step, with the cost and the benefit shown before it happens.
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]