Connector semantics v1
Pilot contract; not a stable general SDK. Managed ophiolite.source-snapshot/1
manifests add contract.schema = "ophiolite.connector-semantics/1". Existing identity,
revision, payload hash and media fields remain. Native protobuf payloads are not
rewritten; a separate descriptive adapter uses the same semantic vocabulary.
| Report field | Meaning |
|---|---|
identity |
Original authority, key, opaque revision and reader profile |
representation |
Profile, media type and SHA-256 of that representation |
mapping |
Exact source schema, mapping version, scientific profile and optional destination schema |
fidelity |
Assessment schema/state/scope, assessor, method, version, losses and limitations |
history |
Current-only, upstream-exact-read or unassessed; separately recorded retention |
distribution |
Conservative declarations; not an authorization credential |
The fidelity states are not-assessed, assessed-no-loss and assessed-with-loss.
Scopes are source-representation, byte-preservation, edited-representation and
scientific-meaning. No-loss with nonempty losses is invalid; with-loss requires
findings. An unassessed report may already list known limitations/losses without
claiming a complete assessment. Unknown versions are refused by conformance tools;
UI consumers show unassessed/unknown rather than certifying them.
Original source and edited output reports describe different representations and must not overwrite each other. LAS no-op returns original bytes. Rewriting LAS reports formatting loss and checks values, missing mask, curve identity, depth index and units by readback. SQL portable edits are selected field views, not database backups.
OSDU reports preserve the exact approved returned kind, SQL reports use the schema digest and saved mapping version, and file reports identify format and reader profile. A scientific profile describes bounded exposed meaning; it does not certify every field of an OSDU well-known schema. Unapproved live schema drift remains refused.
The Stage 0 policy helpers are conformance utilities, not a production authorization
service. Actions are read, export, retain, redistribute; missing grants deny.
Redistribution additionally requires retained content, explicit source retention and
distribution rights, project access and a named recipient audience. The browser only
renders evidence. Current effective source restrictions must still be enforced.
Incompatible meanings require a new contract version. Additive reports preserve old consumer payload fields. Original-byte fidelity, scientific fidelity, live following and native editing remain separately qualified capabilities.
