The About Face Writes Identity and Guide

Note, 2026-09-10 — the face is retired; the door and the wire stand

GB-221 retired the About face. The structured write this record settles is unchanged: a person's guide edit now reaches FolioSchemaAboutWrite from the concertina fold ({ member: "guide" }) and the name from the header; the handle has no people-facing editor and stays read-only in the downloaded YAML. Goldie's door (point 3) is untouched, and her declaration proposals are diffed in the block's Control Panel box. Read "the About face a person edits" below as "the fold and the header".

Decision

Owner ruling, 2026-09-06 (folio unification plan, Stage D gate B; unblocks row 4, "About edit"). The wire was already settled from the evidence: About edits reach the server as the structured FolioSchemaAboutWrite, never as a page of YAML the server re-parses. This record settles what that write may carry, by door.

1. The About face a person edits writes identity and guide. For a block: handle, name (label) and guide. For a module: guide only, per Folio About Is Schema-Bound YAML. For a document: guide. Tags and access are not About-face writes: the lock has its own row, and tags are post-MVP.
2. A block's material is read-only on the About face for people. The clause text is edited on the Content face; the questions in the fields list; the starting level through the card's Starting-level menu. One door per fact. The About face still prints the material, so the card reads whole; the code row a person could type into today goes.
3. Goldie keeps her own door to the material. The owner's condition on this ruling: Goldie must be able to write the members the About face withholds from people — the numbering, and conditions (the logic member the target schema settles). Her writes are proposals (Stage E) and pasted or free text, which pass through parseFolioSchemaAbout to the same applyAboutCard seam the About executors use. The parser stays; the UI stops serialising.
4. The executors refuse what their door does not carry. The canvas door never sends material members, and the row 4 executors refuse a material member arriving through it, so the restriction is a server fact rather than a courtesy of the form. Goldie's door admits numbering and logic and is registered when Stage E registers her tools against Folios.

In plain terms: the cover note on a file says what the file is called and what it is for, and that is what you change on the cover note. The clause itself is amended on the page it sits on. The assistant may still draft numbering and "only if" conditions for you, through her own tray.

Consequences

• Row 4 lands three executors on the structured write: the block row write-edit facet about (handle, label, guide), write-module-about (guide) and write-document-guide (guide, its own row because it is stored proposal data). Each refuses content and data members from the canvas.
• The About face prints and edits the folio card (formatFolioSchemaAbout), not the legacy block card; its material rows render read-only.
• A card shown at a sealed edition offers no About edit (constraint 22), and landing row 4 closes the sealed-edition gate for module and document cards, which still gate on the reader's own pin today.
• The taken-handle question has one home, siblingHandleTaken; a handle the About face writes is refused there when a sibling holds it.
• The numbering flags lose their only people-facing editor. The starting level keeps its menu, but restart, headings, paragraphs and lists were editable by people only on the About face. After this ruling they are Goldie's to write, or a future chooser's behind the still-unbound "Change numbering" catalogue row; the owner may reopen that row when a person needs to set a flag by hand.