plugin-atoms

bootstrap · v0.1.0 plugin-atoms.com

Plugin interface standards — not implementations — making plugins ecosystem-portable across Convergent Systems runtimes. USB-C for software plugins.

At a glance

Specatoms-spec/v1
LicenseApache-2.0
Federationxdao.co
Atom types
  • interface-contract
  • capability-declaration
  • permission-scope
  • lifecycle-hook
  • trust-primitive
Composition conventions · directory conventions/
Rule types
  • capability-grant
  • semver-compatibility
  • trust-chain-verification
Runtime consumers
  • aish
  • olympus
  • universal-bus

Links

README

plugin-atoms

Plugin interface standards — not implementations — making plugins ecosystem-portable across Convergent Systems runtimes. USB-C for software plugins.

plugin-atoms is a *-Atoms catalog in the Convergent Systems ecosystem. It defines what exists in its domain — typed, versioned, machine-readable, composable, and open — so runtimes (and humans) can stand on shared infrastructure instead of reinventing it.

Structure

plugin-atoms/
├── ATOMS.yml              # Catalog manifest
├── atoms/                 # Reusable building blocks
├── conventions/       # Compositions assembled from atoms
├── rules/                 # Typed constraint vocabulary
├── schemas/               # Catalog-specific JSON Schemas
├── exports/               # CI-generated machine-readable exports
└── docs/                  # Human-readable documentation

Atom types

  • interface-contract
  • capability-declaration
  • permission-scope
  • lifecycle-hook
  • trust-primitive

Rule types

  • capability-grant
  • semver-compatibility
  • trust-chain-verification

Runtime consumers

aish, olympus, universal-bus

How to consume

Machine-readable exports are published in exports/ on every release:

  • exports/manifest.json — lightweight discovery (name, version, counts)
  • exports/catalog.json — full catalog dump (every atom, composition, rule)

Exports are deterministic, signed, and versioned. See ATOMS.yml for the manifest and the conformance spec.

How to contribute

  1. Read ATOMS.yml to understand the catalog's atom types, compositions, and rules.
  2. Add a new atom under atoms/<type>/ or a composition under conventions/<name>/.
  3. Open a PR. CI validates the schema, references, and exports.
  4. Larger structural changes go through the XAIP process.

Ecosystem

License

Apache-2.0 — see LICENSE.