Skip to content

The pkg provider has no design document: 3.5.x has an entry for every provider but this one #868

Open

Description

@David-Noble-at-work

Feature: #836 — the pkg provider

Found 2026-09-08 during #647, the sealed-contract documentation pass: every provider has a docs/architecture/3.5.x-<name>-provider.md except pkg. Its resource, its package-manager delegation, its purl surface, and its receipt shape are described nowhere, so the sealed-shape sentence #647 added to eight documents has no home for the ninth.

pkg is not a small provider: eight announced methods, the platform's package-manager layer beneath it, a sealed pkg.Resource, and two open high-priority bugs against its identity surface (#813, #814).

Work

  1. docs/architecture/3.5.17-pkg-provider.md in the form the others take: thesis, design points, API surface, the resource's sealed shape and addressing, the receipt, and the platform delegation.
  2. Its status file.
  3. 3.5-provider-catalog.md's pkg row links it.

Acceptance

Plan and design documents

Kind Document
Plan no branch has opened; the plan arrives with it
Design docs/architecture/3.5-provider-catalog.md
Design docs/architecture/4.3-resource-registration.md

Epic: #815 · Feature: #836

Activity

  1. David-Noble-at-work commented on Sep 9, 2026

    @David-Noble-at-work
    ContributorAuthor

    The design document gains a Package mapping section, ruled 2026-09-09 on #872: how the broker
    decides that two manager-specific names are one project, and where that answer comes from. The data
    side is devlore-registry#91; this document
    states the consumer side (lookup against the local registry clone at plan time, the neutral key
    pkg:generic/<name>, the learned tier's promotion path) and the tasks under #836 follow it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Epic:ProvidersThe provider surface: one feature per providertaskImplementation work item

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions