Skip to content

verify: WAIT/park — a Loop gated on external work parks instead of burning Rounds #11

Description

@shitianfang

When Verify judges "not done, but gated on CI / a deploy / an external approval", every
further tick burns a full Round to rediscover the same wait. Proposal: the Loop parks on a
condition (deadline, file appears, process exits); a tick on a parked Loop is a cheap no-op.

Open design decision (owner call before implementation): parking as a new Exit cause (a
resumable interruption) vs a Verdict extension (a judge ruling) — the semantics differ.
"Only a Verdict settles" must survive either way.

Evidence: hermes judge tri-state done|continue|wait with a lazily self-clearing wait
barrier; wait-with-no-target degrades to continue, never parking on nothing.

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs-triagenew issue awaiting triage

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions