The local (27 passages, no note) lint (note: Lint) says the same thing as the build (note: Build). For the checks the linter (4 passages, no note) computes in --scope repo, listed as LOCAL_CHECKS by the lint package (3 passages, no note) (E-ENCODING, E-FM-INVALID, E-ID-DUP, E-ID-INVALID, E-LINK-BROKEN), concordance lint on a repository (note: Knowledge repository) and concordance build on a configuration (note: Configuration) that declares it as a source (note: Source) produce the same findings: same check, source (4 passages, no note), path, line and entity (note: Entity), same severity (note: Severity), message (22 passages, no note) and remediation (note: Remediation). The build reports (3 passages, no note) more, never less: the checks (note: Check) that need the whole model only exist there.
The rule (note: Rule) holds because both sides call the same functions to list the files of a repository (the globs (21 passages, no note) privacy.exclude and the repository's own exclude name and the files git ignores (4 passages, no note) are left out on both sides), read a note (note: Note), derive its identifier (note: Identifier) and resolve its links (note: Link), and take severities and remediations from the same catalogue (12 passages, no note). A parity test in the repository copies each fixture (note: Golden corpus) corpus (note: Corpus), the golden ones and the faulty ones, lints every source of the copy and builds the same copy, then compares the findings (note: Finding) of the local checks (note: Local check) one by one, and checks that the excluded folder and the git (24 passages, no note)-ignored file of the faulty corpora, which hold faults, are report (47 passages, no note)ed by neither side; any divergence fails continuous integration. The JSON report of the linter (note: Linter) carries scope and checks so that a forge report (note: Forge report) states (36 passages, no note) which checks the guarantee (3 passages, no note) covers. The getting started guide and the architecture guide describe it.