Decision Engine
Evaluates explicit alternatives through a consistent execution contract.
QDIP CORE
A technical foundation for inspectable decision systems.
QDIP Core keeps the decision contract explicit: context, alternatives, rules, constraints, risk, uncertainty, evidence, evaluation and recommendation remain connected through one execution path.
01
ARCHITECTURE
Stable core, extensible decision domains.
Domain capabilities plug into a common decision runtime. This separates reusable decision infrastructure from domain-specific evidence and evaluation logic, so a new use case does not require a new product architecture.
Domain plugins
Supply domain-specific capabilities without redefining the core runtime.
Decision API
Provides a stable boundary between applications and decision execution.
02
DECISION MODEL
Keep the important concepts separate.
State, alternatives, objectives, expected effects, costs, risk, uncertainty, constraints and evidence are modeled as distinct decision concepts. This makes the model easier to review, test and evolve than a single opaque score.
03
EVIDENCE & EXPLAINABILITY
A recommendation should remain inspectable.
QDIP preserves supporting evidence and execution trace so reviewers can inspect why an alternative was selected and which constraints or assumptions shaped the result.
Evidence
Supporting information remains attached to the evaluated decision.
Execution trace
The evaluated path is available for technical review and debugging.
Auditability
Decision context and engine metadata can be retained for governance and reproducibility.
04
PRODUCTION BOUNDARIES
Designed as infrastructure, not a demo-specific calculation.
The platform architecture includes tenant-scoped access, API keys, rate limiting, asynchronous decision jobs, feature definitions and values, and an extensible plugin SDK. These boundaries allow applications such as Observatory and Studio to remain separate from decision execution.
05
PRODUCT SURFACES
Configure, evaluate, inspect.
Studio configures decision models. QDIP Core evaluates them. Observatory exposes recommendations, alternatives, evidence and scenario changes for inspection. Demos are configured applications of the same architecture.
NEXT STEP
Need the technical model behind the demos?
Continue into the research and architecture material, or open a working decision application to inspect the product behavior directly.