Shared core across all libraries
RAG, semantic chunking, HNSW retrieval, MCP servers, agentic workflows, PostgreSQL, Node, and Next.js.
Our Research
Retrieval answers: what evidence exists?
Discursive methodology: how should we think with it - across perspectives - until we can decide?
Our apps belong to a family of methodology-first apps. All share one technical core, and each differentiates through Data Processing Strategies and Discussion Methodologies.
From beginning to end, the flow is efficient and reliable.
Reliable sources are semantically chunked into effective passages.
RAG retrieval maps every query into vector search over indexed knowledge.
HNSW graphs accelerate nearest-neighbor retrieval for low-latency context.
PostgreSQL stores full text, metadata, and citation references for grounding.
Node and Next.js orchestrate streaming delivery in a production web workflow.
Specialized agents run discursive methodologies on retrieved context to produce deep insights.
The platform can be extended with new libraries that share a common core but differ in their data processing strategies and discussion methodologies.
RAG, semantic chunking, HNSW retrieval, MCP servers, agentic workflows, PostgreSQL, Node, and Next.js.
Each library can tune its VectorStore strategy, ranking profile, and corpus scope without losing platform consistency.
Each library adopts a discursive methodology suited to its domain—strategy, law, ethics, product decisions, and more.
Using the methodology created by Edward de Bono, we deploy six parallel lenses to reduce blind spots and improve decision quality.
Facts and evidence
Objective signals, metrics, and known constraints.
Emotions and values
Motivations, fears, and human tension points.
Risk and criticism
Failure modes, weak assumptions, and downside scenarios.
Benefits and opportunity
Value creation paths, upside cases, and leverage points.
Creativity and alternatives
Novel options, experiments, and non-obvious reframing.
Synthesis and governance
Final prioritization, alignment, and actionable direction.
OHP Orchestra is the execution layer that converts multi-perspective analysis into a defensible decision path, moving from problem framing to implementation guidance.
Stage 1
Split the challenge into decision units, assumptions, dependencies, and constraints so the reasoning scope is explicit.
Stage 2
Interpret retrieved evidence through competing lenses, separating textual support from inference and clarifying conceptual tensions.
Stage 3
Model lived impact across stakeholders, incentives, emotions, and adoption context to test practical viability.
Stage 4
Stress-test arguments for logical gaps, bias, unsupported claims, and risk exposure before committing to action.
Stage 5
Integrate validated insights into a coherent recommendation with priorities, trade-offs, and concrete next steps.
See how Six Hats and OHP Orchestra perform when your team needs grounded, defensible decisions.