Audit
Read-only inspection established the real failure modes before source changes.
FDE CASE STUDYPORTABILITY · GOVERNANCE · EVIDENCE
Make the system
describe itself
before changing it.
A hardcoded repository-root assumption became a bounded delivery program: audit, contract, implementation, adversarial review, correction, negative control, independent acceptance, controlled integration, and claims reconciliation.
15path sites converted
4resolver scenarios
39historical commits reconciled
0runtime gates changed
01 / CLIENT PROBLEM
The visible defect was a path string. The delivery risk was systemic.
Multiple modules inferred “where is this checkout?” from one home-directory convention. A launcher combined a fixed checkout assumption with a relative Python import. A relocated clone could fail, import from the wrong tree, or redirect file access only after a normally closed write gate opened.
For a buyer, the work was not a mechanical search-and-replace. It crossed configuration, imports, launchers, safety gates, historical branches, test design, security handling, and the language used to describe success.
OPERATING CONSTRAINTNothing becomes “proven” merely because something green happened.
Fail-closed defaults preservedNo deployment or service changesDisposable checkouts onlyNo durable ledger write
02 / DELIVERY SEQUENCE
Each pass consumed prior evidence
and produced a narrower artifact.
Contract
Two tickets bounded the resolver and the companion launcher repair.
Implement
One fail-safe root resolver replaced distributed path guesses across 15 sites.
Challenge
Review separated passing syntax from the actual relocation property.
Correct
A cwd-dependent launcher fix was exposed, repaired, and preserved in history.
Discriminate
The pre-fix bytes failed under the same conditions that the correction passed.
Integrate
History convergence, portability, and claims reconciliation landed in order.
Bound
Unexercised runtime and data behavior remained explicitly unverified.
03 / FALSE-GREEN CORRECTION
The first fix passed from the expected directory—and still failed the ticket.
The initial launcher repair inserted a relative core path. A first attempted negative control also changed into the relocated checkout, accidentally making that relative path valid. Review discarded the result.
PRE-FIX CONTROLModuleNotFoundError
Executed from an unrelated working directory against relocated bytes.
CORRECTED PROPERTYRelocated import resolves
The launcher derives its directory from its own file and passes an absolute core path.
The control discriminates the cwd-relative import defect. It does not prove the write-enabled sealing path, which was deliberately not invoked.
04 / EVIDENCE LADDER
Implemented
A canonical HOUSE_ROOT resolver and root-relative SCRIBE launcher exist in reviewed commits.
Verified
Four resolver scenarios, relocated import, and a discriminating negative control passed.
Accepted
Independent reviews issued bounded verdicts and retained the open evidence gaps.
Integrated
Three genuine merge commits preserve convergence, correction, and claim discipline.
Published
This page is the first public artifact; the underlying evidence repository remains private.
05 / RESULT
A narrower result is a more credible result.
A single fail-safe contract replaced distributed assumptions.
Defect discovery and repair remain legible in history.
Convergence, portability, and claim discipline integrated in order.
Integration did not silently become deployment authority.
06 / EXPLICIT NON-COVERAGE
This work does not establish:
- Gate-open scribe_seal() behavior
- Direct admin-push denial
- Runtime, deployment, or service health
- Hermes registration or tool serving
- Database identity, contents, or correctness
- LadybugDB behavior or graph integration
- Memory scoring, retrieval, or production mode
- Full-machine portability or bootstrap completeness
07 / WHY IT MATTERS
The value was uncertainty reduced—not lines changed.
This sequence demonstrates the work an FDE performs in a brownfield environment: isolate an implicit operational assumption, convert it into a testable contract, protect live state, challenge the test, repair the repair, reconcile history, and communicate only what the evidence supports.
“A green test inherits only the scope of what it asserts.”
08 / CONTACTBuild carefully.
Build carefully.
Ship honestly.
Available for bounded field-engineering engagements involving local-first agents, brownfield integration, portability, governance, and evidence-led delivery.
hello@dopenoun.dev ↗