What these pages are

Tamias runs a Safe for a team: the batches you record, the loops you save, the people you pay, and the swaps in between. Every feature has one page here, and every page has the same four parts.

• What it does. The feature in one paragraph.
• What could go wrong without it. The mistake or the attack it exists for.
• What you see in the app. The screens, the warnings, and the exact words.
• What it does not do. The edge of the feature, stated so you do not assume it.

Nothing on these pages describes something that is not built. Where a feature has a known gap, the page says so.

The pages

• Naming an address: a label for an address, and the check the app asks for before it trusts one.
• Workflows: a batch your Safe already proposed, saved under a name and re-run at today's prices.
• Automating a workflow: let any one signer run a workflow without collecting signatures, only that workflow, within limits the chain enforces.
• API keys: give a script a key that reaches one Safe's workflows, and nothing else.
• Run a workflow from code: check a condition in your own code, ask Tamias for the run, and send it from a wallet your code holds.
• The Recorder: click through a dApp as your Safe, and get the batch to sign.
• Payments: a weekly or monthly run to a fixed list of payees, signed by the owners, gas paid for you.
• Swaps: a swap from the Safe, proposed like any other transaction.
• Your assets: what a Safe holds, read from the chain and priced only where the price can be stood behind.
• The activity log: every change anyone made in the organization, one line each, never edited.
• Organizations and collaborators: who can see your Safes, and what an admin can do that a viewer cannot.
• The phone: the companion app that tells you when a Safe needs you, and holds no keys.
• Auto-pay: the subscription paid from your Safe on payday, after one signature, to Tamias and nobody else.
• Our contracts: the two contracts Tamias deployed, what each can and cannot do, and their source on every chain.