Ainglish registered construct: start-by / complete-by — say which task event a deadline constrains

Registered form: <ACTION> start-by(<t>) | <ACTION> complete-by(<t>)

Status: ratified; source release 0.35.0.

Careful-English definition:
Attach one phase-qualified deadline to an ACTION clause. `X start-by(t)` means that genuine execution of X begins at or before instant t. Acknowledging X, promising to do it, putting it in a queue, reserving capacity, or scheduling a future start does not satisfy the marker unless that administrative act is itself X. The first task-specific step that can advance X toward its stated outcome does. `X complete-by(t)` means that X's declared successful-completion condition is satisfied at or before t. A process that merely stops, times out, is cancelled, or reaches a terminal failure has not satisfied `complete-by`.

The deadline is inclusive: an event exactly at t qualifies. `start-by` imposes no completion deadline. `complete-by` imposes no separately stated earliest-start constraint, although a non-instantaneous action must logically have started early enough to complete. If X has an explicit completion predicate, that predicate governs; otherwise the ordinary stated task goal governs. An author who cannot identify a completion condition cannot truthfully use `complete-by` as if elapsed time alone made the task successful.

Lossless round-trips: `req: upload the archive start-by(17:00Z)` ⇄ “Please begin actual archive-upload execution no later than 17:00Z; it need not be finished then.” `will: upload the archive complete-by(17:00Z)` ⇄ “I commit that the archive upload's success condition will be satisfied no later than 17:00Z.” Hyphen loss yields the ordinary phrases “start by” and “complete by.”

SCOPE: the markers type which event a deadline constrains; they do not themselves request, promise, report, prioritize, retry, cancel, or prove that the event occurred. Illocutionary force comes separately from `req:`, `will:`, or other discourse context. `<t>` must independently denote an instant; use an absolute timestamp or anchored deixis where needed. Time zone, clock source, completion predicate, and consequences of missing the deadline remain separately stated.

Reviewed usage pairs:
- Ainglish (canonical): req: upload the archive start-by(2026-08-05T17:00Z). · will: upload the archive complete-by(2026-08-05T18:00Z). · req: investigate the incident start-by(now (2026-08-05T14:10Z)). · will: publish the signed report complete-by(2026-08-06T09:00Z); status eta(2026-08-05T20:00Z).
  Careful English: Please begin actual archive-upload execution no later than 17:00Z; acknowledgement or queueing is insufficient. · I commit that the archive upload's success condition will be satisfied no later than 18:00Z; a stopped or failed upload is insufficient. · Please take the first task-specific investigative step no later than the anchored present instant. · I will successfully publish the signed report by 09:00Z tomorrow and will separately report status at 20:00Z today.
- Ainglish (non-normative training): Draft the postmortem start-by(2026-08-18T09:00Z).
  Careful English: Genuine work on drafting the postmortem must begin no later than 09:00 UTC on 18 August 2026.
- Ainglish (non-normative training): Rotate the credentials complete-by(2026-08-20T00:00Z).
  Careful English: Credential rotation must be finished by midnight UTC at the start of 20 August 2026.
- Ainglish (non-normative training): Migrate the DNS records complete-by(Friday 17:00 UTC).
  Careful English: The DNS record migration must be complete by Friday 17:00 UTC.
{"content_digest":"7652c70b8171c2a1e42d605811e00b25c32e13e133750e49181ad79b00358a88","license":"CC0-1.0","register_digest":"ee8978f9ab5adb252aa244dc1a0dbb5abaa81f499758ec18c95caf5dcfa863b8","release_version":"0.35.0","slug":"start-by-complete-by-say-which-task-event-a-deadline-constra","url":"https://ainglish.org/register/start-by-complete-by-say-which-task-event-a-deadline-constra"}