The current canonical Banking proof does not require a framework-wide registration package.
The first priority is proving the contracts.
A future application may compose:
Semantic model
Resolver
Planner
Policy
Execution provider
Verifier
Evidence sink
through the application’s DI container.
Example shape:
services
.AddFoundgine(...)
.AddExecutionProvider(...)
.AddPolicy(...)
.AddEvidence(...);
This is illustrative only; the final API should not be designed until the underlying contracts have been proven.
Transport adapters such as MCP or GraphQL should compose Foundgine services from outside the core.
They should not force their own service abstractions into Foundgine.Foundation.