Two standards-corpus guides: progressive web apps and offline-first applications - #178
Open
wschenk wants to merge 1 commit into
Open
Two standards-corpus guides: progressive web apps and offline-first applications#178wschenk wants to merge 1 commit into
wschenk wants to merge 1 commit into
Conversation
GDE-014 (progressive web apps) and GDE-015 (offline-first applications), written for The-Focus-AI/standards best-practices/ in that repository's guide format and validated against its renderer and document validator. Every claim cites the walking-thoughts commit, PR, or ADR that taught it. Drafted under docs/standards/ because agent tokens cannot push to the standards repository; the README records the destination and the copy- verbatim adoption path (STD-006 3.9). Co-authored-by: Will Schenk <wschenk@gmail.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
wschenk
marked this pull request as ready for review
August 29, 2026 17:20
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No-ticket: true
Two guides distilled from this repository's full history — 210 commits, 19 ADRs, and the merged PR record — written for The-Focus-AI/standards
best-practices/and staged underdocs/standards/because agent tokens cannot push to that repository.GDE-014-progressive-web-apps.md— installability (the maskable-only icon failure, pinning manifestidbefore Chrome strands a phantom install, root-layout service-worker registration, the in-app install button), the hand-rolled service worker (redirect-safe per-path precache, shell refresh on online visits so byte-identicalsw.jsdeploys cannot strand phones, crawling cached HTML for/_next/staticchunks, deep-link fallbacks), the "one bar is worse than offline" navigation cluster, media capture and geolocation on mobile web, the recurringmin-width: autolayout trap, auth × PWA interactions, and the Playwright harness that made it all stick.GDE-015-offline-first-applications.md— the local durable commit invariant, append-only history with a frozen processing basis, the five-state visible lifecycle, the serialized hydrate → recover → outbox sync cycle, idempotency key scoping, the retry-storm lessons (6,400-attempt jobs, ~19k requests per 40 minutes), device-owns-unsynced / server-owns-settled convergence, media retention and verified deletion, capability honesty (no gateway model reads audio; fakes never reach production), sync-schema migration guards, trash/purge as synced state machines, and verified staged-activation Offline Region packs.Every claim cites the walking-thoughts commit, PR, or ADR that taught it. Both files pass the standards repository's own conformance tooling:
node scripts/validate-documents.mjs(38 documents OK) andnode scripts/render-standard.mjs(ok GDE-014 Guide under STD-007,ok GDE-015 Guide under STD-007, STD-008).014/015were the next free numbers on 2026-08-29; the README notes the copy-verbatim adoption path per STD-006 §3.9 and renumbering per §3.11 if the sequence moves.Per STD-001 §3.14 these are guides, not standards: any binding clauses extracted from them into an STD are a person's call to ratify.