---
name: "skill-time-block"
type: skill
description: 'Place Aled''s committed work into calendar holds. Use this whenever running the Aide booking step, or when Aled asks to block time for what the cycle needs. Takes the sized worklist (skill-attention-sweep) and the week''s allocation (skill-time-management), reads the calendar''s free `work.*` windows, and proposes concrete blocks inside them, or into a bare morning or afternoon slot the Owner confirms where the lane carries no live window — batching short items, protecting deep work. Bounded auto-hold: within the envelope — committed-cycle items already sized by skill-attention-sweep, booked inside the exact-named hold windows — it writes the holds unattended; outside the envelope, a confirmed slot included, it proposes and waits for Aled. Never touches anything outside a hold window or a confirmed slot; never moves or responds to other events or invites (it may delete only a hold occurrence it has just filled).'
license: CC BY-NC-SA 4.0
---

# time-block

The booking half of Aide. It turns the sized worklist and the week's allocation into concrete calendar blocks, placed **only inside the hold windows, or in a morning or afternoon slot the Owner has confirmed** — unattended within a bounded envelope, and on Aled's confirmation outside it (bounded auto-hold, APP-828). It is the one part of Aide that writes the calendar — and it writes nothing anywhere else. Runs on the Linear and calendar connectors. Follows `convention-linear` and `core-operating-model` throughout.

**Ownership.** Owned by **Aide** (`A1-DE`); see `assistant-aide`. It is the last of Aide's three skills: `skill-attention-sweep` produces the sized worklist, `skill-time-management` proposes how the week's time should be allocated, and **this skill** places the specific holds.

## Trigger

Runs after `skill-attention-sweep` has produced the sized worklist and `skill-time-management` has proposed the week's allocation. On demand when Aled asks to block time for the cycle.

## The hold windows (`convention-hold-windows`)

Aide's calendar remit is bounded by the **hold windows**, and `convention-hold-windows` is canon for them: the live lanes, their scope, their observed days and times, and the window lifecycle. This skill does not restate the set — a restatement is exactly what went stale when the windows were renamed on 2026-09-08, leaving this section naming `work.Hold`, `mrp.Hold` and `ops.Hold`, none of which exist (APP-1162, APP-1447). Read the window set from the convention at the top of each run. Two of its rules bind every write on this page. **Read capacity by prefix match on `work.*`** — any Free `work.*` event counts as available hold time, so a lane the Owner adds by hand is seen rather than silently stranded (APP-759), and `hold.*` and `personal.*` are excluded from the capacity read. **Write into `work.*` events only**, into the window for the item's lane — and, since the Owner's ruling of 2026-10-20, into a confirmed bare morning or afternoon slot carrying no window name, which is the convention's clause (`convention-hold-windows`, *Left standing deliberately*) and `assistant-aide`'s scope, not this page's to restate, with `hold.Calls` written on an explicit Owner request alone and `personal.*` never. The missing-window rule is the convention's and is not restated here — read it from `convention-hold-windows`, *Read by prefix, write by exact name*, whose closing paragraph both states it and carves out a lane marked **retired**, where there is no event to find by decision of 2026-10-05.

## Behaviour

### Pass 1 — Read the holds and the worklist

Read the sized worklist (from `skill-attention-sweep`) and the allocation shape (from `skill-time-management`). Read the week's Free `work.*` window occurrences, and note anything already placed inside them from a prior run (idempotency — do not double-book a slot). **Also read back Aide's own prior blocks** — the block-identity read of the section below, which finds them by their durable identifier regardless of which window (or none) they now sit in, so a block the Owner has moved is recognised rather than re-booked.

### Pass 2 — Propose the blocks

