This module retains original JSON bytes, number tokens and ordered occurrences for advertising sources. Missing, null, empty object, empty array and repeated equal array values remain distinct. Duplicate decoded member names are refused, including escaped equivalent names. A retained lexical number alone supplies no provider datatype, unit or financial-validity assertion.
This is the unofficial 0.1.0 module specification. Source review and executable correctness are separate standings. Full generation, runtime and publication verification are pending configured GitHub CI; this draft supplies no release, native write or client-adoption qualification.
This module retains original JSON bytes, number tokens and ordered occurrences for advertising sources. Missing, null, empty object, empty array and repeated equal array values remain distinct. Duplicate decoded member names are refused, including escaped equivalent names. A retained lexical number alone supplies no provider datatype, unit or financial-validity assertion.
Agents can inspect the selected retained evidence, ask for missing scope or review, and keep unresolved answers visible. A successful inspection remains separate from permission to act on a live account.
https://ontology.inferal.com/modules/ads-source-fidelity/
The prefix nf names the existing vocabulary. Term identity and the original RDF types remain stable. Shared advertising and commerce concepts supply scope; captured provider terms retain their provider-specific meaning.
RawSource identifies retained bytes and their digest. Occurrence records source order, pointer, kind and exact numeric lexical content. SourceAssessment keeps native datatype and numeric-origin standing separately from identity and write authority. Raw mode uses no native context. Native mode uses a validated captured Google, Meta or Microsoft context and schema, followed by the existing normalization and provider projection.
| Evidence | What the consumer can conclude |
|---|---|
| Retained source | The selected bytes and represented claims remain inspectable. |
| Scoped interpretation | The named contract supplies a result with its own qualification and coverage. |
| Current action authority | Live permission, native applicability and client adoption require separately qualified evidence. |
The source, context, executing interpretation and package are authenticated before replay. CallerDeclaredDatatypeOnly cannot qualify native applicability. A retained read-only codec supplies no native mutation encoder. Identity lexicals still need a reviewed provider/account binding before action. The retained package authenticates its external manifest and complete rederivation, rather than executing foreign retained code.
RDF permits incomplete descriptions. A conforming execution profile must enforce its declared closed-world input and output constraints. Unknown or conflicting business evidence must keep its explicit standing and cannot be converted into a favorable value.
Exact integer and decimal support is bounded to 128 total digits and 64 decimal scale. Native float stays binary32 origin and double stays binary64 origin. Direct nearest-even binary32 rounding preserves negative zero and refuses overflow or nonzero underflow, without first rounding through binary64. JSON admission is bounded to 64 nesting levels, 4096 occurrences and 256 numeric-token bytes. Packages are bounded to 256 files/directories and 64MiB. Unsupported native encoding is distinct from an unqualified business meaning.
Validation establishes conformance to a selected profile. Retained scope, reported evidence and operational success keep their separate meanings. Runtime and generation evidence for this source repair remain pending GitHub CI.
The number 9007199254740993 stays an exact lexical token in the retained occurrence. The example assessment is NativeDatatypeUnassessed and originalDecimalQualified false: exact lexical preservation alone does not authenticate a native datatype or money value.
Inspect the declared roles and independent standings before using this evidence. Omitted source data or an unresolved qualification must remain visible. This example does not attest a live provider request or complete merchant history.
Classes, properties and existing controlled evidence values retain their authored labels and definitions. Listing a controlled value here does not change its RDF type or grant execution authority.
nf:CallerSuppliedIdentityOnly — CallerSuppliedIdentityOnlynf:CallerSuppliedRetainedSource — CallerSuppliedRetainedSourcenf:CapturedNativeDatatypeEvidence — CapturedNativeDatatypeEvidencenf:ExactRetainedDecimalValue — ExactRetainedDecimalValuenf:ExactRetainedIntegerValue — ExactRetainedIntegerValuenf:NativeBinary32OriginUnqualifiedForOriginalDecimal — NativeBinary32OriginUnqualifiedForOriginalDecimalnf:NativeBinary64OriginUnqualifiedForOriginalDecimal — NativeBinary64OriginUnqualifiedForOriginalDecimalnf:NativeDatatypeUnassessed — NativeDatatypeUnassessednf:Occurrence — Occurrencenf:RawSource — RawSourcenf:RetainedNativeDatatypeContext — RetainedNativeDatatypeContextnf:RetainedReadJSONTokenCodecV1 — RetainedReadJSONTokenCodecV1nf:ReviewedOwnerBinding — ReviewedOwnerBindingnf:SourceAssessment — SourceAssessmentnf:WriteAuthorityUnassessed — WriteAuthorityUnassessednf:array — arraynf:boolean — booleannf:booleanValue — booleanValuenf:codec — codecnf:decoded — decodednf:evidenceNeeded — evidenceNeedednf:index — indexnf:kind — kindnf:logicalDatatype — logicalDatatypenf:member — membernf:null — nullnf:number — numbernf:numberLexical — numberLexicalnf:object — objectnf:occurrence — occurrencenf:ordinal — ordinalnf:originalDecimalQualified — originalDecimalQualifiednf:parent — parentnf:pointer — pointernf:reader — readernf:readerName — reader namenf:source — sourcenf:sourceDigest — sourceDigestnf:sourceStanding — sourceStandingnf:standing — standingnf:string — stringnf:writeAuthorityStanding — writeAuthorityStanding