docs: audit is a living document; separate design sins from contained coding slips

This commit is contained in:
2026-08-21 16:50:43 -05:00
parent 86b3f3f607
commit 1ef9f3917d
+24 -6
View File
@@ -1,12 +1,26 @@
# Neuron Fork — Process Audit Log
**Date:** 2026-08-21
**Date:** 2026-08-21 (initial entry)
**Scope:** Everything unusual, odd, or dangerous observed while forking
`anomalyco/opencode``neuron-technologies/neuron`, including mistakes made
during our own surgery.
`anomalyco/opencode``neuron-technologies/neuron`.
## This is a living document
Every future surgery on this codebase appends its findings and its errors
here. Two hard rules:
1. **Design sins and coding slips are logged in different sections.** A design
sin is a deliberate decision with dangerous defaults that ships to users.
A coding slip is an implementation error. They get different scrutiny and
different fixes — conflating them hides both.
2. **Containment is always recorded.** For every slip: which gate caught it,
and whether it ever reached the remote. The containment column is the point
of the log — it proves (or disproves) that our gates work.
---
## Part 1: Dangerous-by-design findings in upstream code
### 1.1 Network-callable self-upgrade endpoint (HIGH)
@@ -90,10 +104,14 @@ with repo housekeeping files.
---
## Part 3: Our own surgery incidents (honest record)
## Part 3: Error log — all contained pre-push
These are mistakes **we** made during the fork process. Logged because a fork
audit that only blames upstream is propaganda.
Implementation slips made during the fork surgery. Categorically distinct
from Part 1: those were design decisions that shipped; these are coding
errors that never reached the remote. Every one was killed locally by a gate
(typecheck, test suite, or pre-push hook) before a commit left the machine.
The lesson is not "everyone makes mistakes" — it is that the gates caught
what invisible-to-upstream rot never could.
| # | Incident | Cause | Caught by | Severity |
|---|----------|-------|-----------|----------|