Handbook

301-01 — Enterprise architecture

A written boundary diagram (ASCII) you can paste into design docs showing LCDL vs consumer vs gateway.

Updated

What you will build

A written boundary diagram (ASCII) you can paste into design docs showing LCDL vs consumer vs gateway.

Prerequisites

Files you will touch

None—conceptual lab.

Step 1 — Inventory components

List actors: application service, LCDL TaskRunner, OpenAI-compatible gateway, optional MCP host, browser automation (outside core).

Step 2 — Draw ASCII data flow

App -> TaskRunner -> contract validation -> chat transport -> gateway
          |                                      ^
          +---- operators / verification ---------+

Browsers, persistent chat threads, and fleet orchestration sit left or below the app—not inside forge_lcdl.

Step 3 — Cross-check Client API

Skim Client API for LcdlClient responsibilities vs raw run_task.

Expected output

Paragraph you could send to security review stating what crosses the wire (prompts, schemas, logs).

Common failures

Pitfall Risk
Assuming LCDL stores transcripts Core is stateless unless consumer persists

Verify

Explain aloud where forge-lcdl-runtime sibling would attach if used (runtime boundary).

What changed

Stakeholders share vocabulary for trust boundaries.

Next step

301-02 — Model routing and gateways.