These are related but not interchangeable. Their value should be assessed mechanism by mechanism before any stack-level claim is made.
Backbone 01
DCA · Dynamic Contextual Activation
Activate only what the current state requires.
A progressive-activation pattern that moves from broad context to narrower context as confidence and relevance become clearer. Legacy source material consistently describes four conceptual tiers: Building → Hallway → Room → Spotlight.
- Primary question: what must be active now?
- Potential role: reduce unnecessary context/capability activation.
- Validation target: workload-specific compute/latency/quality trade-offs.
Canonical state: documented architecture candidate; legacy percentage savings are not treated as validated benchmarks.
Backbone 02
UIOP · User-Intelligence Optimization Protocol
Turn permitted context into a structured progressive pipeline.
A seven-phase context-processing architecture linked in the legacy corpus to five cognitive/knowledge tables and Slot-Based Memory. Its purpose is to avoid repeatedly rediscovering stable, permissioned context from zero.
- Stable source element: seven processing phases.
- Stable source element: five-table / slot-based context structure.
- Validation target: freshness, consent scope, error propagation and total-system cost.
Canonical state: protocol/architecture candidate; exact internal tables and promotion rules remain review material.
Backbone 03
Multi-Brain Group Architecture
Route different workloads to specialized reasoning paths.
A routing architecture that separates task classes rather than treating every request as a single monolithic reasoning path. The legacy corpus is not internally consistent on the exact number of specialized routes, so the public canonical layer does not freeze a route count.
- Primary question: which reasoning path fits this workload?
- Stable concept: differentiated workload routing.
- Open reconciliation: seven-versus-eight route inventory in legacy sources.
Canonical state: architecture candidate; exact route inventory requires source/spec reconciliation.
Backbone 04
Suprompt Architecture
Clarify intent before expensive reasoning begins.
An intent-framing layer that decomposes a request before deeper reasoning. A five-component seed recurs in the source corpus: Intent Vector, Constraint Mask, Depth Index, Output Archetype and Energy Coefficient.
- Primary question: what is actually being requested?
- Potential role: improve routing and reduce avoidable reasoning branches.
- Validation target: quality, latency and failure behavior versus simpler prompting baselines.
Canonical state: documented architecture candidate; performance ranges remain unvalidated.
Backbone 05
OFRP · Output-First Reverse Prompting
Reuse work when query patterns are functionally equivalent.
A precompute/cache-oriented pattern for high-frequency or safely clusterable outputs. The useful idea is repeated-work reuse; the difficult engineering questions are equivalence, invalidation, personalization boundaries and safety.
- Primary question: can this output be safely reused?
- Potential role: reduce repeated generation for stable patterns.
- Validation target: cache correctness, stale-response risk, privacy, quality and hit-rate economics.
Canonical state: architecture candidate; “compute once, serve millions” remains an intuition, not a universal operating claim.
Why five?
Canonical grouping
The five-backbone grouping is the most stable repeated cluster.
DCA, UIOP, Multi-Brain, Suprompt and OFRP repeatedly appear together across Phase 2, HUAI, IP, ZOE, Asset, Portfolio and Framework materials. This page uses that repeated grouping while separating adjacent patterns that have different roles.
Boundary: recurrence across internal sources supports taxonomy consistency; it does not prove novelty, patentability or performance.