The file build.log.json the build (note: Build) writes next to the site (note: Site): its summary (24 passages, no note) (sources (note: Source), files, entities (note: Entity) per type (note: Type), links (note: Link) per method (28 passages, no note), keyword pages (note: Keyword) and expressions under the threshold (3 passages, no note), twin resources (note: Twin resources), the decisions of the lock applied, findings per severity (note: Severity) and per check (note: Check), the contracts imported (3 passages, no note)) and every finding, sorted by check, source (4 passages, no note), path, line and message (22 passages, no note). Its findings array (3 passages, no note) is the same as the one embedded in the model, and its only timestamp is its at field (37 passages, no note). The log is written before the verdict of build.fail_on, so a failing build still leaves it for inspection.
Build log
Properties3
- Application
- Concordance command line
- Domain
- Quality
- Status
- valid
3 declared keys. The rest of the file is free text.
See the neighbourhood map6 pages6Neighbourhood mapBuild log
Neighbourhood map Build log
Distance1 hop
67 neighbours in total, more than the map shows.
The 6 neighbourstextual equivalent
- ModelTermspecializes11
- LockTermspecializes6
- BuildTermgeneralizes13
- Emergent domainTermgeneralizes1
- FindingTermspecializes13
- DeterminismTermspecializes7
Six neighbours at most, always named. Beyond that the map teaches nothing: the list takes over.