Forge Intelligence

Handbook

Product boundaries

Forge Intelligence owns problem-class policy and session telemetry shapes. It does not own execution, UI, or the ForgeRun system of record.

Updated

Boundary principle

Forge Intelligence owns problem-class policy and session telemetry shapes. It does not own execution, UI, or the ForgeRun system of record.

Product Owns Does not own
Forge Intelligence problem-class catalog, pack policies, per-domain lmeta libraries, session dual-wiki, v1 attach schemas LCDL executor, Fleet jobs, Lenses SoR, agent memory, doc hydration
LCDL governed LLM tasks, operators, FlowExecutor problem-class catalog, product policy
Platform ecosystem ADRs, cross-product contracts (references fi schemas) pack bodies, session storage
Lenses run spine, approvals, evidence review intelligence pack runtime

Critical rules

  1. No second LCDL runtime — packs compose existing tasks and lmeta primitives; node_executor is an adapter (ADR-0002).
  2. No ForgeRun SoR — sessions attach to runs via evidence; Lenses remains authoritative.
  3. No doc hydration — claim registries stay in Platform doc-hydration design.
  4. Closed-set LLM — break-in actions must be enumerated in pack policy.
  5. FI-local contracts — intelligence I/O contracts live under lcdl/contracts/ in fi; forge-lcdl owns generic atoms only.

Consumes

  • forge-lcdl tasks (automation_situation_arbitrate, routing helpers)
  • Platform resource-honesty and worker-ladder policy (narrative alignment)

Emits

  • route_trace.v1, token_ledger.v1, ambiguity_assessment.v1 (session machine JSON)
  • Generated human session reports (derived from M)

Ecosystem placement

fp (contracts/ADRs) ──references──> fi (schemas + packs)
fi ──composes──> lcdl (tasks/flows)
fi ──attaches──> fl (evidence on ForgeRun)