Why "why did our infra costs jump in Q2?" doesn't fit a graph

Description and use

The article explains how ctxloom replaces fixed execution graphs with reactive artifacts, enabling dynamic handling of infra cost queries without hidden branching, while ensuring reproducibility and auditability.

Problem

Answering questions like "Why did our infra costs jump in Q2?" requires multiple heterogeneous data sources and computations, but typical graph frameworks force pre‑defined paths or hidden branching, making the workflow brittle and opaque.

Outcome

The ctxloom approach eliminates the need for a fixed execution graph, enabling dynamic, reproducible, and auditable workflows that separate deterministic calculations from LLM reasoning.

Workflow

• Receive Question
• search_docs produces SourceRef
• search_table produces Spreadsheet
• resolver produces TypedDoc
• evidence_builder produces Evidence
• table_resolver produces Spreadsheet
• calculator produces Calculation
• verifier produces Claim
• answer_builder consumes Claim, Calculation, Evidence to produce Answer

Evidence

ctxloom has no execution graph — it has artifacts (typed, versioned objects) and agents that react to their appearance.

Source

The same question goes through text search, table search, a deterministic calculation, and verification — in a single run.

Source