01 / Start the kernel
contract -> generator -> service edge -> runtime moduleNucleuskit is a compact Go toolkit for building backend systems from explicit contracts. The point is not to hide the architecture. The point is to make the service boundary obvious, generated code predictable, and verification close to the edge where systems actually break.
02 / Flip the module deck
| Surface | Repository | Signal |
|---|---|---|
| kernel | nucleus | coordinates generation, evolution, verification |
| contract | contract | keeps service intent explicit |
| core | core | holds runtime primitives |
| http | http | maps contracts to HTTP edges |
| grpc | grpc | maps contracts to gRPC edges |
| worker | worker | runs async/background service work |
03 / Inspect the design rule
If the contract changes, the generated surface should make the blast radius visible.- Prefer explicit service boundaries over clever glue.
- Keep generated code readable enough to debug without ceremony.
- Let modules stay small, named, and replaceable.
- Put verification near the contract, not at the end of the story.