Banner
The real banner responds to the shared controls.
Checks
\nLogout must revoke immediately, which rules out any store whose invalidation is eventually consistent.
"},".facts":{"description":"A grid of labels and values for summary facts, written as a definition list. As a direct child of an `lf-option` titled with a ``, it floats right as a narrow column where the option is wide enough, so the options' figures line up.","x-example":"- \n
- Owner
- payments \n
- Rollout
- behind a flag \n
- \n
- Backfill the new store. \n
- Verify counts, then flip reads. \n
`, which can break inside a cell; a bare identifier is one unbreakable word that holds its column wide and squeezes the others. `page check --render` warns when a table scrolls sideways while one of its cells wraps. A bare `` is a column heading, drawn as a small muted label; ` ` names a row, in bold at the body's size. Add a `` when the section's heading doesn't say what the columns mean. For a few headline figures, put each figure in its own `dl` inside a `layout-tiles` block instead, and for alternatives the user picks between, use `lf-options`.","x-example":"\n Ceilings per plan, and what each is counted against. \n Plan A minute Counted against Free 60 the token Team 600 the token
"},"td.num":{"description":"A table cell holding a quantity, right-aligned so the figures in a column line up on their last digit. Put `class=\"num\"` on the column's heading cell too, or the heading sits left of its figures. Add the class to each such cell yourself. Leaf doesn't infer it, since \"60\" and \"60 sessions\" look alike.","x-example":" Enterprise 6,000 12,000 , its backing collapsed beneath. Native disclosure; find-in-page reaches the collapsed content.","x-example":"\n The parser drops the slash on self-closed custom tags
\n document.querySelector(\"lf-code\").textContent\n// \u2192 \"rest of the paragraph\"
\n"},"pre > code[class*=\"language-\"]":{"description":"A literal the user can select and quote, such as a command, a config file or a snippet of output. To color it, add `class=\"language-NAME\"` with a name from `$languages`; leave the class off where the body isn't source. For a walkthrough with numbered lines, highlighted ranges or remarks at a line, use `lf-code` instead.","x-example":"leaf page check ~/.local/state/leaf/pages/auth-diagnosis --render
"},"lf-ask":{"description":"A heading and context for the asks inside it, each answered separately.","x-instructions":"Give it a heading that states the shared question or context without leaning on the prose around it, with any eyebrow beside it in an ``. Include the evidence the user needs to answer. Each widget inside that asks for input stays its own ask with its own answer. Wrap the context in a `section` when the document needs a section landmark.","type":"object","properties":{"id":{"type":"string","pattern":"^[a-z0-9][a-z0-9-]*$"}},"required":["id"],"additionalProperties":false,"x-content":"markup","x-ask-context":true,"x-upgrade":false,"x-example":"\n \n What should a full store do?
\n The beta never reached the cap. This decides what the first workspace at it sees; each option draws its document list once the store fills.
\n \n editing: continuesrecommendedDrop the oldest documents Editing continues. My take: this keeps work moving without losing server data.\n \n \n \n \n editing: pausedPause offline editing Nothing leaves.\n \n \n \n \n \n \n "},"lf-gloss":{"description":"A short explanation the reader can open beside a phrase without leaving its sentence.","x-instructions":"Write a self-contained explanation at the first useful occurrence rather than on every repetition. Keep the phrase out of authored parentheses: print adds the explanation as a parenthetical note.","type":"object","properties":{"id":{"type":"string","pattern":"^[a-z0-9][a-z0-9-]*$"},"tip":{"type":"string","minLength":1}},"required":["tip"],"additionalProperties":false,"x-content":"markup","x-inline":true,"x-says":{"tip":"after"},"x-upgrade":true,"x-verbatim":true,"x-example":"Deploy through a walking skeleton before parallelizing."},"lf-num":{"description":"A measured number in prose, tied to the data run that produced it.","x-instructions":"Write the value with its unit as the element's text. Bind `source` to the feed that measures it, and set `run` to the receipt `leaf data set` returned. Add `via` when the source id doesn't say which command or query produced it.","type":"object","properties":{"id":{"type":"string","pattern":"^[a-z0-9][a-z0-9-]*$"},"source":{"type":"string","pattern":"^[a-z][a-z0-9-]*$"},"run":{"type":"string","minLength":1},"via":{"type":"string","minLength":1}},"required":["source","run"],"additionalProperties":false,"x-content":"markup","x-data":{"measurement":{"contract":"measured-scalar","source":"source"}},"x-inline":true,"x-measured":{"input":"measurement","run":"run"},"x-upgrade":false,"x-example":"The import now takes 184 ms at p95."},"lf-text-document":{"description":"A text file from page data with numbered lines, syntax coloring, and an optional Markdown or HTML preview.","x-instructions":"Bind `source` to the page's data source and name the file with `label`. Set `preview` to `markdown` or `html` to add Preview and Source tabs over the same text. `language` colors the source, and defaults to the preview's language. An HTML preview is a separate document that inherits no Leaf styles. With a preview, each tab scrolls inside a box `--lf-bound` tall, 28rem by default. To start it collapsed, put it inside `details`.","x-name":"label","type":"object","properties":{"id":{"type":"string","pattern":"^[a-z0-9][a-z0-9-]*$"},"source":{"type":"string","pattern":"^[a-z][a-z0-9-]*$"},"label":{"type":"string","minLength":1},"preview":{"type":"string","enum":["markdown","html"]},"language":{"type":"string"}},"required":["id","source"],"additionalProperties":false,"x-content":"empty","x-data":{"document":{"contract":"text-document","source":"source"}},"x-language":"language","x-upgrade":true,"x-example":"Migration plan
\n\nPrepare
Take a snapshot.
Check capacity
Leave headroom for the copy.
Move
Shift one cohort at a time.
\n Recent activity
\n "},"lf-options":{"description":"Alternatives the user can choose individually or as a set to answer a question.","x-instructions":"Keep shared premises and evidence with the group (lf-ask can frame its question and context), and each alternative's own case inside its lf-option. For an accept-or-reject proposal, a figure of today beside the change compares both answers, so it stays with the group. Use `multiple` when the picks form one answer because they depend on each other, such as a limit on how many; leave it off for mutually exclusive alternatives. Items the user can answer independently are separate asks (references/authoring-asks.md). The built-in Another option field takes unlisted answers, so add no catch-all option. Use `for` only to point at sections or work items that exist apart from the decision. An option the user adds stays in the group from the log, where the user put it; leave it out of revisions. A `multiple` ask needs the user's Done even when `chosen` is authored. `settled` collapses a decided group while keeping its options and anchors.","type":"object","properties":{"id":{"type":"string","pattern":"^[a-z0-9][a-z0-9-]*$"},"choose":{"type":"boolean"},"multiple":{"type":"boolean"},"settled":{"type":"boolean"},"restated":{"type":"boolean"}},"dependentRequired":{"settled":["id"],"multiple":["choose"]},"additionalProperties":false,"x-content":"members","x-word":"module","x-upgrade":true,"x-awaits":{"value":"choose","when":{"choose":[true],"settled":[false]},"retired":"settled","answered":{"choose":{"when":{"multiple":[false]}},"answer":{"when":{"multiple":[true]}}}},"x-state":{"choose":{"unit":"widget","record":{"kind":"attribute","attr":"chosen"}},"add":{"detail":{"type":"object","properties":{"option":{"type":"string","pattern":"^[a-z0-9][a-z0-9-]*$"},"text":{"type":"string","minLength":1}},"required":["option","text"],"additionalProperties":false},"unit":"option","creates":{"child":"lf-option","words":"text"}},"answer":{"detail":{"type":"object","additionalProperties":false},"unit":"widget"}},"x-example":"\n Where should run status appear?
\n Both choices preserve the existing run detail.
\n \n \n effort: lowrisk: medrecommended\n Status on the run list One join; failures are visible without a click.\n \n \n \n \n \n effort: nonerisk: low\n Leave the list alone No work; failures stay one click away.\n \n \n \n \n \n "},"lf-option":{"description":"One alternative in a decision: a compact label, or a card showing what choosing it gives the user.","x-instructions":"Start a card with small.tag labels naming the facts that tell the alternatives apart, then a `` title and a sentence giving its consequence. Mark the option you recommend with `recommended` after its labels, and give the reason in prose. `chosen` records the user's pick. Below, show what choosing it gives the user (references/authoring-asks.md): where options differ in arrangement, structure or mechanism, an svg.drawing thumbnail of each in the same frame, alike except where they differ; where they differ in how an existing interface looks, a capture of each; where they differ in behavior, that behavior working inside each; where they differ in wording, the words as they would appear. Add paragraphs or a fact rail only when that is not enough; a bare label suits an option that needs no case. Direct text takes inline Markdown; block content needs HTML children. A `for` target must stay useful whatever is decided, and does not supply the option's words. Rewriting a picked option needs `restated` ($restated).","type":"object","properties":{"id":{"type":"string","pattern":"^[a-z0-9][a-z0-9-]*$"},"for":{"type":"string","pattern":"^[a-z0-9][a-z0-9-]*$"},"chosen":{"type":"boolean"},"restated":{"type":"boolean"}},"required":["id"],"additionalProperties":false,"x-owners":["lf-options"],"x-content":"markup","x-text-format":"inline-markdown","x-refers":{"for":{}},"x-upgrade":false},"lf-code":{"description":"A source-code excerpt with syntax coloring, highlighted lines, and line-anchored remarks.","x-instructions":"Write the exact code inside pre at column 0, HTML-escaping & before < and >. Set language for source code and omit it for plain transcripts or command output. For excerpts, set lines to the ascending source ranges quoted, such as 1505-1507,1520-1527; hi and lf-note at then use those source numbers. A note addressed to an omitted line captions the elided row.","type":"object","properties":{"id":{"type":"string","pattern":"^[a-z0-9][a-z0-9-]*$"},"language":{"type":"string"},"hi":{"type":"string","pattern":"^[0-9]+(-[0-9]+)?(,[0-9]+(-[0-9]+)?)*$"},"lines":{"type":"string","pattern":"^[1-9][0-9]*(-[1-9][0-9]*)?(,[1-9][0-9]*(-[1-9][0-9]*)?)*$"}},"required":["id"],"additionalProperties":false,"x-content":"data","x-language":"language","x-upgrade":true,"x-example":"\ndef bracket(temp):\n if temp < 0:\n return \"steel\"\n return \"cedar\"\n
\n Freezing is the only threshold that matters. \n`, write a JavaScript expression for the options object you would pass to `Plot.plot`, HTML-escaping & before < and >. `Plot` and `width` are the names in scope, and the data goes inline. The chart requires an `ariaLabel` describing it. Leave `width` and `height` out of the options: read `width` to fit the ticks to the room, and set a height other than the default with `data-height` on the element. Write dates as ISO strings on an explicitly typed time scale, `utc` for days and months, and give moments a time zone, such as 2026-06-01T14:00Z. Use `var(--series-N)` for constant or categorical colors; a continuous color scale needs a Plot scheme. Title the chart in the heading or prose around it rather than with Plot's `title`. Label on the chart each value the page's argument cites, such as a spike the prose explains, with a text mark beside the point. When `page check --render` reports overlapping labels, use fewer category ticks, choose them by `width`, or give the axis label more margin.","type":"object","properties":{"id":{"type":"string","pattern":"^[a-z0-9][a-z0-9-]*$"}},"required":["id"],"additionalProperties":false,"x-content":"data","x-upgrade":true,"x-visual":"whole","x-height":400,"x-example":"\n{\n ariaLabel: \"Hours to first review by week: backend fell from 31 to 12, frontend from 18 to 11\",\n x: {type: \"utc\", ticks: \"monday\", label: null},\n y: {grid: true, label: \"hours to first review\"},\n color: {legend: true, range: [\"var(--series-1)\", \"var(--series-2)\"]},\n marks: [\n Plot.lineY(\n [\n {week: \"2026-05-04\", team: \"backend\", hours: 31},\n {week: \"2026-05-11\", team: \"backend\", hours: 26},\n {week: \"2026-05-18\", team: \"backend\", hours: 12},\n {week: \"2026-05-04\", team: \"frontend\", hours: 18},\n {week: \"2026-05-11\", team: \"frontend\", hours: 21},\n {week: \"2026-05-18\", team: \"frontend\", hours: 11},\n ],\n {x: \"week\", y: \"hours\", stroke: \"team\", marker: true},\n ),\n ],\n}\nThe option cards
\nThe chips now sit above the title, so a scanning eye reads cost before prose.
\n\n \n Heated perch Wire the south feeder. \n Squirrel baffle \n \n \n Camera mount \n \n "},"lf-column":{"description":"One named board column, including empty columns the user can move a card into.","x-instructions":"Write a label that names the column on its own. Use tone when landing here carries a status judgment, such as blocked, needing review, or done; otherwise leave it neutral.","x-name":"label","type":"object","properties":{"id":{"type":"string","pattern":"^[a-z0-9][a-z0-9-]*$"},"label":{"type":"string"},"tone":{"type":"string"}},"required":["id","label"],"additionalProperties":false,"x-owners":["lf-board"],"x-content":"members","x-tone":"tone","x-upgrade":false,"x-says":{"label":"before"}},"lf-card":{"description":"One board card whose identity and comments survive user moves.","x-instructions":"Lead with a `` title and follow with prose. Keep its id stable across moves. Rewriting a card the user moved needs restated; read $restated.","type":"object","properties":{"id":{"type":"string","pattern":"^[a-z0-9][a-z0-9-]*$"},"restated":{"type":"boolean"}},"required":["id"],"additionalProperties":false,"x-owners":["lf-column"],"x-content":"markup","x-work":true,"x-upgrade":false},"lf-tabs":{"description":"Several views shown one at a time: page navigation, a tabbed box, or a queue beside its open item.","x-instructions":"The first `lf-tabs` written directly in `main` is the page's navigation; any other tab set is a framed box within the page. Put the page's title and lede before page tabs, and the main current view first. Make each `lf-tab` a self-contained view; history, threads, versions and sign-off belong to the whole page. When current work no longer needs a view, remove it. Move any context still needed, and any passage an open thread or an unretracted decision is anchored to, into a `details` in the relevant tab. Use `list=\"side\"` for a queue listed beside the item it opens.","type":"object","properties":{"id":{"type":"string","pattern":"^[a-z0-9][a-z0-9-]*$"},"list":{"type":"string","enum":["side"]}},"required":["id"],"additionalProperties":false,"x-content":"members","x-upgrade":true,"x-patch":"members","x-views":true,"x-example":"\n \n Wire the first site this week.
\n \n \n Keep the original outcome and constraints in reach.
\n \n "},"lf-tally":{"description":"A count of the open asks in one region, such as the decisions left in a queue, with an optional control that goes to the next one.","x-instructions":"Write it empty with a stable id, and set `for` to the region whose asks it counts, such as a side-list `lf-tabs` queue. Place it where the reader looks for the queue's state, such as a workspace header beside its `.tag` chips. Add `next` for a Next on me control that steps through the asks waiting on the user. Don't also state the count in prose or chips; the tally keeps it current.","type":"object","properties":{"id":{"type":"string","pattern":"^[a-z0-9][a-z0-9-]*$"},"for":{"type":"string","pattern":"^[a-z0-9][a-z0-9-]*$"},"next":{"type":"boolean"}},"required":["id","for"],"additionalProperties":false,"x-content":"empty","x-inline":true,"x-prepaint":"00 of 00 to answerNothing to answer","x-refers":{"for":{}},"x-upgrade":true,"x-example":"\n Release triage
\n
\n \n\n \n \n Ship the retry cap?
\n \n Ship it \n Hold for a canary \n \n \n \n \n \n Remove the flag?
\n \n Remove it \n Keep it a release \n \n \n \n "},"lf-tab":{"description":"One labeled view in a tab set, optionally summarized and grouped in a side-list queue.","x-instructions":"In a side-list queue each item's `summary` shows under its label, so the user can choose an item without opening it. Start the summary with what the item is about, such as the problem a ticket reports, unless the label already says so, then what sets it apart from its neighbours, such as its age or suggested outcome. Leave out the item's group, which its heading shows. Where items fall into kinds the user works through in turn, such as merge, close and FYI, give each item its kind as `group` and place each kind's items together in the order to take them; adjacent tabs with the same group share one heading. Keep ids distinct across tabs, which share the page's id space.","x-name":"label","type":"object","properties":{"id":{"type":"string","pattern":"^[a-z0-9][a-z0-9-]*$"},"label":{"type":"string"},"summary":{"type":"string"},"group":{"type":"string"}},"required":["id","label"],"additionalProperties":false,"x-owners":["lf-tabs"],"x-content":"markup","x-upgrade":false},"lf-draft":{"description":"A block of text the user owns and can rewrite in place, with recorded revision history.","x-instructions":"Write the exact Markdown source as ``, one newline, the HTML-escaped source (& before < and >), then `
` right after it. HTML drops that first newline; every later character, indentation and trailing newlines included, is part of the draft. For a change you propose to existing prose, use a suggestion instead. With `needed`, a draft asks the user for an edit; without it, it is an optional editing surface. Use lf-ask when the request needs its own heading and evidence, or page sign-off to approve the whole page. Keep the user's exact source on revision (authoring-revisions.md, \"Honor user state\"); to replace an edited passage on purpose, write the new text and mark the draft `restated` ($restated).","type":"object","properties":{"id":{"type":"string","pattern":"^[a-z0-9][a-z0-9-]*$"},"needed":{"type":"boolean"},"restated":{"type":"boolean"}},"required":["id"],"additionalProperties":false,"x-content":"data","x-word":"module","x-awaits":{"value":"edit","when":{"needed":[true]},"answered":{"edit":{}}},"x-upgrade":true,"x-verbatim":true,"x-text-format":"markdown","x-state":{"edit":{"unit":"widget","record":{"kind":"body"}}},"x-example":"\nAdds --dry-run to every mutating command.
\n \n effort: lowPaper maps Nothing to charge. \n effort: medrecommendedDedicated GPS Offline maps, week-long battery. My take: this is the better field tool. \n \n "},"lf-pane":{"description":"A reading region with an optional header and footer, independently scrollable inside a full-height workspace.","x-instructions":"For independent scrolling, place the pane as a full-height workspace\u2019s body or a direct cell; elsewhere the page scrolls. Wrap multiple body blocks in one div or section. Use label to name the region accessibly and its header for the visible heading. Put action widgets in the direct footer when they should remain reachable as the body scrolls.","x-name":"label","type":"object","properties":{"id":{"type":"string","pattern":"^[a-z0-9][a-z0-9-]*$"},"label":{"type":"string","minLength":1}},"required":["id","label"],"additionalProperties":false,"x-content":"markup","x-reading-role":"pane","x-upgrade":true,"x-verbatim":true,"x-example":"Read the selected record.
`, HTML-escaping & before < and >. Give each diagram an `accTitle` naming its subject and an `accDescr` describing its relationships, for a reader who can't see it. Draw a chain of more than three steps top-down (`flowchart TD`), since a long horizontal chain runs past the page's edge. Give a node that needs its own tone a Mermaid class styled in page CSS with theme tokens. Without `parts`, the whole diagram is one comment target; with `parts=\"all\"`, each named box, such as a flowchart node or a sequence participant, is a target of its own. Edges and messages never are.","type":"object","properties":{"id":{"type":"string","pattern":"^[a-z0-9][a-z0-9-]*$"},"parts":{"const":"all"}},"required":["id"],"additionalProperties":false,"x-content":"data","x-upgrade":true,"x-visual":{"parts":"parts"},"x-space":"available","x-height":true,"x-example":"\nflowchart TD\n accTitle: Checkout from cart to receipt\n accDescr: The cart reaches a payment decision; a paid order produces a receipt.\n Cart([Cart]) --> Pay{Paid?}\n Pay --> Receipt[(Receipt)]\n` at column 0, HTML-escaped (& before < and >), or entity text in the patch will change silently. Keep Git's file headers and metadata, and make each hunk's `@@` counts match its lines. Keep the leading space on context lines, and write a context line that is only a space as ` ` so HTML parsing keeps it. With `source`, bind a page-owned patch feed or files manifest and leave the `` empty. Add `collapsed` to start every file closed.","type":"object","properties":{"id":{"type":"string","pattern":"^[a-z0-9][a-z0-9-]*$"},"source":{"type":"string","pattern":"^[a-z][a-z0-9-]*$"},"collapsed":{"type":"boolean"}},"required":["id"],"additionalProperties":false,"x-content":"data","x-data":{"document":{"contract":"unified-diff","source":"source"}},"x-upgrade":true,"x-shadow":true,"x-thread-surface":true,"x-height":true,"x-example":"\ndiff --git a/feeders/mount.py b/feeders/mount.py\n--- a/feeders/mount.py\n+++ b/feeders/mount.py\n@@ -1,2 +1,2 @@\n def bracket():\n- return \"plastic\"\n+ return \"steel\"\n
\n```\n\nKeep the unchanged items in the tree as landmarks. In a large repository, give each widget one file or entry point. Don't copy the output into markup, add attribute reads as calls, or draw separate before and after diagrams.","type":"object","properties":{"id":{"type":"string","pattern":"^[a-z0-9][a-z0-9-]*$"},"source":{"type":"string","pattern":"^[a-z][a-z0-9-]*$"},"diff":{"type":"string","pattern":"^[a-z0-9][a-z0-9-]*$"}},"required":["id","source","diff"],"additionalProperties":false,"x-content":"empty","x-data":{"document":{"contract":"text-document","source":"source"}},"x-refers":{"diff":{"via":"$diff.widgets","where":{"role":"patch"}}},"x-upgrade":true,"x-height":true,"x-example":"Which notification should we build?
Status strip
The real status strip responds to the same controls.
Build the Waiting for a Playwright recording.
"},"lf-trace-bookmark":{"description":"A labeled link to one captured image or action phase in its trace.","x-instructions":"Set `target` to a capture in the trace: `trace-ARCHIVE_SHA256-image-IMAGE_ID` or `trace-ARCHIVE_SHA256-phase-ACTION_ID-PHASE`, where PHASE is before, action, after, start or end. Read the ids from the imported source. A target the recording lacks shows as unavailable. In an `lf-trace-compare`, give the bookmarks for the same result in each recording the same `key`; Leaf never pairs them by time or label.","type":"object","properties":{"label":{"type":"string","minLength":1},"target":{"type":"string","pattern":"^trace-[a-f0-9]{64}-(image|phase)-[a-z0-9-]+$"},"key":{"type":"string","pattern":"^[a-z][a-z0-9-]*$"}},"required":["label","target"],"additionalProperties":false,"x-content":"empty","x-owners":["lf-trace"],"x-name":"label","x-example":"Generative UI for your agent.
The agent builds the page your task needs.