Ingestion
4 pages filed under Business objects › ingestion. A business object is a thing the business names and handles, with its attributes and its lifecycle.
| Business object | Lifecycle | First line | Links |
|---|---|---|---|
| Build | started, ingested, inferred, checked, written | One run of the build pipeline on a configuration: the sources it ingested with their commits, the model and the build log it wrote, and its summary. The summary counts the entities per type, the links per method, the keyword pages published and the expressions under the threshold, the twin resources reconciled, the decisions of the lock file applied, the domains the neighbourhood suggests with their pivots, and the findings per severity and per check; the log carries the same figures, the contracts imported and every finding. The only dated part of a build is its timestamp, taken from the injected clock, so that two builds on unchanged sources are byte-identical. Next to the model and the log, a build writes one fragment per entity, the rendered note or the passages of a keyword page, and the site itself; concordance render rebuilds the site from the model and the fragments without touching a source. A build fails only according to build.fail_on, after its model, its log, its fragments and its site are written. | 229 |
| Representation | read, converted, grouped | One of the files an entity is made of: its note, a slide deck, the PDF produced from it, a transcript, the contract an operation was imported from. A note alone has one; twin resources merged into one entity carry several, each with its path, its kind and, for a document, its extracted text position by position, and the page shows them one after the other. An imported operation matched by a note lists the contract as a representation next to the note's own file. | 63 |
| Resource | ingested, converted, reconciled | A file read from a source: a markdown note, a document, a slide deck, a transcript, a contract. A resource carries its path, commit and date, and, for documents, the metadata extracted by a reader, the PDF produced by a converter and the text extracted from that PDF, page by page, or the cues of a transcript with their timecodes; an office document never gives its text any other way, so that one extraction path serves every format. Twin resources of the same document are grouped into one entity with several representations when their reconciliation score is high enough. | 70 |
| Source | declared, fetched, ingested | A repository or a local folder declared in sources: of the configuration: a unique name that prefixes every identifier from it, a git URL cloned at depth 1 on its ref or a local path, its locale, its default application, whether it is a glossary, and its typing rules. The build fetches it into the pipeline cache without ever writing into it, records the commit of the ingestion in the build block of the model, and goes on without it when it cannot be reached. Every resource and every entity knows its source. | 173 |
4 ingestion of 4 — pagination by twenty. The Links column counts the related pages, which brings the most central ingestion of the journey to the top.