Skip to content

T7-2 DECISION: ModelManifest / AdapterManifest vs SourceOSModelCarryRef #242

Description

@mdheller

Part of #241 (Tranche 7). Deferred from #240 pending a decision — not a mechanical schema add.

Spec §XIV T7-2 calls for schemas/ModelManifest.json + schemas/AdapterManifest.json (content-addressed store manifests: architecture, quant, tokenizer ref, signature; LoRA base-digest/rank/alpha/eval-report).

Conflict with what already exists:

  1. SourceOSModelCarryRef already models the governed model/adapter reference (carryPolicy, cachePolicy, mutableModelState:false, router/governance refs). Is a store-level ModelManifest a genuinely new type, or an extension of the carry-ref?
  2. AdapterDescriptor already exists and means a connector/actuation adapter (api/cli/sdk/event/file). A LoRA "AdapterManifest" would collide in name/concept. Proposed rename: ModelAdapterManifest.

Decision requested:

Blocks the store/catalog wiring in source-os T7-11.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions