concordance.lock.yaml, in the configuration repository (note: Configuration repository), records what a person decided and the tool must not reconsider: accepted and rejected (8 passages, no note) links (note: Link), merged and separated twin resources (note: Twin resources), rejected term (4 passages, no note) candidates. The build (note: Build) reads the file the lock key (46 passages, no note) names, validates (10 passages, no note) it against its schema (31 passages, no note) and stops on a missing or invalid (5 passages, no note) one, as on a configuration (note: Configuration) error (29 passages, no note): a decision (62 passages, no note) is never dropped in silence. The keyword discovery (3 passages, no note) honours rejected_terms, compared on the normalised form (note: Comparison form) of the language pack (note: Language pack), and the reconciliation of twin resources the merged and separated pairs (47 passages, no note), whatever the score (note: Confidence); the links are recorded for a later version, and the configuration validator (4 passages, no note) says so. The build log (note: Build log) counts the decisions applied. Nothing is ever written into a knowledge repository (note: Knowledge repository), and a decision lives next to the configuration, versioned (4 passages, no note), reviewed like any change.
Lock file for human decisions
Decision · Acceptedspecs/decisions/ingestion/lock-file-for-human-decisions
Properties
- Status
- Accepted
- Decided on
2 keys: the status and the date are authoritative.
See the neighbourhood map6 pages6Neighbourhood mapLock file for human decisions
Neighbourhood map Lock file for human decisions
Distance1 hop
17 neighbours in total, more than the map shows.
The 6 neighbourstextual equivalent
- Build pipelineProcessaffects1
- CandidateBusiness objectaffects1
- LinkBusiness objectaffects1
- BuildBusiness objectaffects1
- LinkTermaffects1
- LinkTermaffects1
Six neighbours at most, always named. Beyond that the map teaches nothing: the list takes over.