Governed data that keeps its origin.

Operational data arrives from sensors, operational systems, enterprise records, partner feeds and open sources, in different formats, at different rates and with different reliability. Most integration layers resolve that variety by flattening it. Reality Fabric resolves it by making the origin of every record part of the record.

• Multi-source ingestionSensor, operational, enterprise and open-source inputs through one governed write path.
• Streaming and batchContinuous feeds and bulk imports follow the same validation and labeling rules.
• NormalizationFormats, units, reference systems and time bases reconciled into one operational model.
• DeduplicationRepeated reports recognized as repeats, so volume is never mistaken for corroboration.
• Classification labelingEvery record carries a label at entry; unlabeled data does not enter.
• Source identityAuthenticated source identity attached to each record, distinct from the source's reliability.
• Data lineageDerived records keep a traceable path back to the originals they came from.
• ConfidenceConfidence values carry the method that produced them.
• Contradiction handlingConflicting inputs are both kept and marked as a contradiction, never silently merged.
• Provenance at ingestionSource, time, label and lineage are fixed at the moment of entry and cannot be rewritten later.

Reality Fabric has one rule that everything else depends on: a record without an identifiable source, a classification label and its time does not enter the operational picture. It is refused at the write path, and the refusal is recorded.

The rule is enforced by the Authority Kernel rather than by the connector, so a new integration cannot relax it. That is what allows the Reality Graph, Atlas and Intelligence modules to show the basis of anything they display.

Reality Fabric does not decide what is true. It records what each source asserted, how reliable that source has been, and where sources disagree. A false report from a genuine sensor remains a correctly attributed false report — visible as such, rather than hidden inside an average.

Three rules follow. Aggregation does not create certainty: five reports that derive from one original are one source, and the lineage shows it. Absence of evidence is recorded as absence, not as a negative finding. And a contradiction stays open until an accountable assessment adjudicates it, with both original records preserved.

Connectors for operational, enterprise and sensor systems are built on the SDK and Integration Framework, which defines Reality Object and Relationship types and the event contracts a connector must satisfy. Connector identity is issued by QECNet Trust Fabric, so every source can be authenticated and, when necessary, revoked.

Imports into air-gapped environments pass signature, provenance and content checks before they are admitted, and the import decision is itself evidenced.