Ingest groups
A disease can only be caught as early as its fact reaches the register. When a test result or a variation lands on time and says where it came from, the five diseases are caught while they are still cheap. The ingest group is the pipe that gets it there.
An ingest group is how a fact actually gets recorded. Every connector that reads from your ERP, every field-ops harvester, every document extraction, and every computed reconciliation writes into Civil Memory through an ingest group. It’s the pipe - as distinct from the register, which is the product the pipe fills.
What travels with an ingest group
Section titled “What travels with an ingest group”An ingest group is more than a data path. It’s the single place the platform records:
- Entitlement - which tier, and which of your organisation’s permissions, are required for this data to flow at all
- Provenance - where the fact came from, stamped on every record it writes
- Routing - which register, or registers, it feeds
Because these properties live on the ingest group rather than scattered across individual writes, a fact’s origin and the rules that approved it are never ambiguous after the fact.
One register, several ingest groups
Section titled “One register, several ingest groups”A register can be filled by more than one ingest group. A register has one owner ingest group - the primary source, which sets the shared rules other contributors must agree to - and can have any number of contributor ingest groups layering additional facts on top. A document-extraction pipeline can, for instance, backfill a register that a structured form submission normally owns. When you ask for that register, you see facts from every ingest group that feeds it, not just the owner.
Next steps
Section titled “Next steps”- Registers - the product an ingest group fills
- Connectors - the systems most ingest groups read from
- Agents - producer agents write to memory the same way an ingest group does
Frequently asked questions
- What is an ingest group in Demiton?
- An ingest group is the producer/transport axis of Civil Memory - the pipe that carries a fact from a source system, a document, or a computation into memory. Every ingest group carries its own entitlement rules, provenance stamp, and routing configuration. An ingest group writes to one or more registers.
- Can more than one ingest group write to the same register?
- Yes. A register can have an owner ingest group and one or more contributor ingest groups. For example, a document-extraction ingest group can backfill a register that a form-submission ingest group primarily owns. Reads against the register see facts from every contributing ingest group.
- What happened to conduits?
- Conduit was the earlier name for this concept and has been retired as public-facing terminology. The concept is unchanged - it is now called an ingest group.
Talk to the team
Tell us what you run - your ERP, field, payroll and document systems - and we will show you the registers Demiton would fill from them, on your data, in a 30-minute call.