ValueLogics.ai
The Governed Core
The Value Ontology
Four modules, one core — plan value, quantify it, communicate it, and prove it.
The traceability thread — a claim, all the way down to a hash
→
Problem Pyramid
REAL Requirement
→
→
The four modules
1
Problem Pyramid
what they value
Classes
ProblemCauseBAUGoal MeasureREAL Requirement
Aligns to OMG BMM (ends & means) · design-time stage 1
2
ROI
what it's worth
Classes
CostBenefitROIMetric · NPV/IRR/paybackCashFlowRisk
Aligns to your ROI ontology (four value buckets)
3
Value Marketing
how you say it
Classes
PersonaValue PropositionValue MessageChannelCase Study
Aligns to BVPM (the intent model → OMG Business Architecture TF)
4
Proof
did it happen?
Classes
ClaimEvidenceActualBaselineDriftAttestationProvenanceConfidenceHash
Aligns to AAEI · VDSC · STT — the evidence & settlement layer
Shared join keys — what makes it one ontology, not four
These entities are shared across modules — so a value message traces to a requirement, to a benefit, to a proof, without breaking.
REAL RequirementGoal MeasureValue / BenefitPersona
business_case_idMeasure
Module 3 · Value Marketing
Concept-map walkthrough
A guided walkthrough of the Value Marketing module — how Persona, Value Proposition, Value Message and Channel resolve back to the shared join keys, so a message traces to a requirement, to a benefit, to a proof. Mapped in CmapTools (IHMC).
The discipline: one ontology · four modules · shared join keys · profiled per domain (data warehouse, healthcare, Salesforce) — never forked. Each domain is a profile on top of the same governed core; the GPT-trainer front end runs the conversation, the ontology and ROI-DSL do the math — the LLM never invents a number.