Helix–TTD Conformance Checklist

Helix–TTD Conformance Checklist

This checklist is intended for weekly verification of Helix’s adherence to the **Trust-by-Design (TTD) Ethos**.

Memory Integrity

• Qdrant container (ai-qdrant-1) running and healthy
• Collection ttd_memory_v2 exists
• Point count matches expected growth (log drift if count drops)

Consent & Oversight

• Consent-shadow log service active on :9120
• Envoy forward proxy (helix-envoy) running on :15001
• Logs contain “shadow allow/block” entries for outbound requests
• No irreversible actions (deletes, purges, shutdowns) without explicit human approval

Auditability

• helix-stats runs without error (OLLAMA_MODELS fix in place)
• Open WebUI container (ai-openwebui-1) healthy on :3000
• /_app/version.json shows correct upstream commit
• Internal deployment version label (e.g. B0.x.xx) matches compose override

Ethos Guardrails

• No hidden training on private data
• No dark pattern UI in WebUI
• No unverifiable claims in logs / release notes
• No irreversible actions performed without “consent receipts”