Every architectural decision, every test report, every security control. In the repo, in plain Markdown, dated and committed. CISOs read this before booking the demo.
On the laptop where you’ll evaluate Vertirite:
# 1. Install the desktop app
brew install --cask vertirite # macOS (early access)
choco install vertirite # Windows
appimage-install Vertirite-0.2.0.AppImage # Linux
# 2. Open Vertirite, click ▶ Vertirite Theatre in the sidebar.
# 3. (Optional) Live-mode requires a local broker.
# The broker bundle ships with the desktop install —
# request early access via [email protected].
# 4. From your own AI / RPA / cron stack, point at the broker:
export SURGE_BROKER_URL=http://127.0.0.1:8220
# Then send actions through surge-agentd's CLI or HTTP API.Desktop installers are in early access. Request the current build via [email protected].
Documentation is being finalized for public release. Click any card to request the current version by email — [email protected].
Start here
Repo layout, what lives where, which repo to edit when, end-to-end request path through the broker, audit log, and capability registry.
Day-by-day path from build to first customer. Daily exit gates; slip rule documented.
Single source of truth for Vertirite palette + typography. Status-color delineation across approved / pending / blocked.
Product
How the live demo works. Event-stream contract. Scenario authoring. Real-vs-scripted honesty panel.
Which OS / form-factor ships when. Tier-1 (mac+win at launch) → Tier-4 (Vertirite Notify mobile+watch companion, post-launch).
100% pass rate before any release. Format every test report follows. Stress-test categories. CI integration.
Reference
SurgeXi/Vertirite — currently private. Request access for evaluation.
Day-1 launch testing — 28/28 scenario runs green; 1 bug found, fixed, re-verified.
P0/P1 findings against the marketing landing page; tracked into the seven-day plan.
For evaluators going past the public docs, we share — under NDA where appropriate — the following: