at.happyproto.plugin.releaseExtension

The HappyView-specific half of a release, carried at extensions['at.happyproto.plugin.releaseExtension']. It is the plugin manifest, moved into the signed record so a consent screen renders without downloading the module. It is not trusted: the loader checks it against the module's plugin_info export and its import section, so a release that misstates what its WASM does is refused exactly as a checksum mismatch is.

Repository @happyproto.at did:plc:mo7vq4jbioxwafy5zkcc3eux namespace authority
Details · object
Kindobject
Authorityplugin.happyproto.at
Indexed

Object

object

Properties

Hosts an outbound request may reach, as in today's manifest. The one constraint the capability model already has.

itemsstring
  • maxLength: 256

apiVersion

requiredstring

'2' or later, as validate_manifest already requires.

  • maxLength: 16

capabilities

requiredarray

The trust contract. The loader cross-checks it against the module's actual imports, so a plugin cannot import what this does not cover.

itemsstring
  • maxLength: 128

Interpreters only: the file extensions a project's scripts in this language use, without the dot, as in the manifest's `extensions`. A project maps `getArtifact.lua` to the interpreter claiming `lua`, so a client that installs from the registry needs this to build that map without downloading the module. Optional, because releases published before it existed carry none.

  • maxLength: 8
itemsstring
  • minLength: 1
  • maxLength: 16

Interpreters only: what scripts.script_type holds. Lowercase alphanumerics plus '-' and '_', starting with a letter, because the value has to survive a column, a URL and an editor mode name.

  • maxLength: 64

namespace

string

Libraries only: the require() name, which is unique across installed plugins.

  • maxLength: 256

pluginType

requiredstring

Every type requires an api_version of '2' or later and must declare its capabilities; there is no lower-version fallback for any of them.

  • knownValues: auth | library | interpreter

Similar lexicons

semantic match

Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.

  • A HappyView plugin, as one entry in a software.release.manifest's `artifacts`. It carries the module and its manifest.json as blobs, so they are verified by their CIDs, and the manifest's facts in the signed record, so a consent screen renders without downloading the module. Those facts are not trusted: the loader checks them against the module itself and refuses a plugin that misstates what it does. The registry refuses a manifest whose artifact breaks a rule stated here, including the ones a l

  • One version of a package. The record key is '<slug>:<version>'. A release at a given version is never modified: a registry that later sees a different CID at this key keeps the first and flags the conflict.

  • com.emdashcms.experimental.package.release

    record not from the namespace authority

    Plugin package release record. EXPERIMENTAL: this NSID is part of the experimental phase of the EmDash plugin registry. The stable namespace target is com.emdashcms.package.release.