Product capability · Semantic Intelligence

Catch a change in business meaning before it becomes a downstream error.

Semantic data contracts

A schema can stay valid while a field’s meaning changes. Native Semantic Data Contracts bind eligible field constraints and meaning to a sealed semantic revision.

Why it matters

Validate strictly, see receipts, identify stale contracts and detect structural or semantic drift. Reuse the governed asset across platforms.

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.

What a contract binds

A contract can bind field identity, definition, domain, category, established role/class, physical type and evidence-supported constraints to a revision. Strict validation does not silently coerce strings to numbers.

Illustrative fieldConstraintExample
amountnumber; explicit currency1250 accepted by example type check; "1250" rejected
loan_idstringL-001
currencystringUSD

Validation receipts identify the contract/revision. Physical, structural, definition, domain, relationship or semantic drift can make a downstream dependency stale; bounded impact analysis identifies affected bindings. A pass is not business permission.

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.

Controlled versus teaching mode

The earlier rich, micro and lifecycle demonstrations retain their empty native catalogues. A distinct native contract track now contains eligible fields, exact recorded receipts and sealed revision comparisons. The teaching dataset remains separate.

Native catalogue status · Illustrative contract workbench

Current demonstration scope

The rich, micro and lifecycle runs still contain no eligible contracts. Native receipts and drift are shown only in the dedicated controlled contract track, not attributed to those runs. Teaching mode is not runtime validation or permission to act.

Inspect actual run evidence

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

Evidence and buyer questions

What is a semantic data contract?

A semantic data contract binds field constraints and evidence-qualified business meaning to a sealed semantic revision. The v1.89.332 native workbench records seven validation outcomes and exposes drift and impact; validation does not authorize effects.

Inspect source or product evidence