Handbook

Tutorial 301 — Operating LCDL in enterprise environments

Architects and operators wiring LCDL into CI/CD, Cursor/MCP topologies, and governed gateways—offline gates first, live Granite opt-in.

Updated

Audience

Architects and operators wiring LCDL into CI/CD, Cursor/MCP topologies, and governed gateways—offline gates first, live Granite opt-in.

Enterprise LCDL operation lanes

How offline CI gates, optional live Granite, and MCP Cursor tooling partition governed LCDL work in enterprise environments.

  1. Offline CI ─ audits pytest fake_chatDefault path where audits, pytest, and fake_chat block regressions without live credentials.
  2. Optional live ─ Granite credentials isolated markersLive Granite stays opt-in with isolated credentials and explicit markers.
  3. MCP Cursor ─ IDE tool bridge owned by consumer policyMCP connects Cursor to LCDL tools under consumer-owned policy boundaries.

Prerequisites

Final artifact

Documented answers for:

  • Where LCDL ends and consumer/browser/fleet begins
  • How fake vs live transport maps to CI jobs
  • Which agent docs to hand new Cursor users
  • Which commands block regressions before deploy

Lesson table

Step Page Focus
1 Enterprise architecture Boundaries + diagrams (ASCII)
2 Model routing and gateways Profiles, timeouts, optional live
3 MCP and Cursor Client vs sidecar topology
4 Benchmarks and CI Audits + pytest defaults
5 Production readiness Go/no-go checklist pointers

Hubs

Enterprise · Agents · Benchmarks

Next steps after 301