An application repository should describe the product, not quietly become the control plane for an entire server. TotalInfra owns the host-specific layer: ingress, shared data services, network wiring, durable storage, identity delivery, release orchestration, and recovery. Individual projects remain independently understandable while the platform keeps deployment behavior consistent.

The platform also provides a lifecycle rather than a single deploy button. A project establishes repository identity, defines its service and persistence contract, enters a reviewed deployment lane, adopts the appropriate human or machine identity flow, and produces readiness evidence before appearing in the broader application catalog.

A canonical application registry ties those concerns together without exposing every field to every consumer. Public presentation, deployment ownership, identity delivery, privileged entitlement, and readiness evidence are projected into separate generated views. This reduces configuration drift while preserving confidentiality boundaries.

The result is an infrastructure repository that acts as an executable platform specification. It records how services enter the host, what may receive credentials, what data must survive a release, what evidence declares a service healthy, and how the previous release remains recoverable.