IF Commons GitHub

Packaging

0002Draft

0002-packaging · owner if · domain commons · part of 0001-software-supply-chain

The ontology

FR-001checkpassing

The vocabulary MUST be commons/ontology/supply-chain/packaging/packaging.ts in the namespace https://www.intellectualfrontiers.com/ontology/packaging# (pm:), the data managers.ts, families.ts, programs.ts, pins.ts, rules.ts and record.ts beside it, with individuals in https://www.intellectualfrontiers.com/id/packaging/ (pmid:), each a TypeScript module of 0012-ontology FR-008 (amended 2026-11-16: the files were Turtle). A class MUST specialize a schema.org class where schema.org has one; every term MUST have a label and a definition.

Enforced (check): .github: bun test ./tests/ — Generator: a term with no definition is refused; Layout: the files are there

Proved by: tests/commons-packaging.test.ts

Tests: passed: tests/commons-packaging.test.ts Generator: a term with no definition is refused

FR-002checkpassing

The data MUST hold every package manager and every operating-system row of the tables of upt, whatever the platform (Linux, the BSDs, macOS, Windows, Android and Haiku), so that a future harness is not limited to the families the retired engine ran on. A test MUST fail where a manager or a row of tests/fixtures/upt/ is missing.

Enforced (check): .github: bun test ./tests/ — Generated: every manager and operating-system row of upt is in the table

Proved by: tests/commons-packaging.test.ts

Tests: passed: tests/commons-packaging.test.ts Generated: every manager and every os row of upt is here

Cited by: Ontology, supply-chain/packaging/families, supply-chain/packaging/managers, GRC documents and serializers

FR-003checkpassing

The data seeded from upt MUST say so, with its licence (MIT or Apache-2.0) and the identifier it leaves out (oubes, which is not an os-release ID). A command MUST say where it comes from (pm:origin: upt, archon (the commands the retired Stolos engine ran, before commons/archon of 0034-archon replaced it), memory (written from knowledge) or upt+memory where the non-interactive form was written from knowledge), and a command, a family or a flag run on a real computer MUST say where and when (pm:verifiedOn); one with none is unverified (0001-software-supply-chain FR-006).

Enforced (check): .github: bun test ./tests/ — Generated: upt is credited with its licence and the identifier left out is said

Proved by: tests/commons-packaging.test.ts

Tests: passed: tests/commons-packaging.test.ts Generated: upt is credited with its licence and the ID it leaves out is said

Cited by: Ontology, supply-chain/packaging/managers, supply-chain/packaging/packaging

FR-004checkpassing

A family MUST be supported where a harness acts on it and catalogued where it is only known, and MUST have an assurance: verified, stand-in, untested or none. A supported family that installs packages MUST have a preferred manager whose install command has a non-interactive form that comes from a harness (origin archon), a command that says whether a package is installed, the command a person with administrator rights runs, and a removal hint; one that installs none (a Mac) MUST say so. A verified family MUST say where and when.

Enforced (check): .github: bun test ./tests/ — Generated: a supported family is complete and says how far it has been tried; Generator: a verified family with no where or when is refused

Proved by: tests/commons-packaging.test.ts

Tests: passed: tests/commons-packaging.test.ts Generated: a supported family is complete and says how far it has been tried

Cited by: Ontology, supply-chain/packaging/families, The ontology in TypeScript

FR-005checkpassing

A command that must never be run MUST be a pm:Prohibition with its reason, and MUST NOT appear as a usable command: pacman -Sy (a refresh alone leaves a rolling release partly upgraded) and every command of an AUR helper (it runs the build scripts of packages nobody reviewed).

Enforced (check): .github: bun test ./tests/ — Generated: pacman -Sy and AUR helpers are prohibitions with reasons, and nothing usable is forbidden; Generator: a forbidden command is refused

Proved by: tests/commons-packaging.test.ts

Tests: passed: tests/commons-packaging.test.ts Generator: a forbidden command and shell syntax are refused; passed: tests/commons-packaging.test.ts Generated: what must never be run is a prohibition with a reason, and nothing usable is it

Cited by: Ontology, supply-chain/packaging/managers

FR-006checkpassing

A command MUST be a list of words, with {packages} or {package} where names go; it MUST NOT hold shell syntax, because a harness runs it without a shell.

