Handbook

Data handling

Forge LCDL does not introduce durable storage for prompts, completions, or chat sessions. Anything persisted is done by consumer code (your service, notebooks, or runtime sibling packages).

Updated

Storage posture (core library)

Forge LCDL does not introduce durable storage for prompts, completions, or chat sessions. Anything persisted is done by consumer code (your service, notebooks, or runtime sibling packages).

Data in motion

Stage Typical contents Notes
Task input dict Business payloads, URLs, chunk text Treat as sensitive per domain
Chat requests Serialized messages to gateway May cross WAN
Chat responses Model JSON Validate before acting
Logs (consumer) Retry metadata, HTTP codes Avoid logging secrets

Data-in-motion through LCDL

How task payloads cross chat transport and land in consumer-owned logs without LCDL durable storage by default.

  1. Task payloadBusiness input dict enters the governed task layer.
  2. chat request → gateway → chat responseSerialized messages traverse the configured chat gateway.
  3. validation → consumer logs / sinksResponses are validated before your service logs or routes them.
  4. (LCDL stores none by default)Core library adds no durable prompt or completion storage.

What must not be committed

  • .env, *.pem, live certification-llm.local.env style files
  • Firebase tokens, internal gateway URLs tied to production
  • Captured production payloads in examples or tests

Use .gitignore + pre-commit review for notebooks.

Redaction guidance

When filing bugs:

  • Replace bearer tokens with REDACTED
  • Trim prompts to minimal repro snippets
  • Prefer fake_chat traces over live transcripts