How Blobify Works
Draft and published
Blobify separates:
- dashboard and editor outputs
- consumer-facing published outputs
Draft summaries include the system metadata the dashboard needs.
Published summaries stay model-configurable so frontend payloads stay lean.
Summaries and indexes
Blobify publishes:
- summaries for listings
- lookup indexes for exact field lookups such as slug
- list indexes for ordered pagination
Use:
- summaries for broad listing
- lookup indexes for exact lookups
- list indexes for ordered feeds
Routing
Routing is published separately from content.
That keeps:
- content semantic
- routes rebuildable
- generated clients deterministic
Assets
Assets have:
- a metadata JSON document
- an asset catalog entry
- the original file
Content summaries store asset references, not final URLs.
Clients resolve those references using asset metadata.
Permissions
Members and API keys use the same access model:
- role
- spaces
Automation behaves like a service member instead of a separate permission system.