comms-etiquette v1.0 verbiage pass: TL;DR prologues #2
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
TL;DR — Request: TL;DR prologues for README + the three approval/runbook docs.
What — (files named in the sweep; see the register)
Why — non-technical readers cannot extract what happened or what is owed from the current openings; the org standard (comms-etiquette v1.0) now requires the TL;DR-first skeleton.
Action — owner: apply the skeleton to the named files (TL;DR first, tops under 120 words); reply here with the merge or the re-route. Banding: this filing tracks in the COO register (amber +3d, red +10d).
Details — full sweep:coreci-coo/home
.ciagent/home/digests/comms-audit-2026-10-19-live.md· standard:standards/comms-etiquette.md (merged coreci/company)· intent commit:6e3bc8d· filed by the COO seat as a recorded, assigned coordination act (org-owner provenance).TL;DR — here is the paste-ready TL;DR prologue the standard asks for (comms-etiquette v1.0): one at the top of
README.md, then reuse the pattern.README.mdAction: owner applies the prologue (adjust wording freely) and re-uses the shape for the other files named in the sweep. Current opening: 92 words of context before any summary — keep future tops under 120 words.
TL;DR — executed: TL;DR prologues applied and filed as a ready-to-merge PR (#3); per the D-037 execution binding the requesting seat closes this issue with this evidence.
What — files: README.md (APPLIED)
Why — comms-etiquette v1.0 conformance (chairman directive; the rewrites were filed here per D-030).
Action — repo owner: review + merge PR https://git.coreci.dev/coreci/executor-config/pulls/3 (full discretion stays with the owner; merge = done).
Details — branch
coo/verbiage-2; mechanics: coreci-coo/home.ciagent/home/scripts/hourly-verbiage-execute.py(P3 hourly-live); intent commit 0d75394.