Fluid Forge
Why Forge
Concepts
Get Started
  • Consume a Data Product
  • See it run
  • Demos
  • Local (DuckDB)
  • Source-Aligned (Postgres → DuckDB)
  • AI Forge + Data Models
  • MCP Output Port — Serve to AI Agents
  • GCP (BigQuery)
  • Snowflake Team Collaboration
  • Declarative Airflow
  • Orchestration Export
  • Jenkins CI/CD
  • Universal Pipeline
  • 11-Stage Production Pipeline
  • Catalog Forge End-to-End
CLI Reference
  • Agent Policy (concept)
  • MCP Output Port — Serve to Agents
  • MCP deep-dive
  • AI-assisted authoring
  • LLM providers & backends
  • Overview
  • Quickstart
  • Examples
  • Your own CI
  • Your own scaffolding
  • Custom validator
  • Apply hook
  • Reference
  • Overview
  • Architecture
  • GCP (BigQuery)
  • AWS (S3 + Athena)
  • Snowflake
  • Local (DuckDB)
  • Custom Providers
  • Roadmap
GitHub
Why Forge
Concepts
Get Started
  • Consume a Data Product
  • See it run
  • Demos
  • Local (DuckDB)
  • Source-Aligned (Postgres → DuckDB)
  • AI Forge + Data Models
  • MCP Output Port — Serve to AI Agents
  • GCP (BigQuery)
  • Snowflake Team Collaboration
  • Declarative Airflow
  • Orchestration Export
  • Jenkins CI/CD
  • Universal Pipeline
  • 11-Stage Production Pipeline
  • Catalog Forge End-to-End
CLI Reference
  • Agent Policy (concept)
  • MCP Output Port — Serve to Agents
  • MCP deep-dive
  • AI-assisted authoring
  • LLM providers & backends
  • Overview
  • Quickstart
  • Examples
  • Your own CI
  • Your own scaffolding
  • Custom validator
  • Apply hook
  • Reference
  • Overview
  • Architecture
  • GCP (BigQuery)
  • AWS (S3 + Athena)
  • Snowflake
  • Local (DuckDB)
  • Custom Providers
  • Roadmap
