Acquire
- Success means
- One bounded, complete unit is available.
- Owned responsibility
- Source identity, selected range or cursor, stable work identity, replayable input, and settlement information.
Building Blocks
Cohesive.
Cohesive.Integrations declares bounded ingestion flows and lowers their acquisition, publication, progress, and settlement responsibilities into canonical Cohesive.Processes.
Core Idea
An ingestion definition is a composition compiler. It connects exact request contracts into a durable Process; it is not an ingestion service, scheduler, transport, or second execution runtime.
Bounded Ingestion
Each definition names a stable source-to-destination application binding and pins its revision, fingerprint, and exact interaction contracts. Different consumers or independently advancing destinations use different identities.
Bounded ingestion flow
Acquire one complete unit of work, then exact result schema, Publish application data and coverage, then verified receipt, Advance progress when the profile requires it, then confirmed progress, Settle the source obligation
Operation Contracts
Publish
- Success means
- Destination effects, coverage, and operation evidence were accepted together.
- Owned responsibility
- Domain validation, ordering or CAS rules, stable retry identity, and an exact receipt.
Advance ledger
- Success means
- Progress and its original-result receipt committed atomically.
- Owned responsibility
- Revision checks, position rules, replay, conflicts, and unknown visibility.
Settle
- Success means
- The source obligation is complete after publication.
- Owned responsibility
- Acknowledgment or a declared successful no-op for sources without an acknowledgment protocol.
Request schemas own application payloads. Integration ledger contracts own progress and receipt metadata. Adjacent successful-result and input schemas must match exactly; shape compatibility alone does not authorize an implicit mapping.
Recovery and Evidence
The compiler requires stable retry identity, ambiguity reconciliation, and reuse of duplicate outcomes. Unknown publication remains unresolved; an adapter cannot reinterpret missing evidence as proof that an effect failed.
This keeps recovery aligned with idempotency, retained receipts, and the actual commit boundaries supplied by a realization.
Ledger Profile
The atomic profile compiles acquire, publish, and settle. The separate-ledger profile inserts an exact AdvanceLedger request between publication and settlement. Its address scopes progress by flow, source, destination, and partition; a changed semantic revision cannot silently create an empty ledger and restart ingestion.
An advance must retain both the new entry and the original-result receipt atomically. A replay returns that original receipt before current revision checks, even if later work has advanced the ledger. A definite conflict stops the flow without pretending the published destination effect rolled back.
Qualification Boundary
Physical guarantees require an explicit realization with evidence for atomic placement, scoped idempotency, retention horizons, source completeness, safe advancement, and unknown-outcome handling. The current compiler emits a structured unqualified-realization warning until those obligations are supplied.