Skip to content

Prototype guide

Explore all 25 screens and six workflows.

This is a navigable prototype with realistic demonstration data. Changes you make in the practitioner app are saved in your browser — use “Reset demo data” in the sidebar to start again.

Screens

Workflows

Each workflow shows how the screens connect. Click through the steps in order.

A

New client

Create a client, enter birth data and generate their natal chart.

  1. 1 Create client
  2. 2 Enter birth data
  3. 3 Generate natal chart
  4. 4 Save chart
  5. 5 Open client profile
B

Chart analysis

Review a client’s chart and record an observation against it.

  1. 1 Open client
  2. 2 Select chart
  3. 3 Review placements & aspects
  4. 4 Add observation
  5. 5 Saved to chart history
D

Recorded reading

Record a chart walkthrough and deliver it to the client portal.

  1. 1 Open client chart
  2. 2 Launch Recording Studio
  3. 3 Record interpretation
  4. 4 Review recording
  5. 5 Deliver to client portal
E

Written reading delivery

Upload a PDF reading and follow it through to the client.

  1. 1 Open Reading Delivery
  2. 2 Select client
  3. 3 Upload PDF & add message
  4. 4 Send
  5. 5 Client receives notification
  6. 6 Client opens reading
F

Knowledge retrieval

Search your observations by configuration and jump to the source.

  1. 1 Search notes
  2. 2 Filter by configuration
  3. 3 Open observation
  4. 4 Go to related chart
  5. 5 Go to client

Simulated functionality

Throughout the app, simulated features carry a dashed amber “Simulated” label. The full list, with what each would need to become functional, is in SIMULATED_FEATURES.md in the repository.

Chart calculations

Positions come from a clearly labelled demonstration engine behind an abstraction layer. A production adapter for an existing ephemeris-based engine is needed.

AI assistant

Responses are scripted from the chart data and saved observations. Requires an LLM integration with retrieval over the practitioner’s records.

Recording Studio

Recording uses the browser where permitted, otherwise a simulated timer and preview. Needs media capture, upload and transcoding services.

File uploads & delivery

Files are not uploaded; deliveries update local state only. Needs object storage, signed URLs and an email/notification service.

Authentication

Sign-in, sign-up, verification, reset and invitations are visual flows only. Needs an identity provider and role-based access.

Data persistence

Demo data lives in the browser (localStorage) and can be reset. Needs a database and API matching the store’s actions.

Import/export, billing, calendar sync, reminders

Shown as interface only; integrations are future work.