Meet your unit. Set its boundaries.
A practical guide to the TAPPET command workspace: configure a unit, review a scenario and test a protocol against your own price data.
Your first session
Open the Command app. A local unit profile is created automatically, so you can explore every tab without a wallet. Drag the unit in the Hangar, run its diagnostic, then move to Protocols to save a rule set. Your changes remain on this browser and device.
Five configurable protocols
Accumulate allocates a fixed amount at an interval. Balance compares a position with a target weight. Guard tests a take-profit and stop-loss around an initial entry. Trend compares a closing price with a trailing average. Physical AI combines a recurring NVDA allocation with a dip trigger. Enabled protocols are available to the scenario reviewer; any protocol can be inspected through historical testing.
From proposal to recorded result
In Command Center, enter an asset, a protocol, an amount, a price and estimated slippage. Review scenario checks the operating mode, enabled protocol, whitelist, per-action cap, daily budget and slippage tolerance. Failed checks stop the scenario. Supervised mode asks for operator acceptance; Autonomous mode records passing scenarios immediately. Both modes are local calculations, not live trading or remote AI inference.
Shield limits
Set a per-action amount, daily spending cap and slippage tolerance. Choose at least one allowed asset. The daily cap must not be lower than the per-action cap. Accepted local scenarios count against the UTC day’s test budget. Saving new limits cancels a pending scenario; accepted scenarios are rechecked at acceptance. Standby cancels pending scenarios and pauses new reviews.
Import a daily price series
Historical Testing accepts a CSV with the exact header date,close and between 2 and 366 data rows. Dates must be real calendar dates in YYYY-MM-DD format, strictly increasing and unique. Prices must be positive. The file stays in your browser. The calculator uses saved protocol settings, a chosen starting value and a 0.10% cost per modeled fill. Spread, execution slippage, taxes, network fees and intraday price paths are not modeled. A rejected action is counted separately.
Black Box and Passport
The Black Box records local configuration changes, diagnostics, proposals, rejections and accepted scenarios. Filter by role, search text, inspect a record or export the last 300 stored events as JSON. Passport shows the local serial and settings. Its export is a configuration file, not a blockchain credential or a signed attestation.
Optional wallet connection
Connect a supported Solana wallet, such as Phantom or Solflare, to display its public address in the local Passport. The wallet connection requests your public key only. It does not ask for signatures, approvals, deposits or transaction broadcasts. Disconnect removes the active address from the page; the profile remains on the device.
Network and contract status
Solana is the intended network context. TAPPET has no published SPL mint, Solana program, vault, registry or execution adapter in this release. No external project’s contracts or wallet balances are reused. Deployment details must be independently configured and verified before live funds can be handled.
The robotic interface
The unit is rendered with Three.js as a procedural chrome body, curved visor, emissive eyes and articulated feet. Pointer movement controls its gaze, dragging rotates it, and expression controls expose six states. The landing page combines a shared grid, depth layers, focus transitions and a sticky anatomy view. Reduced-motion preferences reduce ambient animation.
Integration boundaries
The shipped workspace has no public trading API or remote AI backend. Its model module handles rule evaluation and historical replay locally. Future adapters must provide independently verified prices, wallet-owned permissions, transaction simulation and receipts. A configured provider is required before an AI response or a blockchain execution can be described as live.