Build Log
Known goes multi-family, and the Crucible gets teeth
July 2, 2026
Household login, Labs opt-in, and soft delete shipped to prod for Jan's first session — and the Crucible checkpoint that should have caught the design gaps got rebuilt three times until it actually enforces itself.
Timeline
What shipped
Known: household-scoped multi-user login via Clerk Organizations — flat access, no roles, every portrait/entry/enrichment route and page scoped by orgId from auth().orgId server-side
Known: Labs/research opt-in — default off, explicit toggle, every change written to a labs_opt_in_audit_log table
Known: soft delete for portrait entries — tombstone fields, cascading invalidation of AI-drafted guidance sourced only from the deleted entry, visible warning before confirming
Known: fixed a pre-existing path bug in sync-brain-content.mjs that silently blocked every production build
Known: wired a Neon dev branch (.env.development.local, gitignored) — Known had no dev/prod database split before this session
ForgeKit OS: Crucible Checkpoint rebuilt as an explicit question Claude must ask (ignition.md §1.6 pre-build, §1.7 post-build) instead of a silently self-graded Mode A/B classification
ForgeKit OS: all 9 Crucible personas now give their own recommended answer per question (ANSWER_SUFFIX), not just questions — a skeptic that only interrogates still leaves the synthesis to the human
ForgeKit OS: new crucible:council mode — one API call, multiple personas in labeled sections, blended synthesis at the end
ForgeKit OS: two evidence-based miss detectors in build-session.mjs — pre-build Crucible-miss (schema/auth/automation/OS-mechanism diff with no recorded checkpoint) and post-build Crucible-miss (Deploy Gate ran with no recorded checkpoint)
ForgeKit OS: crucible_wrap made a hard stop in ignition.md §6 step 3, not a checklist line — Claude cannot proceed to git commit without having actually run it and printed real output this session
ForgeKit OS: crucible_wrap findings now render as their own visible section on the build-log page, same visibility standard as the pre-build Council review
“I don't want to rely on this at all. Glad we will catch it, but proactively — I thought we were triggering it to ensure it runs?”