Mark/kimi_agent_kin_app_sync
1
0
Fork 0
Code Issues 3 Pull requests Projects Releases 2 Packages Wiki Activity Actions

Guidance frameworks — structured developmental relationships (parent, mentor, coach, teacher) #87

New issue
Closed
opened 2026-06-09 02:46:34 +00:00 by Mark · 0 comments
Mark commented 2026-06-09 02:46:34 +00:00
Owner
Copy link

Summary

In relationships where one person holds legitimate authority or responsibility over another's development — parent over child, mentor over mentee, coach over athlete, teacher over student, manager over direct report — there is a natural role for structured guidance.

This isn't punishment or control. It's the responsible use of influence: setting clear expectations, providing consistent feedback, tracking growth over time, and adjusting approach based on what works. The same cadence mechanics from #81 applied to someone else's development, with the humility that you're shaping, not controlling.

P1: Guidance relationship setup

Define the nature of the relationship and the scope of guidance.

  • Relationship sub-types that enable guidance features:
    • Parent / guardian — child development tracking, habit building, screen time boundaries
    • Mentor / mentee — skill-building plans, milestone tracking, check-in cadence
    • Coach / athlete — practice adherence, progressive overload, performance reviews
    • Teacher / student — learning progress, assignment pacing, mastery tracking
    • Manager / direct report — growth goals, feedback cadence, skill development
    • Elder / community member — traditional mentorship, wisdom transfer, rite-of-passage tracking (cultural context)
  • Each sub-type gets appropriate defaults, vocabulary, and available feature set
  • Explicit consent marker: user acknowledges the nature of the guidance relationship when activating features. The relationship is mutual, the tracking is transparent.
  • The person under guidance does NOT need to be a Kin user — all tracking is from the authority figure's perspective only

P2: Expectation setting & agreements

Define the framework together (or from your side, with their awareness).

  • Create guidance agreements per relationship: what are we working on, what does success look like, what's the timeline?
  • Agreement types:
    • Skill / habit building — "Practice guitar 15 min/day, check in weekly"
    • Behavioral expectations — "Bedtime by 9pm on school nights, gradual independence on weekends"
    • Growth milestones — "Complete 3 mentorship projects over the next quarter"
    • Accountability check-ins — "Weekly 1:1 to review progress on goals"
    • Boundary reinforcement — "No screens after 10pm — consistency matters"
  • Shared language: instead of "rules," use "agreements" or "commitments" — language that implies mutual understanding
  • Optional: share the agreement with the other person (outside the app, or via a shareable summary card)

P3: Cadence-driven shaping

