Enterprise Architecture Checklist · The Book

Is the service boundary clear?
Does the service own a coherent business capability?
Are persistent business concepts represented as model declarations?
Are public request and response shapes represented as named type declarations?
Are business workflows implemented as action declarations instead of route-heavy logic?
Are transaction boundaries explicit?
Are protected routes authenticated?
Are sensitive and tenant-scoped models governed by policy?
Are imports intentional and directionally clean?
Has carrier check passed?
Has carrier build --target node passed before handoff?
Has OpenAPI been regenerated when API shape changed?
Have migrations been generated and reviewed when schema changed?
Is .carrier/manifest.json usable as governance evidence?