18 published packages

The whole ecosystem, in one place

16 on npm and 2 on PyPI, grouped by the job they do. What each one is, where to install it, and where to read more if there is more to read.

9 of them have a page here that goes deeper. The rest link straight to their registry and repository.

The execution layer

A model asks for an action by name; the runtime decides whether it may, performs it, and writes down what happened. Everything else on this page is built on these.

@openverb/runtimenpm

The execution runtime. Resolves a named verb, runs it, and records the result.

npm

@openverb/policynpm

The policy engine. Decides whether a requested action is allowed before it runs.

npm Read more

@openverb/sdknpm

The client SDK — how an application hands actions to the runtime.

npm

@openverb/clinpm

Command-line tools for working with verbs and documents outside an app.

npm

openverbnpm

Helpers for loading and validating verb libraries. The smallest way in.

npm Source Read more

The document format

A .ov file is a sequence of actions a runtime can execute — which is what makes a document portable between hosts rather than tied to the tool that wrote it.

@openverb/formatnpm

Parser, validator and runtime bridge for the .ov document format.

npm Read more

@openverb/markdownnpm

The OpenVerb Markdown spec — generate, validate and sync verb manifests a person can read.

npm

Verb libraries

A runtime on its own knows no verbs. These are the vocabularies: what a model is allowed to ask for in a given domain.

@openverb/stdlibnpm

The standard library — theme, navigation, search, modals, forms, sessions and focus. The starting vocabulary for any interface.

npm Source Read more

@openverb/idenpm

Verbs for AI-native coding environments: files, the editor, git, the terminal and preview.

npm Source

@openverb/gisnpm

Verbs for geographic work — layers, cameras, selection and measurement.

npm Source Read more

@openverb/crmnpm

A developer-native CRM template, protocol-compliant, with AI-driven communication workflows.

npm Read more

@openverb/music-atlasnpm

The Open Music Atlas SDK — places and their songs, editions, GeoJSON and embeds.

npm Source

Geographic storytelling

One profile of the format, and the renderer that draws it. GeoStory is what a document says; Motion is what a frame looks like.

@openverb/geostorynpm

The GeoStory profile — scenes, places, basemaps and cameras as a portable narrative format.

npm Source Read more

@openverb/motionnpm

Renders a .ov document to frames and video, with or without a map. The preview and the export are the same code.

npm Source Read more

Tooling

Things built on the execution layer that are useful on their own, and double as evidence that the layer carries real work.

@openverb/demonpm

Runs a product demo on the product. A .ov file drives the real interface through its own verbs — not a recording of someone else doing it.

npm Source

@openverb/pulsenpm

An AI-friendly project log that updates itself from builds, tests and errors.

npm

Python

The same ideas where the agents actually live. Published to PyPI rather than npm, so they are counted separately.

openverbpypi

Helpers for loading and validating verb libraries, for Python.

PyPI

openverb-fellowshippypi

The Fellowship pattern for Python agents — register, execute and audit verbs with no ceremony.

PyPI Read more

Download figures are last-week totals, read live from the npm and PyPI APIs when this page loads — the same source as the weekly stats. They count installs, which is not the same as use: a package can be pulled by a build a hundred times and never run by anyone. Shown here so the list reads as something alive, not as a measure of adoption.