GitHub
  • Introduction

    • Home
    • Why Fluid Forge
    • Getting Started
    • Snowflake Quickstart
    • See it run
    • Forge Data Model
    • Vision & Roadmap
    • Playground
    • FAQ
  • Concepts

    • Concepts
    • Builds, Exposes, Bindings
    • What is a contract?
    • Quality, SLAs & Lineage
    • Governance & Policy
    • Agent Policy (LLM/AI governance)
    • Providers vs Platforms
    • Fluid Forge vs alternatives
  • Data Products

    • Consume a Data Product
    • Product Types — SDP, ADP, CDP
  • Walkthroughs

    • Walkthrough: Local Development
    • Source-Aligned: Postgres → DuckDB → Parquet
    • AI Forge And Data-Model Journeys
    • Walkthrough: MCP Output Port
    • Walkthrough: Deploy to Google Cloud Platform
    • Walkthrough: Snowflake Team Collaboration
    • Declarative Airflow DAG Generation - The FLUID Way
    • Generating Orchestration Code from Contracts
    • Jenkins CI/CD for FLUID Data Products
    • Universal Pipeline
    • The 11-Stage Pipeline
    • End-to-End Walkthrough: Catalog → Contract → Transformation
  • CLI Reference

    • CLI Reference
    • Core workflow

      • fluid init
      • fluid demo
      • fluid forge
      • fluid validate
      • fluid plan
      • fluid apply
      • fluid diff
      • fluid status
    • Build & ship

      • fluid bundle
      • fluid generate
      • fluid generate artifacts
      • fluid validate-artifacts
      • fluid verify-signature
      • fluid generate iac
      • fluid generate-airflow
      • fluid generate-pipeline
      • fluid viz-graph
      • fluid publish
      • fluid ship
      • fluid rollback
      • fluid schedule-sync
    • AI & Agents

      • fluid ai
      • fluid agents
      • fluid mcp
      • fluid memory
      • fluid stats
      • fluid skills
    • Quality & governance

      • fluid test
      • fluid verify
      • fluid contract-tests
      • fluid contract-validation
      • fluid policy
      • fluid policy check
      • fluid policy compile
      • fluid policy apply
    • Standards & interoperability

      • fluid odps
      • fluid odps-bitol
      • fluid odcs
      • fluid export
      • fluid export-odps
      • fluid exporters
      • fluid import
      • fluid market
      • fluid datamesh-manager
    • Project & workspace

      • fluid product-new
      • fluid product-add
      • fluid workspace
      • fluid contract
      • fluid split
      • fluid config
      • fluid providers
      • fluid plugins
      • fluid provider-init
      • fluid auth
      • fluid secrets
      • fluid ide
      • fluid scaffold-ci
      • fluid scaffold-composer
      • fluid scaffold-ide
      • fluid docs
      • fluid runs
      • fluid retention
      • fluid describe
      • fluid doctor
      • fluid roadmap
      • fluid version
    • Catalog adapters

      • Source Catalog Integration (V1.5)
      • Publishing to a Catalog — Overview
      • BigQuery Catalog
      • Snowflake Horizon Catalog
      • Databricks Unity Catalog
      • Google Dataplex Catalog
      • AWS Glue Data Catalog
      • DataHub Catalog
      • Data Mesh Manager Catalog
      • OpenMetadata Catalog
    • CLI by task

      • CLI by task
      • Add quality rules
      • Add agent governance
      • Debug a failed pipeline run
      • Switch clouds with one line
  • Recipes

    • Recipes
    • Recipe — add a quality rule
    • Recipe — switch clouds with one line
    • Recipe — tag PII in your schema
    • Write a contract that consumes another contract
    • Generate per-environment overlays
  • SDK & Plugins

    • SDK & Plugins
    • Quickstart — your first plugin
    • Examples

      • Runnable examples
      • Example: hello-scaffold — the minimal viable plugin
      • Example: gitlab-ci-scaffold — generate a complete CI project
      • Example: steward-validator — a custom governance rule
      • Example: prod-key-guard — apply-time invariant check
    • Journeys

      • Journeys
      • Your own CI/CD

        • You have your own CI/CD setup, no problem
        • GitLab CI — the bundle template
        • GitHub Actions — the bundle template
        • Jenkins — the bundle template
        • CircleCI — the bundle template
      • You have a strict project layout, no problem
      • You have governance rules, no problem
      • You want a check at apply time, no problem
    • Reference

      • Reference
      • Roles reference
      • Entry points reference
      • Trust model
      • Packaging
      • Companion packages
  • Providers

    • Providers
    • Provider Architecture
    • GCP Provider
    • AWS Provider
    • Snowflake Provider
    • Local Provider
    • Creating Custom Providers
    • Provider Roadmap
  • AI & Agents

    • MCP Server
    • Built-in And Custom Forge Guidance
    • Forge Discovery Guide
    • Forge Memory Guide
    • Authoring Forge Tools
    • Guided fluid forge UX
    • LLM Providers
    • LiteLLM Backend
    • Capability Warnings
    • Cost Tracking
    • FLUID Forge Contract GPT Packet
    • Agentic Primitives
  • Operate & Deploy

    • Airflow Integration
    • Blueprints
    • Source-Aligned Acquisition
  • Govern & Secure

    • Governance, Compliance & the Business Case
    • Governance & Compliance
    • Network Safety
    • Credential Resolver — Security Model
  • Configuration & Reference

    • Environment Variables
    • Typed Errors
    • Typed CLI Errors
    • API Stability — fluid_build.api
  • Architecture & Releases

    • V1.5 Catalog Integration — Architecture Deep-Dive
    • V1.5 + V2 Hardening — Release Notes
  • Project

    • Contributing to Fluid Forge
    • Fluid Forge Docs Baseline: CLI 0.9.0
    • Fluid Forge Docs Baseline: CLI 0.8.11
    • Fluid Forge Docs Baseline: CLI 0.8.10
    • Fluid Forge Docs Baseline: CLI 0.8.9
    • Fluid Forge Docs Baseline: CLI 0.8.8
    • Fluid Forge Docs Baseline: CLI 0.8.7
    • Fluid Forge Docs Baseline: CLI 0.8.6
    • Fluid Forge Docs Baseline: CLI 0.8.5
    • Fluid Forge Docs Baseline: CLI 0.8.4
    • Fluid Forge Docs Baseline: CLI 0.8.3
    • Fluid Forge Docs Baseline: CLI 0.8.0
    • Fluid Forge Docs Baseline: CLI 0.7.11
    • Fluid Forge Docs Baseline: CLI 0.7.9
    • Fluid Forge v0.7.1 - Multi-Provider Export Release

Fluid Forge Docs Baseline: CLI 0.8.5

Release Date: May 28, 2026 Status: Superseded by 0.8.6 (supersedes 0.8.4)

Headline

0.8.5 is the agentic world-class uplift. The LLM layer moves to a true LiteLLM Router with cross-cloud fallback, automatic Anthropic prompt-caching, and accurate per-call cost accounting; a new JudgeAgent scores every generated contract on a 6-axis rubric and can gate CI; fluid forge runs become pausable and resumable (Ctrl-C now writes a checkpoint instead of losing work); a post-synthesis enrichment pass adds dbt tests, freshness, and physical-layout hints without overwriting your fields; and the model registry plus the three-tier (project / team / personal) memory and catalog adapters are hardened. It also lands the describe surface (fluid describe --self, fluid_build.describe, FluidSchemaManager.latest_schema_path()). No schema break vs v0.8.4.


What changed in v0.8.5

1 — LiteLLM Router with cross-cloud fallback + cache_control

