32 lines
1.5 KiB
Markdown
32 lines
1.5 KiB
Markdown
# govoplan-datasources
|
|
|
|
<!-- govoplan-repository-type:start -->
|
|
**Repository type:** module (platform).
|
|
<!-- govoplan-repository-type:end -->
|
|
|
|
`govoplan-datasources` is GovOPlaN's provider-neutral data access layer. It owns
|
|
the tenant catalogue, lifecycle, staging, immutable materializations, frozen
|
|
states, schema and fingerprint metadata, provenance, and bounded reads.
|
|
|
|
The module deliberately separates two layers:
|
|
|
|
- **Datasources** describe governed data that modules can consume consistently.
|
|
- **Connectors** acquire data from external systems and expose provider origins.
|
|
|
|
Dataflow, Workflow, Reporting, Risk Compliance, and other consumers depend on
|
|
Datasource contracts rather than connector implementations.
|
|
|
|
The first executable slice supports tabular static uploads, connector-backed
|
|
live and cached sources, staging and promotion, refresh, immutable snapshots,
|
|
explicit frozen states, previews, retirement, and atomic producer publication.
|
|
Producer modules can append a bounded tabular result or create a new static
|
|
datasource through an idempotent capability. The publication ledger retains the
|
|
producer run, output materialization, provenance, and replay identity.
|
|
|
|
The contracts already model database, HTTP/REST, directory, file, feed,
|
|
document, binary, directory, and stream sources so providers can be added
|
|
without changing consumers. Larger durable artifact-backed publications remain
|
|
a later storage-provider slice.
|
|
|
|
See [docs/CONCEPT.md](docs/CONCEPT.md) for ownership and lifecycle details.
|