The idea got narrower before it got better
Stage 1 began with a broad prompt: build an AI agent. I explored security-intake and governance-assurance directions first, but I could not find a durable edge strong enough to justify another general-purpose agent. Crypto-tax reconciliation was different. People with activity across wallets, bridges, exchanges, and DeFi protocols already spend real time and money cleaning up incomplete records, and CPAs need evidence they can inspect.
That led to Triage: an evidence-first reconstruction tool that organizes what can be supported, labels what cannot, and leaves the final review with a human. The key product decision was not “use an LLM.” It was to make uncertainty visible instead of hiding it.
The product contract: cited evidence, honest gaps, and no invented cost basis.
What ClawUp changed
ClawUp turned the internal agent concept into a public Telegram experience. That mattered because a product cannot be evaluated only through its repository or architecture. A user needs a clear entry point, a concrete task, and an output they can challenge.
For the public demo, I chose a deliberately narrow flow: inspect a published wallet on GOAT Network using public, read-only data. The prompt explicitly forbids signatures, writes, transfers, approvals, and requests for secrets. That gives people something real to test without pretending that a single wallet scan can produce a complete tax result.
The build, step by step
- Define the job. Reconstruct messy crypto activity and produce evidence a taxpayer or CPA can review.
- Define the boundaries. Never file, sign as a preparer, move funds, request secrets, or invent missing basis.
- Give the agent durable context. Product identity, users, methodology, safety rules, and known limitations live in project memory rather than in one oversized prompt.
- Create one public test. The Telegram demo uses a known public address, chain 2345, and a reproducible read-only request.
- Separate evidence from interpretation. Observable balances, transactions, contracts, and hashes should be distinguished from hypotheses and unresolved gaps.
- Publish the limitations. Wallet ownership, off-chain records, historical valuation, complete cost basis, and final tax treatment still require more evidence and human review.
Where GOAT, ERC-8004, and x402 fit
GOAT Network provides the environment for the public wallet demonstration. ERC-8004 and x402 shape the longer-term product design around agent identity, report provenance, and per-report settlement. Those rails are useful only when they reinforce the evidence trail; they are not substitutes for a correct reconciliation.
The current public experience should therefore be read as a constrained product demo, not a claim that every identity, attestation, payment, or tax workflow is production-complete. That distinction is important to how I am approaching Stage 2.
What the demo proves — and what it does not
It can demonstrate
- A public user can reach Triage through Telegram.
- The agent can receive a constrained wallet-analysis request.
- The result can distinguish traceable observations from unresolved information.
- The interaction can preserve explicit read-only safety boundaries.
It cannot establish by itself
- Who owns the wallet or why each transaction occurred.
- Records held only by centralized exchanges or other off-chain systems.
- Historical fair-market value and a complete, supported cost-basis history.
- The correct final tax treatment or readiness to file.
What Stage 2 means for Triage
Stage 1 proved I could define and ship an agent. Stage 2 is about learning whether it can become a business. That means talking to crypto CPAs and DeFi-heavy taxpayers, documenting real workflows, measuring where the reconstruction saves time, and publishing useful material that answers exact questions. The website, FAQ, demo walkthrough, and this guide are part of making the product understandable before asking anyone to trust it.
The next evidence I care about is not another feature list. It is whether a real user can bring a messy case, inspect Triage’s evidence, challenge its gaps, and say the resulting workpaper made review easier.
Try the same public test
The live-demo section publishes the wallet address, chain, safety rules, and exact prompt. Use only public data. Do not share a private key or seed phrase, and do not approve a signature or transaction.
Build your own agent with ClawUp
If this build pattern is useful, you can explore ClawUp through Triage’s assigned referral link. Using the link may be attributed to this project’s Stage 2 ecosystem contribution.