Skip to content

HANDOFF_FLOW.md

Latest commit

 

History

History
53 lines (31 loc) · 3.57 KB

HANDOFF_FLOW.md

File metadata and controls

53 lines (31 loc) · 3.57 KB

Context Handoff Flow

"Document then continue" — write handoff, open new chat, paste continue prompt.

Operational superset (local workspace): This file is the portable handoff narrative for OpenHarness and canonical bundle consumers. It does not duplicate archive scripts, pre-commit hooks, or integrity tooling. When your machine has the portfolio workspace checked out, follow the detailed procedure in the sibling MiscRepos repo: MiscRepos/.cursor/HANDOFF_FLOW.md (paths relative to your GitHub folder: e.g. Documents/GitHub/MiscRepos/.cursor/HANDOFF_FLOW.md).

Flow

  1. Trigger — Say "handoff", "write handoff", or "context handoff".
  2. Archive then write — Copy existing handoff to archive; write handoff_latest.md with Done, Next, Paths, Decisions.
  3. Append to daily log — Add short block to daily/YYYY-MM-DD.md.
  4. New chat — Open new chat (Cmd/Ctrl+L).
  5. Paste — Paste continue prompt (or run copy script), then send.

Trust Boundary

Handoff is a trust boundary. Before pasting:

  • Run SCP validation on handoff when staged (pre-commit).
  • Optional: Run integrity check to verify handoff was not modified.

Content that originated outside this workspace (web paste, tool output, unknown files) belongs in the same cautious posture: see .cursor/skills/secure-contain-protect/SKILL.md for inspection and containment patterns; align with your SCP workflow before promoting text into durable state/ or RAG.

Continue Prompt

Canonical source: state/continue_prompt.txt. Run copy script to paste.

Clipboard and headless agents

copy_continue_prompt.ps1 / .sh / .cmd targets the system clipboard and expects an interactive environment. Headless sessions, CI, or agents without clipboard access should read state/continue_prompt.txt directly (or cat / type it) instead of relying on clipboard copy.

Scripts

  • copy_continue_prompt.ps1 (Windows) / copy_continue_prompt.sh (macOS/Linux) — Copy prompt to clipboard.
  • validate_handoff_scp.py — SCP validation; use as pre-commit hook when handoff is staged.

Human Gate

When agent reaches a human gate: write handoff with "Awaiting approval"; next session asks human before proceeding. See INTENT_ENGINEERING.md.

Definition of done (P1 — verifiable rewards + dual gates)

When the session produced substantive code, config, or behavior-changing docs, add a block (below Next or under Paths):

  • Verification commands run — e.g. pytest, ruff check, mypy, npm test, npm run build (project-appropriate). Record pass / fail.
  • UI / E2E — if the change touches UI, note browser or Playwright runs when applicable.
  • Dual gates (multi-file / high-stakes) — attach or summarize critic JSON (critic-loop-gate.mdc) and intent-alignment JSON (intent-alignment-gate.mdc). If aligned=false or escalate=true, state that the next step requires human review before merge.

This aligns “done” with green CI (tests/lint/build), not model confidence alone. See 2511.18538-harness-gap-analysis.md § Value-add.

Public repos

Do not commit real handoffs to a public harness fork. Use a private state/ (or private remote) for live handoffs. For teaching the format, see examples/HANDOFF_EXAMPLE_SYNTHETIC.md and PUBLIC_AND_PRIVATE_HARNESS.md.