JDON stands for JSONFIRST Domain Object Notation. It is the executable intent format produced by the JSONFIRST protocol. JDON transforms a human instruction into a structured, validated, machine-readable JSON object with explicit action, object, domain, constraints, and execution metadata — ready to be executed by any AI agent or automation pipeline.

What is the difference between JDON and JSON?

Regular JSON is a data format — it stores arbitrary key-value pairs. JDON is a structured intent format — it specifically encodes a human intent as an executable AI action with defined fields: action, object, domain, constraints, and execution rules. JDON is not just data; it is a structured AI command that can be validated, governed, and executed deterministically.

How is JDON generated?

JDON is generated by JSONFIRST's intent parsing engine. When a user sends a human instruction (text), JSONFIRST parses the intent and produces a JDON object with explicit fields. The JDON is then validated against the governance mode and Action Registry before being passed to the LLM or execution engine.

What is structured AI commands?

Structured AI commands are machine-readable instructions that explicitly encode what an AI agent should do, on what object, with what constraints, and under what governance rules. JDON is JSONFIRST's implementation of structured AI commands — replacing fragile prompt engineering with deterministic, validatable intent.

JSONFIRST · CORE FORMAT

What is JDON?

JDON is the executable intent format produced by JSONFIRST.

JSONFIRST = the protocol. JDON = the core object of the protocol.

JDON stands for JSONFIRST Domain Object Notation. It is a structured JSON format that represents a human instruction transformed into a validated, governable, executable AI command.

What JDON Means

JSONFIRST

The source protocol

Domain

The agent's domain

Object

The structured object

Notation

The representation format

JDON is not just JSON. It is a structured intent format — every JDON encodes a specific action, its object, its domain, its execution constraints, and its governance rules. That is the difference between "data" and "executable AI command".

How JDON Is Generated

User Instruction"Analyze this balance sheet"

↓

JSONFIRSTIntent parsing engine

↓

★JDONStructured intent — validated, governed

↓

Action RegistryAction selection and validation

↓

Policy ContractGovernance rules and constraints

↓

ExecutionLLM · Tools · APIs · Workflows

GENERATED JDON

output.jdon.json

{
  "spec": "JSONFIRST",
  "version": "2.0",
  "input": {
    "raw_text": "Analyse ce bilan comptable",
    "language": "fr"
  },
  "jdons": [
    {
      "jdon_id": "jdon_a1b2c3d4",
      "confidence": 0.97,
      "action": {
        "raw": "analyze",
        "normalized": "analyze"
      },
      "object": {
        "type": "financial_report",
        "raw": "balance_sheet"
      },
      "domain": {
        "primary": "finance"
      },
      "constraints": {
        "require_validation": true,
        "governance_mode": "FINANCE_ALGO"
      }
    }
  ],
  "execution": {
    "parsable": true,
    "executable": true,
    "mode": "strict",
    "state": "VALIDATED"
  }
}

ValidatedGovernedExecutable

JDON vs JSON

JDON represents a structured action — not just data.

Regular JSON

{
  "message": "analyse ce bilan"
}

Ambiguous intent
No defined action
Not validatable
LLM must guess

JDON

{
  "intent": {
    "action": "analyze_financial_report",
    "object": "balance_sheet",
    "domain": "finance",
    "constraints": {
      "require_validation": true
    }
  }
}

Explicit action
Defined object
Programmatically validatable
Deterministic execution

JSON vs JDON

JSON = generic data format

Stores arbitrary key-value pairs. No semantics, no governance, no traceability.

JDON = JSON-Defined Object Notation

→structured according to JSONFIRST protocol
→certified by pipeline v4.1
→traceable, versioned, auditable
→not just data — a governed decision

JDON in the JSONFIRST Pipeline

InstructionJSONFIRST★ JDONAction RegistryPolicy ContractExecution

JDON is produced by

JSONFIRST

JSONFIRST parses the instruction and generates a validated JDON with all required fields.

JDON is consumed by

Action Registry

The Action Registry reads the JDON, selects the appropriate action, and validates constraints.

JDON is executed by

LLM · Tools · APIs

The LLM or tools receive a structured JDON — not an ambiguous prompt.

JDON Examples

USER INSTRUCTION

"Analyze this balance sheet"

JSONFIRST parse

ACTIVE MODE:FINANCE_EXPERT

PRODUCED JDON

intent.jdon.json

{
  "action": "analyze_financial_report",
  "object": "balance_sheet",
  "domain": "finance",
  "constraints": {
    "require_validation": true
  }
}

START GENERATING JDON

Transform your intent into JDON.

Every instruction becomes a validated, governed, executable JDON.