{
  "format": "vercy-selected-source-comparison",
  "readDate": "2026-09-22",
  "scope": "Selected primary sections and original design proposals; no wholesale standards conformance or copied upstream schemas.",
  "sources": [
    {"id":"SRC-PROV","url":"https://www.w3.org/TR/prov-dm/#term-Invalidation","edition":"W3C Recommendation 2013-04-30","section":"5.1.8 Invalidation","status":"observed","claim":"Invalidation concerns an entity's availability after an event.","decision":"Align source representation availability. The inference that this must not retire every business referent is our design decision.","limits":"No PROV-CONSTRAINTS or complete encoding conformance reviewed."},
    {"id":"SRC-AIRBYTE","url":"https://docs.airbyte.com/platform/understanding-airbyte/airbyte-protocol","edition":"Moving official page; changelog includes protocol v0.19.0 dated 2025-10-10","section":"State & Checkpointing; State & the Whole Sync; Schema Mismatches; changelog","status":"observed","claim":"Source state alone is insufficient for safe progress; destination confirmation matters. State is opaque outside its producer.","decision":"Adopt local receipt-linked progress shape, not Airbyte message schemas. Reject silent loss of mapped fields in this closed contract.","limits":"No live connector compliance tested. Claude's older changelog interpretation is not adopted as the current page version. Stream/global extension remains outside first release."},
    {"id":"SRC-GRAPH","url":"https://learn.microsoft.com/en-us/graph/delta-query-overview","edition":"Moving official page; last updated 2025-04-30 observed","section":"State tokens; replay; synchronization reset; removed resources","status":"observed","claim":"Tokens are opaque and query-qualified; clients must handle repeated changes and resets. Removal meanings and lifetimes are resource-specific.","decision":"Keep scope and epoch explicit; do not infer business-object death or record reincarnation from reset.","limits":"No universal TTL or resource-specific deletion contract is imported."},
    {"id":"SRC-DEBEZIUM","url":"https://debezium.io/documentation/reference/stable/connectors/postgresql.html","edition":"Moving stable page; examples show 3.6.3.Final","section":"Snapshots; Replica identity; Primary key updates; delete/tombstone events; selected pgoutput limitation","status":"observed","claim":"A primary-key update is described using old-key delete/new-key create with linking headers. Before-image visibility depends on replica identity; tombstones support log compaction.","decision":"Record key changes separately from business identity and source-instance generation. Never invent missing before-values.","limits":"Full connector, failure behavior and plugin-specific behavior were not independently audited. No claimed normative contradiction about tombstones is adopted; configuration controls their emission."},
    {"id":"SRC-SINGER","url":"https://github.com/singer-io/getting-started/blob/master/docs/SPEC.md","edition":"Singer Specification 0.3.0, moving master","section":"Entire rendered specification body: input/output, RECORD, SCHEMA, STATE, versioning","status":"observed","claim":"Tap state semantics are producer-defined; the specification describes source messages and does not define this contract's destination receipt protocol.","decision":"Use as an alternative approach comparison; do not treat source STATE as proof of destination commitment.","limits":"No conclusion about all Singer targets, orchestrators or deployment guarantees follows."},
    {"id":"SRC-SCIM","url":"https://www.rfc-editor.org/rfc/rfc7643","edition":"RFC 7643, September 2015; page names later updates","section":"3.1 Common Attributes: id, externalId, meta","status":"observed","claim":"Provider id and client externalId have different authority, stability and uniqueness scopes.","decision":"Separate qualified source identity from client mapping identifiers.","limits":"Selected original section only. Later RFC 9865 and RFC 9967 titles were opened, not their full specifications; no current whole-SCIM conformance."},
    {"id":"SRC-CONNECT","url":"https://docs.confluent.io/platform/current/connect/design.html","edition":"Moving official documentation; page published 2026-09-10 observed","section":"Architecture; Internal Connect Offsets","status":"observed","claim":"Connector-defined partition/offset information and persistent runtime configuration have an operational role distinct from business mappings.","decision":"Keep installations and progress separate from subjects and authority.","limits":"No full Kafka KIP or exactly-once audit; the provider's broader delivery claims are not independently ratified here."},
    {"id":"SRC-SQLITE","url":"https://www.sqlite.org/lang_transaction.html","edition":"Official page updated 2026-02-18","section":"2.1, 2.2, 3","status":"observed","claim":"One writer operates at a time; BEGIN IMMEDIATE obtains a write transaction and may encounter contention. Errors require explicit transaction handling.","decision":"Propose one local transaction for head/fence checks and durable receipt metadata.","limits":"This does not establish distributed leases, authentic host identity, external evidence durability or performance."},
    {"id":"SRC-SQLITE-ATOMIC","url":"https://www.sqlite.org/atomiccommit.html","edition":"Official moving documentation","section":"Introduction and stated rollback-mode scope; hardware assumptions opening","status":"observed","claim":"Atomic commit depends on storage behavior; the described mechanism is for rollback journal mode, with WAL treated separately.","decision":"State storage/flush and local-host limits explicitly.","limits":"Full hardware/failure sections and WAL mechanism were not read in this pass. No unconditional durability claim."}
  ],
  "unverifiedSuggestions": ["Data Vault/MDM school-level suggestions in Claude's S0 are prior knowledge, not adopted normative evidence.","Provider-reported hashes are distinguished from independent host retrieval hashes.","Source content is referenced in original summaries; no upstream schema or vocabulary copied into the implementation."],
  "designStatus": "proposed research boundary under S2 clarification; no implementation test or publication acceptance implied"
}