Inference
6 pages filed under Business objects › inference. A business object is a thing the business names and handles, with its attributes and its lifecycle.
| Business object | Lifecycle | First line | Links |
|---|---|---|---|
| Candidate | proposed, accepted, rejected | Something the build proposes without asserting it, listed under candidates of the model for a person to settle: a recurring expression without a note, with its score, counts and contexts, which becomes a keyword page above the publication threshold; a schema an imported contract names, offered as an object without a link; a pair of resources scored as twins without reaching the merge threshold. A decision on a candidate goes to the lock file of the configuration repository, never into a source. | 69 |
| Entity | typed, linked, rendered | A node of the model: a note recognised by the type cascade, or a keyword that crossed the publication threshold without a note. An entity has an identifier derived from its source and path, a type with the origin of that decision, a title, aliases, an application, a domain, a locale, its declared attributes and its source with path, commit and last-modified date. Every entity has a page, rendered by the entity page or the keyword page. | 179 |
| Keyword page | discovered, published, forwarded | An entity the build creates for an expression that recurs above the publication threshold without a note: a term marked as a keyword, located on the first mention of its expression, carrying its occurrences, files and score as attributes and its passages in its fragment. It has a page at keywords/<slug>, enters the search index and the alphabetical index, and is listed on the to-do page as work to do; when a note defines the expression later, the address forwards to the note's page so that a link written to it survives. | 110 |
| Link | inferred, combined, rendered | A typed relation between two entities, carrying a confidence between 0 and 1 and at least one provenance: method, file, line, section, context. When several methods produce the same source, target and relation, the confidences combine and every provenance is kept. Links are sorted canonically by source, target and relation in the model. | 189 |
| Model | built, validated, rendered | The single serialised result of a build: the build block with the tool version, timestamp, profile fingerprint and per-source commits; every entity; every link with its provenances; every finding; the term candidates and duplicate candidates; the bounded neighbourhoods. Canonically sorted, validated by a published schema, byte-identical from one build to the next on unchanged sources. The site is rendered from it without reading the sources again, and a Cypher export is provided. | 161 |
| Neighbourhood | accumulated, ranked, displayed | The entities around an entity, in two forms the model keeps apart. The bounded neighbourhood counts, per entity, the paragraphs it shares with every other, keeps the fifty best by count then by identifier, and feeds the co-occurrence links and the accompanying words of a keyword page. The displayed neighbourhood is the list of the one-hop neighbours a page shows: both ends of every link, each with the largest confidence and the relation of its most confident link, ranked by the order the profile declares for the type of the page, then by confidence, then by identifier, and cut at the configured size. Both are computed at build and written, never in the browser. | 62 |
6 inference of 6 — pagination by twenty. The Links column counts the related pages, which brings the most central inference of the journey to the top.