Architecture
These pages explain why Viking separates infrastructure, private editing, publication and public file delivery. Read the overview first, then the component involved in your change. The reference contracts specify shared fields/names, while operations gives runnable procedures. Historical proposals are under planning, not a second description of current behaviour.
Files and folders in this directory
| File or folder | Detailed scope |
|---|---|
| README.md | Architecture reading path and complete direct-file index. |
| operator.md | Website reconciliation, auth routing, resource ownership/retention, RBAC, status and namespace/realm boundaries. |
| cms.md | Browser/source authority, backend auth/CSRF layers, single-replica constraints, security and asynchronous status writes. |
| webserver.md | Read-only static delivery, independent scaling, supported versus proposed HTTP features and isolation/performance boundaries. |
| publisher.md | Snapshot/render/durability/activation ordering, history recovery, late-failure semantics, retention, rollback and concurrency. |
| security.md | Trust boundaries, sessions/tokens/CSRF, sanitization, container/init privileges and current network/supply-chain limitations. |