Rule Ingestion Flow
How instructions fire in the HyperNet routing workflow
1
Governance Input Received
User submits request via CCW console. Raw text enters the system.
Actor: End User (e.g., Rita from Marketing)
Input Validation
Session Init
2
Pre-Processing & Classification
Request is tokenized, classified by type, and tagged with metadata. Intent detection determines routing priority.
Actor: Kimi (Context Manager)
Token Limits
Intent Classification
Priority Tagging
3
Lane Selection Decision
Router determines which lanes should process this request based on content type, complexity, and required capabilities.
Actor: HyperNet SDC Router
Routing Rules
Lane Availability
Load Balancing
4
Parallel Lane Processing
Selected lanes receive the request simultaneously. Each applies its specialized perspective and rules.
Actor: Lola, Claude, Grok, Deep, Gemini
Identity Rules
Behavioral Rules
Output Format
5
Consensus Check Gate
System evaluates lane agreement levels. If consensus exceeds threshold, Catfish is triggered for mandatory dissent review.
Actor: BC-006 Drift Detection
85% Warning
95% Critical
100% Catfish Required
6
Response Synthesis
Gemini integrates lane outputs into coherent response. Conflicts are surfaced, not hidden.
Actor: Gemini (Synthesis)
Conflict Resolution
Weight Calculation
Citation Tracking
7
CPN Review Gate
High-risk outputs are held for human review. CPN can approve, modify, or reject before delivery.
Actor: CPN (Steve Kawa)
Embarrassment Risk
External Communication
High Confidence Claims
8
Governed Output Delivered
Final response is delivered to user with full audit trail. Memory updated, metrics logged.
Actor: CCW Console
Audit Log
Memory Update
Metrics Capture
Processing Step
Decision Point
Gate / Checkpoint
Output