Controlled technical evidence

Native semantic data contract case study

Controlled v1.89.332 lending fixture: native validation receipts and sealed semantic changes, with explicit review and authority limits.

What did the native runtime actually validate?

In the v1.89.332 controlled contract track, two eligible properties yielded one native contract in A and B and two in C. A/B/C are sealed revisions of one asset. T is a separate source-edited sealed asset, not a fourth revision. A/B and T have unresolved owner label/meaning; C has a reviewed owner binding. The native certification label describes contract coverage, not production qualification or authority.

Recorded caseNative resultViolation / scope
A: Principal Amount 10000 (integer)PASSNo violation
A: Principal Amount "10000" (string)FAILTYPE_MISMATCH
A: Undeclared fieldFAILUNEXPECTED_FIELD
B: 30000 with original claimed contractFAILVALUE_NOT_ALLOWED; stale contract
C: Valid Loan IdentifierPASSNo violation
C: Missing required Loan IdentifierFAILMISSING_REQUIRED_FIELD
C: Integer instead of string identifierFAILTYPE_MISMATCH

Does unchanged physical type mean unchanged business meaning?

No. A→B is structural allowed-value drift ([10000, 20000]), introduced by reviewer policy; the original receipt becomes STALE_CONTRACT and requires revalidation. B→C is a reviewed semantic owner-identity change and contract restructuring; the Loan Identifier remains STRING, but the comparator reports semantic identity and relationship drift. Requiredness in C is reviewer policy, not a source-selected constraint. A→T compares different sealed assets: the Principal Amount definition changes from excluding interest and other charges to including capitalized interest but excluding other charges, while INTEGER is unchanged. That is native DEFINITION_DRIFT, not same-asset definition drift.

The missing required identifier case has one affected concept, one affected source, one affected relationship and one violation in the native impact response. Nullability remains UNKNOWN. This is recorded native validation, not a live arbitrary browser call or authorization to act.

Inspect native contracts, receipts and comparisons · Download the exact public-safe projection and source workbooks · Recorded native projection. The controlled demonstration is scoped; owner disclosure and publisher authentication remain pending.

Technical note by OntoGuard · product evidence and review scope are identified in the linked materials. Publication approval pending.

Evidence and buyer questions

What is stale contract validation?

The A receipt assessed against same-asset revision B returns STALE_CONTRACT and requires revalidation. B changes allowed values by reviewer policy. A/B/C are same-asset revisions; T is a distinct source-edited asset.

Inspect source or product evidence

Does SI detect meaning drift?

Yes. A→T compares separate sealed v1.89.332 assets: Principal Amount changes from excluding interest and other charges to including capitalized interest but excluding other charges; INTEGER is unchanged and the native comparator reports DEFINITION_DRIFT.

Inspect source or product evidence

What is native validation impact?

The native missing-required Loan Identifier validation in revision C reports one affected concept, one source, one relationship and one violation. The v1.89.332 impact result is scoped to this recorded synthetic contract and does not authorize any action.

Inspect source or product evidence

Is release evidence publisher authenticated?

Not independently. The exact native records and original exports have been privately checked, and the browser pins the audited projection and verifies bytes and a native digest subset. A same-origin code/data replacement is outside that trust boundary; independent publisher identity remains pending.

Inspect source or product evidence