Apply #81's expanding-interval and lock-in mechanics to the other person's development.

  • For a skill/habit goal: set an initial check-in cadence (e.g., daily for a new habit), let the app use spaced repetition to naturally stretch intervals as consistency builds
  • Example flow: "Help child build reading habit" → app suggests daily check-ins for week 1 → stretches to every 2 days in week 2-3 → weekly once habit is locked → if a miss happens, compresses back
  • Lock-in scoring applied externally: "Sarah has practiced guitar consistently for 6 weeks — 92% adherence. The habit is forming well. Consider reducing check-ins to every 3 days."
  • Progressive difficulty: when a skill is mastered at current level, auto-suggest the next stage (like #85's shaping)
  • All intervals are suggestions — the authority figure always has discretion to override

P4: Feedback & review system

Structured feedback loops, not criticism.

  • Per-interaction feedback logging: after a check-in or session, log how it went
    • Rating scale: 1-5 (how did it feel?) + optional notes
    • What worked / what didn't / what to try next
  • Trend analysis: "Feedback is trending positive over the last 4 weeks" or "Consistency is dropping — consider a different approach"
  • Milestone celebrations: when an agreement reaches a significant point (30-day streak, skill milestone, etc.), log a celebration
  • Periodic review prompts: "You've been in this guidance role for 3 months. Time for a structured review of progress and plan adjustment?"
  • Review template: what's working, what's changed, what needs adjusting, next phase goals

P5: Boundary enforcement for guidance

Some boundaries in guidance relationships need active support (ties into #86).

  • Time boundaries: "No practice after 8pm" / "Homework before screens" — app can help enforce by delaying check-in visibility
  • Consistency tracking: if the guidance cadence is slipping on your side (you're the one not showing up), the app flags that: "You set a weekly check-in with your mentee — it's been 2 weeks. Consistency matters here."
  • Overstepping detection: if you're logging feedback more frequently than the agreement calls for, the app gently asks: "You've checked in 4x this week — the agreement is weekly. Is this intentional?"
  • Escalation guidance: if the person under guidance is consistently not meeting agreements, offer reflection prompts rather than tighter control — "Consider whether the agreement needs adjustment, not enforcement"

P6: Graduation & independence

The goal of guidance is to eventually not need it.

  • When lock-in scores reach threshold (e.g., 12+ weeks of 90%+ adherence), suggest graduating: "This habit is fully formed. Consider moving to self-directed tracking."
  • Phase-down plans: gradually reduce check-in frequency over weeks until the person is independent
  • Graduation ceremony: log a milestone, mark the agreement complete, archive with a growth summary
  • Relationship transition: when a guidance relationship naturally shifts (child becomes adult, mentee becomes peer), the app can archive guidance features and transition to a peer-to-peer Kin relationship
  • Never suggest graduation without the user's context — timing is deeply personal

P7: Privacy & ethics

This is the most sensitive category in the entire app. Handling it wrong is harmful.

  • Default-off for every guidance feature — nothing activates without explicit opt-in per relationship
  • All guidance data is on-device only, biometric gate (#26)
  • Clear persistent label: "Guidance tracking — for your awareness. The person you're tracking does not see this data."
  • No data about the person under guidance is ever shared, exported, or backed up
  • Emergency stop: one tap hides all guidance data and pauses all active agreements
  • Hard delete: confirm-delete wipes all guidance data for a person without affecting their other Kin data
  • Ethical disclaimer in the app: "This feature helps you be more intentional in guidance relationships. It is not a tool for surveillance or control. If you feel the need to hide this feature from the person you're tracking, reconsider whether the feature is appropriate."
  • Regular prompts: "Is this guidance still serving both of you?" — periodic ethics check-in

Tech notes

  • Reuses #81's cadence engine and lock-in scoring — same math, different domain
  • Reuses #86's boundary types and enforcement mechanisms (time boundaries, consistency tracking)
  • Guidance agreement data: new store/table GuidanceAgreement { id, personId, type, title, description, stages[], currentStage, cadence, lockInScore, createdAt, graduatedAt?, archived }
  • Feedback log: new store/table GuidanceFeedback { id, agreementId, date, rating, notes, tags[] } (lightweight, doesn't need full interaction schema)
  • Parent/child relationships are distinct from romantic tracking — no overlap with #83's features
  • The ethical guardrails (P7) are not optional — they must ship before any P1-P6 feature is exposed to users
## Summary In relationships where one person holds legitimate authority or responsibility over another's development — parent over child, mentor over mentee, coach over athlete, teacher over student, manager over direct report — there is a natural role for structured guidance. This isn't punishment or control. It's the responsible use of influence: setting clear expectations, providing consistent feedback, tracking growth over time, and adjusting approach based on what works. The same cadence mechanics from #81 applied to *someone else's* development, with the humility that you're shaping, not controlling. --- ### P1: Guidance relationship setup Define the nature of the relationship and the scope of guidance. - [ ] Relationship sub-types that enable guidance features: - **Parent / guardian** — child development tracking, habit building, screen time boundaries - **Mentor / mentee** — skill-building plans, milestone tracking, check-in cadence - **Coach / athlete** — practice adherence, progressive overload, performance reviews - **Teacher / student** — learning progress, assignment pacing, mastery tracking - **Manager / direct report** — growth goals, feedback cadence, skill development - **Elder / community member** — traditional mentorship, wisdom transfer, rite-of-passage tracking (cultural context) - [ ] Each sub-type gets appropriate defaults, vocabulary, and available feature set - [ ] Explicit consent marker: user acknowledges the nature of the guidance relationship when activating features. The relationship is mutual, the tracking is transparent. - [ ] The person under guidance does NOT need to be a Kin user — all tracking is from the authority figure's perspective only ### P2: Expectation setting & agreements Define the framework together (or from your side, with their awareness). - [ ] Create guidance agreements per relationship: what are we working on, what does success look like, what's the timeline? - [ ] Agreement types: - **Skill / habit building** — "Practice guitar 15 min/day, check in weekly" - **Behavioral expectations** — "Bedtime by 9pm on school nights, gradual independence on weekends" - **Growth milestones** — "Complete 3 mentorship projects over the next quarter" - **Accountability check-ins** — "Weekly 1:1 to review progress on goals" - **Boundary reinforcement** — "No screens after 10pm — consistency matters" - [ ] Shared language: instead of "rules," use "agreements" or "commitments" — language that implies mutual understanding - [ ] Optional: share the agreement with the other person (outside the app, or via a shareable summary card) ### P3: Cadence-driven shaping Apply #81's expanding-interval and lock-in mechanics to the other person's development. - [ ] For a skill/habit goal: set an initial check-in cadence (e.g., daily for a new habit), let the app use spaced repetition to naturally stretch intervals as consistency builds - [ ] Example flow: "Help child build reading habit" → app suggests daily check-ins for week 1 → stretches to every 2 days in week 2-3 → weekly once habit is locked → if a miss happens, compresses back - [ ] Lock-in scoring applied externally: "Sarah has practiced guitar consistently for 6 weeks — 92% adherence. The habit is forming well. Consider reducing check-ins to every 3 days." - [ ] Progressive difficulty: when a skill is mastered at current level, auto-suggest the next stage (like #85's shaping) - [ ] All intervals are suggestions — the authority figure always has discretion to override ### P4: Feedback & review system Structured feedback loops, not criticism. - [ ] Per-interaction feedback logging: after a check-in or session, log how it went - Rating scale: 1-5 (how did it feel?) + optional notes - What worked / what didn't / what to try next - [ ] Trend analysis: "Feedback is trending positive over the last 4 weeks" or "Consistency is dropping — consider a different approach" - [ ] Milestone celebrations: when an agreement reaches a significant point (30-day streak, skill milestone, etc.), log a celebration - [ ] Periodic review prompts: "You've been in this guidance role for 3 months. Time for a structured review of progress and plan adjustment?" - [ ] Review template: what's working, what's changed, what needs adjusting, next phase goals ### P5: Boundary enforcement for guidance Some boundaries in guidance relationships need active support (ties into #86). - [ ] Time boundaries: "No practice after 8pm" / "Homework before screens" — app can help enforce by delaying check-in visibility - [ ] Consistency tracking: if the guidance cadence is slipping on your side (you're the one not showing up), the app flags that: "You set a weekly check-in with your mentee — it's been 2 weeks. Consistency matters here." - [ ] Overstepping detection: if you're logging feedback more frequently than the agreement calls for, the app gently asks: "You've checked in 4x this week — the agreement is weekly. Is this intentional?" - [ ] Escalation guidance: if the person under guidance is consistently not meeting agreements, offer reflection prompts rather than tighter control — "Consider whether the agreement needs adjustment, not enforcement" ### P6: Graduation & independence The goal of guidance is to eventually not need it. - [ ] When lock-in scores reach threshold (e.g., 12+ weeks of 90%+ adherence), suggest graduating: "This habit is fully formed. Consider moving to self-directed tracking." - [ ] Phase-down plans: gradually reduce check-in frequency over weeks until the person is independent - [ ] Graduation ceremony: log a milestone, mark the agreement complete, archive with a growth summary - [ ] Relationship transition: when a guidance relationship naturally shifts (child becomes adult, mentee becomes peer), the app can archive guidance features and transition to a peer-to-peer Kin relationship - [ ] Never suggest graduation without the user's context — timing is deeply personal ### P7: Privacy & ethics This is the most sensitive category in the entire app. Handling it wrong is harmful. - [ ] Default-off for every guidance feature — nothing activates without explicit opt-in per relationship - [ ] All guidance data is on-device only, biometric gate (#26) - [ ] Clear persistent label: "Guidance tracking — for your awareness. The person you're tracking does not see this data." - [ ] No data about the person under guidance is ever shared, exported, or backed up - [ ] Emergency stop: one tap hides all guidance data and pauses all active agreements - [ ] Hard delete: confirm-delete wipes all guidance data for a person without affecting their other Kin data - [ ] Ethical disclaimer in the app: "This feature helps you be more intentional in guidance relationships. It is not a tool for surveillance or control. If you feel the need to hide this feature from the person you're tracking, reconsider whether the feature is appropriate." - [ ] Regular prompts: "Is this guidance still serving both of you?" — periodic ethics check-in ## Tech notes - Reuses #81's cadence engine and lock-in scoring — same math, different domain - Reuses #86's boundary types and enforcement mechanisms (time boundaries, consistency tracking) - Guidance agreement data: new store/table `GuidanceAgreement { id, personId, type, title, description, stages[], currentStage, cadence, lockInScore, createdAt, graduatedAt?, archived }` - Feedback log: new store/table `GuidanceFeedback { id, agreementId, date, rating, notes, tags[] }` (lightweight, doesn't need full interaction schema) - Parent/child relationships are distinct from romantic tracking — no overlap with #83's features - The ethical guardrails (P7) are not optional — they must ship before any P1-P6 feature is exposed to users
Mark closed this issue 2026-06-13 13:55:44 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
v1.1.0
v1.0.0
Labels
Clear labels   
blocked:depends-p1

Depends on #139 (P1) landing first. Picker should not auto-dispatch.

  
blocked:gate-research

   
blocked:lint-failed

   
blocked:needs-decision

   
blocked:needs-human

   
blocked:verify-failed

   
bug

   
data-loss

Data integrity or data loss risk

  
documentation

   
enhancement

   
feature-request

   
in-progress

   
needs-decompose

Issue needs decompose processing

  
needs-triage

   
pwa

Progressive Web App functionality

  
quickfix

   
security

Security vulnerability or hardening

  
security/high

High severity security issue

  
security/medium

Medium severity security issue

  
test

   
test-coverage

Test coverage review / gap report

  
triage-approved

Approved for automated fix pipeline

  
vault

Requires vault/LBB authentication (#26) — discretion-sensitive feature

No labels
blocked:depends-p1
blocked:gate-research
blocked:lint-failed
blocked:needs-decision
blocked:needs-human
blocked:verify-failed
bug
data-loss
documentation
enhancement
feature-request
in-progress
needs-decompose
needs-triage
pwa
quickfix
security
security/high
security/medium
test
test-coverage
triage-approved
vault
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Mark/kimi_agent_kin_app_sync#87
No description provided.