RAPP/1 convergence.
Structural gates are live; authenticated acceptance is pending.
The target-owned strict core, exact /chat facade, and
compliance gates are available for review. Legacy installers, Azure
deployment, browser runtimes, and Copilot Studio bundles are retired and
are not current RAPP/1 distribution paths.
Installation is disabled until the owner-action gates in RAPP1_STATUS.md close.
About
Who it's for · how it gets adoptedLeadership one-pager
Workshops become production-bound agents. Same week. One file.
System integratorPartner one-pager
What partners receive, what they build, what they own — and why this is easier than a 20-page spec.
Workshop leadHow a session runs
60-minute customer session → working agent by week's end. The motion in detail.
Security reviewerSecurity & compliance
Local-first by design. What leaves the device, what doesn't.
Product
What it actually doesFAQ
Straight answers. How is RAPP different from GPT, Copilot, Studio? Why this instead of skills?
Reader in a hurryPlatform one-pager
The whole product in one page. Read in 90 seconds.
Buyer building scenariosUse cases
What teams actually build with RAPP, by industry and shape.
Speaker companionFAQ slide
Single-slide version of the FAQ for a presentation deck.
Release
What's shipped, what's nextReference
For buildersDocs
RAPP/1 authority and status, current guides, and clearly marked historical specs and host-onboarding files.
Curious contributorVault
Long-form decision narratives — why every non-trivial choice was made the way it was. Real Obsidian vault, static SPA viewer.
SourceGitHub repository
Structural core, pre-acceptance facade, retired legacy surfaces, and the auditable vault.
Pitch playbook
A 6-slide deck that frames RAPP as an adoption layer on top of whatever AI tools your team already pays for. Built for execs and team leads. Same product, different conversation.
Open the pitch ↗