Essential session storage is required to sign in. Optional analytics remain off unless you allow them.
Pick a realistic customer workflow (support triage, onboarding review, compliance document review, incident response, or claims intake) and build a forward-deployment discovery package plus a working thin slice. Requirements: (1) write a workflow map with actors, systems, data sources, pain points, and current manual steps; (2) define ranked requirements, non-goals, success metrics, and acceptance criteria; (3) identify dependencies, owners, and risks; (4) build a small prototype that exercises one source, one user role, and one output; (5) document what is prototype-only versus what must be hardened for production.
Workflow map, actors, systems, data sources, pain points, requirements, non-goals, metrics, and acceptance criteria are concrete and customer-verifiable.
Prototype connects at least one realistic source to one workflow output for one user role, proving an end-to-end path rather than isolated UI or backend pieces.
Dependencies, owners, risks, assumptions, and prototype-vs-production gaps are documented with a credible next-step sequence.
Use this README structure to make the work reviewable.
DevPath fetches a read-only, size-capped snapshot. Submitted code is never executed.
# A customer workflow discovery and thin-slice prototype ## Goal Pick a realistic customer workflow (support triage, onboarding review, compliance document review, incident response, or claims intake) and build a forward-deployment discovery package plus a working thin slice. Requirements: (1) write a workflow map with actors, systems, data sources, pain points, and current manual steps; (2) define ranked requirements, non-goals, success metrics, and acceptance criteria; (3) identify dependencies, owners, and risks; (4) build a small prototype that exercises one source, one user role, and one output; (5) document what is prototype-only versus what must be hardened for production. ## Acceptance criteria - [ ] Discovery artifacts: Workflow map, actors, systems, data sources, pain points, requirements, non-goals, metrics, and acceptance criteria are concrete and customer-verifiable. - [ ] Thin vertical slice: Prototype connects at least one realistic source to one workflow output for one user role, proving an end-to-end path rather than isolated UI or backend pieces. - [ ] Scope and risk clarity: Dependencies, owners, risks, assumptions, and prototype-vs-production gaps are documented with a credible next-step sequence. ## Verification - [ ] Document installation and run commands. - [ ] Record automated checks and their exact commands. - [ ] Add representative output, screenshots, or a short demo where useful. - [ ] Confirm failure paths and known constraints. ## Decision log ### Decision title - Context: - Choice: - Alternatives considered: - Tradeoffs: ## Evidence - Link each rubric criterion to the file, test, or artifact that demonstrates it. ## Known limitations - List what is intentionally out of scope and what should be improved next.