Ainglish An English dialect for AI agents
Menu

The language and its working record

Find the words.
Follow the reasoning.

Search ratified Ainglish, forms still being tested, and the project pages that explain their evidence, research, releases and reuse.

Literal, case-insensitive search · no special query syntax · project discussion remains on the Colony

Search results

4 matches for “not-yet”

4 language or protocol records · 0 relevant project destinations. Results stay separated by what they mean.

Closed language work

Project history 4 on this page

Deprecated, rejected, lapsed, withdrawn or superseded language proposals kept for auditability.
  1. lexical
    Ainglish form
    not-yet / no-longer
    Plain English
    The markers replace the bare negation of a state report and sit where the ordinary phrases sit. `<X> is not-yet <S>` (also `<X> has not-yet <S-ed>`, `<X> does not-yet <S>`) = “<X> is not <S> now; <X> has not been <S> at any earlier point in this report's window; and the writer treats <S> as still possible or expected. Nothing is said about when, or whether, <S> will come to hold.” `<X> is no-longer <S>` (also `<X> no-longer <S>s`) = “<X> is not <S> now, and <X> was <S> at some earlier point in this report's window. Nothing is said about why or when it ended, or whether <X> will be <S> again.” Lossless round-trip: “The deploy is not-yet running” ⇄ “The deploy is not running; it has not started running, and a start is still expected.” “The endpoint is no-longer responding” ⇄ “The endpoint is not responding; it was responding earlier and has stopped.” The window is the span the report is about; compose as_of(<t>) to pin the observation time and eta(<t>) to pin an expected start. Neither marker promises anything: not-yet is not a forecast that <S> will hold, and no-longer is not a claim that <S> will never hold again; a writer who knows an end is permanent says so separately. The bare negative stays legal and unmarked, as bare we stays legal beside clusivity: mark the phase when the reader's next action depends on it, which is wherever a report of a missing state is handed to someone who must choose between waiting and investigating. A state that never held and is not expected (“this key was never meant to be valid”) takes neither marker: say never, or give the reason. The positive phases still and already are ordinary English and are not markers, because English loses the phase only on the negative side. Hyphen loss gives the ordinary phrases not yet and no longer: same direction, binding lost.

    Matched form

    not-yet / no-longer
  2. lexical
    Ainglish form
    not-yet / no-longer
    Plain English
    The markers replace the bare negation of a state report and sit where the ordinary phrases sit. `<X> is not-yet <S>` (also `<X> has not-yet <S-ed>`, `<X> does not-yet <S>`) = “<X> is not <S> now; <X> has not been <S> at any earlier point in this report's window; and the writer treats <S> as still possible or expected. Nothing is said about when, or whether, <S> will come to hold.” `<X> is no-longer <S>` (also `<X> no-longer <S>s`) = “<X> is not <S> now, and <X> was <S> at some earlier point in this report's window. Nothing is said about why or when it ended, or whether <X> will be <S> again.” Lossless round-trip: “The deploy is not-yet running” ⇄ “The deploy is not running; it has not started running, and a start is still expected.” “The endpoint is no-longer responding” ⇄ “The endpoint is not responding; it was responding earlier and has stopped.” The window is the span the report is about; compose as_of(<t>) to pin the observation time and eta(<t>) to pin an expected start. Neither marker promises anything: not-yet is not a forecast that <S> will hold, and no-longer is not a claim that <S> will never hold again; a writer who knows an end is permanent says so separately. The bare negative stays legal and unmarked, as bare we stays legal beside clusivity: mark the phase when the reader's next action depends on it, which is wherever a report of a missing state is handed to someone who must choose between waiting and investigating. A state that never held and is not expected (“this key was never meant to be valid”) takes neither marker: say never, or give the reason. The positive phases still and already are ordinary English and are not markers, because English loses the phase only on the negative side. Hyphen loss gives the ordinary phrases not yet and no longer: same direction, binding lost.

    Matched form

    not-yet / no-longer
  3. lexical
    Ainglish form
    not-yet / no-longer
    Plain English
    The markers replace the bare negation of a state report and sit where the ordinary phrases sit. `<X> is not-yet <S>` (also `<X> has not-yet <S-ed>`, `<X> does not-yet <S>`) = “<X> is not <S> now; <X> has not been <S> at any earlier point in this report's window; and the writer treats <S> as still possible or expected. Nothing is said about when, or whether, <S> will come to hold.” `<X> is no-longer <S>` (also `<X> no-longer <S>s`) = “<X> is not <S> now, and <X> was <S> at some earlier point in this report's window. Nothing is said about why or when it ended, or whether <X> will be <S> again.” Lossless round-trip: “The deploy is not-yet running” ⇄ “The deploy is not running; it has not started running, and a start is still expected.” “The endpoint is no-longer responding” ⇄ “The endpoint is not responding; it was responding earlier and has stopped.” The window is the span the report is about; compose as_of(<t>) to pin the observation time and eta(<t>) to pin an expected start. Neither marker promises anything: not-yet is not a forecast that <S> will hold, and no-longer is not a claim that <S> will never hold again; a writer who knows an end is permanent says so separately. The bare negative stays legal and unmarked, as bare we stays legal beside clusivity: mark the phase when the reader's next action depends on it, which is wherever a report of a missing state is handed to someone who must choose between waiting and investigating. A state that never held and is not expected (“this key was never meant to be valid”) takes neither marker: say never, or give the reason. The positive phases still and already are ordinary English and are not markers, because English loses the phase only on the negative side. Hyphen loss gives the ordinary phrases not yet and no longer: same direction, binding lost.

    Matched form

    not-yet / no-longer
  4. discourse
    Ainglish form
    Stop <S>, finish-started. | Stop <S>, interrupt-started. — a stop directive scoped to a named set of task instances
    Plain English
    Two trailing qualifiers distinguish how a stop directive treats work already running. Use exactly one in an affirmative directive: Stop <S>, finish-started. / Stop <S>, interrupt-started. S names one bounded set of task instances, such as downloads D1-D4 or batch B. The task unit and the point at which the directive takes effect must be recoverable from the shared context. 'Started' means execution actually began before that point and the task is still running; being submitted, queued, scheduled, or reserved is not enough. Canonical concise English templates, substituting S unchanged: Stop <S>, finish-started. <=> In <S>, start no new tasks; let running tasks finish. Stop <S>, interrupt-started. <=> In <S>, start no new tasks; interrupt running tasks. Both policies forbid starting not-yet-running members of S after the stop takes effect. finish-started keeps the already-running members eligible to continue their existing execution to a normal terminal outcome; it does not demand that they succeed, restart a failed member, or drain the waiting queue. interrupt-started asks the executor to interrupt those already-running members promptly, rather than deliberately let their ordinary work finish. Interruption follows the already applicable safe, authorised mechanism; it is not permission to kill an unsafe process, bypass a constraint, or destroy an artifact. If interruption is unsupported, delayed, or unsafe, report that constraint and the actual remaining work rather than claiming everything stopped. The same external constraints apply to both the marked and English templates. For example, batch B contains four report downloads. D1 has finished, D2 is running, and D3-D4 are queued when the stop takes effect. With finish-started, D2 may continue; D3-D4 must not start. With interrupt-started, D2 is to be interrupted and D3-D4 must not start. Neither instruction changes D1's completed status. A directive is not a receipt that the requested stopping has happened. Scope and boundary rules: several running members all fall within the chosen policy; 'finish-started' does not pick just the one currently being watched. Tasks outside S are unaffected. A completion ordered before the stop is already finished; a start ordered after it is prohibited. If simultaneous events or missing records leave that ordering unknown, clarify it rather than inventing a race winner. If there are no running members, the two policies have the same immediate running-work effect, but still forbid new starts in S. Task granularity is fixed by the stated job definitions; neither qualifier relabels queued jobs as internal subtasks to evade the stop. Neither form says to delete queued records, roll back completed effects, discard partial files, issue refunds, save a checkpoint, retry, or restart later. Those policies require separate instructions. The stop remains in force for the named instances until changed by an authorised instruction; it is not a standing rule for every future batch. An authorised safety rule or failure can still terminate work under finish-started. Already completed or partially produced effects do not disappear merely because a running task is interrupted. This is the stop/continuation axis, not the register's stopped/done completion-report axis, all-or-nothing/keep-successes effect-retention axis, resume-from/redo-from-start restart axis, or in-parallel/in-sequence scheduling axis. Bare 'stop', 'cancel', or 'finish up' remains legal but does not select this convention. Quoting a directive does not issue it. The literal lowercase hyphenated forms are the registered spellings; spaced words are intelligible English, not extra machine-parsed aliases. A damaged or missing qualifier does not license guessing the other policy. This entry claims neither reliable typo correction nor successful remote cancellation.

    Matched english mapping

    …ks; interrupt running tasks. Both policies forbid starting not-yet-running members of S after the stop takes effect. finish-started keeps the already-running members eligible to c…