@openverb/format (v2.0.0-beta.3)

The Living Document for AI Workflows

The .ov format isn't just a configuration file—it's a deterministic, executable digital asset that makes AI workflows transparent and safe.

Beyond Raw YAML

When a user opens an .ov file, they shouldn't just see code. They should see the workflow, the required inputs, the data flow, and the permissions required.

Location Analysis.ov

Valid OpenVerb Document

Required Inputs

Address
Buffer distance
Export format

Action Sequence

1

gis.search_place

Automated action

2

gis.geocode_address

Automated action

3

gis.buffer_geometry

Automated action

4

gis.export_map

Automated action

Required Libraries

@openverb/gis

Permissions

gis.read
gis.export

Actions

Strict Validation

Powered by the @openverb/format parser, every document is strictly validated against JSON Schema definitions of your verbs. No hallucinations.

Explicit Permissions

Before execution, the OpenVerb runtime inspects the `.ov` file to ensure the executing agent has the required permissions to run the sequence of actions.

Platform Agnostic

Whether you are executing workflows in a web CRM, a desktop QGIS plugin, or a CLI tool, the `.ov` format remains portable and interoperable.

OpenVerb Sandbox

Paste a Verb Library JSON schema here to define what actions the AI can perform.

Ask the AI to perform a task. It will use the vocabulary defined in your library.

The AI proposes a structured action based on your library vocabulary.

Waiting for prompt...

OpenVerb Core intercepts the AI's action and validates it before execution.

Verb exists in library
Payload matches JSON Schema
Policy requirements passed
Inputs valid and sanitized

The validated action is routed to the application backend for execution.

Waiting...

OpenVerb Core generates an execution receipt for full auditability.

Waiting for execution...