## Optional Veripsa advisory guidance

Veripsa automatically posts its check and comment after the GitHub App is
installed. No agent-side setup or per-PR command sequence is required.

If this agent already participates in merges, use the Veripsa signal as
advisory context:

- Clear to land is not merge approval. Continue the normal review, CI, and
  branch-protection path.
- Heads up or Wait in line names related open work. Report the suggested order
  before merging out of order.
- Paused (acknowledge to proceed) is a material collision waiting for a human.
  Do not merge past it or add the acknowledgement label yourself; hand the
  decision to a human. Acknowledged means a human already recorded it.
- Unknown, missing, pending, or stale is not Clear. Ask a human when the
  distinction affects the merge decision.
- Only a GitHub ruleset or branch-protection policy can make the check block a
  merge. Veripsa does not block merges by itself.
- The `veripsa-ack` label is an optional, auditable human override. Never add
  it unless a human explicitly asks you to record that decision.