Converted "fundraising" into a concrete list of what funding actually pays for. Not "growth" or "hiring." Specific things: security hardening, partner-proof onboarding, and reliability work. If someone asks "what does the money do," the answer is a list of engineering tasks, not a pitch deck slide about TAM.
Cleaned the narrative distinction between Pilot learning and Alpha readiness. Pilot is free, low-risk, and designed to build trust. Alpha is where real actions hit real systems with real consequences. The gap between those two is entirely about hardening, not features.
The Alpha plan is now concrete: hardened integrations with real API providers, constrained real-mode execution with strict allowlists, mature execution semantics with proper claim/finalize/timeout handling, and receipts and controls that meet production operability standards.
Tightened the internal definition for what "ready to deploy" means. It is not a feature checklist. It is security plus operability. Can we guarantee that a misconfigured policy does not cause a production incident? Can an operator understand what happened from the receipts alone? Those are the gates.
The story is now: learn safely in Pilot, then harden for real deployment with funding.