Documentation

Read the source.
Trust the source.

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.

30-second quickstart

On the laptop where you’ll evaluate Vertirite:

# 1. Install the desktop app
brew install --cask vertirite          # macOS (after Day 4)
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:
git clone https://github.com/SurgeXi/Vertirite.git
cd Vertirite
./run-surge-shell

# 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.

The desktop install paths above light up Day 4 of the seven-day launch (5/4). Until then, request the dev build via [email protected].

The docs that matter

All public; all in the repo. Each link opens GitHub.

Start here

Architecture overview ↗

Repo layout, what lives where, which repo to edit when, end-to-end request path through the broker, audit log, and capability registry.

Seven-day launch plan ↗

Day-by-day path from build to first customer. Daily exit gates; slip rule documented.

Brand & color system ↗

Single source of truth for Vertirite palette + typography. Status-color delineation across approved / pending / blocked.

Product

Vertirite Theatre ↗

How the live demo works. Event-stream contract. Scenario authoring. Real-vs-scripted honesty panel.

Platform matrix ↗

Which OS / form-factor ships when. Tier-1 (mac+win at launch) → Tier-4 (Vertirite Notify mobile+watch companion, post-launch).

Testing standard ↗

100% pass rate before any release. Format every test report follows. Stress-test categories. CI integration.

Reference

Repository on GitHub ↗

SurgeXi/Vertirite — currently private. Request access for evaluation.

Test report — 2026-05-01 ↗

Day-1 launch testing — 28/28 scenario runs green; 1 bug found, fixed, re-verified.

Site proofread — 2026-05-01 ↗

P0/P1 findings against the marketing landing page; tracked into the seven-day plan.

Deeper material on request

For evaluators going past the public docs, we share — under NDA where appropriate — the following:

  • Capability registry schema — the YAML format that drives every authorization decision.
  • Audit-log signing model — how the per-tenant key chain works, how rotation works, what a tampered chain looks like.
  • Mode-authority protocol — the out-of-band channel that the AI cannot reach.
  • Pilot deployment runbook — what we do at the customer site for an on-prem trial. Windows Server, Linux, hybrid.
  • Threat model + last pen-test report — when commissioned (first scheduled Q3 2026).
  • SOC2 Type 2 in-flight letter — once Drata onboarding completes (Day 5 of launch).
  • BAA template — for medical-vertical evaluators.
Request technical docs