Projects
The label by which keys are grouped among themselves: creating a project, moving a key into one, what its card shows, and how archiving differs from deleting.
What a project groups
A project is a label over keys and never a funding container. A key pays with whatever is chosen on the key itself — the account package or the balance — and a project does not change that: moving a key into a project or out of it leaves that choice untouched.
The point of a project is elsewhere — to keep keys and their spend together, so that "what does this piece of work cost" is answered by one card instead of by adding rows up by hand.
A project has three properties of its own: a name (1 to 120 characters after trimming spaces, counted in characters), a color from the palette, and whether it is archived.
How a key is issued → Where to watch spend →
Make a project
- Create the projectA name and a color; that is all it takes.
- Move keys into itOn the keys screen, in the project cell. A new project can be made from right there, without leaving the list.
- Watch the spendThe project's card shows its keys and its share.
A key sits in at most one project, and "no project" is a legitimate state rather than an unfilled field. The target project must belong to the same organization and must not be archived.
The name and the color are editable afterwards. The edit checks the version it read: two concurrent edits cannot both win, and the loser is refused rather than quietly overwriting a name it never saw.
What the card shows
A project's card counts its wallet spend for the current month and its share of every project's wallet spend, as whole percentages.
The wallet half only — and that is a limit of substance rather than an omission. Spend from the balance is in dollars, spend from the package is in package tokens, and the platform publishes no rate between those units. A sum of two units would be a figure with no unit, which is why there is none.
The key list inside a project shows: name, status, the key, usage, package and project. Keys can be viewed grouped by project or as one flat list.
Archiving and deleting
Two different actions, and they are worth keeping apart.
| Archive | Delete | |
|---|---|---|
| What it does | hides the project from cards and filters | removes the project for good |
| What happens to the keys | they stay in it and keep working | they are left without a project and keep working |
| Reversible | yes | no |
Archiving moves nothing: the project's keys stay in it and go on working. What it stops is one thing — an archived project is no longer offered as a target for moving keys into. It can be un-archived at any time.
Deleting, in the same transaction, leaves every key that named the project without one. The keys are not deleted with it: a project is a label, and removing a label does not remove what it was stuck to. It is the one action on the screen that asks twice — and it asks because it is irreversible.