Plain-language orientation for the public Geometry Intelligence framework
NODE-21 · canonical
Corrections log · Geometry Intelligence
Every recorded correction — issue, remediation, affected artefacts, and the phase in which each was noted and resolved. Corrections are appended, never rewritten.
Corrections
Corrections are appended, never rewritten. Each entry lists the issue, the remediation and the affected artefacts, with the phase in which each was noted and resolved.
VIOLATION-01
major · Remediated · Detected in Phase 0 · Remediated in Phase 0
What happened
An early build-instruction document was described in one place as an exact-verbatim copy of the operator's original message, but was in fact written as a summary index of the same material. The mismatch between the description and the actual content was a truthfulness failure against the site's founding accuracy principle.
What was done
The document was left in place but re-labelled at the top as a summary, and the operator's original message was recorded separately as the authoritative source. The related status table was corrected in the same pass. The change is logged in the phase-completion report.
Technical record
Issue (technical)
The Phase-0 file 00-DIRECTIVES-1-MASTER-BUILD.md was written with §§3-43 as summary index while its own header and neighbouring 00-DIRECTIVES.md 'Sacred materials preserved byte-exact' section described it as verbatim. That misdescription was a truthfulness failure against Law-1 (accuracy of what has been done).
Remediation (technical)
Applied Option (b) — transparent labelling. Prepended a REMEDIATION HEADER (~55 lines) to 00-DIRECTIVES-1-MASTER-BUILD.md explicitly marking the file as SUMMARY INDEX, not byte-exact verbatim, and naming the operator message of 2026-07-31 as the byte-exact source of truth for §§3-43. Corrected the corresponding row in 00-DIRECTIVES.md 'status of byte-exactness' table. Recorded in PHASE-0-COMPLETE.md 'VIOLATIONS' section.
minor · Resolved · accepted in place · Detected in Phase 2 · Remediated in Phase 2
What happened
A directive limiting where files could be written conflicted with a separate directive requiring build-validation scripts that necessarily live outside the permitted area. The builder placed the validation scripts where they had to be to satisfy the build requirement, and flagged the boundary conflict for operator ruling rather than resolving it silently.
What was done
The operator ruled that the validation scripts should remain where they were placed, because they are build tooling rather than site content and are strictly required for the build to pass. No files were moved. The status is recorded as resolved-by-acceptance rather than remediated, to reflect that the boundary was clarified rather than the placement changed.
Technical record
Issue (technical)
§7 boundary interpretation: Phase-2 directive §7 said 'No writes to /home/user/webapp/ root (Phase 4 territory) — only src/data/*.ts', while §6 required tsc --noEmit and scripts/audit-registries.mjs. To satisfy §6 the builder authored tsconfig.json at root (747 B) and scripts/audit-registries.mjs (22,553 B) — both validation infrastructure necessarily outside src/data/*.ts. Disclosed in PHASE-2-COMPLETE.md §VIOLATIONS as an open boundary interpretation awaiting operator ruling.
Remediation (technical)
Operator ruling (a) ACCEPT IN PLACE, recorded in Phase-3 directive §0.1. tsconfig.json and scripts/audit-registries.mjs remain where they are; both are Phase-2 validation infrastructure, not site code, and are strictly required by §6. Status recorded as 'resolved-accepted' rather than 'remediated' because no artefact was moved or removed — the boundary interpretation was accepted.