Go reaches PostgreSQL as daemon through daemon.* helpers; sign-out and liveness gaps named
- The Go process connects as daemon, not apibot, and reaches api.* only
through SECURITY DEFINER helpers in schema daemon (as AppServer does
through daemon.fetch). apibot remains as the transitional path until
the helpers ship in db-platform.
- Sign-out has no v2 replacement yet: AuthServer has no /oauth2/revoke;
AppServer cannot be switched off before it exists.
- /ping: end-to-end liveness is a health resource of the Go process
through the gateway, sent without credentials; two new traps.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
d7f1b41
Development strategy and the v1 → v2 migration procedure
Two pages for AI agents and engineers, in English: how an application on
Apostol CRM is built now that business logic lives in the Go layer over
db-platform (three layers, the decision table for placing logic, the
shape of a project, stages 1 / 1.5 / 2 / Platform 2.0, rules for agents,
anti-patterns), and the procedure for moving an existing application from
/api/v1 to /api/v2 (inventory, shape translation, packages, parity,
switching consumers, retiring rest.*, traps). Home links both.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01AZjvUCCNN3QS94DGAnPD2q
cdcb940