DOL Kid Home Parent Split Architecture Implementation Plan

Execution note: Use executing-plans to implement this plan task-by-task.

Goal: Refactor DOL Kid documentation so guest intro and parent-managed post-login logic are separated cleanly, with reusable AI-facing guidance and updated context routing.

Architecture: Keep pre-login logic inside Home & Discovery as a DOL Kid-only guest intro lane, and move post-login guardian-managed behavior into Parent Experience with explicit multi-child rules. Update context cards and documentation guidelines so future AI/doc work does not reintroduce the old single-child self-study hub model.

Tech Stack: Markdown docs, .mdc context cards, .agent/rules references, npm context quality scripts

---

Task 1: Lock the target document topology

Files:

• Modify: docs/Domains/DOL Kid/UX Design/Home & Discovery/HOME_KID_00_Overview.md
• Modify: docs/Domains/DOL Kid/UX Design/Home & Discovery/HOME_KID_Home_Information_Architecture.md
• Modify: docs/Domains/DOL Kid/UX Design/Home & Discovery/HOME_KID_Home_Navigation_Conversion_Flow.md
• Move: docs/Domains/DOL Kid/UX Design/Home & Discovery/HOME_KID_Self_Study_Hub.md
• Modify: docs/Domains/DOL Kid/UX Design/Parent Experience/KID_Parent_Experience_00_Overview.md

Step 1: Replace the old “post-login self-study hub” assumption with a guest-intro-only home scope.

Step 2: Move the old hub doc into Parent Experience and rewrite it as the parent-managed learning dashboard canon.

Step 3: Make every touched overview file state the boundary explicitly: guest intro owns entry/conversion, parent experience owns post-login management.

Task 2: Write the new parent-managed dashboard logic

Files:

• Create or move to: docs/Domains/DOL Kid/UX Design/Parent Experience/KID_Parent_Learning_Management_Dashboard.md
• Modify: docs/Domains/DOL Kid/UX Design/Identity & Access/KID_Identity_Access_00_Overview.md

Step 1: Describe the post-login product model: parent overview, child switcher, per-child dashboard, alerts, reporting, and next-best action.

Step 2: Add the minimum identity/access dependencies needed for multi-child management without expanding into unnecessary technical detail.

Step 3: Keep the spec lean by removing any stale single-user or learner-home assumptions that conflict with guardian-managed ownership.

Task 3: Upgrade AI-facing guidance and context routing

Files:

• Modify: docs/Domains/DOL Kid/UX Design/Home & Discovery/HOME_KID_UX_Doc_Guidelines.md
• Modify: docs/context/home-discovery.mdc
• Modify: docs/context/account.mdc
• Modify: docs/context/domains.mdc

Step 1: Add reusable writing rules so AI keeps guest intro and parent-managed dashboard separate.

Step 2: Update context cards to route DOL Kid guest-home requests to Home & Discovery docs and parent/multi-child requests to Parent Experience and Identity & Access.

Step 3: Remove stale references to self-study hub where they would misroute future work.

Task 4: Verify and trim

Files:

• Review all files touched in Tasks 1-3

Step 1: Run npm run context:guard.

Step 2: Run npm run context:benchmark.

Step 3: Run npm run context:stale.

Step 4: Re-open any file that still contains stale assumptions, trim duplicated language, and keep only the minimum durable guidance.