This is a working example of an APR project space: a public research explorer, a member assistant named APRIL, private conversation history, and personally owned scenario directories.
1. Explore before signing in
Choose a payment archetype or change the four design dimensions. Compare configurations and illustrative shocks. The synthetic hospital and formulas are explanatory assumptions, not validated predictions, study findings or official recommendations.
2. Activate APRIL in the bottom corner
Select the small illustrated avatar. Enter your full name, email and phone number, and confirm that you are an APR member. Twilio sends a six-digit code. Entering a name or phone number alone never grants write access.
The existing phone service currently accepts US and Canadian numbers. Verification proves control of the phone; name, email and APR membership are self-reported. There is no separate email verification or roster check in this flow. Existing per-number and service-wide limits apply.
3. One person, with continuity
A successful phone sign-in reuses your existing identity when the system recognizes you. A new number creates a private relationship record stewarded by Blake. APR registration adds or reuses your person bead: a persistent space that links your profile, project work and conversations.
On this browser, a device-bound sign-in cookie remembers you for up to 30 days. On another device, verify the same phone again. History belongs to your account, not your display name or a temporary browser identifier. Clearing browser storage does not delete your saved history.
4. Ask questions, then publish deliberately
APRIL can discuss the project's published context and help you understand alternatives. Web conversation history is saved privately under your person bead. Service failures are shown as errors, never substituted with a scripted answer claiming success.
Adjust a scenario in the explorer, then open Publish your current scenario in APRIL. The site suggests a first-lastname directory if available. You can choose another available name before your first publication. The server rechecks and reserves the name when you publish.
Your directory is your blast radius: the only project directory this publishing flow lets you update. It does not grant access to the main project, server code, or another person's work. Published scenario parameters and notes are public. Do not put personal or patient information in them.
This release publishes scenario configurations, not arbitrary executable code. APRIL does not silently edit or deploy changes during a conversation.
5. Call APRIL about an APR project
Call 505-GIS-FISH (505-447-3474) from your registered phone and ask for APRIL and the APR project you want to discuss. Project access is drawn from the APR project catalog and your membership permissions; adding a project does not expose unrelated private material.
Phone conversations use the existing voice service. Caller recognition alone is not permission to publish changes. Web publishing still requires your authenticated browser. Phone and web use the same person identity; their transcript records may be maintained separately by the voice service.
6. Where the information lives
- Public: the explorer, this guide, the project catalog and intentionally published scenarios.
- Private: contact details, relationship records, member registration and web conversation history. The member and Stephen can access their project history; other members cannot.
- Infrastructure: browser-first pages, with server-backed verification and persistence. Twilio handles phone verification and the voice service handles calls. The project's configured AI service processes submitted questions and public project context; do not submit sensitive personal or patient information.
7. Project hosting and releases
alliancepolicyresearch.acequia.org is a persistent public copy on Cloudflare. Public pages remain available when the authoring computer is offline. Releases are copied explicitly, not continuously. Register, chat and publish at the original stephenguerin.live member workspace: a static replica is not an identity or private-history replica.
Hosting and privacy boundary / Cloudflare snapshot version
Technical README / Release version / Project bead (sign-in required)