🚦 Operations

Operations are split between the app service and this public Quartz wiki.

• app access since D-169 (2026-09-26):

  • public without a forced login; anonymous visitors share the non-admin public identity
  • optional Authelia SSO supplies signed-in identity/groups through trusted nginx headers
  • admins or pwiz-admins enables admin routes; anonymous and signed-in non-admin visitors receive 403 on those routes
  • Settings → Admin sign-in opens login; ordinary signed-in libraries are scoped to that identity
  • older all-public/all-gated vhosts remain historical rollback anchors, not current installation recipes

• wiki access:

  • public because it is documentation and audit evidence

• pages:

  • deploy:
    • systemd service shape
    • nginx app and wiki routing
    • public anonymous fallback and optional-SSO identity boundary
    • certificate process
  • wiki-publish:
    • required wiki files
    • content rules
    • publish command order
  • 🔒 Private runbook (login):
    • JSX proof
    • build and source residue checks
    • API and omp bridge smokes
    • browser and open-access identity checks

Public troubleshooting

• Missing admin tabs or HTTP 403: sign in from Settings and check admins/pwiz-admins membership; enabling developer tools alone does not grant a group.
• Seed wizard cannot be edited: duplicate it, then edit the owned copy. See settings.
• Library appears shared: anonymous visitors all use public; sign in for your own effective-identity library and do not store confidential content anonymously.
• Generation is slow or fails: preserve the visible error; admins can inspect pipeline-timings to distinguish queue, attempts and repair. Role labels are not three independent agents or a measured completion percentage.
• Code rain is a synthetic visualization, not reasoning. Only Live mode requests real thought chunks.
• Successful text/image AI calls are stored in llm_logs (admin-only), with no implemented automatic TTL. See api > Logging, retention and public storage before submitting sensitive content.
• Privileged operational checks are at Private verification (login required), not the removed public /operations/verification route.

Operator rules

• do not publish completion claims before source and live checks agree
• keep machine-specific absolute home paths out of wiki pages except the load-bearing gated-vhost restore path
• keep loopback addresses out of published prose and examples
• use placeholders such as ${APP_ROOT}, ${WIKI_ROOT}, ${BACKEND_ORIGIN}, and ${BUN} in public snippets
• treat inherited archive claims as evidence, not truth