Handbook
Enterprise and operations
These pages document how to run LCDL responsibly in shared environments—not marketing copy.
Updated
Responsibility snapshot
| LCDL provides | Host owns |
|---|---|
| Contracts, runner, operators, parsing primitives | Credentials, secrets, model gateways |
| Docs + verification commands | Data custody, retention, regional rules |
| MCP patterns documented in-repo | Deployment topology, SLAs, observability |
Risk and resilience
- Threat model — assets, boundaries, threats, controls.
- Data handling — transit, retention, redaction.
- Incident response — containment + triage.
Architecture and lifecycle
- Architecture — system boundaries.
- Library vs runtime boundary — what ships here vs
forge-lcdl-runtimevs deployment hosts. - Deployment topologies — service, batch, MCP patterns.
- API and contract compatibility — breaking vs non-breaking changes.
- Task maturity matrix — promoting tasks safely.
Security and governance
Operations
- Operations — CI-style checks and handbook builds.
- Operational runbook — day-2 checks and rollback cues.
- Support boundaries
- Production readiness checklist
Releases
Deep dives
- Known limitations
- Benchmarks — offline fake transport defaults; optional live gates.
- Cheap model operating guide
- Alpha roadmap
- Dogfooding
Tutorials and handbook routing
- 301 — Operating LCDL in enterprise environments
- Governance and release: Release checklist, CONTRIBUTING.md.