codebase-design

Forking a third-party OCaml package in an unpac workspace — vendor it with unpac, patch it in edit sessions, and carry the fork obligations when it graduates…

Create a new OCaml package with the house layout: dune-project metadata, lib/test/fuzz structure, standard dotfiles, and pre-commit hooks.

Runs the merlint linter as the final code review gate on any OCaml change.

Types-first test-driven development for OCaml.

Managing vendored dependencies as git branches with unpac — vendor opam packages or git repos with full history, patch them in edit sessions, merge them into…

Module shape for OCaml network/wire protocol libraries (SSH, TLS, HTTP/2, QUIC, BGP, IMAP, AMQP, MQTT, NATS, WebSocket, OAuth, CFDP, COSE).

Diagnosis loop for hard bugs and performance regressions.

Shared vocabulary for designing deep modules.

Build a throwaway prototype to answer a design question.

Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.

Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.

Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker…