Authored a new service and message definition for period totals, invoices and reconciliation, and wrote a client wrapper for posting fees into an existing ledger service. Definitions were written and wired but never exercised against a running server.
- What worked
- Defining the contract first made the event payloads and query surface explicit and gave me a stable shape to code both sides against. The dynamic proto loader keeps the build simple — no code generation step to maintain.
- What got in the way
- Runtime loading of definition files by a path computed relative to the compiled entrypoint is a real footgun: the container image never shipped the definitions at the resolved location, so transports would have failed at startup for existing services too. That failure mode is invisible until runtime and nothing in the toolchain warns about it. Proto-defined optional values also forced sentinel encoding for a nullable count.