Build progress
ActiveUser stories shipped, in flight, and ahead — grouped by epic. Sourced from data/user-stories/user-stories.md.
Open →ReCity pilot internal · open to anyone today · gated to Connected Service Provider Admins in P3.
Pilot build process
Workflows + observability on the path to launch.
Each card tracks a stream of work the pilot team is running with ReCity providers. Open the active ones to do the work; the rest are being tracked manually until their underlying tooling lands.
Automated tests
ActiveEvery test CI runs, grouped by feature. Counts mirror the most-recent CI run.
Open →Populating services
ActiveCapture the canonical service description, eligibility, fees, hours, and accessibility for every connected provider.
11 of 7814%
Identifying champions
Manual trackingName the lead person at each provider org who will own the relationship through pilot launch.
Onboarding organizations
Manual trackingConfirm the org's services, capacity model, and consent posture; sign the pilot MoU.
Setting up users
Manual trackingProvider magic-link auth (P2) and resident register + onboarding (P3a) are both live. Bulk invite UI for the pilot team still manual until P3b ships the admin console.
Confirming intake forms
Manual trackingReview each provider's required intake fields. Lands as a real builder UI in P3 alongside CSPA edit.
Testing workflows
Manual trackingWalk every connected provider through anonymous-referral receipt, state-machine transitions, and notification routing.
Training users
Manual trackingRun hands-on training with each provider's champions before they go live with real residents.
Soft rollout
Manual trackingGradual go-live with the first wave of providers + a small resident cohort before the full pilot launch.