Fit the sized items into the holds. **This runs on two cadences (APP-625):** **weekly**, place only the **deep-focus** blocks (whole, unbroken holds) plus the standing lanes — **read by name from `convention-hold-windows`' live table, never restated here**, per the no-restatement rule in *The hold windows* above — so the big work gets week-level protection and does not churn. **And `work.Unblock` is not a lane this pass fills:** it is **Owner-filled**, its content decided live by Aled at the end of the stand-up from whatever stand-up items ran over, so it is never placed into on the routine fill — and since the 2026-10-05 retirement there is no occurrence to read for capacity either (`convention-hold-windows`, the `work.Unblock` row) — the same exception `hold.Calls` carries (Owner correction, Aled 2026-09-23 — APP-1706). The wording this replaces named `work.Unblock` as a lane to fill and named two lanes that do not exist in the live table at all, "admin/networking" and "a reactive buffer": the generic cycle-goal lanes are `work.Focus` and `work.Overflow`, and no admin lane and no buffer lane is declared (`convention-hold-windows`, *The named windows and their lane scope*). It is the exact staleness this page's own restatement rule was written against — a restated set survived the 2026-09-08 rename and then survived an Owner correction on top of it (surfaced by APP-1761); **daily** (end of day), read Linear's *actual* state, check off what closed, and fill **tomorrow's** standing lanes at ticket granularity from the current sized worklist — done-early and net-new resolve overnight. **"Tomorrow" is the next working day, resolved against the day shape rather than against the next live window occurrence (APP-872, restated under the 2026-10-05 retirement and the Owner ruling of 2026-10-20 — APP-2162).** `convention-hold-windows` defers this restatement here by name, and it now reads: a day no longer has to carry a live `work.*` window for work to be done on it, so "tomorrow" is the **next working day**. A Friday-evening run's "tomorrow" is the next **Monday**; a weekend carries no working day and no window and is skipped; any pre-holiday run rolls forward the same way. Where that day carries a **live window for the item's lane**, the fill goes there as before. Where it carries **none** — now the common case, six lanes having been retired on 2026-10-05 — the block is **proposed** into that day's morning or afternoon on the convention's placement rule (mornings for focus and deep thinking; afternoons for overflow, smaller tasks and tasks that need actions rather than cognitive load) and waits for the Owner's confirmation. It is never written unattended: bounded auto-hold (APP-828) reaches only a write inside a live `work.*` event. **No retired lane is revived by this** — a proposed slot carries no name, no row in the window table and no recurrence (`convention-hold-windows`, *Left standing deliberately* and *Windows carry a working-day cadence*). Friday is exactly when queuing Monday's first holds is most useful, so the daily loop resolves the next window occurrence rather than no-opping into an empty weekend. **But "tomorrow" must also fall inside a committed cycle (APP-1047).** Every delivery team's cycle ends on the Sunday, so a Friday or Saturday run's Monday sits in cycle N+1; `skill-attention-sweep` resolves the target day's cycle and applies the approval test to it before handing over a worklist. Where that cycle has no Owner commit yet, the sweep hands over nothing and this pass books nothing — never fill Monday from the worklist of the cycle that is expiring (Owner decision, Aled 2026-09-03). The calendar is tomorrow's rendering of Linear, never a second copy of the queue. Then:

- **Batch the short items** — group 15m/30m items so they share a hold rather than fragmenting it.
- **Protect deep work** — give `deep-work` items a whole, unbroken hold; never chop a focus block into slivers.
- **Honour the allocation** — weight the placement to the lanes/ventures `skill-time-management` prioritised for the week.
- **Respect capacity** — place only what fits the available hold-time.
- **Buffer meetings (APP-793)** — leave **15 minutes clear either side of any meeting** (a non-`work.*` event falling inside or adjacent to a hold) for prep before and review after, and book no ticket work into that buffer. Where a meeting sits inside or touching a hold, carve the buffers out of the placeable time before fitting items, so a hold abutting an 11:30 call offers nothing from 11:15 and nothing until 12:15. Aide **leaves the buffer clear** rather than creating prep/review events — an event outside a hold window is still forbidden; the buffer is simply placeable time Aide declines to fill. The 15-minute default is configurable by Aled.

