Legacy projects (verification needed)
Status: ⚠️ verify if still active
What these are
Projects that appeared in the recovered shared-docs (last known good 2026-01-22) and in prior memory entries. State from January 2026; not verified since.
| Project | Last known state | Verdict needed |
|---|---|---|
| DiscipleConnect | V2, live at discipleconnect.pages.dev, Firebase backend, Cloudflare Pages host | Is it still active? Has it been FVW v8-aligned? |
| SmartPantry | In development (Project Structure phase), Firebase smartpantry-66c66, Cloudflare Pages | Is it still active? |
| TaskDomination | In development (per memory), FVS work referenced | Is it still active? |
| TreeAcademy | Account type: non-linked (cannot access /workspace/shared/) | Is it still relevant? |
| Hope for Europe | Mentioned in CROSS_PROJECT_STRATEGY (sync example) | Is it still active? |
Why verification needed
The 2026-06-22 case-variant dup cleanup nuked 5 case-variant pairs. The canonicals DominicsTasks, FreshvibeUI, FreshVibe-Gallery, Home-studio, freshcards are all 404 now. If these legacy projects lived in those repos, they're gone.
Specifically:
avidtech6/dominicstasks→ 404. DominicsTasks work now lives... where? In FVS Studio? In a different repo? Unknown.avidtech6/Home-studio→ 404. Home-studio work... unknown.
What to do
For each legacy project:
- Check if there's a current repo in FVS Studio or elsewhere
- Check the FreshCards substrate for cross-references (D-056 lists D-056 in its tags, indicating it has dependencies)
- Ask the operator if these projects are still in scope
If a project is still active, write a per-project page in dev/projects/. If archived, move to dev/archive/.
DiscipleConnect alignment plan
A specific FVW v8 alignment plan exists for DiscipleConnect: studio/.fvs/plans/2026-06-22-disciple-connect-plan-correction.md. This is the new constitutional artifact. The plan follows the contamination-fix guidance: drops B1 (workspace partitioning), defaults B2-B5, adds §6 identity contract.
This plan is the "what to do if DiscipleConnect comes back" guide. It's a plan, not a project page. It lives in studio/.fvs/plans/, mirrored in dev/plans/ if we add it later.
Cross-references
- Plan:
studio/.fvs/plans/2026-06-22-disciple-connect-plan-correction.md(FWV v8 alignment for DiscipleConnect) - Decision: D-062 (Phase 4 cleanup that produced the plan-correction)
- Lane: fvre (when HYBRID-mode sign-off needed for these)