Overview
Multi-Paradigm Problem Solving enables platform agents to apply multiple problem-solving paradigms to complex challenges. Rather than constraining agents to a single computational model, the Prismatic Platform embraces the insight that different problem domains respond optimally to different computational paradigms. Agents combine functional programming patterns, logical reasoning, heuristic approaches, graph-based analysis, and formal verification methods to achieve solutions that no single paradigm could deliver alone.
This capability is foundational to the platform's approach to Intelligence Synthesis, where real-world problems rarely conform to a single analytical model. A compliance assessment, for instance, may require functional data transformations, logical rule evaluation, graph traversal for entity relationships, and formal proofs for regulatory completeness -- all within a single investigation workflow.
The multi-paradigm approach is not eclecticism. It is a structured capability where paradigm selection is governed by problem characteristics, agent tier authority, and quality requirements. Each paradigm has defined strengths, known limitations, and measurable performance characteristics. The platform's paradigm selection protocol matches problems to paradigms based on empirical evidence, not arbitrary preference.
Paradigm Catalog
The platform supports six distinct problem-solving paradigms, each implemented through Elixir/OTP's capabilities and extended through specialized libraries and formal tools.
Functional Programming
The platform's Elixir/OTP foundation makes functional programming the default paradigm. Pure functions, immutable data structures, and composable transformations provide the backbone for data processing pipelines.
| Functional Pattern | Platform Application | Benefit |
|---|---|---|
| Pure Transformations | OSINT data normalization, entity extraction | Deterministic, testable, cacheable |
| Pipeline Composition | Multi-stage analysis workflows | Each stage independent and replaceable |
| Pattern Matching | Protocol dispatch, error handling | Exhaustive case coverage at compile time |
| Immutable Data | Evidence chain preservation | Tamper-proof audit trails |
| Higher-Order Functions | Agent capability composition | Dynamic behavior assembly |
# Functional pipeline for OSINT entity enrichment
defmodule PrismaticOsint.EntityEnrichment do
@moduledoc """
Pure functional pipeline for entity enrichment.
Each stage is a pure transformation with no side effects.
"""
@spec enrich(entity()) :: {:ok, enriched_entity()} | {:error, term()}
def enrich(entity) do
entity
|> normalize_identifiers()
|> resolve_aliases()
|> enrich_from_registries()
|> score_risk_factors()
|> validate_through_trinity_gate()
end
defp normalize_identifiers(%{identifiers: ids} = entity) do
normalized = Enum.map(ids, &Identifier.normalize/1)
%{entity | identifiers: normalized}
end
defp score_risk_factors(entity) do
risk_score =
entity.signals
|> Enum.map(&Signal.risk_weight/1)
|> Enum.sum()
|> normalize_score()
Map.put(entity, :risk_score, risk_score)
end
endOTP Concurrency Patterns
OTP provides the concurrency paradigm through lightweight processes, message passing, and supervision trees. This paradigm excels at problems requiring parallel execution, fault isolation, and stateful coordination.
| OTP Pattern | Platform Application | Benefit |
|---|---|---|
| GenServer | Agent state management, rate limiters | Controlled state with crash recovery |
| Supervisor | Fault-tolerant agent hierarchies | Automatic restart on failure |
| Task | Parallel OSINT source queries | Concurrent execution with timeouts |
| GenStage/Broadway | High-throughput data ingestion | Backpressure-managed pipelines |
| DynamicSupervisor | On-demand investigation workers | Elastic resource allocation |
# Parallel OSINT collection with timeout and fault isolation
defmodule PrismaticOsint.ParallelCollector do
@moduledoc """
Concurrent data collection across multiple OSINT sources.
Uses Task.async_stream for parallel execution with timeout.
"""
@timeout_ms 30_000
@spec collect(list(source()), query()) :: list(result())
def collect(sources, query) do
sources
|> Task.async_stream(
fn source -> source.adapter.fetch(query) end,
max_concurrency: 10,
timeout: @timeout_ms,
on_timeout: :kill_task
)
|> Enum.reduce([], fn
{:ok, {:ok, data}}, acc -> [data | acc]
{:ok, {:error, _reason}}, acc -> acc
{:exit, _reason}, acc -> acc
end)
|> Enum.reverse()
end
endGraph-Based Reasoning
Entity relationships, dependency chains, and knowledge networks require graph-based reasoning. The platform uses KuzuDB for persistent graph queries and in-memory graph algorithms for real-time analysis.
| Graph Technique | Platform Application | Benefit |
|---|---|---|
| Traversal | Entity relationship discovery | Multi-hop connection analysis |
| Centrality | Key entity identification in networks | Influence and risk propagation modeling |
| Community Detection | Cluster identification in corporate structures | Hidden relationship exposure |
| Shortest Path | Connection chain analysis | Minimum-hop entity linking |
| Cycle Detection | Circular ownership identification | Fraud and evasion pattern detection |
Formal Verification
The White Team agents employ formal verification through Lean4 theorem proving, property-based testing, and contract validation. This paradigm provides mathematical certainty where heuristic approaches offer only probabilistic confidence.
| Formal Method | Platform Application | Guarantee Level |
|---|---|---|
| Lean4 Proofs | Trinity Gate Layer 3 (Formal Necessity) | Mathematical certainty |
| Property-Based Testing | Adapter contract compliance | Exhaustive input space coverage |
| Typespec + Dialyzer | Type safety across modules | Static type verification |
| Contract Testing | Storage adapter behavior | Interface compliance proof |
| Invariant Proofs | NABLA Axioms enforcement | Epistemic correctness |
Epistemic Reasoning
NABLA Infinity provides the epistemic paradigm where agents reason about uncertainty, confidence, and belief revision. This paradigm governs how the platform handles incomplete or contradictory information.
| Epistemic Pattern | Platform Application | Outcome |
|---|---|---|
| Confidence Scoring | Intelligence assessment reliability | Calibrated uncertainty quantification |
| Belief Graph | Knowledge network representation | Traceable reasoning chains |
| Contradiction Preservation | Conflicting intelligence handling | No premature resolution of ambiguity |
| Signal Plurality | Multi-source corroboration | Minimum evidence thresholds enforced |
| Time Decay | Temporal relevance weighting | Stale intelligence automatically discounted |
Heuristic Pattern Recognition
For problems where formal methods are impractical and pure functional approaches lack domain knowledge, heuristic pattern recognition applies learned patterns from historical data to current situations.
| Heuristic Method | Platform Application | Accuracy |
|---|---|---|
| Risk Scoring Models | Entity risk assessment | 85-92% |
| Anomaly Detection | Financial transaction analysis | 88-95% |
| Behavioral Profiling | Agent performance baseline | 90-97% |
| Historical Correlation | Threat pattern matching | 82-90% |
Paradigm Selection Protocol
The platform does not randomly apply paradigms. A structured selection protocol matches problem characteristics to optimal paradigm combinations.
Problem Input --> Complexity Assessment --> Paradigm Selection --> Execute --> Validate
| | | | |
Classify Measure Pick optimal Apply Trinity
domain constraints approach(es) solution GateSelection Criteria
| Problem Characteristic | Primary Paradigm | Supporting Paradigms |
|---|---|---|
| Data transformation | Functional | OTP (parallelism) |
| Entity relationships | Graph | Epistemic (confidence) |
| Regulatory compliance | Formal | Logical (rules) |
| Uncertainty management | Epistemic | Functional (composition) |
| Real-time processing | OTP | Functional (purity) |
| Pattern detection | Heuristic | Graph (structure), Epistemic (scoring) |
| Proof obligations | Formal | Logical (inference) |
Combined Paradigm Example
A typical EASM security assessment demonstrates multi-paradigm synergy.
| Phase | Paradigm | Operation | Output |
|---|---|---|---|
| 1 | Functional | Transform raw scan data into normalized asset records | Canonical asset inventory |
| 2 | OTP | Parallel discovery across DNS, certificates, ports, cloud | Raw discovery data |
| 3 | Graph | Map relationships between discovered assets and entities | Asset relationship graph |
| 4 | Epistemic | Score findings with NABLA-compliant confidence levels | Calibrated risk scores |
| 5 | Formal | Verify Compliance claims against NIS2 requirements | Formal compliance proof |
| 6 | Heuristic | Apply pattern-based risk scoring from historical data | Comparative risk assessment |
Agent Tier Integration
Paradigm availability is governed by the AIAD Standard tier system, ensuring that complex multi-paradigm operations are coordinated by appropriately authorized agents.
| Agent Tier | Available Paradigms | Authority |
|---|---|---|
| L1 (Tactical) | Functional, OTP | Single-paradigm execution |
| L2 (Operational) | Functional, OTP, Heuristic | Dual-paradigm composition |
| L3 (Strategic) | All paradigms | Full multi-paradigm orchestration |
| L4 (Specialist) | Domain-specific subset | Deep single-paradigm expertise |
L3 agents serve as orchestrators, decomposing complex problems into paradigm-specific sub-tasks and delegating to L1/L2 agents with the appropriate specialization. This ensures that multi-paradigm operations maintain coherent coordination while leveraging specialized execution at each step.
Quality Enforcement
Every paradigm application passes through the platform's quality infrastructure.
| Quality Layer | Paradigm Validation | Enforcement |
|---|---|---|
| Quality Gates | Compilation, Credo, Dialyzer, test coverage | BLOCKING |
| Trinity Gate | Structural, logical, formal verification | BLOCKING for epistemic output |
| NO MERCY | Zero tolerance for incomplete paradigm application | BLOCKING |
| NO DOUBTS | Evidence-based paradigm selection with documented rationale | BLOCKING |
| NABLA Axioms | Epistemic paradigm axiom compliance | BLOCKING for epistemic operations |
Performance and Metrics
| Metric | Current Value | Target |
|---|---|---|
| Paradigms supported | 6 | 6 |
| Multi-paradigm operations/day | 500+ | Growing |
| Paradigm selection accuracy | 94%+ | 97% |
| Cross-paradigm integration latency | < 100ms | < 50ms |
| Single-paradigm fallback rate | < 5% | < 2% |
| Formal verification coverage | L1-L4 complete | L5 in progress |
Configuration
Paradigm selection behavior and availability can be configured per agent tier and per domain context.
# config/config.exs
config :prismatic_agents, PrismaticAgents.ParadigmSelector,
default_paradigm: :functional,
max_paradigms_per_operation: 4,
formal_verification_enabled: true,
heuristic_confidence_floor: 0.7,
paradigm_timeout_ms: 30_000,
selection_strategy: :evidence_based
config :prismatic_agents, PrismaticAgents.ParadigmMonitor,
track_selection_accuracy: true,
report_interval: :timer.minutes(15),
alert_on_fallback: true,
performance_baseline_window: :timer.hours(24)| Configuration Key | Default | Description |
|---|---|---|
default_paradigm | :functional | Fallback paradigm when selection is ambiguous |
max_paradigms_per_operation | 4 | Maximum concurrent paradigms in single operation |
formal_verification_enabled | true | Whether Lean4 formal proofs are available |
heuristic_confidence_floor | 0.7 | Minimum confidence for heuristic pattern matches |
paradigm_timeout_ms | 30,000 | Maximum execution time per paradigm phase |
selection_strategy | :evidence_based | Strategy for paradigm selection (:evidence_based, :tier_default) |
Integration
- Applied through NABLA Axioms for epistemic problems
- Validated by Trinity Gate formal verification for all conclusions
- Powered by Telemetry Integration for paradigm performance tracking
- Governed by NO DOUBTS evidence requirements for paradigm selection
- Quality enforced by NO MERCY zero-tolerance standards
- Supports Autonomous Self-Healing through multi-paradigm diagnostic analysis
- Feeds Intelligence Synthesis with paradigm-appropriate analytical outputs
- Tier-governed by AIAD Standard authority definitions
- Compliance verified by AIAD Compliance
- Monitored by Real-Time Monitoring for operational metrics
- Quality Gates enforce paradigm-specific quality requirements
- Cross-Domain Flexibility enables paradigm application across domains
- Color Teams White Team provides formal verification paradigm
Connect & Contribute
Created by Tomáš Korcak (korczis) | Open Source under GHL