Workflowreviewgovernancelocal-dbhuman-review

    Local review and promotion loop

    How a generated Hyphenomenon project stays editable and accountable after the first intake run: local pages expose the draft record, the operator reviews narrative, artifacts, workflows, and graph links, then decides whether to revise the packet, keep the record local, or later request a separate production apply.

    Context

    This workflow is part of How This Site Works project.

    Workflow

    Local review and promotion loop

    6 steps
    1. Record a checkpoint with absolute timestamp, dry-run/apply artifacts, verification, and next review decision
      action
    2. Check whether the record explains what happened, what artifacts prove it, what AI did, and what the human operator decided
      subprocess
    3. Open the local project route, workflow route, notes, and Explore map created by the intake apply
      action
    4. Keep production apply separate until explicitly approved with a fresh dry-run and scoped mutation plan
      state
    5. Decide whether the output is a useful proof record or whether the packet/dossier needs another rewrite
      decision
    6. If weak, revise packet copy or workflow logic and rerun dry-run before another local apply
      action

    Related notes

    Note

    ../../DOCS/features/projects.md

    Source Summary title: Projects description: Public list/detail pages for project supernodes that function as Hyphenomenon's primary project and proof surface...

    Note

    ../../DOCS/features/workflows.md

    Source Summary title: Workflows description: Public list/detail pages for workflow entries with Mermaid diagrams sourced from the merged content catalog stat...

    Note

    Knowledge data safety model

    Database operations policy for keeping production canonical while local remains a review mirror.