Record the long-form service shape and the no-uptime-figures direction in the docs #218

New Issue

Closed

opened 2026-09-10 04:13:32 -05:00 by null · 1 comment

null commented

2026-09-10 04:13:32 -05:00

Owner

Docs that would send the next writer the wrong way once the two pages ship. Edited in place, in the same commit as the pages; no new markdown files.

docs/design/REDESIGN_REVIEW.md recommends "uptime guarantees", "SLA metrics" and "99.99% uptime" (its Include and Example Metrics lists, and lines 151, 231 and 284). Levi's direction of 2026-08-28 is the opposite: no generic uptime claim, only current, vendor-attributed and verified figures, and no superlatives. Add a dated correction.
README.md:227 says "uptime SLAs front and center". README.md:102-104 says the SPA hydrates on top and that /privacy-policy has a server-rendered fallback; neither is true.
docs/design/OVERHAUL_PLAN.md: add the long-form service-detail blueprint; line 695 lists an Accordion for FAQs, which the sheets rule out (FAQs are visible text).
docs/architecture/README.md: the content shape (page: { seo, hero, sections, related } and the block vocabulary), Governs gains src/data/** (nothing governs it today, so content-only commits fire no doc), and the false claim at lines 45-46.

Verify: python3 scripts/doc-triggers.py over the commit leaves no fired document unedited, and docs/design/REDESIGN_REVIEW.md carries the dated 2026-08-28 correction.

Docs that would send the next writer the wrong way once the two pages ship. Edited in place, in the same commit as the pages; no new markdown files. - `docs/design/REDESIGN_REVIEW.md` recommends "uptime guarantees", "SLA metrics" and "99.99% uptime" (its *Include* and *Example Metrics* lists, and lines 151, 231 and 284). Levi's direction of 2026-08-28 is the opposite: no generic uptime claim, only current, vendor-attributed and verified figures, and no superlatives. Add a dated correction. - `README.md:227` says "uptime SLAs front and center". `README.md:102-104` says the SPA hydrates on top and that `/privacy-policy` has a server-rendered fallback; neither is true. - `docs/design/OVERHAUL_PLAN.md`: add the long-form service-detail blueprint; line 695 lists an Accordion for FAQs, which the sheets rule out (FAQs are visible text). - `docs/architecture/README.md`: the content shape (`page: { seo, hero, sections, related }` and the block vocabulary), `Governs` gains `src/data/**` (nothing governs it today, so content-only commits fire no doc), and the false claim at lines 45-46. Verify: `python3 scripts/doc-triggers.py` over the commit leaves no fired document unedited, and `docs/design/REDESIGN_REVIEW.md` carries the dated 2026-08-28 correction.

null added this to the Batch 17: Long-form Unified Communications and Contact Center pages milestone 2026-09-10 04:13:32 -05:00

null added the

content

label 2026-09-10 04:13:32 -05:00

null referenced this issue from a commit

2026-09-10 05:05:25 -05:00

feat(content): publish Levi's approved UC and Contact Center pages

null commented

2026-09-10 05:05:50 -05:00

Author

Owner

Done in aff8033. docs/design/REDESIGN_REVIEW.md's Include and Example Metrics lists now carry a dated 2026-09-10 correction recording the owner's direction: a figure appears only when current, vendor-attributed and verified, a vendor SLA is never presented as a Queue North guarantee, and no unsupported superlatives. docs/design/OVERHAUL_PLAN.md gains the long-form service page blueprint and no longer recommends an Accordion for an FAQ. README.md stops claiming a server-rendered privacy-policy fallback that never existed and describes what hydration now does. docs/architecture/README.md carries the content shape and Governs src/data/**. scripts/doc-triggers.py reports no fired document left unedited.

Done in aff8033. docs/design/REDESIGN_REVIEW.md's Include and Example Metrics lists now carry a dated 2026-09-10 correction recording the owner's direction: a figure appears only when current, vendor-attributed and verified, a vendor SLA is never presented as a Queue North guarantee, and no unsupported superlatives. docs/design/OVERHAUL_PLAN.md gains the long-form service page blueprint and no longer recommends an Accordion for an FAQ. README.md stops claiming a server-rendered privacy-policy fallback that never existed and describes what hydration now does. docs/architecture/README.md carries the content shape and Governs src/data/**. scripts/doc-triggers.py reports no fired document left unedited.

null closed this issue

2026-09-10 05:05:50 -05:00