Enforced (check): .github: bun test ./tests/ — Generated: a command is a list of words with no shell syntax; Generator: shell syntax is refused

Proved by: tests/commons-packaging.test.ts

Tests: passed: tests/commons-packaging.test.ts Generator: a forbidden command and shell syntax are refused; passed: tests/commons-packaging.test.ts Generated: a command is a list of words with no shell syntax

Cited by: Ontology, supply-chain/packaging/managers, The ontology in TypeScript

FR-007checkpassing

Every ID that detects a family (a word of the ID or ID_LIKE of /etc/os-release, or a platform name) MUST detect exactly one family; the fallback * is the one exception.

Enforced (check): .github: bun test ./tests/ — Generated: every detecting ID detects one family; Generator: two families claiming one ID are refused

Proved by: tests/commons-packaging.test.ts

Tests: passed: tests/commons-packaging.test.ts Generated: every detecting ID detects one family, and Omarchy is Arch by ID_LIKE

Cited by: Ontology, supply-chain/packaging/families

FR-008checkpassing

A program MUST be named once, with a tier (required for what a setup needs from a computer, comfort for the everyday programs) and, for each family, the package that gives it (alternatives separated by | where a release renamed it). Every required program MUST have a package for every supported family that installs packages, and a package MUST NOT be named for a family that is not supported.

Enforced (check): .github: bun test ./tests/ — Generated: required programs are named for every supported family

Proved by: tests/commons-packaging.test.ts

Tests: passed: tests/commons-packaging.test.ts Generated: programs are named once, and required ones for every supported family

Cited by: The ontology in TypeScript

The generated tables

FR-009checkpassing

