Using packages

A package is Jadpo code shared between apps.

packages/ holds only packages you installed.

jadpo package add <name> looks for a package in a fixed order and records which step it used, so an agent never improvises where to look.

A package's surface is everything it offers an app, in one file you can read.

A provider package may act on its own API, but never on your app's data.

The approval report (Reviewing a change) lists, for each change.

A provider's description doesn't slow your build, however large it is, because the compiler never reads it.

How your app writes a package's enum values and failures: through the package's name, as its types are.

This is the detail behind Installing safely: what jadpo package add, update, remove, link and unlink do, and what each refuses.

How a name written through a package is told apart from the app's own, and how jadpo dev and jadpo test --watch follow a package you have linked to a checkout you are working on.

How an app holds two major versions of one package while it moves between them, and how Jadpo avoids compiling and checking package code the app doesn't use.

What jadpo package import openapi <file> reads from a provider's OpenAPI document, what it writes, and what it leaves for you.

How the importer turns a provider's fields into standard types, by their shape and their names.

This is the detail behind layers 4 and 5 of Mapping imported types to standard types: which imported types you review, how a review is marked, and which calls still need a recording to confirm them.