Repository navigation
08. Mockups
| User Story ID | User Story | Mockup | Description |
|---|---|---|---|
| US-1.1 | As a staff member, I want to upload a client’s source documents (sales transcript, intake answers) into the Brain component, so that the onboarding agent has real, client-specific information to work from. | Briefly describe what the mockup shows and how the feature works. | |
| US-1.2 | As a reviewer, I want the system to keep versioned history of client profiles and playbooks, so that I can see what changed and when, rather than only ever seeing the latest version. |  |
Shows each client’s current progress. |
| US-2.1 | As a developer, I want a minimal script that calls the selected AI provider with a basic prompt, so that we have a working baseline before adding any Brain context. | Briefly describe what the mockup shows and how the feature works. | |
| US-2.2 | As a developer, I want to compare the baseline prompt against a Brain-assisted version (hand the AI some of FA Systems' own business knowledge), so we know if business context actually improves the output before putting more work into it. | Briefly describe what the mockup shows and how the feature works. | |
| US-3.1 | As a staff member, I want to upload a client's sales transcript and intake answers through the app, so I don't have to run anything manually. | Briefly describe what the mockup shows and how the feature works. | |
| US-3.2 | As a reviewer, I want each field in the draft profile linked to where it came from, so I can check the AI didn't make anything up. | Briefly describe what the mockup shows and how the feature works. | |
| US-3.3 | As a reviewer, I want missing or conflicting info flagged on the draft, so I know what needs my attention. | Briefly describe what the mockup shows and how the feature works. |