Chat

    Hyphenomenon Intake Preview and Release Boundary Incident

    Large Hyphenomenon operations thread that began with TMORA chat intake and local preview verification, expanded into additional chat intakes, candidate-review infrastructure, preview/production promotion and branch reconciliation, and ended with a read-only incident audit after unapproved homepage and card work reached main and production.

    Highlights

    • Completed the TMORA production chat intake, added supporting Figma links, verified the local preview database, and kept production untouched for that pass.
    • Intaked and preview-applied the customer-email cleanup and Shopify B2B/trade portal chats as separate first-class records with complete private archives.
    • Created project 1086 as a manual Codex chat candidate audit and sensitivity-review lane, including a Google Sheet review workbook and later visual-evidence shortlist.
    • Created project 1088 for trails, concepts, related-projects, visualization architecture, and database safety planning without running database mutations.
    • Completed project 1089 to reconcile intake branches, apply approved preview records, clean branches/worktrees, and synchronize main.
    • Completed project 1090 to promote the approved additive July 13 preview batch to production after backup and route/drift verification.
    • Later merged unapproved visual workstreams through project 1093, causing homepage and card regressions to reach production; the thread ended with a read-only incident audit, explicit stop, and a plan for a proper blocked docs-only project 1095.

    Source conversation

    Chat Transcript
    Private

    This transcript is not public. You can request access below; requests are reviewed before anything is shared.

    Created artifacts

    ProjectProject 1086: Codex chat intake candidate audit and sensitivity review

    Manual review lane for chat and generated-visual intake candidates, including transcript review and privacy classification.

    ProjectProject 1088: Trails, concepts, relationships, and visualization architecture

    Architecture and safety-planning project for graph semantics, backups, restore drills, and visualization projections.

    ProjectProject 1089: Intake branch reconciliation and preview apply

    Reconciled July 13 intake work across branches, applied approved preview records, verified drift, and synchronized main.

    ProjectProject 1090: July 13 intake production promotion

    Promoted the approved additive preview batch to production after backup, media-prefix isolation, drift checks, and route verification.

    ProjectProject 1093: Branch integration preview and cleanup

    Integration project later identified as the release-boundary failure that merged unapproved homepage and card work to main.

    Actions and follow-ups

    Actions Taken

    • Extracted, validated, synced, applied, and route-verified multiple chat intake artifacts.
    • Logged intake runs, committed local artifacts, and verified preview database entities/routes.
    • Built candidate audit spreadsheets, transcript reviews, and visual-evidence shortlists.
    • Ran production backup and additive production promotion for the approved July 13 intake batch.
    • Merged and cleaned several branches during the later integration pass, then audited the resulting production regression after user review.
    • Performed a read-only incident audit and stopped before writing the recovery project plan when the user requested a model switch.

    Actions Outstanding

    • Create project 1095 as a docs-only recovery plan before any operational recovery work.
    • Archive or preserve the unapproved visual workstreams while restoring approved production/main state through an explicitly approved process.
    • Rebuild card/index work from the restored approved baseline on a preview-only branch.
    • Do not merge to main, deploy, mutate production data, or clean branches unless the user gives explicit current approval.

    Source extracts

    “
    Initial intake request
    intake 019f56c9-2fc8-7970-8993-72685d08c587 then tell me what we have waiting in the intake queue
    “
    Preview database request
    make sure the intake was applied to the local preview db and then spin up a preview
    “
    Additional chat intakes
    then intake the following two chats and add then both to the local/preview db and then refresh the preview.
    “
    Main merge boundary
    youre recommendation was to keep thigns away from main until i approved it. this is a big mistake
    “
    Recovery project requirement
    this new plan needs a propoer numbered project and needs to clearly label what you will be doing versus what i need to do.

    Decisions

    • Routine additive chat intakes can be applied to the local preview database after artifact validation and route verification, while production apply requires explicit approval.
    • Candidate chat and visual audit outputs remain review queues, not automatic public intakes.
    • App Growth's misleading active workflow packet and MLNNA's stale paused packet must stay unapplied rather than overwrite current killed-state truth.
    • Approved production promotion should be additive, backed up first, use a non-overwriting media prefix, and verify preview/production parity.
    • Merging tested or review-ready visual branches into main is not approval; main merges require an explicit current instruction from the user.
    • The recovery from the unapproved visual release needs its own numbered project, docs-only first pass, Maggie-owned signoff gates, and collaborative review stops before any operational recovery.