Handbook

ADR-0011: Intelligence Comprehension Service (ICS)

Accepted — ICS PDCA program (I00–I15).

Updated

Status

Accepted — ICS PDCA program (I00–I15).

Context

Forge Intelligence ships as a library with packs, orchestration, and session dual-wiki. Consumers (agents, KA, Cockpit, product bots) would otherwise embed FI packs and LCDL/lmeta directly, duplicating runtime policy, allowlists, and secrets handling.

CDP manager exposes POST /v1/flows/run for automation lmeta — not problem-class comprehension. FI Studio (:9791) is a local workbench, not a Granite production spine.

Decision

  1. ICS (forge-intelligence/runtime/) is the Granite-resident HTTP service that embeds FI orchestration and one in-process LCDL substrate. Clients call https://ics.forgedc.net/v1/comprehend — they do not import pack lmeta or FI-local contracts.
  2. Public URL — ics.forgedc.net via Cloudflare tunnel to Fleet container on Granite (same pattern as matrix.forgedc.net).
  3. No ForgeRun SoR — ICS returns session attach payloads; Lenses remains authoritative.
  4. No CDP merge — automation flows stay on forge-cdp-manager; comprehension stays on ICS.
  5. Platform publishes hub + reference-architecture section; canonical API docs live in forge-intelligence/docs/comprehension/.
  6. Schemas — forge.intelligence.comprehend_request.v1 / comprehend_response.v1 in forge-intelligence/schemas/; Platform references samples.

Consequences

  • Single upgrade path for pack bundles on Granite.
  • Laptop is not on the comprehension runtime path.
  • Bot-platform work (rooms, Versona bots, product bots) remains separate PDCAs (see FI OUT-OF-SCOPE-FOLLOW-ONS.md).
  • ADR-0009 — FI reasoning economy
  • ADR-0010 — channel agents (future ICS clients)
  • forge-intelligence/docs/comprehension/overview.md