Glossary

Account. Your identity on the hub. One account signs you in to every site in the family.

Acting token. A key a persona holds so that it can act on your behalf. Every consequential thing it does with that key is checked against what you have allowed.

Admin workspace. The workspace the people who run the hub use to operate it.

Agent. A program driven by an AI model that reaches the hub over MCP, with the tools the hub gives it.

All Data. A browser over every table in your workspace. You open a schema, pick a table and edit its rows in place.

API. The way a program reaches the hub instead of a person clicking. The hub's REST API is documented in the reference on the help site.

API token. A personal key, starting with tmp_, that lets a program act as you. It can be limited to a scope, and it is the key an agent brings to the hub.

Application. A piece of software that belongs to one of your products and reaches the hub with tokens of its own.

Artifact. A file or a link attached to a project.

Bucket. A named place your data is grouped under, the way a folder groups files. A bucket does not hold data itself; it gives data an address and a line of permission.

Bucket type. What kind of thing a bucket holds, such as documents or notes.

Client auth. The sign-in your product offers its own users, run by the hub.

Community. A public place on the hub where people talk, with discussions, messaging and notifications.

Dashboard. A view of the sites and endpoints you monitor, and whether they are up.

Tech Detail. The card on each feature's page that says why the feature is built the way it is.

Ecosystem. The boundary that keeps one owner's data apart from everyone else's. Your workspace has one. Each product you build is one too, nested under yours. A persona is one as well.

End user. A person who uses one of your products, as distinct from you, the developer.

Environment ladder. The order a repository moves through in Shipr: testing, then staging, then production.

Feature. One thing the hub can do for a workspace, such as keeping documents or running personas.

Feature flag. A switch inside a product that turns part of it on or off for its users.

Feature rail. The list of the features a workspace has, from which you open each one.

Grant. Permission given to someone, or to a token, over something: a bucket, a feature area, an item.

Help site. The site that holds this documentation and the generated references for the API and MCP.

Integration. A connection from a product to an outside service.

Iteration. A stretch of time work is planned into, with a start and an end.

Knowledge. What a persona has been given to read and draw on when it answers.

LLM provider. The service that runs the model behind a persona, connected by you.

MCP. The Model Context Protocol: how an AI agent connects to the hub and calls its tools. The hub's MCP server is documented in the reference on the help site.

Member. A person who belongs to a workspace, an organization or a team.

Memory. What a persona keeps from past conversations.

Monitoring. Watching your sites and endpoints, and showing their state on a status site.

Organization. A group of people who own things together. An organization has a workspace of its own.

Persona. An AI character you design: its prompt, its knowledge and memory, what it may do and the model that runs it.

Principal. Whoever a request is made as: you, an organization, a token, or a persona acting for you.

Product. Something you build and offer to end users. A product is an ecosystem with its own users, applications, billing, flags and integrations.

Program. A named group of related projects.

Project. A place where work that belongs together is planned and tracked.

Registry. A public directory you publish, which others register in. The persona registry is one.

Research. A searchable notebook of markdown documents, kept in versions.

Saved view. A filter and a layout of a project board that you name and return to.

Scope. The parts of the hub a token may reach. A token with no scope has its owner's full authority.

Server bag. A set of values a product keeps on the server for its applications to read.

Session. Being signed in. One session carries across every site in the family.

Settings. Your account, security, appearance, notifications, usage and subscription.

Shipr. The deployment console: where you register repositories and move them up the environment ladder.

Status. A column on a project board, named by you, and sorted by the hub into backlog, to do, in progress, done or cancelled.

Status site. The public page that shows whether the sites you monitor are up.

Storage. Where your data is kept and where you decide who can reach it.

Storage token. A key, starting with adh_, bound to one bucket and reaching nothing else.

Team. A roster of people. A team owns nothing; it is given access to things.

Template. A saved shape for a new project: its statuses, fields and layout.

Token. A key that lets something that is not you reach your data. See API token, storage token and acting token.

Work item. One piece of work in a project.

Workspace. The place you work in. It is yours, an organization's, or a team's, and everything you do in the hub happens inside one.

Workspace role. A named set of permissions over the feature areas of a workspace, given to a member.