**Placement heuristics (APP-599 — governed by `skill-time-management`'s adaptation layer).** The adaptation layer and its evidence-graded reject-list live in `skill-time-management`; read them before editing any of these. Applied here at placement: **batch by cognitive mode as the primary axis** (decide / review / make), venture secondary within a block, one mode per block with other modes off the board; **split a whole 3h hold into two working stretches with a real 20–30 min break** (not 5-minute breaks — they do not restore performance on demanding work); **name the specific ticket and the specific next action in the calendar entry** rather than a generic lane label (the implementation-intention mechanism, the best-evidenced item in the review); and **prompt a 1-minute ready-to-resume note** when a block ends with an item unfinished. These are heuristics Aide *proposes changes to* via the retrospective pass; it never silently self-tunes them (distinct from the auto-hold booking grant).

### Pass 3 — Book: bounded auto-hold inside the envelope, propose-and-confirm outside it

Aide has graduated from propose-and-confirm to **bounded auto-hold** (APP-828). The envelope is precise: **committed-cycle items that `skill-attention-sweep` has already sized (15m/30m/1h/2h), booked inside the exact-named hold windows for their lane.** Within that envelope Aide **writes the holds unattended** — no confirmation step — because every constraint that made confirmation the safety has already been satisfied upstream: the item is in the approved cycle, it is sized, and it lands only inside a declared window. The rule "without approval, write nothing" is **superseded within the envelope** and **retained in full outside it**.

Outside the envelope, still propose-and-confirm — Aide proposes and waits for Aled:

- an item not in the committed cycle, or not yet sized — including any item drawn from a cycle that does not cover the day being booked (APP-1047);
- anything oversized (>2h) that `skill-attention-sweep` routed to Relay to split;
- any write that would land anywhere but inside an exact-named hold window;
- the genuine-overcommitment call about what to drop when demand exceeds live capacity (below).

**Emit the Proposal object as a record, not a gate (APP-833).** On each run, serialise the sized worklist, the `work.*` capacity slots, and the proposed blocks into the **Proposal object** and refresh the `aide-weekly-review` surface via `update_artifact`. Under bounded auto-hold this object is an **emit-and-proceed record**: it renders what Aide has already booked (inside the envelope) and what it is proposing for confirmation (outside it) — it is **not** a gate that holds the in-envelope write. The panel's accept/edit/reject controls let Aled adjust after the fact and confirm the out-of-envelope items. `update_artifact` on Aide's own review surface is not a Linear or calendar write and loosens no guardrail; the artifact is a rendering of the Proposal, and Linear stays source of truth. Headless fallback: with no Cowork/artifact bridge, fall back to the prose proposal.

**Hand-booked lane already full (APP-828).** The standing lane the daily loop expects to fill may already be full — some weeks Aled hand-books his own holds (a whole live `work.*` occurrence taken by STRATEGY blocks — the worked case was the `work.Focus` morning and the `work.Overflow` window, both retired on 2026-10-05 and now the day-shape convention rather than lanes to read). Read what already sits inside the window occurrence before booking, and treat a hand-booked block exactly as the never-touch guardrail requires: never move, overwrite, or delete it. Where the lane has no free capacity left, Aide books nothing into it and **surfaces** that the lane is already full rather than forcing work in or silently no-opping — it is a capacity signal, not an error. This is the same idempotency that stops a double-book, extended to Aled's own events.

**A meeting has a run-up and a tail, and both are booked or explicitly declined (APP-1164).** A meeting generates work on either side of itself that is on nobody's board when the week is planned: prep, whose deadline is fixed by someone else's diary, and the actions or write-up the meeting itself creates. So at the **weekly** pass, list the Busy events falling in or beside the coming window set and put two questions to the Owner in a single batched ask — does each need prep, and how long; does it need a write-up or action slot after, and how long — with a same-day catch for anything added mid-week, so a busy diary does not generate one question per event. Size each answer on the same 15m/30m/1h/2h scale and book it into the surrounding windows like any other item. **Silence is not consent:** an unanswered question books nothing and is named in the run report — a prep or write-up block is not a committed-cycle item and therefore sits outside the bounded auto-hold envelope (`skill-attention-sweep`; APP-828). And never book flush against the end of a call: the actions land in whatever comes next.

**Consume the filled occurrence (`convention-hold-windows`).** Once the blocks for a given window occurrence are written, Aide may **delete that single occurrence** so the calendar reads as real work rather than a reservation around it. Bounded precisely: the single occurrence only, **never the series**; gated on the successful write into it; an occurrence left unfilled (the worklist ran out, the week is light) survives. This is a narrow, named exemption to the never-delete guardrail below, not a softening of it.

**Overcommitment vs elapsed capacity (APP-829).** If there is **more committed work than hold-time**, do not silently drop items: flag the **overcommitment** to Aled, and send it to **Atlas** as a capacity signal, naming what did not fit. But count only the hold capacity **still ahead** at run time — windows already elapsed (a Monday morning gone by a Wednesday-afternoon run) are not capacity the week failed to absorb. Distinguish *genuine overcommitment* (demand exceeds the week's **full** live capacity) from *elapsed capacity* (demand exceeds only what **remains** because the run fired late — a run-timing artefact), and never report the second as the first. Re-timing the weekly loader to fire at cycle start (Monday AM) is the structural fix and is an Owner config action, not canon.

## Block identity and the read-back (APP-898)

The prefix-match capacity read (above) is what stops hand-added extensions being stranded — and it is exactly why a block the Owner drags to Tuesday afternoon, or out of the window set entirely, leaves Aide's field of view. Under bounded auto-hold the confirmation step that would once have caught a re-book is gone, so without a way to recognise its own prior blocks Aide would produce **one duplicate block per run, indefinitely**, from the first unnoticed Owner move. This primitive is therefore a **precondition of the APP-828 auto-hold grant**, not an enhancement of it. It is stated entirely in terms of **reads** — reading an event is not touching it, and nothing here loosens the never-move/never-delete write guardrail.

Three coupled clauses:

1. **Stamp a durable identifier at write time.** Every block Aide writes carries a **stable marker in the event** (an extended property or a structured tag in the body — **not the title alone**, since the Owner may retitle a block), so a later run can recognise the block as Aide's own regardless of retitling or relocation.
2. **Read back and diff before booking.** Before writing, search the calendar for Aide's own stamped blocks **regardless of which window they now sit in, or whether they sit in a window at all**, and diff *intended* (the APP-833 Proposal object — the "intended" side this clause needs) against *actual*. **Skip anything already placed** — an item whose block is found, wherever it now sits, is already booked and is not re-created.
3. **The Owner's manual move is authoritative.** A block found outside the window Aide first placed it in — or outside the window set entirely — is **still Aide's and still counts as booked**. His placement **wins**: Aide **records** the new placement, **counts** the item as booked, and **never restores** its original slot or **re-books** over it. The move is also captured as a learning signal for `skill-time-management`'s retrospective pass (APP-599) — the strongest evidence of his placement preference available.

## Guardrails

- **Writes only inside the hold windows, or into a slot the Owner has confirmed.** Never creates, moves, deletes, reschedules, or responds to any event or invite **outside** the windows on the run's own initiative — the one addition is the morning or afternoon block the Owner has confirmed in this run (`convention-hold-windows`, *Left standing deliberately*; APP-2162), which is created and then left alone like any other block — no touching the rest of Aled's calendar, ever. The one exemption is consuming a hold occurrence Aide has just filled: a single occurrence, never the series, gated on a successful write (`convention-hold-windows`).
- **Reading is not touching (APP-898).** The block-identity read-back reads events — including a block the Owner has moved — to recognise Aide's own prior work; it never restores, re-books, moves, or deletes. An Owner move is recorded and counted as booked, never clobbered.
- **Bounded auto-hold, not blanket autonomy (APP-828).** Within the envelope — committed-cycle, already-sized items, inside the exact-named windows — Aide writes holds unattended. Outside the envelope the "without approval, write nothing" rule is retained in full: oversized items, uncommitted or unsized work, any write outside a hold window, and the genuine-overcommitment drop call all still wait for Aled.
- **Only Aled's calendar.** Never touches anyone else's.
- **Idempotent.** Re-running does not double-book a slot already filled by a prior run — extended by the block-identity read-back to items the Owner has since moved (APP-898).
- **Overcommitment is surfaced, not hidden** — flag to Aled and signal Atlas; never quietly drop committed work.
- Aled is the gate at the envelope's edge. Inside the envelope Aide books unattended; outside it Aide proposes and Aled confirms before anything is written there.

## Setup

- Deployed as part of the Aide driver task. Connectors: Linear (read) and Calendar (read + write inside `work.*` only).
- Cadence: per cycle (weekly), after the sweep and allocation, or on demand.

Owned by Aide (A1-DE).

On finish, run skill-ops-retro capture on this run's friction: **search the Pulse queue first and add the evidence to a same-root note if one exists, otherwise file a new FRICTION note** for the drain pass to assess, in capture step 3's literal shape — team Apps, project os.Claude, `FRICTION:` title, labels `task` + `work:configuration` + `PUL-5E`, Backlog, unassigned — filing the friction, never the run report.
