Define Fraud Decision Intelligence ontology and SHACL surface

[mdheller]

Purpose

Define the ontology and SHACL surface for the Fraud Decision Intelligence capability family.

Upstream doctrine anchor:

• SocioProphet/ProCybernetica:docs/capabilities/fraud-decision-intelligence-control-plane.md

Minimum vocabulary

Define canonical classes/properties for:

• FraudEvent;
• FraudEntity;
• FraudRelationship;
• FraudEvidenceBundle;
• FraudDecisionReceipt;
• FraudLabelProvenance;
• FraudFeatureHealth;
• FraudScenarioCandidate;
• FraudControlAction;
• FraudOutcome;
• ResidualFraudLift;
• FalsePositiveCluster;
• FraudRingHypothesis.

Required distinctions

The ontology should distinguish:

• risk signal vs proof;
• scenario candidate vs confirmed typology;
• graph relationship vs attribution/intent;
• observed fraud vs residual fraud;
• weak label vs confirmed label;
• public-synthetic evidence vs private customer evidence;
• model recommendation vs policy-authorized control action.

Acceptance criteria

• RDF/OWL vocabulary lands under the existing ontology structure.
• SHACL shapes reject model-score-as-proof patterns.
• SHACL shapes require label provenance for confirmed fraud labels.
• SHACL shapes distinguish recommendation from authorized action.
• Public-synthetic examples do not include private customer data.
• Documentation states Ontogenesis owns ontology semantics, not runtime scoring or enforcement.

[mdheller]

Implementation progress:

• Added Domains/fraud-decision-intelligence.ttl as the compact domain ontology module.
• Added shapes/fraud-decision-intelligence.shacl.ttl with promotion gates for decision receipts, evidence bundles, label provenance, feature health, scenario candidates, control actions, and the key negative boundaries:
  • model score cannot directly assert fraud proof;
  • benchmark metric cannot directly assert production validation;
  • human-impacting authorized action requires policy reference;
  • confirmed fraud outcome requires label provenance.
• Registered og:DomainFraudDecisionIntelligence in catalog/registry.ttl.
• Added matching JSON-LD module registry entry in catalog/registry.jsonld.

Commit trail observed from connector:

• Ontology module: 9a4c51deba8ad007abc5b3d670261d74bafc4ab2
• SHACL gates: 6e7f30d451111a78a3696a70d3c0663f098847b7
• TTL registry: 6a6e72334cd5f5881654085428f6e82327116187
• JSON-LD registry: 4f21e1febdfca6aaa607946b82d0996f4298a50f

Remaining before closure:

• Run/observe make validate and make shacl green.
• Optionally add public-synthetic positive/negative examples if this repo expects examples for every SHACL surface.