commons/tools/generate-packaging.ts MUST read the ontology and write commons/generated/packaging.auto.toml, commons/generated/packaging.auto.sh and commons/generated/packaging.auto.ts (the same facts as typed TypeScript data, which a harness's setup imports: the families with their commands as lists of words, the programs, the platforms, the pins and the fields of the record), and the Turtle of 0012-ontology FR-011, MUST write the same bytes from the same ontology, and with --check MUST write nothing and fail (exit 1) where a file is not what the ontology makes (0001-software-supply-chain FR-002). It MUST be TypeScript that Bun (the default) or Node 26 runs (bun commons/tools/generate-packaging.ts), importing nothing outside commons/tools/ but the ontology's modules, whose typed values it reads (it parses no Turtle), and the tables it writes MUST be those it wrote from the Turtle the ontology was taken from, but for the source hash (0012-ontology FR-012) and the name of the source in their first line (amended 2026-11-16: the tool read the Turtle itself, with a reader of its own; amended 2026-11-15: the tool was Python, run by uv with rdflib).

Enforced (check): .github: bun test ./tests/ — Generator: the committed files and the TypeScript module are what the ontology makes, the same bytes twice, and a hand edit fails --check

Proved by: tests/commons-packaging.test.ts

Tests: passed: tests/commons-packaging.test.ts Generator: the committed files are what the ontology makes; passed: tests/commons-packaging.test.ts Generator: --check fails where a generated file was edited by hand, and writes nothing; passed: tests/commons-packaging.test.ts Generator: it makes the same bytes twice, and they are the committed ones

FR-010checkpassing

Before it writes anything the tool MUST check FR-001, FR-004 to FR-008 and name every rule broken, and MUST write nothing (exit 2) where one is; an ontology module that does not load stops it before it writes anything, with the runtime's own message naming the file and the line (amended 2026-11-16: it read Turtle, and named the file of a syntax error itself).

Enforced (check): .github: bun test ./tests/ — Generator: every rule broken is named and nothing is written

Proved by: tests/commons-packaging.test.ts

Tests: passed: tests/commons-packaging.test.ts Generator: a module of the ontology that does not load stops it before it writes anything,; passed: tests/commons-packaging.test.ts Generator: it names every rule the ontology breaks and writes nothing

Cited by: Intellectual Frontiers Commons, Integrations standards registry, The ontology in TypeScript

FR-011checkpassing

The TOML MUST begin with a line saying it is generated, schema = 1 and source_sha256 of the ontology (0012-ontology FR-012); hold every family, every manager with its commands (as lists of words, with the origin and verification of each), every prohibition and every program; and be valid TOML.

Enforced (check): .github: bun test ./tests/ — Generated: the schema, the source hash and the content

Proved by: tests/commons-packaging.test.ts

Tests: passed: tests/commons-packaging.test.ts Generated: it says it is generated and is the schema a reader expects

Cited by: The ontology in TypeScript

FR-012checkpassing

The shell fragment MUST be POSIX sh, free of the warnings of shellcheck, between # >>> packaging.auto >>> and # <<< packaging.auto <<<, and give, by family: pm_family_of (the family the words of an os-release name), pm_family_of_uname, pm_label, pm_status, pm_assurance, pm_manager, pm_installs_packages, pm_removal_hint, pm_note, pm_install_words, pm_refresh_words, pm_query_installed_words, pm_query_candidate_words, pm_environment, pm_admin_install, pm_package and pm_programs.

Enforced (check): .github: bun test ./tests/ — ShellFragment: marks, POSIX sh, shellcheck, and what each function answers

Proved by: tests/commons-packaging.test.ts

Tests: passed: tests/commons-packaging.test.ts ShellFragment: it answers what a script asks, by family; passed: tests/commons-packaging.test.ts ShellFragment: it is between marks, POSIX sh and free of shellcheck's warnings

FR-013checkno test run

A program that reads the TOML MUST ignore a table whose schema is newer than it understands and say so, MUST run a command as a list of words (never through a shell), and MUST run only executables its own allowlist names, so that a changed table cannot make it run something it does not know.

Enforced (check): archon: archon test — archon's packaging tests: only an allowed executable is run, shell syntax and forbidden commands are refused

FR-014checkpassing

The ontology MUST name the platforms a harness runs on (each with its name, operating system, processor and the ending of its pin variables; the operating system one of linux, macos and windows, the processor x86_64 or aarch64, and the name <os>-<x64|arm64>, Windows among them because a harness may set up natively there) and the downloads a script pins before any harness exists (each with a key, one version and a SHA-256 of 64 lower-case hexadecimal digits per platform), and the tool MUST write them to commons/generated/pins.auto.env (one KEY=value line each), and the platforms and pins into the TOML and the TypeScript module, so that a version or a checksum is written once. It MUST refuse, naming it, a pin with no version, a checksum that is not 64 digits, a platform or pin key used twice and a checksum for a platform or pin that does not exist.

Enforced (check): .github: bun test ./tests/ — Pins: the env file, the TOML and the TypeScript module agree, and Bun is pinned on every platform; Generator: a bad checksum, a pin with no version and a repeated key are refused

Proved by: tests/commons-packaging.test.ts

Tests: passed: tests/commons-packaging.test.ts Pins: the env file, the TOML and the module agree; passed: tests/commons-packaging.test.ts Generator: a bad checksum, a pin with no version, a repeated key and a checksum for nothin; passed: tests/commons-packaging.test.ts Pins: every platform names an operating system and a processor

Cited by: Ontology, supply-chain/packaging/packaging, supply-chain/packaging/pins, TypeScript practice, The ontology in TypeScript

FR-015checkpassing

A harness that keeps a copy of the pins MUST take it from pins.auto.env and not from a person's hand, and MUST NOT fetch pins at run time: a pin is trusted because a maintainer committed it, so it is the one thing in the table that is not refreshed by an update.

Enforced (check): archon: archon test — archon's pin tests: its built-in pins are the file commons generates, and the store reads them

Proved by: tests/commons-packaging.test.ts

Tests: passed: tests/commons-packaging.test.ts Pins: the env file, the TOML and the module agree

Cited by: Ontology, supply-chain/packaging/pins, Intellectual Frontiers Commons, Integrations standards registry

FR-016checkpassing

The ontology MUST name the fields of the record a setup keeps of how an account was set up (~/.config/erga/install.toml): each with a name, a type (text, boolean or date), an order and a definition, and the values it may hold where it may hold only some; the tool MUST write them, in order, to commons/generated/install-record.auto.toml, and the setup that writes the record MUST write exactly those fields in that order, so that what writes the record and what reads it cannot drift.

Enforced (check): .github: bun test ./tests/ — Record: the fields, their order and their values, as the TypeScript module carries them; Generator: a bad field is refused

Proved by: tests/commons-packaging.test.ts

Tests: passed: tests/commons-packaging.test.ts Record: the fields are in order, with a type, and the methods and hosts a setup can write; passed: tests/commons-packaging.test.ts Record: a bad rule or field is refused

Cited by: Ontology, supply-chain/packaging/packaging, supply-chain/packaging/record

The download of a pin

FR-017checkpassing

A checksum (pm:Checksum, a pin on a platform) MUST say what a download of it needs, so that the pin is the one source of where a program comes from: pm:downloadUrl (the https address of the publisher's artifact for that pin and platform, in which {version} stands for the pin's version, so that a version is written once), pm:archiveFormat (zip, tar or file: a zip archive, a tar archive plain or compressed, or the one file itself) and pm:binPath (the folder of the programs inside the unpacked artifact, relative to its root; empty for the root). A platform whose address is not known MUST NOT be given one: it MUST carry pm:unpinnedReason, the sentence that says why, and none of the three, so that a script and a harness see it is not downloadable and no address is invented. Exactly one of the two forms MUST be present.

Enforced (check): .github: bun test ./tests/ — Pins: a pinned platform has an address, a format and a folder, an unpinned one says why, and the pins state each

Proved by: tests/commons-packaging.test.ts

Tests: passed: tests/commons-packaging.test.ts Pins: a pinned platform has an https address, a format and a folder, an unpinned one says

Cited by: Ontology, supply-chain/downloads, supply-chain/packaging/packaging, supply-chain/packaging/pins

FR-018checkpassing

The tool MUST refuse, naming the pin and the platform, an address that is not https (after {version} is replaced), an address with a user name or a password, an address that is not an address, an archive format that is none of the three, a binPath that is absolute, holds \ or has a .. word, a checksum with some but not all of the three, a checksum with both an address and an unpinned reason and with neither, and more than one checksum for the same pin and platform (FR-010).

Enforced (check): .github: bun test ./tests/ — Generator: an address that is not https, holds a user name, a format that is none of three, a folder that leaves its root, a half-stated checksum and a checksum twice are each refused

Proved by: tests/commons-packaging.test.ts

Tests: passed: tests/commons-packaging.test.ts Generator: an address that is not https, holds a user name or is no address, a format that

FR-019checkpassing

The generated files MUST carry what FR-017 says, written from the pins and nowhere else: pins.auto.env MUST add to each pinned platform of a pin the lines KEY_URL_SUFFIX (the address, {version} replaced), KEY_FORMAT_SUFFIX and KEY_BINPATH_SUFFIX, and the TOML and the TypeScript module MUST hold, for each pin, each platform as { state: "pinned", sha256, downloadUrl, archiveFormat, binPath } or { state: "unpinned", sha256, reason } (a closed union; the module's pins entry has platforms and no separate sha256 map). A program of this repository that downloads a pin (the Bun installer of CI, the OpenTelemetry Collector step of the conformance job) MUST read the address, the format and the folder from pins.auto.env and MUST NOT write them again, so that a change of pin is made in pins.ts and in no other file.

Enforced (check): .github: bun test ./tests/ — Pins: the env file, the TOML and the module carry the addresses of the pins, and the Bun installer and the conformance job read them

Proved by: libraries/suite/pins.test.ts, tests/commons-packaging.test.ts

Tests: passed: suite/pins.test.ts commons pins Bun with a checksum for each platform Bun builds for, and the installer finds; passed: tests/commons-packaging.test.ts Pins: a pinned platform has an https address, a format and a folder, an unpinned one says

Cited by: Libraries, pins

FR-020checkpassing

The ontology MUST export, for a reader that holds no pin of its own (commons/toolchain), the downloads as typed values: downloadOf(pin, platform) of @intellectual-frontiers/ontology/supply-chain/downloads, which MUST give for a pin id (mise, python, uv, rustup-init, gh, jq, bun, otelcol-contrib) and a platform name (linux-x64, linux-arm64, macos-x64, macos-arm64, windows-x64) a Result of { version, downloadUrl, sha256, archiveFormat, binPath }, or the reason the platform is unpinned, or that the pin or platform is unknown; each a value of a closed union and each id a branded smart-constructed value.

Enforced (check): .github: bun test ./tests/ — Pins: downloadOf gives the version, address, SHA-256, format and folder of a pin on a platform, or why it is unpinned

Proved by: tests/commons-packaging.test.ts

Tests: passed: tests/commons-packaging.test.ts Pins: downloadOf gives the version, address, SHA-256, format and folder of a pin on a plat

Cited by: Ontology, supply-chain/downloads

FR-021checkpassing

The package managers MUST include manager-mise (mise, a tool manager: the kind tool, which is no family's manager), with the commands install, query version, list installed and install exact (FR-024) as words, each of origin memory and unverified (FR-003), so that nothing acts on them until they are run on a real computer.

Enforced (check): .github: bun test ./tests/ — Managers: mise is a tool manager with four unverified commands of origin memory

Proved by: tests/commons-packaging.test.ts

Tests: passed: tests/commons-packaging.test.ts Managers: mise is a tool manager with four unverified commands of origin memory

FR-022checkpassing

Each of the managers apt, pacman, dnf, brew and winget (those of the Linux, macOS and Windows families a harness meets first) MUST have a command for the operation query version, which says the version of one installed package for an SBOM; where one was not yet in the table it MUST be added with origin memory and no verification (FR-003). The query version of brew (brew list --versions {package}) and of winget (winget list --exact --id {package}) are of that kind.

Enforced (check): .github: bun test ./tests/ — Managers: apt, pacman, dnf, brew and winget each have a query-version command

Proved by: tests/commons-packaging.test.ts

Tests: passed: tests/commons-packaging.test.ts Managers: apt, pacman, dnf, brew and winget each have a query-version command, those writt

FR-023checkpassing

The name archon MUST be used in the ontology, its generated files and this specification only for commons/archon (0034-archon) and for the origin archon of FR-003; a sentence MUST NOT call it a harness the ontology's data was taken from.

Enforced (check): .github: bun test ./tests/ — Names: the ontology and its generated files say archon only of commons/archon and of the origin archon

Proved by: tests/commons-packaging.test.ts

Tests: passed: tests/commons-packaging.test.ts Names: the ontology and its generated files say archon only of commons/archon and of the o

FR-024checkpassing

The operations of a manager MUST include install exact: install one package at one version, written with {package} and {version}. Each of apt, brew, winget and mise MUST have it, of origin memory and unverified (FR-003), as that manager's own documented syntax writes an exact version: apt install {package}={version}, brew install {package}@{version}, winget install --exact --id {package} --version {version}, mise install {package}@{version}. A manager that has none states none, and nothing supplies one.

Enforced (check): .github: bun test ./tests/ — Managers: apt, brew, winget and mise have an install-exact command of origin memory, unverified

Proved by: tests/commons-packaging.test.ts

Tests: passed: tests/commons-packaging.test.ts Commands: apt, brew, winget and mise write an exact version unverified, any other manager

Cited by: Ontology, supply-chain/commands

FR-025checkpassing

The ontology MUST export, for a reader that parses no RDF and copies no template (a manager dialect of commons/toolchain), the commands as typed values: commandOf(manager, operation) of @intellectual-frontiers/ontology/supply-chain/commands, which MUST give for a manager id (ManagerId, branded, made only by parseManagerId, which accepts the identifiers the ontology states) and an operation (the closed union Install | QueryVersion | QueryInstalled | Refresh, made by parseOperation) a Result of { manager, executable, environment?, needsAdministrator, template, nonInteractive?, missingExitStatus?, verified }: template and nonInteractive lists of words with {package}, {packages} and {version} where the ontology holds them (no shell string), environment the variables the manager's commands run with as the ontology holds them (NAME=value), nonInteractive and environment absent where the ontology states none, missingExitStatus (FR-029), and verified true only where the command carries pm:verifiedOn (FR-003).

Enforced (check): .github: bun test ./tests/ — Commands: commandOf gives the words, executable, environment, administrator need and verification of an operation of a manager, for every manager and operation

Proved by: tests/commons-packaging.test.ts

Tests: passed: tests/commons-packaging.test.ts Commands: commandOf gives, for every manager and operation, the words of the table or not-

FR-026checkpassing

exactVersionOf(manager) of the same module MUST give the InstallExact command of FR-024 in the same shape, or not-defined; managerIds() and operationNames() MUST list every manager of the ontology and the four operations; prohibitionsOf(manager) MUST give each command the ontology forbids for a manager (FR-005) as words with its reason, or unknown-manager; and describeCommandError MUST tell each error in one sentence.

Enforced (check): .github: bun test ./tests/ — Commands: exactVersionOf, managerIds, operationNames, prohibitionsOf and describeCommandError

Proved by: tests/commons-packaging.test.ts

Tests: passed: tests/commons-packaging.test.ts Commands: apt, brew, winget and mise write an exact version unverified, any other manager

FR-027checkpassing

The error of the reader MUST be a closed union: unknown-manager (no such identifier), unknown-operation (not one of the four), not-defined (the ontology states no command of that operation for that manager: no reader invents one, and Refresh of a manager that has none is this), malformed (a template that is empty, holds a quotation, an escape or a shell word, or an environment that is not NAME=value). A matching of an operation or of an error MUST be exhaustive.

Enforced (check): .github: bun test ./tests/ — Commands: every error of the reader is a value of a closed union and is told in one sentence

Proved by: tests/commons-packaging.test.ts

Tests: passed: tests/commons-packaging.test.ts Commands: commandOf gives, for every manager and operation, the words of the table or not-; passed: tests/commons-packaging.test.ts Commands: every error of the reader is a value of a closed union and is told in one senten

Cited by: Ontology, supply-chain/commands

FR-028checkpassing

The generated files MUST carry the operation of FR-024: the TOML as the command install-exact of each manager that has it, and the Turtle as the individual InstallExact of the operations and its commands.

Enforced (check): .github: bun test ./tests/ — Tables: the generated files carry install-exact

Proved by: tests/commons-packaging.test.ts

Tests: passed: tests/commons-packaging.test.ts Commands: apt, brew, winget and mise write an exact version unverified, any other manager

FR-029checkpassing

A command of the operation query installed MAY carry pm:missingExitStatus, the exit status that says the package is not installed and not that the manager failed; it is stated only where the manager's documented behaviour supports it, of origin memory and unverified where the command is (FR-003), and the reader MUST give it as missingExitStatus and leave it absent where the ontology states none. It is stated for apt (dpkg-query exits 1 for a package it does not know) and brew (brew list --formula exits 1 for a formula that is not installed); winget and mise have no query-installed command, so none is stated; no reader supplies one.

Enforced (check): .github: bun test ./tests/ — Commands: missingExitStatus is stated for the query-installed of apt and brew and absent elsewhere

Proved by: tests/commons-packaging.test.ts

Tests: passed: tests/commons-packaging.test.ts Commands: missingExitStatus is 1 for the query-installed of apt and brew and absent for ev

Out of scope

  • Acting on a family: what a harness does with the table (commons/archon, 0034-archon, and erga's machine bootstrap specification).
  • Downloading, unpacking and installing a pin: commons/toolchain reads the addresses and hashes of the pins through the ontology's exports and holds no version or hash of its own; the pin only says where the publisher's artifact is.
  • The download entries of erga's catalog: reviewed by a person later, not generated here.
  • A command for a manager nobody has run: it is recorded unverified and used by no one.
  • Package versions and the repositories' contents.

Acceptance scenarios

  1. Given a pin whose checksum names http:// as its address, When the tool runs, Then it exits 2 and names the pin and the platform and says the address is not https, and writes nothing, per FR-018.
  2. Given an address https://user:secret@example.com/x, When the tool runs, Then it exits 2 and says the address holds a user name or a password, per FR-018.
  3. Given a binPath of ../x or /usr/bin, or an archive format rar, When the tool runs, Then it exits 2 naming each, per FR-018.
  4. Given a checksum with an address and no format, When the tool runs, Then it exits 2 and says the three go together, per FR-017 and FR-018.
  5. Given a platform with no known address and an unpinned reason, When the tool runs, Then it writes the platform as unpinned with its reason in the TOML and the module and no KEY_URL_ line in pins.auto.env, per FR-017 and FR-019.
  6. Given the committed pins, When pins.auto.env is read, Then the Bun address of each of its five platforms is there, and the Bun installer takes its address from it, per FR-019.
  7. Given the ontology's exports, When downloadOf is asked for Bun on linux-x64, Then it gives the version, the address with the version in it, the SHA-256, zip and bun-linux-x64, and for a platform that is unpinned it gives the reason, per FR-020.
  8. Given the table of managers, When it is read, Then mise is there with four commands of origin memory and no verification, and apt, brew and winget each have a query-version command, per FR-021 and FR-022.
  9. Given a manager id and an operation, When commandOf is asked for each of the four operations of each of apt, brew, winget, mise and pacman, Then it gives the words of the template, the executable, the environment, whether it needs administrator rights and whether it was verified, or not-defined, per FR-025 and FR-027.
  10. Given an identifier or an operation the ontology does not state, or a manager with no command of an operation, When the reader is asked, Then it gives unknown-manager, unknown-operation or not-defined, each told in one sentence, per FR-027.
  11. Given apt, brew, winget and mise, When exactVersionOf is asked, Then it gives {package}={version}, {package}@{version}, --exact --id {package} --version {version} and {package}@{version} as words and unverified, and for pacman it gives not-defined, per FR-024 and FR-026.
  12. Given pacman, When prohibitionsOf is asked, Then it gives pacman -Sy with its reason, per FR-026.
  13. Given apt and brew, When commandOf is asked for QueryInstalled, Then missingExitStatus is 1, and for any other command it is absent, per FR-029.

Edge cases

  • A command in upt's table that is a prohibition (pacman -Sy): it is not recorded as a usable command, per FR-005.
  • A family whose non-interactive form was written from knowledge: it stays catalogued, and no harness runs it until it is run on a real computer, per FR-003 and FR-004.
  • A computer whose ID is unknown but whose ID_LIKE names a family (Omarchy, ID_LIKE=arch): the first word that detects a family decides it, per FR-007.
  • A required program with no package for a supported family: the tool names it and writes nothing, per FR-008 and FR-010.
  • The ontology and a generated file disagree: --check fails and says to run the tool, per FR-009.
  • An ontology module with a syntax error: the tool stops, and the runtime names the file and the line, per FR-010.
  • A computer whose family the table knows but no script acts on (Fedora, ID=fedora): the setup stops before changing anything and names the family and its package manager, per FR-004.

Assumptions

  • Bun (the version pins.auto.env pins) or Node 26 is on the computer that regenerates; the tables are committed, so a computer that only reads them needs nothing (amended 2026-11-15: it was uv).
  • upt's README stays under its MIT or Apache-2.0 licence.

Open questions

OQ-1open question

Whether the non-interactive forms written from knowledge are right for each manager: each is checked on a real computer before its family is supported.

OQ-2open question

The package URL type of the managers upt lists that have none (nix, guix, flatpak, snap, winget, scoop, chocolatey, xbps, portage, opkg, FreeBSD's pkg), if the specification adds them.

Key entities

  • Checksum - a pin on a platform, with the address, format and folder of its download (pm:Checksum).
  • Package manager - a program that installs software (pm:PackageManager).
  • System family - the computers that share a manager and package names (pm:SystemFamily).
  • Command - one operation of a manager as a list of words (pm:Command).
  • Prohibition - a command never to run, with the reason (pm:Prohibition).
  • Program and package name - what is installed and what a family calls it.

Success criteria

SC-001success criterion

bun commons/tools/generate-packaging.ts --check succeeds on the committed files.

SC-002success criterion

Every manager and operating-system row of upt is in the table.

SC-003success criterion

Adding a family is a change to the ontology and a run of the tool.

Review & acceptance checklist

  • [x] Every requirement is testable (MUST / MUST NOT), not aspirational
  • [x] No company fact is asserted here
  • [x] Every open item is marked, not silently decided
  • [x] Confidential: no sensitive fact written as a literal

Cited by

Libraries, pins, Ontology, supply-chain/commands, supply-chain/downloads, supply-chain/packaging/families, supply-chain/packaging/managers, supply-chain/packaging/mod, supply-chain/packaging/packaging, supply-chain/packaging/pins, supply-chain/packaging/record, Intellectual Frontiers Commons, Software supply chain, GRC documents and serializers, Toolchain ontology adapter, Native-pinned pin tool, TypeScript practice, Integrations standards registry, The ontology in TypeScript, Two languages: natural language and TypeScript 7

Titles, headings, exports, tables, columns and requirements. Esc closes.