Build Log · June 29, 2026

Known Enrichment Bridge

Built the bridge between raw family memory and reviewed caregiver guidance — with a hard gate that keeps AI-drafted content off caregivers until a family member approves it.

  • Known
  • Feature
  • Schema
  • Architecture
new DB table
1

new DB table

new files shipped
3

new files shipped

files updated for enrichment second-pass
5

files updated for enrichment second-pass

knowledge-architecture docs created
4

knowledge-architecture docs created

Timeline

  1. Start

    Session pivoted to Known

    Zeb redirected from general work to Known as flagship product

  2. 1h

    Architecture docs written

    knowledge-architecture, public-library-plan, research-corpus-plan, experiment-template

  3. 2h

    Known app review complete

    Read all pages, components, schema, API routes — two parallel systems identified

  4. 3h

    Enrichment Bridge designed

    Three paths proposed, Path C chosen: AI drafts, family reviews, gate enforced at query layer

  5. 4h

    Bridge shipped

    Schema live, form page, API routes, enrichment second-pass on all caregiver-facing outputs, BookPortrait dots

What shipped

  • entryEnrichments DB table — cardLabel, guidance, suggestedPhrase, careMoments, emotionalTone, enrichmentSource, reviewStatus, reviewedBy, reviewedAt

  • Enrichment form at /portraits/[id]/enrich/[entryId] — raw answer shown read-only, enrichment fields below, single approve step

  • Enrichment API routes — POST (create) and PATCH (update/approve/reject)

  • Caregiver gate — care-card and KnownCard query only reviewStatus=approved|edited enrichments

  • BookPortrait enrichment dots — green (approved), amber (draft), grey (none) with link to enrich form

  • Four Known knowledge-architecture docs — knowledge-architecture, public-library-plan, research-corpus-plan, labs/experiment-template