Integration without a way around the rules.

• Connector SDKBuild ingestion connectors that satisfy provenance, labeling and lineage rules.
• Reality Object and Relationship definitionsTyped definitions for the objects and links a domain adds to the graph.
• Reality Graph read and write APIsGoverned access, evaluated object by object against mission and label.
• Authority Kernel integrationEnforcement-point interfaces for requesting and applying decisions.
• Authority Envelope verificationLibraries to verify signature, digest, scope and validity locally.
• Enforcement-point librariesConsistent fail-closed enforcement in services and adapters.
• Evidence client librariesSubmit and verify evidence records, including execution receipts.
• Event contractsVersioned contracts for the events a component emits and consumes.
• OpenAPI and AsyncAPI interfacesMachine-readable descriptions of synchronous and event interfaces.
• Third-party application integrationApplications as registered principals with scoped grants.
• Hardware and sensor adaptersAdapters that bring devices and operational systems under Verity Edge.

Every integration is a principal. It is enrolled with an identity from QECNet Trust Fabric, granted narrowly, and revocable. What it may read, write and trigger is decided by the Authority Kernel at each call, not configured once in the integration.

• A connector cannot write a record without source identity, label and time.
• An application cannot cause an effect without an authority envelope.
• An adapter at the edge cannot accept an instruction that Verity Edge has not validated.
• An integration's calls, permitted or refused, are evidenced like any other principal's.

Interfaces are described as OpenAPI and AsyncAPI documents and versioned alongside the platform release that serves them. Object and relationship definitions are data delivered through Verity Forge, so a domain model change follows the same review, approval and evidence as any other change.