A change is a question about consumers, not about files.
For every capability, the graph records which products depend on which version. That list is the first thing shown when a change is proposed: a published capability with four consumers is a different decision from one with none. Impact follows the recorded dependencies, so a change to an identity capability also surfaces the products that reach it through the billing capability. None of it is inferred by searching the code for imports.
Reach is known before the branch exists
The consumer list is read while the change is still a proposal, not after a pull request breaks something downstream. An Architect proposing a change sees every product it touches at the moment of proposing it.
Indirect consumers count as consumers
Impact walks the recorded dependencies instead of stopping at direct use. A product that never names a capability still appears in the list when it consumes something that does.
Scrutiny scales with what is at stake
Consumer count and capability status are inputs the policy engine evaluates, against thresholds written in the policy profile. Wide reach requires human approval before the change proceeds; a capability nothing consumes still goes to an independent reviewer, without the extra approval step.
In this capability
- Per-version consumer lists
- Indirect dependency tracing
- Reach shown at proposal time
- Reach as a policy input
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.
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]