The product and platform taxonomy defines standard capability assets, operational engines, and delivery primitives.
1. The Four-Layer Product Line Catalogue
Product-line capabilities are organized into a four-layer hierarchy:
+-------------------------------------------------------------------+
| PLATFORMS |
| Standard, reusable product suites sold directly to the market |
+-------------------------------------------------------------------+
│
▼
+-------------------------------------------------------------------+
| HUBS |
| Bounded operational domains organizing work, people, and AI |
+-------------------------------------------------------------------+
│
▼
+-------------------------------------------------------------------+
| BANKING FABRICS |
| Domain-specific, contract-bound systems of record |
+-------------------------------------------------------------------+
│
▼
+-------------------------------------------------------------------+
| INFRA FABRICS |
| Foundational, non-substitutable technical capability layers |
+-------------------------------------------------------------------+
1.1 Layer 1: Infrastructure Fabrics
Infrastructure Fabrics are foundational, domain-neutral technical capabilities required by every platform. The eleven infrastructure fabrics are:
- Trust Fabric: Identity, authentication, and consent management.
- Truth Fabric: Data integrity and authoritative state verification.
- Cloud Fabric: Cloud operations, logging, and metrics management.
- Evolution Fabric: System migration, modernization, and model-driven work isolation.
- Agent Fabric: AI agent lifecycle, state tracking, and permission boundaries.
- Memory Fabric: Cognitive auditing and decision traceability for AI execution.
- Cognition Fabric: AI inference and goal-seeking execution.
- Engagement Fabric: Interface orchestration across consumer and RM-facing experience surfaces.
- Intelligence Fabric: Analytics, reporting, and transactional telemetry feeding.
- Experimentation Fabric: Feature flagging, A/B testing, and controlled code rollouts.
- Foundry Fabric: Meta-compilation and workspace session management.
1.2 Layer 2: Banking Fabrics
Banking Fabrics are domain-specific systems of record, data structures, and transactional processing engines. These fabrics expose contract-bound APIs to manage state:
- Accounts Fabric: Balance processing and ledger operations.
- Payments Fabric: Payment routing and clearing integrations.
- Credit & Cards Fabric: Underwriting ledgers and card-issuance data structures.
- Compliance & Relationship Fabric: KYC states and master party relationship graphs.
- Concierge & Family Fabric: Ledger consolidation and policy-bounded authorization structures.
1.3 Layer 3: Hubs
Hubs are bounded operational domains that run on the Evolution Fabric to organize personnel, AI agents, and communication channels. Operational workflows and exception handling occur at this layer.
1.4 Layer 4: Platforms
Platforms are standard product suites grouped into three classes:
- Technology Platforms: Tachyon (deposits and balance-sheet processing), Photon (payments and clearing), Electron (commercial cards and spend management), and Olympus (runtime infrastructure).
- Digital Platforms: Neutrino (client engagement and marketing).
- Agentic Platforms: Estates (agentic transition framework) and Quark (pre-built domain hub classes).
2. The Hub Way Model
The Hub Way structures a bank's operational architecture into three tiers: Estates, Hubs, and Fabrics.
┌────────────────────────────────────────────────────────────────────────┐
│ PRODUCT ESTATES │
│ [Cloud] [Engineering] [Data] [Payments] [Banking] [Influence] [Exec] │
└───────────────────────────────────┬────────────────────────────────────┘
│
▼
┌────────────────────────────────────────────────────────────────────────┐
│ BOUNDED HUBS │
│ Instantiated Hubs from the 6 Classes: │
│ 1. Customer 2. Product 3. Distribution │
│ 4. Relation 5. Operations 6. Systems │
└───────────────────────────────────┬────────────────────────────────────┘
│
▼
┌────────────────────────────────────────────────────────────────────────┐
│ ENTERPRISE FABRICS │
│ Authoritative processing engines (e.g., Accounts, Cards) │
└────────────────────────────────────────────────────────────────────────┘
2.1 The 7 Product Estates
An Estate is a target customer transformation domain containing software, operational hubs, human-agent teams, and channels:
- Cloud Estate: Infrastructure scaling and cloud environment management.
- Engineering Estate: Software build lifecycles and validation tools.
- Data Estate: Analytical databases, stream processing, and model tuning.
- Payments Estate: Clearing and settlement routing.
- Banking Estate: Core deposits, ledger accounting, and underwriting.
- Influence Estate: Client advising interfaces and relationship graphs.
- Execution Estate: Back-office casework and support operations.
2.2 The 6 Hub Classes
Hubs are instantiated from six classes to manage specific business operations:
- Customer Hub: Party governance, identity verification, and KYC tracking.
- Product Hub: Product blueprint parameters, rate rules, and fee structures.
- Distribution Hub: Consumer application experience layers and portals.
- Relationship Hub: Advisor workspaces and client relationship interfaces.
- Operations Hub: Back-office exception processing and file reconciliation.
- Systems Hub: USE signal monitoring and tool-contract logging.
2.3 Structural Binding Rules
- Cross-Estate Reusability: Standard Fabrics and Hubs are reusable across different Estates.
- Mandatory Pair Bindings: Certain hubs require specific matching fabrics to maintain data integrity:
- Product Hub requires Product Fabric.
- Customer Hub requires Customer Record Fabric.
3. Bounded Work Architecture (Quark Work Models)
Quark delivers Work Models that organize workforce, machine, and communication interfaces. Each model consists of six primitives:
- Streams: Workflows triggered when external actions cross a domain boundary, leading to an external commitment.
- Loops: Schedule-triggered cycles of continuous feedback that maintain risk posture and operational hygiene (e.g., daily ledger reconciliation).
- Adaptive Scenarios: Goal-oriented declarations of outcomes. Scenarios allow human operators and AI agents to collaborate during exception management.
- Teams: Operational structures organizing human operators and AI Agent Swarms into permissioned groups.
- Machines: Technical systems registered via Tool Contracts using the Model Context Protocol (MCP).
- Channels: Interface workspaces (such as SRE Workbenches, messaging interfaces, and voice portals) mapped to specific roles.
4. Platform Substitution and Customization Policy
Platform integrity is protected by strict substitution boundaries for custom bank code:
4.1 Infrastructure Fabrics
Infrastructure Fabrics (Trust, Truth, Cloud, Evolution, Agent, Memory, Cognition, Engagement, Intelligence, Experimentation, Foundry) are non-substitutable and cannot be bypassed.
4.2 Banking Fabrics (The Induction Principle)
Transactional banking systems are substitutable. Integration of external transactional systems occurs through Induction:
- External systems are wrapped in Model Context Protocol (MCP) Tool Contracts.
- These systems are registered as Machines inside the Bounded Hub.
- The Hub's Work Model accesses these systems as contract-bound services via the MCP, managing data via declarative configurations.
- Inducted systems can be substituted individually without altering the core Work Model.