Product capability · Semantic Intelligence
Separate the business obligation from its actual fulfillment.
Obligations, lifecycle and lineage
Requested, approved, executed, settled and reversed are different lifecycle states. OntoGuard preserves source context and keeps unsupported consequences unknown.
Why it matters
Reconcile temporal and conditional information without turning candidate lineage into an established transaction identity.
How it works
Separate intent, authorization, submission, execution, settlement and discharge. Preserve parties, currency, conditions, dates and evidence lineage. A missing settlement observation is UNKNOWN, not proof of failure or success. Interpreted meaning does not establish operative authority.
Illustrative explanations describe the boundary, not a customer result. For specific evidence and integration scope see the linked product page.
Further reading
Submission is not settlement
A policy may define a repayment obligation, a source may record submission and another may establish settlement. Track parties, conditions, timing and provenance independently; missing later evidence remains unknown. Amendments or reversals require separate history. The semantic asset does not issue a legal determination or authorize a payment. Lifecycle semantics.
What does the lifecycle demonstration establish?
The v1.89.332 lifecycle projection contains eight constituted concepts, three candidate RELATED_TO edges, 16 exact source-cell locators and seven financial-context records. The following are source-asserted interpreted states, not independently observed transactions.
| Source date | Native interpreted state |
|---|---|
| January 15, 2026 | SUBMITTED |
| January 16, 2026 | EXECUTED |
| January 17, 2026 | REVERSED |
Repayment conditions and January 20 due-date context are retained. These are distinct event concepts: identity linkage is not established, and dates alone cannot establish same-transaction lineage. Settlement, discharge and operative authority remain UNKNOWN. Inspect source-backed lifecycle · Download projection.
What did the native lineage example establish?
The v1.89.332 controlled lineage dataset contains eight concepts, seven candidate graph edges and sixteen exact source locators. Synthetic records preserve SYN-PMT-01 and SYN-LOAN-01; the runtime returns candidate INTENDED_TO_FULFILL between Payment Submission and Repayment Obligation. Source-asserted dates describe submission on January 15, execution on January 16 and reversal on January 17, 2026.
Matching identifiers or dates alone do not establish canonical same-transaction identity. Settlement, discharge and operative authority are UNKNOWN or not established. A semantic interpretation is not permission to act.
Inspect native lineage evidence · Evaluate obligation intelligence
Technical note by OntoGuard · product evidence and review scope are identified in the linked materials. Publication approval pending.