Skip to content

parent.md

Latest commit

 

History

History
128 lines (101 loc) · 3.55 KB

parent.md

File metadata and controls

128 lines (101 loc) · 3.55 KB

Beacon Archetype: Parent

For parents who want an AI-accessible memory layer for the household — maintenance schedules, kid info, medical records, service contacts, and the thousand small facts that currently live in your head or a random notes app.

Run These SQL Files

schema/00_core.sql       ← Required
schema/02_life.sql       ← Household + relationships (core value for this archetype)
schema/04_rls.sql        ← Required (run last)

Optional additions:

schema/01_projects.sql   ← If you have side projects or work streams to track
schema/03_career.sql     ← If you're job hunting or want to track career moves

Seed These Tables First

1. household — the institutional memory of your home

Start with the things you look up most often or have to dig for:

Home details:

category: 'home_details'
- Paint colors (room, brand, color name, finish, where purchased, date)
- Appliance model numbers and purchase dates
- Wifi network name and password location
- Utility account numbers
- HOA contact and rules

Maintenance:

category: 'maintenance'
- HVAC filter size + last changed date + recurrence_interval: '3 months'
- Furnace last serviced + next_service_due
- Roof age and last inspection
- Gutter cleaning schedule
- Pest control schedule

Vehicles:

category: 'vehicles'
- Make, model, year, VIN for each car
- Last oil change + mileage + next_service_due
- Tire size and last rotation
- Insurance policy number and renewal date

Medical (per person):

category: 'medical', applies_to: ['[Child Name]']
- Pediatrician name, phone, address
- Allergies and medications
- Vaccine history and next due
- Insurance card info
- Dentist and last visit

School:

category: 'school', applies_to: ['[Child Name]']
- School name, grade, teacher name
- School hours, calendar link
- Lunch account info
- After-school activities and schedules

Contacts:

category: 'contacts'
- Plumber (name, company, phone, when used, what for)
- Electrician
- Pediatrician
- Babysitters
- Neighbors you trust

2. professional_relationships — people worth tracking

Even for a parent-focused setup, tracking a small network is valuable:

- Key school contacts (principal, teachers)
- Trusted service providers (the plumber who actually shows up)
- Close family friends
- Your own professional contacts if relevant

3. thoughts — the stuff that doesn't fit a category

Capture via platform extraction (see docs/SEEDING.md):

  • Parenting decisions you've made and why
  • Things you've learned about each kid
  • Household systems that work (or don't)
  • Financial decisions and reasoning

Daily Habit

The household domain is less about daily capture and more about just-in-time capture: record it when you first deal with it so you can find it in 18 months.

Trigger points:

  • Service visit happened → update last_service_date, set next_service_due
  • New appliance/purchase → capture model, date, warranty, receipt location
  • Kid milestone → capture_thought with type insight, applies_to their name
  • Useful contact → household with category: 'contacts'
  • Recurring thing you had to look up → if you had to search for it once, capture it

Query Examples

Ask your AI assistant (with Beacon MCP connected):

  • "When is the HVAC filter due to be changed?"
  • "What's [child]'s pediatrician's phone number?"
  • "What paint color is the living room?"
  • "What service providers do we have for the house?"
  • "What household items need attention soon?"