Registry client

Platform spec area

Registry client

Back to Tooling ◎ Open in platform map

Owner

Piotr Mikstacki pmikstacki@cybernomad.it

Submitter

Piotr Mikstacki pmikstacki@cybernomad.it

Current document

ADRs

No architecture decision records under adr/ for this feature yet. Standard features must publish at least one ADR or keep a ## Decisions summary on the hub.

Articles

• No directly attached article pages for this node. Nested descendants exist deeper in this subtree.

History

0 revisions (git unavailable at build; counts may be empty)

Open full history on GitHub

No commits recorded for this path.

Completeness

OKarea · 2 SpecSection(s) · 0 H2 heading(s)

Section id	Required	Found
scope	yes	yes
features	yes	yes

Full tree: run pnpm verify:platform-spec-layout (writes src/generated/platform-spec-layout-report.json).

Related spec docs

• Domain
  Tooling

  Parent domain

Scope

Toolchain-facing package registry client contracts used by Beskid CLI and workflows. Package kinds defines library, template, and reserved tool roles on beskid.package.v1.

Feature index

Use the tiles below for normative feature contracts in this area.

Features

• Package kindsRegistry taxonomy for `packageKind` on `beskid.package.v1` — Standard surfaces for library, template, and tool packages.
• pckg client contractContract surface for the Beskid package registry client crate used by tooling workflows.