Build Log · July 2, 2026

Known goes multi-family, and the Crucible gets teeth

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.

  • Known
  • Auth
  • Ethics
  • Crucible
  • OS
Known features shipped to prod
3

Known features shipped to prod

Crucible enforcement passes (each one found the last one incomplete)
3

Crucible enforcement passes (each one found the last one incomplete)

databases wired (prod fixed, dev branch added)
2

databases wired (prod fixed, dev branch added)

Timeline

  1. Start

    Pre-session audit

    Known product/docs audit — what's built vs. described, ethics gate verified real

  2. ~1h

    Charge: household login, Labs, delete, AI chat design

    Anvil Check run solo — household-not-org reframe, Labs-opt-in-vs-ethics-doc tension

  3. ~1.5h

    Zeb asks: where was the skeptic?

    Crucible/Council never ran on the org/Labs decisions — Mode A/B fork was self-graded

  4. ~2h

    Crucible Checkpoint rebuilt as explicit question, not silent classification

    ignition.md §1.6/§1.7 — Claude asks Zeb, doesn't infer

  5. ~2.5h

    Council run live — architect, qe, steward, then single-call council mode

    All personas now give recommendations, not just questions

  6. ~3h

    Build: org scoping, Labs toggle + audit log, soft delete + cascade

    Every portrait/entry/enrichment route scoped by orgId

  7. ~4h

    Prod migration surprise: real data found mid-push

    Backfilled Thomas Jungeberg's portrait into the correct org; wired a Neon dev branch afterward

  8. ~4.5h

    Deployed to known.forgekits.build, Zeb tested live

    Sign-in, household creation, portrait creation all confirmed working

  9. ~5h

    Post-build Crucible checkpoint also skipped

    Same failure, different point in the arc — moved from build-complete into deploy prep without asking §1.7

  10. ~5.5h

    crucible:wrap enforcement rebuilt a third time

    First pass was detection-only; Zeb rejected it — rebuilt as an actual hard stop

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?”
— Zeb, rejecting the first (detection-only) fix for the skipped post-build Crucible checkpoint