Phosphor docs
These pages are the user documentation for Phosphor, the local Mac app that holds your keys, your venue connections and your rules while an agent proposes moves and you click. They describe version 0.11.4, the version in package.json. The site at phosphor.money/docs is rendered from these files, and the four developer documents below sit beside them.
- Getting starteddownload, check the file, make or restore a wallet, back it up, move your vault to Touch ID, the lock and the brake.
- Connect an agentpick the agent you already use, start it in the chat or your terminal, what it sees and what it can never do.
- Moneythe two pockets, the vault and the allowance once it moves to Touch ID, top-ups and the sweep, deposit, swap, send, fund and withdraw from Hyperliquid, settling, fees and refusals.
- TradingTrade mode, a proposed trade, the click, armed plans and their session key, what runs after a lock.
- Policythe rules, the click threshold, the click after a web page, policy as sentences, changing a rule, the three verdicts.
- Securitywhat the agent can read, draft and never decide, why a web page is not an instruction, the window token, the Secure Enclave, the lock, the honest limits.
- Toolsevery MCP tool the app registers, grouped, one line each.
- Troubleshootinga late or unconfirmed move, a venue that does not answer, Gatekeeper, an agent that will not connect, the unlock queue, a refused address, moving the vault to Touch ID.
- Known limitswhat this build does not cover, what each limit means for your money, and what closes it.
- Changelogwhat changed in each version, newest first.
For developers
- Architecturethe two-process topology, module map, data flow and failure modes.
- Security modelthe threat model with the test behind each defence, the trust boundary, the three verdicts, fail-closed rules, the approval token and the v1 limits.
- Referencethe tool surface, policy as sentences, the first run, config, keys and signing.
- Check it yourselfthe wallet's seven security claims, each with the code that enforces it, the test that proves it and the command that runs it; checking your download and your vault on NEAR.