fluid forge's LLM calls now route through a LiteLLM Router rather than a single client.

  • Cross-cloud fallback chain — opt in with FLUID_LLM_FALLBACK_CHAIN (e.g. anthropic→bedrock→vertex). When the primary provider errors or rate-limits, the Router transparently retries the next link.
  • Automatic Anthropic cache_control — cache points are injected automatically so repeated system / context blocks are billed at the cached rate.
  • 3-token cost tracking — cost accounting now splits cache-creation (1.25×) and cache-read (0.10×) multipliers from ordinary input/output tokens, and persists the breakdown to cost.json. fluid stats aggregates it.

2 — JudgeAgent + CI judge-gate

A new JudgeAgent scores generated contracts on a 6-axis chain-of-thought rubric: correctness, completeness, security, governance, performance, documentation.

  • An optional Self-Refine self-critique pass lets the agent revise before emitting a verdict.
  • Ships with a 10-contract eval set and a snapshot regression gate so a model or prompt change that degrades output quality fails CI.
  • Surfaced to operators via fluid stats --judge.

3 — Pause / resume + the fluid agents namespace

Long fluid forge runs are now interruptible without losing progress.

  • Ctrl-C writes a .paused checkpoint marker mid-run; the next fluid forge auto-detects it and offers to resume. Use --resume to resume explicitly.
  • Checkpointing uses a LangGraph-shape BaseCheckpointSaver with a JSON-only file backend (no pickle) — checkpoints are inspectable and safe to commit/transport.
  • New fluid agents list / show / prune namespace manages saved runs, with safe-by-default archiving (prune archives rather than hard-deletes).

4 — Post-synthesis enrichment (Wave 2)

A deterministic enrichment pass runs after the contract is synthesised, adding the fields a human reviewer usually adds by hand:

  • dbt_test_generator — proposes dbt tests for the modelled columns.
  • freshness_emitter — adds freshness expectations.
  • physical_layout — emits platform-appropriate physical-layout hints for Snowflake / BigQuery / Athena / Redshift.

Run it with fluid forge --apply-enrichment. Every change is shown as a diff preview and never overwrites a field you set — enrichment only fills gaps.

5 — 15-class PII classifier on both intake paths

A 15-class PII classifier (pattern borrowed from Presidio / piicatcher / GCP DLP / AWS Glue) is now wired into both the catalog intake path and the JDBC intake path, so sensitive columns are flagged consistently regardless of where the schema came from.

6 — Catalog-driven model registry + 3-tier memory hardening

  • Model registry is now catalog-driven — the static, hand-maintained model tables are retired in favour of cli/llm_models.json (weekly-refreshed). New models show up without a code change.
  • Three-tier memory (project / team / personal) gets a documented precedence ladder; inspect the resolved view with fluid forge --show-memory.
  • fluid doctor --env enumerates the FLUID_* kill switches so you can see which behaviours are toggled in your environment.

7 — Describe surface (CC alignment)

A new programmatic + CLI surface for "what is this install capable of":

  • FluidSchemaManager.latest_schema_path() — returns the absolute path to the newest bundled schema JSON without hardcoding a filename.
  • fluid_build.describe.self_describe() — a flat, JSON-serialisable snapshot of the installed environment (version, schema, providers, build engines, templates, capability flags), importable in-process. Capability flags are derived from importable backing modules (à la pulumi about), never hardcoded.
  • fluid describe --self [--json] — human-readable summary by default, JSON with --json.

Notable for upgraders

  • No schema break. Contracts that validated on v0.8.4 validate unchanged on v0.8.5.
  • Fallback chains are opt-in. FLUID_LLM_FALLBACK_CHAIN is unset by default — behaviour is unchanged unless you configure it. Each link must have working credentials.
  • Ctrl-C behaviour changed. Interrupting fluid forge now writes a checkpoint and exits cleanly instead of aborting. Run fluid agents prune periodically (or rely on the safe-by-default archiving) to keep the checkpoint directory tidy.
  • Enrichment is non-destructive but opt-in. --apply-enrichment only fills empty fields and always previews a diff; it will not silently rewrite a value you authored.
  • Model tables moved to cli/llm_models.json. If you patched the old in-code model tables downstream, re-point at the JSON registry.

What changed in the docs

  • fluid stats — documents the new --judge view and the cache-split cost columns.
  • LiteLLM Backend — Router, FLUID_LLM_FALLBACK_CHAIN, automatic cache_control, and 3-token cost accounting.
  • Guided Forge UX — pause/resume, --resume, the fluid agents namespace, --apply-enrichment, and --show-memory.
  • Environment Variables — new FLUID_* toggles surfaced by fluid doctor --env.
  • RELEASE_NOTES_0.8.5.md — this file.

Installing

pip install --upgrade data-product-forge
pip install "data-product-forge==0.8.5"

# Verify
fluid version
# -> 0.8.5

Archive note

Older release notes remain available: 0.8.4, 0.8.3, 0.8.0, 0.7.11, 0.7.9, 0.7.1.

Edit this page on GitHub
Last Updated: 5/29/26, 3:47 PM
Contributors: fas89
Prev
Fluid Forge Docs Baseline: CLI 0.8.6
Next
Fluid Forge Docs Baseline: CLI 0.8.4