Handbook

LCDL enterprise trust patterns

Direct, constrained, and operational. Avoid marketing claims unless backed by a verification command, schema, or test reference.

Updated

Enterprise pages must answer

  1. What responsibility does LCDL own?
  2. What remains the host application's responsibility?
  3. What can be verified in CI?
  4. What should be logged or audited?
  5. What is explicitly unsupported?

Trust components

  • Responsibility matrix (LCDL vs host).
  • Data-handling and secret-handling callouts.
  • Failure-mode accordion or expandable tiles.
  • Verification command blocks.
  • Evidence checklist (what to archive for audits).
  • Operational runbook cross-links.

Tone

Direct, constrained, and operational. Avoid marketing claims unless backed by a verification command, schema, or test reference.