A versioned (4 passages, no note) file in the configuration repository (note: Configuration repository), concordance.lock.yaml, named by the lock key (46 passages, no note) of the configuration, that records human decisions: accepted and rejected links, merged and separated twin resources, rejected candidate expressions, promoted emergent domains. The build reads it, validates it against the published lock schema and stops on a missing or invalid file as on a configuration error. It applies the rejected terms, compared on the normalised form of the language pack, so that a rejected expression has no candidate, no finding, no keyword page and no mark in the text, and the merged and separated pairs, a merged pair grouped under the criterion lock file whatever its score, a separated pair never reported, and the domains, a note the proposal reached filed under the domain of the integrator's choice unless a declaration files it already. The links are recorded, not read. The build log counts the decisions (62 passages, no note) applied. Nothing is ever written into a knowledge repository (note: Knowledge repository).
Lock
Properties3
- Application
- Concordance command line
- Domain
- Ingestion
- Status
- valid
3 declared keys. The rest of the file is free text.
See the neighbourhood map6 pages6Neighbourhood mapLock
Neighbourhood map Lock
Distance1 hop
82 neighbours in total, more than the map shows.
The 6 neighbourstextual equivalent
- LinkTermspecializes9
- Candidate expressionTermspecializes4
- KeywordTermspecializes8
- ConfigurationTermspecializes11
- Configuration repositoryTermgeneralizes3
- BuildTermspecializes9
Six neighbours at most, always named. Beyond that the map teaches nothing: the list takes over.