Skip to content

Document Space 0 / stub-asset storage semantics (blocked on design decisions) #12

Description

@tomcrane

Since protagonist's May 2026 migration (StopSpaceZeroCustomerStorage), Space 0 is a real per-customer space whose storage row holds stub-asset storage; the customer-wide aggregate lives on the Space=NULL row. /customers/{customer}/spaces/0/storage is therefore a live, user-visible resource with a distinct meaning — and the docs say nothing about it.

Ruled in hygiene session 1 (card ACC-17): leave undocumented for now — stub assets are not yet a customer-facing concept, and a space-0 note would dangle without that context.

Before this can be documented, design decisions are needed (protagonist/iiif-presentation owners):

  • What can an end user actually do with Space 0 — and what should they be allowed to do?
  • Stub assets follow naming conventions used by iiif-presentation; are those conventions part of the public contract?
  • Does asset creation in Space 0 need additional enforcement — validation of those conventions, or complete prevention, or something else?

When those are settled, document: what Space 0 is, what /spaces/0/storage reports, and whatever creation rules apply (storage.mdx + space.mdx, plus sample parity per XC-10).

See https://github.com/dlcs/protagonist/blob/develop/docs/rfcs/022-stub-assets.md and https://github.com/dlcs/iiif-presentation/blob/develop/docs/rfcs/0006-adjuncts.md

🤖 Generated with Claude Code

Activity

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions