Choose a product and inspect the evidence with its scope, provenance and limitations.
Two evidence tracks
OntoGuard Semantic Intelligence Runtime OEM
Actual v1.89.332 rich, micro and lifecycle projections from private synthetic-source runs. The rich run published 22 constituted concepts and 20 edges; a separate lifecycle run preserves three source-asserted temporal states. Demo production qualification and public disclosure approval are distinct and pending. A separate native contract track shows seven validation receipts and sealed revision drift; teaching mode is separate.
Historical controlled cases, independently reviewed bounded PR integrations, ten current reference packets and a local mock-target execution with signed outcome. No real payment, external production log or customer deployment.
Merged September 20, 2026. Independent maintainer reproduction: 27 adapter tests. Authorized $250,000 path committed once with TRACE; altered $260,000 path refused, pending, zero commits and no TRACE.
Merged October 6, 2026; October 3 review by Carlos (carloshvp): 36 integration tests, 97 negative wrapper/direct-executor probes refused with zero commits and no protected effect, four positive probes executed the validated exact action. Imran Siddique approved and merged.
Bounded adapter and software harness, not independent validation of the complete runtime, SI, customer deployment or universal non-bypassability. Source: linked PRs; launch recheck required.
Evidence scope
Actual controlled runtime output, independently reviewed bounded integration, release-reported qualification, historical artifact and illustrative scenario are separate evidence categories. A checksum verifies consistency against a manifest, not independent publisher authenticity.
v1.5.2 archived verifier tests were reproduced privately using test trust keys and historical age settings; no new customer or live execution evidence. Read scope and results.
Inspect current reference evidence
Semantic Intelligence
Actual controlled synthetic v332 run: 22 constituted concepts, 20 graph edges and two Needs Review rows, with exact source-cell projection; native artifact approval and demo production qualification remain pending.
Fresh v1.5.2 reference packets and a separate controlled local mock-target execution, with test keys and recorded offline checks; not production deployment.
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.
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.
v1.89.332: eight concepts, seven candidate edges, sixteen source locators; source identifiers and a candidate INTENDED_TO_FULFILL relationship. The source linkage is not independently established transaction identity, settlement, discharge or authority.
The SI demonstrations expose native source-backed concepts, contracts, receipts and revision comparisons; the DA proof exposes reviewed public integration and controlled v1.5.2 local reference evidence. Demo qualification, independent publisher identity, disclosure and deployment approval remain separate.