Product capability · Semantic Intelligence

Know who owes what, under which terms, and what is still unknown.

Obligation, lifecycle and lineage intelligence

A field name or status label cannot tell you whether an obligation is in force or discharged. OntoGuard reconstructs supported financial and operational meaning across parties, amounts, conditions and lifecycle.

Why it matters

Bring payment, lending and contract information together without mistaking source assertions for actual settlement or authority.

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 dateNative interpreted state
January 15, 2026SUBMITTED
January 16, 2026EXECUTED
January 17, 2026REVERSED

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.

Finance-first, domain-extensible

Reconcile parties, identities, currencies, units, dates, source lineage and conditions. Preserve amendments and reversals. Do not infer settlement from submission or discharge from absence of evidence.

IntentAuthorizationSubmissionExecutionSettlementFulfillment / discharge
Truth levelExample
Source assertionA policy says payment is due on a specified date.
Interpreted meaningThe clause describes an obligation subject to stated conditions.
Current operative factSettlement or discharge remains UNKNOWN until separately supported.

Not a financial execution engine or automatic authoritative legal/financial rule. Optional DA integration is separate.

Evaluate the runtime

Define the source or protected-action boundary, success criteria and integration responsibilities before a focused evaluation. No confidential data through the public site.

Source-backed lifecycle and obligation example

In a separate installed v1.89.332 run, two synthetic workbooks produced eight constituted concepts, three candidate graph edges and sixteen exact evidence locators. Native interpretation retained SUBMITTED (January 15), EXECUTED (January 16) and REVERSED (January 17) source-asserted states, with repayment conditions and USD context. Settlement, legal discharge and operative authority remain UNKNOWN. The example does not establish a linked real payment chain or production qualification.

Actual native contracts and sealed revision evidence

v1.89.332 generated a contract with two eligible properties. Recorded native validation, sealed revisions A/B/C, structural and semantic identity drift, stale receipt assessment, and downstream impact are available. A separate source-edited asset demonstrates definition drift with unchanged INTEGER type. Synthetic data; disclosure review pending; no action authority.

Inspect actual contract evidence · Download native-record projection

Native source-linked payment lineage

The R8 controlled v332 fixture preserves shared synthetic payment reference SYN-PMT-01 and explicit source-described links between submission, execution and reversal. Eight constituted concepts, seven candidate graph edges and sixteen source locators include a native candidate INTENDED_TO_FULFILL relation. These are source assertions and candidate semantic relationships, not independently established transaction identity, settlement, discharge or permission to act.

Explore the native lineage dataset · Download the scoped projection

Evidence and buyer questions

Can SI establish financial lineage?

The controlled lineage run has eight concepts, seven candidate edges and 16 exact locators. Shared source references SYN-PMT-01/SYN-LOAN-01 and a candidate INTENDED_TO_FULFILL edge link source assertions, not independently established transaction identity, settlement, discharge or operative authority.

Inspect source or product evidence

Does the candidate lineage establish identity?

No. The v1.89.332 lineage sample retains candidate relationships and source identifiers, not canonical same-transaction identity. Dates and matching source strings alone do not establish settlement, discharge, fulfillment or operative truth.

Inspect source or product evidence