feat(datasources): govern approvals and retention

README.md

@@ -38,6 +38,14 @@ promotion preserves the exact policy hash and validation result in immutable
 materialization provenance. The supported contract is documented in
 [docs/QUALITY_POLICY.md](docs/QUALITY_POLICY.md).
 
+The same lifecycle contract can require an attributable, separated approval
+quorum before a stage or cached refresh becomes current. Versioned retention
+rules cover transient stages, ordinary materializations, and frozen evidence.
+Retention remains an explicit preview-and-apply operation: current revisions,
+legal holds, pending approvals, and publication evidence are blocked, while
+every decision, promotion, and disposition is preserved in hash-chained local
+evidence even when the optional Audit, Access, or Policy modules are absent.
+
 The contracts already model database, HTTP/REST, directory, file, feed,
 document, binary, directory, and stream sources so providers can be added
 without changing consumers. Storage modules contribute artifact backends
@@ -49,7 +57,8 @@ See [docs/CONCEPT.md](docs/CONCEPT.md) for ownership and lifecycle details.
 ## Data-subject requests
 
 Datasources publishes `privacy.dsar.datasources` for exact catalogue,
-governance-reference, materialization, payload, stage, and publication
+governance-reference, materialization, payload, stage, publication, and
+lifecycle-evidence
 references and for minimized operator attribution. It never exports connector
 references, locators, credentials, arbitrary rows, schemas, validation
 samples, metadata, provenance bodies, checkpoints, replay material, or hashes.
@@ -57,6 +66,7 @@ The module does not guess subject identity by scanning schema-dependent tabular
 payloads; the authoritative source module locates and corrects those facts.
 
 Unpromoted stages and unreferenced payloads can be deleted idempotently.
-Published or referenced state, immutable materializations, governance evidence,
+Published or referenced state, immutable materializations, lifecycle evidence,
+governance evidence,
 holds, and operator attribution require data-steward review. Dataflow and
 Reporting derivatives must be refreshed after the source correction.