HARLEY'S OS · For Accountable Operations

J05 · Find, record and defer eligible work

Reading first on fresh entry; preserve positions during the visit. Existing task cap is two, +15 then +30. Reading/type/boundary exclusions and second-Later reasons are required patch work, not existing protection.

REFERENCE ONLY — mixed frame claims; see R3 manifest · Frame claims and source evidence

REFERENCE describes publication of a static artifact. PROPOSED in the canonical inventory describes its design lifecycle/history, not a competing KB lifecycle or a frame implementation status. BUILT TODAY = source-observed only at e984edfceecf2656f87cc9b0834a37eae985c3b1; IN PATCH = proposed pilot work; DESIGN ONLY = future work. Each frame badge follows its strongest dependency, including proposed chrome; its atomic claims retain their separate labels and source pointers. Availability/enablement and deployment remain UNKNOWN; runtime/UAT acceptance is NOT RUN. CURRENT, dates and STATUS: DONE describe reference currency or authoring only, never deployment, enablement or UAT passage.

IN PATCH = proposed, not built. DESIGN ONLY = later scope. BUILT TODAY atomic claims mean source-observed at e984edfc, switches/deployment unverified; no runtime verification claimed. All names, figures and times are synthetic examples. Static controls perform no actions.

Open work · correct actor

IN PATCH

Atomic claims: chrome: IN PATCH; task: BUILT TODAY; big: IN PATCH; later: IN PATCH. Strongest dependency: IN PATCH.

Mixed: source-backed behavior + proposed presentation. Static state; buttons are illustrative. Scroll within the phone and gallery.

Scope and evidence

chrome: IN PATCH — Δ0 — A397/A400; revised textual brand and staging chrome

task: BUILT TODAY — NF2 — dashboard/src/components/TaskList.tsx:106-138; src/tasks/respond.js:85-109

big: IN PATCH — Δ1 — 64 px Done; 56 px secondary actions; stable grouping

later: IN PATCH — Δ2/Δ3 — client AND server guards, separate reason persistence and rollup

Source-observed claims: e984edfceecf2656f87cc9b0834a37eae985c3b1. Runtime, switches and deployment unverified; no verified-built badge.

Routine · first Later

IN PATCH

Atomic claims: chrome: IN PATCH; task: BUILT TODAY; later: IN PATCH. Strongest dependency: IN PATCH.

Mixed: source-backed behavior + proposed presentation. Static state; buttons are illustrative. Scroll within the phone and gallery.

Scope and evidence

chrome: IN PATCH — Δ0 — A397/A400; revised textual brand and staging chrome

task: BUILT TODAY — NF2 — dashboard/src/components/TaskList.tsx:106-138; src/tasks/respond.js:85-109

later: IN PATCH — Δ2/Δ3 — client AND server guards, separate reason persistence and rollup

Source-observed claims: e984edfceecf2656f87cc9b0834a37eae985c3b1. Runtime, switches and deployment unverified; no verified-built badge.

Routine · second Later

IN PATCH

Atomic claims: chrome: IN PATCH; later: IN PATCH. Strongest dependency: IN PATCH.

Static state; buttons are illustrative. Scroll within the phone and gallery.

Scope and evidence

chrome: IN PATCH — Δ0 — A397/A400; revised textual brand and staging chrome

later: IN PATCH — Δ2/Δ3 — client AND server guards, separate reason persistence and rollup

Source-observed claims: e984edfceecf2656f87cc9b0834a37eae985c3b1. Runtime, switches and deployment unverified; no verified-built badge.

Boundary or third Later refused

IN PATCH

Atomic claims: chrome: IN PATCH; later: IN PATCH. Strongest dependency: IN PATCH.

Static state; buttons are illustrative. Scroll within the phone and gallery.

Scope and evidence

chrome: IN PATCH — Δ0 — A397/A400; revised textual brand and staging chrome

later: IN PATCH — Δ2/Δ3 — client AND server guards, separate reason persistence and rollup

Source-observed claims: e984edfceecf2656f87cc9b0834a37eae985c3b1. Runtime, switches and deployment unverified; no verified-built badge.

Manager sees the recorded answer

IN PATCH

Atomic claims: chrome: IN PATCH; later: IN PATCH. Strongest dependency: IN PATCH.

Static state; buttons are illustrative. Scroll within the phone and gallery.

Scope and evidence

chrome: IN PATCH — Δ0 — A397/A400; revised textual brand and staging chrome

later: IN PATCH — Δ2/Δ3 — client AND server guards, separate reason persistence and rollup

Source-observed claims: e984edfceecf2656f87cc9b0834a37eae985c3b1. Runtime, switches and deployment unverified; no verified-built badge.

ClassLater ruleScope
Reading; food/safety; cash; lock-up; accountableNo control; forged API attempts refusedΔ2 IN PATCH, including readings
Routine own occurrenceTwo fixed durations only if return ≤ original due and handoverServer serialisation, replay receipt and policy version
NoticeCurrent duration/count behavior retained; one-snooze cap is not enforced todayNo new cap in this patch
Named critical takeoverFive minutes, at most twice; cannot clear critical ownershipDESIGN ONLY A383
Pooled workNo LaterDESIGN ONLY
STATUS: DONE