Roadmap
Roadmap
FPR Monster v1 is moving from planning-only pages toward verified commerce, source-backed public claims, and practical support systems. The rule remains the same: visible progress can move quickly, but sensitive programs stay blocked until the safety, partner, legal, insurance, staffing, facility, consent, and review gates are real.
Current Verified Status
Evidence is tracked locally in the FPR shop cleanup and mockup rollout reports. This public page summarizes the state without exposing internal credentials, raw logs, or private operator details.
Roadmap Overview
Now
- Keep the Monster v1 planning pages public-safe and boundary-forward.
- Operate FPRMerch as the live shop front while the ranch site points visitors to the shop cleanly.
- Continue Abbe-first product cleanup: no duplicate public products, no Big Daddy/placeholder merch, no default Printify people as final presentation.
- Use approved product-only flat lays as featured images and Mike/Abbe lifestyle images only as supporting gallery images.
- Keep public support asks tied to concrete needs, not open-ended program promises.
Next
- Finish the remaining 86-product mockup rollout in 5-10 product batches with a database backup before each WordPress media update.
- Verify every updated product page and the shop grid after each batch.
- Refresh public shop copy around Abbe originals, mission funding, and the ranch build without making unsupported claims.
- Complete live-site legacy content triage: archive, noindex, redirect, or rewrite only after approval.
- Confirm newsletter, social tracking, and Open Graph behavior without adding noisy or unreviewed plugins.
Later
- Publish deeper program pages only after source-backed copy and Mike/Abbe review.
- Add supporter dashboards after the needs, sponsor, and commerce flows are stable.
- Connect more media, field evidence, and Trail Lens outputs to public storytelling after privacy review.
- Expand Teach the Ridge into reviewed mentor and lesson workflows.
- Move from planning pages to operational pages only when the underlying process exists.
Blocked Until Safe
- Emergency shelter, residency, public camping, public kitchen, intake, medical, legal, crisis, and children/family services.
- Any claim that FPR is open as a public service site before facilities, staffing, insurance, partners, and review are in place.
- Autonomous public publishing without human approval.
- Donation, sponsor, or product claims that imply guaranteed outcomes, tax status, or services not yet active.
Review Gates
Each roadmap item has a reviewer expectation. Public copy, shop copy, product imagery, sponsor asks, and sensitive program language require human review before they move from draft or internal tooling into public claims.
Commerce cleanup can proceed in small verified batches. Program expansion cannot. A cleaned shop page is not the same thing as opening public ranch services.
How Supporters Can Help Without Rushing Unsafe Work
Supporters can help most by using the live shop, reviewing concrete needs, offering specific expertise, and funding materials tied to the next build step. This moves the mission forward without pressuring FPR to open Blocked Until Safe programs before they are ready.
Boundary Language
Blocked Until Safe means not active, not open, and not promised. FPR will not rush sensitive work past safety, partner, legal, insurance, staffing, facility, consent, and review requirements.