Architectural decision
Website is a projection
Public presentation reuses canonical contexts.
Before · Conflated concepts
WebsitePublicationProfileProduction
After · Explicit boundaries
Relationships
- Production has public projection Website
- Profile has public projection Website
- Website is configured for Publication
Problem and decision
Publishing application records directly risks exposing private context.
Build an explicit public projection and independent publication configuration.
Alternatives considered
- Duplicate identity into an unrelated website product
- Expose private application records directly
Tradeoffs and consequences
Projection and publication versions require their own maintenance.
A website can change presentation without redefining private ownership.
Related architecture
Related workflows
Current architectural direction; this record does not establish production release.