FLUIDFLUID
  • Introduction
  • Quickstart
  • Why FLUID
  • FAQ
  • What FLUID Is
  • Core Principles
  • Agentic-Native Layer
  • FLUID vs ODCS / ODPS
  • Reference Implementation
  • Anatomy
  • Cheatsheet
  • Minimal Contract
  • Specification
  • Versions
  • Changelog
  • JSON Schema 0.7.5 (stable) ↗
  • Reference 0.7.5 (HTML) ↗
  • Preview: 0.7.6
Examples
How-to
What's New
Deck
  • Contributing
  • Governance ↗
  • Conformance Corpus ↗
  • Vision
GitHub
GitHub
  • Introduction
  • Quickstart
  • Why FLUID
  • FAQ
  • What FLUID Is
  • Core Principles
  • Agentic-Native Layer
  • FLUID vs ODCS / ODPS
  • Reference Implementation
  • Anatomy
  • Cheatsheet
  • Minimal Contract
  • Specification
  • Versions
  • Changelog
  • JSON Schema 0.7.5 (stable) ↗
  • Reference 0.7.5 (HTML) ↗
  • Preview: 0.7.6
Examples
How-to
What's New
Deck
  • Contributing
  • Governance ↗
  • Conformance Corpus ↗
  • Vision
GitHub
GitHub
  • Vision

    • Vision
    • The FLUID Ecosystem in 2030: A Five-Year Projection
    • The FLUID Protocol: A Multi-Stakeholder Perspective on the Agentic Data Fabric

Vision

Where FLUID is headed, and why it matters across the organization. Two longer-form pieces:

  • The FLUID Ecosystem in 2030 — a five-year projection: the shift from pipelines to products, the FLUID-compliant tooling landscape, and the rise of the Data Product Manager.
  • A Multi-Stakeholder Perspective — FLUID seen through four lenses: C-suite executives, data engineers, MCP agents, and software vendors.

These are forward-looking, opinion-led pieces. For what's shipped today, see the release notes and the Schema Reference.

Edit this page on GitHub
Last Updated: 5/29/26, 5:26 PM
Contributors: fas89, Claude Opus 4.8
Next
The FLUID Ecosystem in 2030: A Five-Year Projection