Changes

The versioning rules govern a change, and the advancement rule states when a construct advances from draft to stable.

The entries below 0.6 are reconstructed from the repository history. From 0.6 onward, this page is updated with the change that makes it.

0.6 — current draft

Restructured. Rationale moved to the design rationale, and guidance moved to the authoring guide. The specification holds requirements alone. The conditions of static validation are listed once, in the error code registry.

New normative documents.

• The error code registry. Every condition of static validation and every evaluation fault has a code.
• The standard library. The canonical connectors time, store, http, data, and llm, and ten canonical filter packages, are defined normatively.
• The JSON Schema, which is the machine-readable form of the structural rules.
• The conformance suite, with one case per fixture format.

Format changes.

• outputs and the call contract are defined.
• route and choose bind the scope of the branch that executed.
• on_error is unified across for_each and parallel.
• match supplies correlation keys, and creates no binding.
• Connection parameters and self_hosted addresses are declared in the manifest.
• Trigger input schemas are declared and validated.
• idempotent: true without idempotency_param promises natural idempotency.
• The from_json filter is added.
• Value semantics and comparison are specified.
• The grammar is stated in ABNF.
• Security considerations are stated.
• The portable profile and the lib-* capabilities are defined.
• A signing filter is excluded by contract, because a signature requires a credential.

0.5

• Schema overlays for tenant-defined fields.
• Inline render templates, alongside file templates.
• max: unbounded on for_each.
• Per-action scopes in the manifest.
• states subscriptions, and a scope per state entry.
• The terms manifest, connector, and catalog are defined.
• A type expression is always quoted.
• Resolution is pinned across the runs of one deployment.

0.4

• The keep filter, the computed counterpart of where.
• Multi-trigger into projections.
• Guarded groups, as a single-arm choose.
• Evaluation faults are specified.
• Filter package namespaces are reserved.
• Local templates need no manifest.
• The per-element binding is renamed from it to current.

0.3

• The each projection filter, and where(path, op, value).
• The extract_all filter.
• store.increment.

0.2

• Keywords renamed for clarity: choose, wait_for, queue_by, deterministic, validated_output, human_size.
• The value, wait, and stop constructs.
• The conditional expression.
• Run metadata, as run.id and run.started_at.
• Correlation for a suspended run.
• Manifest booleans are defined as promises.
• The conformance suite governs, and a reference engine does not.

0.1

The initial draft.