Platform adapter
Runs contract apply operations against a warehouse, lakehouse, or query engine.
Architecture
Custom adapters without a custom platform.
Kirimana OSS Edition ships as one prescribed OSS path. Custom adapters are for extending Kirimana after that path is understood, not for turning first install into a tool-selection workshop.
Where adapters fit
Kirimana separates the contract lifecycle from the runtime that executes work. The contract stays ODCS-based, versioned in git, and governed by the same state machine. An adapter translates that contract intent into a specific platform, framework, catalog, vault, orchestration, or incident surface.
OSS Edition path
Fixed for production onboarding
Airbyte → Airflow → Iceberg → Trino → Polaris → Ranger → dbt-core → Kirimana.
Adapter surface
Extension point for real platform variation
Add a runtime only when there is a clear operating need: a new catalog, warehouse, orchestration engine, vault provider, or incident system that must receive contract context.
Adapter types
Framework adapter
Adds contract context to dbt-core or another modelling framework.
Catalog adapter
Pushes owner, classification, lineage, and contract version into metadata systems.
Policy adapter
Turns classifications into row, column, masking, and approval policies.
Vault adapter
Resolves `${vault:...}` references without storing plaintext in contracts.
Incident adapter
Dispatches SLA breaches, schema drift, and apply failures to operational tools.
Rules for a good adapter
- Preserve the contract. The adapter must not create a second governance model.
- Stay deterministic. Apply, validate, and rollback behaviour must be repeatable in CI.
- Emit audit evidence. Every external action needs a traceable result.
- Keep secrets out of YAML. Runtime credentials resolve through vault references.
- Fail closed. Unknown classification, owner, or policy state must block production promotion.
Practical guidance
Start from Kirimana OSS Edition, then adapt.
The recommended implementation path is to install Kirimana OSS Edition as-is, prove the contract lifecycle end to end, then add adapters for platform-specific gaps. That keeps first value fast and makes custom engineering reviewable.
Back to Kirimana OSS Edition