← back to home · engineering log

Engineering log.

Posts about how nl2protocol works under the hood, what’s broken inside, and what the fix looks like. Architectural drift, contract gaps, design tradeoffs — the stuff that doesn’t belong on the user-facing limitations page. Written for engineers reading the project who want depth.

  1. Architectural limits we know about

    What’s broken inside the implementation: where the spec can be wrong without anyone noticing, why the verifier sometimes flags legitimate citations as fabricated, what gets overwritten when the gap-resolver applies a fix, and which limits are operational versus structural. Catalogued from a session of reading the actual code against the architectural doc.

More posts coming as the implementation evolves. Next likely topics: fixing the wells_provenance schema, what the eval set surfaced, processing the first batch of user-testing feedback.