Methods and recipes: what a request brings along, and how a thing is done
here. canon/ says what a module should be and why; these say what to do,
in what order, when someone asks for one.
| Doc | Answers | Status |
|---|---|---|
00-building-a-module.md | I was asked for a new module; what does that bring along, in what order, and where do the five named modules already stand | written 2026-08-17 |
01-consuming-a-module.md | I was asked to call module X from our app; identity, tenant, envelope, reading back, what stays app-side | written 2026-08-17 |
02-deploying-a-module.md | repo to running, on GCP first, with a Render variant | written 2026-08-18 |
03-upgrading-services-api.md | the worked migration of the first real module, parity ledger first | written 2026-08-17 |
04-identity-recipe.md | the auth blueprint as a checklist: new module, existing service, calling app, direct caller | written 2026-08-17 |
05-authoring-an-agentic-module.md | the seed doc the owner asked for with V1: what is factored, the six layers of an agentic payload, options as recipes per module, prompts, evals, bespoke; vocabulary naming test two (passed, one friction on prompts) | written 2026-08-18 |