Public milestones recorded from the same database that powers Crownvo Docs. Internal incidents, deployment details, and due-diligence notes remain protected in the platform documentation system.
2 recorded updates
architecturerecorded
Documentation history moved into the product database
Crownvo Docs gained a database-backed activity timeline for features, releases, CI, deployments, incidents, and decisions, with public and internal visibility controls.
crownvo-apiproduction
Capabilities
structured activity events
idempotent history seeding
public history reader
platform-protected internal records
audit logging
architecturerecorded
Product surfaces moved toward independent repositories
Status, docs, marketing, account, product dashboards, and other surfaces were prepared for independent GitHub and Coolify deployments while sharing the API contract.
crownvo-web-statusproduction
Principles
one deployable surface per repository where useful
database and auth remain API-owned
Coolify resources build from the matching repository and branch
