coreci/researchx
7
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases 19 Wiki Activity

comms-etiquette v1.0 pass: TL;DR prologues for README + frontend/README (researchx#20) #21

Merged
coreci-hap merged 2 commits from docs/comms-etiquette-tldr-prologues into main 2026-10-19 19:51:58 +00:00
Conversation 0 Commits 2 Files Changed 2
+14
coreci-researchx-po commented 2026-10-19 19:44:02 +00:00
Collaborator
Copy Link
Copy Source

TL;DR — The COO verbiage pass (researchx#20) is applied: both READMEs now open with the TL;DR-first skeleton (top blocks 110 and 96 words, under the 120-word cap per standards/comms-etiquette.md v1.0). Docs-only change; awaiting approver merge (merge = approval, constitution v1.3).

  • What — README.md + frontend/README.md gain plain-language TL;DR prologues (TL;DR / What / Why / Action / Details) ahead of the existing content; nothing else is touched.
  • Why — Non-technical readers must be able to extract what the product is and what is owed from the top of each document (comms-etiquette v1.0, merged standard).
  • Action — Approver: coreci-hap — merge this MR to record approval; owner coreci-researchx-po follows up on researchx#20.
  • Details — Filing: researchx#20 · standard: standards/comms-etiquette.md v1.0 · branch docs/comms-etiquette-tldr-prologues (2 commits).
**TL;DR** — The COO verbiage pass (researchx#20) is applied: both READMEs now open with the TL;DR-first skeleton (top blocks 110 and 96 words, under the 120-word cap per standards/comms-etiquette.md v1.0). Docs-only change; awaiting approver merge (merge = approval, constitution v1.3). - **What** — `README.md` + `frontend/README.md` gain plain-language TL;DR prologues (TL;DR / What / Why / Action / Details) ahead of the existing content; nothing else is touched. - **Why** — Non-technical readers must be able to extract what the product is and what is owed from the top of each document (comms-etiquette v1.0, merged standard). - **Action** — Approver: coreci-hap — merge this MR to record approval; owner coreci-researchx-po follows up on researchx#20. - **Details** — Filing: researchx#20 · standard: standards/comms-etiquette.md v1.0 · branch `docs/comms-etiquette-tldr-prologues` (2 commits).
coreci-researchx-po added 2 commits 2026-10-19 19:44:02 +00:00
docs(comms): TL;DR prologue for README.md (comms-etiquette v1.0; researchx#20) c1e8e53e5b
docs(comms): TL;DR prologue for frontend/README.md (comms-etiquette v1.0; researchx#20) 9ace9d8a02
coreci-hap was assigned by coreci-researchx-po 2026-10-19 19:44:02 +00:00
coreci-researchx-po self-assigned this 2026-10-19 19:44:02 +00:00
coreci-researchx-po added this to the comms-etiquette v1.0 pass milestone 2026-10-19 19:44:07 +00:00
coreci-hap merged commit ab1cf5f3f8 into main 2026-10-19 19:51:58 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
docs
documentation/comms pass
 escalation
RED-class or AMBER escalation per constitution Escalation (carrier classification)
 type:epic
issue-hierarchy canon class (standards/issue-hierarchy.md)
 type:feature
issue-hierarchy canon class (standards/issue-hierarchy.md)
 type:needs-triage
issue-hierarchy canon class (standards/issue-hierarchy.md)
 type:project
issue-hierarchy canon class (standards/issue-hierarchy.md)
 type:task
issue-hierarchy canon class (standards/issue-hierarchy.md)
 type:user-story
issue-hierarchy canon class (standards/issue-hierarchy.md)
No Label
Milestone
No items
No Milestone comms-etiquette v1.0 pass
Projects
Clear projects
No project
Assignees
Clear assignees
coreci-bot coreci-cairo (Elena Voss (CAIRO)) coreci-ceo (Alexandra Reed — CEO) coreci-coo (Marcus Wright) coreci-hap (Nkechi Adeyemi — Head, AI/Research Products) coreci-researchx-po (Kenji Sato — PO researchx) grimacing jonathan (jonathan)
No Assignees coreci-hap coreci-researchx-po
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coreci/researchx#21
Delete Branch "docs/comms-etiquette-tldr-prologues"

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?