CATALOG · GOVERNANCE AND CONTEXT
One catalog.
The whole brand.
The governance and context layer for your brand: everything your organization holds, governed in one place, and read the same way by people, AI agents and code.
- Catalog
- Corporate
- Brands
- Acme
- Collections
- Assets
- Images
- logo-primary.svg
- wordmark-white.png
- Videos
- Fonts
- Documents
- Portals
- Q4 Campaign
Corporate Assets Images
logo-primary.svg
AssetCurrentacme/corporate/asset/logo-primary
OverviewLineageAccessActivity
Changing logo-primary.svg reaches 7 things downstream, in 2 projects.
One hop each way. + on a card's outer side brings the next hop; cards can be dragged.Illustration of the app · Acme and its numbers are made up
WHAT IT DOES
Know what you have.
And who may use it.
Assets say what exists. The catalog says where it comes from, what uses it, who can reach it and what was done with it. In the open-source core: on Cloud and self-hosted alike.
One catalog
Every brand, rule, guideline page, collection, asset and portal, in one tree: projects, then a folder per type, assets folded by Images, Videos, Audio, Fonts, Documents and Other. Each has an address, and a button back to its catalog page wherever the app shows it.
One search
Words and filters in one box:
type:asset,rule,project:corporate,status:current,tag:,admin:me.uses:andusedby:take an address and follow the links.Lineage and impact
What it comes from, what uses it: an asset to its replacement and what was made from it, the brands whose rules name it, the collections it is in, on to the portals. Before you change it, you know what it reaches.
Access in one place
Viewer, Contributor, Editor or Admin, granted on the organization, a project, a brand, a collection or one asset. The Access tab names the grant behind every role, and admins grant there.
Activity and audit
Who did what, newest first: an asset's versions and reviews, a brand's edits and releases, people and agents alike, each under its own name.
Context for agents
The same catalog over MCP. Before it acts, an agent knows what exists, whether it may be used, and by whom.
ADDRESSES AND QUERIES
Everything has
an address.
Organization, project, type, name: acme/corporate/brand/acme reads the same in the app, the API, the CLI and an agent's tool call. Ask with words, filter with the rest.
- Brands, rules, guideline pages, collections, assets, portals
uses:andusedby:follow lineage in a search- Only what you may see comes back
type:asset logo status:current
the current logos
type:asset,rule project:corporate
assets and rules of one project
uses:acme/corporate/asset/logo-primary
everything that uses the logo
usedby:acme/corporate/brand/acme
everything the Acme brand uses
admin:me
what you administerLINEAGE AND IMPACT
Change it
with your eyes open.
Every card in the graph says status, version, license and expiry, so a replaced logo or a lapsing license shows where it is used. A brand leads to its forks; collections and brands lead to the portals that show them.
- One hop each way, the next one a click away
- "Changing X reaches N things downstream, in M projects"
- Then
check_userefuses a replaced or expired asset, and names the replacement
- photo-team-2025.jpgExpires in 9 days
- logo-primary-2023.svgReplaced by v2
- Press portalPublic
ACCESS IN ONE PLACE
Who can reach it,
and why.
Grants reach down, and the highest on the path wins. A grant is held by a person, a group, or another project: share a brand, a collection or an asset into it, and its members read it as Viewers there while it is edited at home.
- Viewer, Contributor, Editor, Admin
- A private object turns away the roles from above
- An agent's key is held to its person's role
- DanaPerson · Admin of the organizationAdmin
- Brand teamGroup · Editor on the project CorporateEditor
- SamPerson · Contributor on the brand AcmeContributor
- Sam's agentAgent key · held to Sam's roleContributor
- Q4 CampaignProject · shared into it, read thereViewer
CONTEXT FOR AGENTS AND CODE
The same catalog,
every way in.
The app reads the catalog through the public API, and so do your scripts, the CLI and your agents over MCP. An agent asks what exists, what uses it and who can reach it before it acts.
search_catalog,describe_object,lineagewho_can,share_object- Held to the role of the person who connected it
GET /api/v1/catalog?q=type:asset logo status:current
GET /api/v1/catalog/{ref}/lineage
GET /api/v1/catalog/{ref}/access
$ npx artbucket catalog search "logo type:asset"
$ npx artbucket catalog lineage acme/corporate/brand/acme
$ npx artbucket catalog access acme/corporate/asset/logo-primary
$ npx artbucket share acme/corporate/brand/acme --to q4-campaign
Acme is shared into Q4 Campaign, as Viewer: kept and edited in CorporateREAD MORE
Governed once.
Read everywhere.
A LITTLE ORDER. A LOT OF POSSIBILITY.
Everything you hold.
Governed in one place.
Free to start, on Cloud or on your own servers.
Start free