Every blocker at once in errors (empty narrative, closed or missing matter, a required attribute missing or a value outside the matter's list). Already released is a no-op answering the same entry and the delivery it already has. There is no inverse (D-61). From release the entry is FROZEN: nothing is edited after release (D-164). In the same transaction the judged text of the intervals it covers is cleared (for an entry the pipeline drafted by a person matter learning is on for, held for its learning and deleted within the hour); their evidence stays, and no batch writes those intervals again, so the evidence behind a released line is the evidence that was behind it when the person released it. The practice system receives the entry's minutes, its override_seconds where one is set and else the sum of its parts, and applies any rounding of its own (D-218). The judged text cleared is under the entry's parts only: an interval in a gap between two of them keeps its text.

Where the firm has a practice system, the entry is released only once the system has taken it. A connector in any status but connected is the blocker connector.not_connected; a connected one adds its own blockers, each under a path of its own: connector.matter (a matter the system does not hold), connector.timekeeper (no employee, or an inactive one, bound to the author), connector.narrative (longer than the system's declared ceiling, both numbers in the message) and connector.matter_blocked; a required field the system declares is the attribute's own blocker. Then the entry is pushed inside this request, a connection failure retried quietly (three attempts within twenty seconds), and the release and its delivery (released, with the system's id) are committed only when the system has answered with its own id. A refused login at that connect marks the connector needs_reconnect and answers the 422 connector.not_connected; the system's own refusal is a 422 on one of connector.matter_not_found, connector.matter_closed, connector.person_not_found, connector.person_inactive, connector.not_accepted and connector.reviewer (the reviewer the firm chose was refused: its setting needs changing); a system that could not be reached is a 503 practice-system-unreachable. Each leaves the entry a draft. Where the practice system is one each member signs in to with their own account, the push goes out on the AUTHOR's own session: a member who has not signed in, whose session the system stopped accepting, or whose session is refused during the push is answered the 422 connector.sign_in (sign in under Settings, Practice system, and release again), which marks that member's session alone and never the firm's connector, so colleagues keep releasing; a member whose account there books no time is answered connector.timekeeper; and a matter the system does not show the member is answered as a matter that is not there, on matter_id. An entry edited while it was being released is a 409 entry.changed, still a draft, and a second release of an entry whose first is still with the practice system a 409: one push is in flight per entry. The push is idempotent on the entry id, so a release retried after a lost answer books nothing twice. Every blocker carries its rule and params (narrative.*, matter.*, attribute.*, release.*); a deleted draft is a 409 entry.deleted, and an entry that is not the caller's a 404 entry.not_found.