Janady13/thatstupidcomputer / private/standards/SEO-AIO-Library.txt · Lines 7501–9000

7501============================================================================== 7502DOCUMENT 062 OF 135 7503Title: Next.js metadata, streaming and rendering validation 7504Path: Library/Framework/framework-nextjs-metadata-validation.md 7505Group: baseline 7506Label: NEW · researched 7507Review status: new_researched_module 7508============================================================================== 7509 7510# Next.js metadata, streaming and rendering validation 7511 7512**Edition:** 2026.09.09 · **Status:** researched guidance and proposed operating procedure 7513**Applies to:** Next.js App Router and React public-content routes 7514**Evidence:** S14, S24, S25, S26, S27 in the [source register](../../Research/SOURCE-REGISTER.md). 7515**Boundary:** Official facts are attributed below. Acceptance gates, priorities and workflows are agency recommendations, not secret ranking factors or performance guarantees. 7516 7517## Pin the implementation context 7518 7519Record the installed Next.js and React versions, router, runtime, hosting target, cache strategy and deployment adapter. Do not copy a server configuration from another client's machine or assume that a framework version mentioned in an old document matches the project. 7520 7521Next.js supports metadata streaming and has an `htmlLimitedBots` configuration introduced in 15.2. A custom expression replaces its default list rather than extending it automatically. The official documentation recommends leaving the default sufficient for most cases. [S25–S27] 7522 7523## Route contract 7524 7525For each public route, identify the content owner, metadata source, intended canonical, social preview and required initial content. Static metadata is appropriate when the values are static; dynamic metadata should be derived from the actual route record. Ensure invalid identifiers lead to the intended missing-page behavior rather than fabricated titles or successful empty pages. 7526 7527Keep canonical and visible product/article identity consistent. Do not generate one canonical in the initial response and change it to a conflicting value after hydration. Google can render JavaScript, but that does not prove every retrieval client sees the same content or behaves identically. [S14] 7528 7529## Capture the right evidence 7530 7531Test a normal browser and the specific limited consumers relevant to the project. Save complete response bodies, response timing, headers and rendered output; a first-chunk-only grep can misread streamed metadata. Distinguish “not in the first chunk” from “not delivered at all.” A spoofed user agent is a response-variant test, not proof that a real provider fetched the page. 7532 7533Check title, description, canonical, language, robots directives, Open Graph fields and JSON-LD for duplicates and contradictions. Use a slow content source and a failure fixture to test error behavior. Recheck after a content update to expose cache-invalidation problems. 7534 7535## Configuration changes 7536 7537Do not disable metadata streaming globally simply because a legacy checklist says all tags must be in the first byte. Establish a failing consumer case, compare alternatives and measure the latency tradeoff. If overriding `htmlLimitedBots`, preserve the intended consumers and verify the resulting behavior against the pinned release. 7538 7539## Release result 7540 7541The acceptance package contains version information, template tests, raw and rendered captures, exceptions and the reason for any advanced override. The offline HTML checker in this release can inspect a saved complete response but cannot execute the Next.js app or certify streaming behavior. Browser and production-edge tests remain required. 7542 7543React itself is not an SEO verdict. Choose CSR, SSG, SSR or a hybrid based on route purpose, user experience and the consumers that must retrieve it. Treat rendering choice as an engineering decision with evidence, not a claim that every public CSR route is inherently professional malpractice. [S24] 7544 7545============================================================================== 7546DOCUMENT 063 OF 135 7547Title: Next.js SEO implementation — versioned route contracts 7548Path: Library/Framework/framework-nextjs.md 7549Group: baseline 7550Label: REWRITTEN · researched 7551Review status: rewritten_current_guidance 7552============================================================================== 7553 7554# Next.js SEO implementation — versioned route contracts 7555 7556**Edition:** 2026.09.09 · **Status:** researched replacement of the legacy entry point 7557**Primary sources:** S14 S24 S25 S26 S27 in the [source register](../../Research/SOURCE-REGISTER.md). 7558**Preservation:** The complete prior document remains byte-for-byte in `99-Originals/Framework/framework-nextjs.md`. This replacement deliberately removes unsupported universal rules; it does not claim to have tested a client website. 7559 7560## Record the environment before writing code 7561 7562Capture the installed Next.js/React versions, App versus Pages Router, runtime, deployment adapter and caching strategy. An older nginx/PM2 example is not a requirement for every Next.js deployment. Choose the project's actual supported hosting path. 7563 7564Use the framework's current APIs for the pinned release. A snippet that compiles against another major version is not ready merely because its comments say “2026.” Check route parameters, data fetching, metadata behavior and error handling against the installed version. 7565 7566## Public route contract 7567 7568For each route class define the source record, meaningful content, canonical, indexing intent, social metadata, structured data and user action. Use static generation or server rendering where it provides the required delivery reliability; use client interaction where it serves the task. React itself supports multiple rendering approaches through frameworks. [S24] 7569 7570Missing records need the intended not-found behavior, not an empty successful template. Redirects must follow the approved URL map. Do not emit a staging domain, unresolved slug or default product name as production metadata. 7571 7572## Metadata and streaming 7573 7574Next.js documents metadata streaming and limited-bot handling. The `htmlLimitedBots` option, introduced in 15.2, replaces the default list when customized. Do not blindly add a partial regex and assume the framework keeps all existing matches. [S25–S27] 7575 7576Use [Next.js metadata validation](framework-nextjs-metadata-validation.md) for complete-response captures and consumer-specific tests. A first-byte grep is not a sufficient streaming test. Disabling streaming globally is an advanced tradeoff requiring evidence, not a mandatory SEO improvement. 7577 7578## Structured data and content 7579 7580Generate public JSON-LD from the same approved record as the visible page. Serialize safely, including escaping `<` when embedding untrusted text in a script element. Avoid duplicating a graph across CMS and application layers with conflicting identities. 7581 7582Google can render JavaScript; this does not prove every consumer will execute the same code or see the same output. Test the actual route against its required consumers and preserve useful content when nonessential scripts fail. [S14] 7583 7584## Caching and release 7585 7586Identify which content can be cached, what invalidates it and how changes reach page HTML, metadata and feeds. Test stale data, missing data and failed upstream requests. Do not apply `no-store` to every page by default or cache personalized content publicly because a generic guide says caching helps SEO. 7587 7588Run route, accessibility, business-function and live-edge checks before accepting the release. The package's offline tools inspect saved artifacts only; they do not execute a Next.js build. Client-specific implementation remains a separate step grounded in the actual codebase and installed dependencies. 7589 7590============================================================================== 7591DOCUMENT 064 OF 135 7592Title: Preferred Sources and publisher relationship design 7593Path: Library/Framework/framework-publisher-preferences.md 7594Group: baseline 7595Label: NEW · researched 7596Review status: new_researched_module 7597============================================================================== 7598 7599# Preferred Sources and publisher relationship design 7600 7601**Edition:** 2026.09.09 · **Status:** researched guidance and proposed operating procedure 7602**Applies to:** Eligible publisher sites and reader-facing preference controls 7603**Evidence:** S45, S43, S44 in the [source register](../../Research/SOURCE-REGISTER.md). 7604**Boundary:** Official facts are attributed below. Acceptance gates, priorities and workflows are agency recommendations, not secret ranking factors or performance guarantees. 7605 7606## A reader preference is not an SEO switch 7607 7608Google provides a Preferred Sources workflow and publisher guidance, including an interactive button option. The feature is based on reader choices and supported Search contexts. Do not market a button installation as guaranteed placement, universal availability or a substitute for useful publishing. [S45] 7609 7610## Applicability assessment 7611 7612Verify the current feature's domain, page and market requirements from the official guide before implementation. Confirm that the client is a relevant publisher and that the destination identifies the correct publication. A generic service business may gain more from a better service page than from a publisher-specific feature. 7613 7614Record the intended reader action and why it is useful. Use clear wording that tells the reader what the preference affects. Do not obscure the destination, imitate a browser warning or make the action appear necessary to access ordinary content. 7615 7616## Design and implementation 7617 7618Follow the current official integration method rather than embedding a stale copied URL pattern. Keep the control accessible and visually distinct from primary navigation or a purchase action. Test keyboard access, mobile layout, loading failure and the destination on the supported surfaces. 7619 7620Avoid introducing heavy scripts or layout shifts for a secondary preference action. Preserve core content when the integration fails. Do not require an unrelated subscription or collect unnecessary personal information merely to expose the preference control. 7621 7622## Measurement 7623 7624Track an approved button interaction separately from a confirmed preference or later Search exposure. A click on the button does not prove the user completed the preference flow, and subsequent traffic cannot automatically be attributed to it. Use the current platform report definitions and disclose any unavailable outcome. 7625 7626Where the publication also has supported social/video profiles, maintain consistent factual identity and evaluate their Search Console properties separately. Those reports measure different assets and should not be combined into a fabricated publisher-authority score. [S43, S44] 7627 7628## Acceptance 7629 7630Deliver the applicability record, official-source date, approved UI copy, tested destination, accessibility evidence and measurement limitations. Remove or revise the integration if its official contract changes. This library release adds the workflow but does not install a button or change any publisher account. 7631 7632============================================================================== 7633DOCUMENT 065 OF 135 7634Title: Regional Search eligibility and policy differences 7635Path: Library/Framework/framework-regional-search-eligibility.md 7636Group: baseline 7637Label: NEW · researched 7638Review status: new_researched_module 7639============================================================================== 7640 7641# Regional Search eligibility and policy differences 7642 7643**Edition:** 2026.09.09 · **Status:** researched guidance and proposed operating procedure 7644**Applies to:** International clients and geographically limited search features 7645**Evidence:** S41, S42, S40 in the [source register](../../Research/SOURCE-REGISTER.md). 7646**Boundary:** Official facts are attributed below. Acceptance gates, priorities and workflows are agency recommendations, not secret ranking factors or performance guarantees. 7647 7648## Keep three geographies separate 7649 7650Record the business's operating jurisdiction, the content's intended market and the searcher's location. They are not interchangeable. A feature may depend on user geography, language, query category and provider participation even when the website is technically correct. 7651 7652Google's regional-differences documentation describes feature-specific availability rather than one worldwide Search experience. The August 2026 site-reputation policy update also changes treatment in relation to the EEA. Do not infer that a rule applies everywhere from one local screenshot, or that regional enforcement differences authorize abusive content. [S41, S42] 7653 7654## Eligibility register 7655 7656Create one row per proposed feature: engine, feature, content type, target countries, languages, required partner/account participation, required data, evidence source, source date and observed availability. Use `unknown` where a condition has not been verified. Do not market an unavailable feature as part of a guaranteed deliverable. 7657 7658For international URLs, define the canonical and alternate-language relationships before implementation. Hreflang is for localized alternatives; it is not a substitute for translation quality or a technique for making unrelated pages equivalent. Test reciprocity and URL validity using the selected implementation method. [S40] 7659 7660## Research and deployment workflow 7661 7662Begin with the current official feature documentation, then verify the client's actual account and market. Keep compliance review separate from technical eligibility. For example, a technically valid product offer may still need business approval for local terms, currency, tax presentation or availability. 7663 7664Test representative locale routes without forcing the tester through an irreversible geolocation redirect. Ensure a customer can select the appropriate language/market. Record how the application behaves when location cannot be inferred, a locale is unsupported or a product is unavailable. 7665 7666## Policy incidents 7667 7668When a manual action or policy notice appears, preserve its exact text, affected scope, date and property. Analyze the specific issue instead of applying an old universal recovery recipe. An EEA-related enforcement distinction concerns the documented treatment; it is not a promise that an affected section will retain visibility. 7669 7670Coordinate SEO, operations and qualified legal/compliance review for jurisdiction-specific decisions. This module is a technical research workflow, not legal advice. Do not remove user protections or fabricate editorial independence to chase a regional exception. 7671 7672Acceptance requires a signed eligibility register, locale test evidence, source dates and a clear distinction between documented availability and observed client access. A globally deployed website is not evidence that every Search feature is globally available. 7673 7674============================================================================== 7675DOCUMENT 066 OF 135 7676Title: Research maintenance and documentation drift control 7677Path: Library/Framework/framework-research-maintenance.md 7678Group: baseline 7679Label: NEW · researched 7680Review status: new_researched_module 7681============================================================================== 7682 7683# Research maintenance and documentation drift control 7684 7685**Edition:** 2026.09.09 · **Status:** researched guidance and proposed operating procedure 7686**Applies to:** Ongoing stewardship of this library 7687**Evidence:** S01, S02, S04, S05, S47 in the [source register](../../Research/SOURCE-REGISTER.md). 7688**Boundary:** Official facts are attributed below. Acceptance gates, priorities and workflows are agency recommendations, not secret ranking factors or performance guarantees. 7689 7690## Use a source ledger rather than a refresh slogan 7691 7692Each maintained rule needs an owner, current source, observed date, affected modules and a next-review condition. A document is not current merely because its title includes the year. Preserve the difference between publication date, source update date, retrieval date and the effective date of a product change. 7693 7694This release encountered a concrete example: older Google AI documentation described overall reporting, while a later announcement and help page document a dedicated report. Keep a conflict record so the next editor does not accidentally restore the older interpretation. [S03–S05 in the source register] 7695 7696## Proposed review cadence 7697 7698Review engine bot controls, eligibility changes and critical policies before each relevant deployment and on a recurring team-owned schedule. Review framework-specific examples when the installed major version changes. Review business facts when their source changes. These are recommended operating practices; no background monitoring service has been scheduled by this package. 7699 7700Use the official changelog as a trigger, not a substitute for reading the affected page. A documentation clarification may not mean a new ranking factor or a newly launched feature. Record the event type explicitly. [S01] 7701 7702## Change workflow 7703 7704Open a change record with the source, exact changed claim, affected modules, urgency and test impact. Update the canonical owner first, then dependent tiers, templates, sales wording and acceptance tests. Keep a concise before/after explanation and the original evidence location. 7705 7706For protocol and software changes, distinguish stable, older supported and draft versions. A draft security page can inform a threat review, but should not silently redefine a pinned production implementation. The MCP module intentionally records version boundaries. [S47] 7707 7708## Automated checks 7709 7710Run the supplied library auditor for local file links, JSON syntax, metadata references and preserved-original hashes. These checks do not confirm that an external page is still live or that its content supports a claim. External link checking and semantic source review are separate activities. 7711 7712Maintain a queue for unverified historical claims. A regex match is a lead for review, not a confirmed defect. Close a claim only after a reviewer records a disposition: verified, narrowed, superseded, removed or still unresolved. 7713 7714## Acceptance 7715 7716Every release should carry a manifest, migration map, source register, coverage matrix and test report. Mark retained legacy documents honestly instead of assigning a current research stamp to untouched prose. Preserve rollback copies and make the authoritative entry point obvious to both humans and AI assistants. 7717 7718The objective is controlled, traceable improvement, not endless document growth. Add a new module only when it owns a distinct decision, implementation contract or evidence workflow. 7719 7720============================================================================== 7721DOCUMENT 067 OF 135 7722Title: Structured-data lifecycle and feature eligibility 7723Path: Library/Framework/framework-schema-lifecycle.md 7724Group: baseline 7725Label: NEW · researched 7726Review status: new_researched_module 7727============================================================================== 7728 7729# Structured-data lifecycle and feature eligibility 7730 7731**Edition:** 2026.09.09 · **Status:** researched guidance and proposed operating procedure 7732**Applies to:** Every schema template and client deliverable 7733**Evidence:** S01, S20, S21, S22, S23 in the [source register](../../Research/SOURCE-REGISTER.md). 7734**Boundary:** Official facts are attributed below. Acceptance gates, priorities and workflows are agency recommendations, not secret ranking factors or performance guarantees. 7735 7736## Three separate questions 7737 7738Ask whether the JSON is syntactically valid, whether the vocabulary describes the page truthfully, and whether a named consumer currently supports a related feature. These are separate checks. Passing a generic validator does not establish rich-result eligibility or guarantee appearance. [S20] 7739 7740Google stopped showing FAQ rich results on May 7, 2026. HowTo rich results were retired in September 2023. This does not make the underlying Schema.org vocabulary invalid, but these Google features must not be sold as current benefits. [S01, S21] 7741 7742## Registry design 7743 7744For every template, maintain type, consumer, feature, required properties, recommended properties, page-class applicability, policy constraints, current status, source date, test method and owner. Mark entries as supported, restricted, deprecated, vocabulary-only or unverified. Avoid a single “schema installed” column. 7745 7746Keep eligibility logic next to the generator. A Product template needs genuine product information and a current offer when it represents a purchasable item; a LocalBusiness template must not manufacture a storefront; an Article must identify its actual content and authorship. Optional ratings should never be filled with invented values simply to satisfy an example. 7747 7748## Change management 7749 7750When a feature is retired, search the library, sales scope, QA tests and codebase for the feature name. Update expected outcomes and acceptance criteria. Do not automatically delete useful customer-facing questions or step-by-step instructions because a search decoration disappeared. 7751 7752If markup still serves another documented consumer, retain it with that consumer and rationale recorded. Otherwise evaluate maintenance cost against actual use. Remove dead code through a tested change, not a blind text replacement across every type name. 7753 7754## Review integrity 7755 7756Review and rating markup must reflect genuine visible evidence. Google's review guidance excludes fake or undisclosed incentivized reviews and restricts self-serving LocalBusiness/Organization star eligibility. [S22] Disclosing an incentive is not permission to fabricate an experience or ignore another platform's stricter policy. 7757 7758## Acceptance evidence 7759 7760Save representative rendered pages, generated JSON-LD, validator results, policy checklist and source version. For commerce, compare offer values with the live landing page and approved feed. Record known warnings rather than creating fake data to eliminate them. For large deployments, test edge cases such as missing images, unavailable products, absent ratings, multiple authors and multilingual URLs. 7761 7762The `Schema.org` directory contains small fictional examples and a release checklist. They are intentionally not marked as Google-approved or production-ready. Replace example facts, validate the intended feature and verify the visible page before publishing. The library's schema work is semantic modeling and eligibility engineering, not a promised citation multiplier. 7763 7764============================================================================== 7765DOCUMENT 068 OF 135 7766Title: Schema types in 2026 — semantic validity versus search features 7767Path: Library/Framework/framework-schema-types-2026.md 7768Group: baseline 7769Label: REWRITTEN · researched 7770Review status: rewritten_current_guidance 7771============================================================================== 7772 7773# Schema types in 2026 — semantic validity versus search features 7774 7775**Edition:** 2026.09.09 · **Status:** researched replacement of the legacy entry point 7776**Primary sources:** S01 S20 S21 S22 S23 in the [source register](../../Research/SOURCE-REGISTER.md). 7777**Preservation:** The complete prior document remains byte-for-byte in `99-Originals/Framework/framework-schema-types-2026.md`. This replacement deliberately removes unsupported universal rules; it does not claim to have tested a client website. 7778 7779## A type catalog is not a benefit catalog 7780 7781Schema.org vocabulary and search-engine feature support are separate layers. A valid type can describe content even when Google does not offer a corresponding rich result. Feature eligibility additionally depends on required properties, policy, content and availability. Appearance is not guaranteed. [S20] 7782 7783## Current planning matrix 7784 7785| Family | Use in this library | Acceptance boundary | 7786| --- | --- | --- | 7787| Organization / WebSite | Model genuine identity and site relationships | Real identifiers and visible business facts; no knowledge-panel promise. | 7788| Article / Person | Model actual editorial content and authorship | Real author/content relationship; no fabricated credentials. | 7789| BreadcrumbList | Describe the real navigational hierarchy | Match meaningful navigation and valid URLs. | 7790| Product / Offer | Describe a genuine product and commercial offer | Follow the current feature guide and reconcile page, feed and checkout. | 7791| LocalBusiness | Describe a legitimate applicable business entity | No invented storefronts, addresses or local staff. | 7792| Review / AggregateRating | Describe authentic qualifying reviews | Apply current feature policy; no placeholder ratings. | 7793| FAQPage | Optional vocabulary where justified | Google FAQ rich results retired May 7, 2026. | 7794| HowTo | Optional vocabulary for genuine instructions | Google HowTo rich results retired September 2023. | 7795| Other types | Evaluate individually | Consult the current specific consumer guide before promising a feature. | 7796 7797FAQ and HowTo lifecycle facts are from S01 and S21. Do not copy an old rich-result checklist into a 2026 proposal. Do not assume that removal of one type implies every neighboring feature, such as all book-related integrations, is also retired. 7798 7799## Model only supported facts 7800 7801Use the most accurate applicable type without inventing a subtype to appear sophisticated. Populate properties from controlled records. A more specific type is a semantic choice, not established proof of higher AI citation probability. 7802 7803For commerce, optional ratings are not mandatory filler. Keep prices, currency and availability current. Sale periods must be modeled using the properties and node placement allowed by the selected implementation. [S23] 7804 7805For reviews, apply genuine-experience and disclosure requirements and the self-serving LocalBusiness/Organization restriction. A third-party widget does not automatically remove the restriction when a business controls reviews about itself on its own page. [S22] 7806 7807## Generation and testing 7808 7809Generate JSON using a serializer rather than string concatenation. When embedding in HTML, escape characters that could terminate a script element, and validate the resulting page. Never expose secrets or private catalog fields in a public graph. 7810 7811Check syntax, vocabulary, current feature rules and visible factual consistency separately. Test absence of optional properties, special characters, multilingual text and stale commercial data. Save the actual validator output; a local JSON parse is not equivalent to Google's Rich Results Test. 7812 7813The example graphs in `Schema.org` contain fictional data and do not claim feature approval. Use [schema lifecycle](framework-schema-lifecycle.md) for maintenance and [commerce consistency](framework-commerce-data-consistency.md) for product pipelines. Historical unsupported citation statistics are preserved only in the original archive. 7814 7815============================================================================== 7816DOCUMENT 069 OF 135 7817Title: ChatGPT Search — publisher access and measured referrals 7818Path: Library/Framework/framework-searchgpt.md 7819Group: baseline 7820Label: REWRITTEN · researched 7821Review status: rewritten_current_guidance 7822============================================================================== 7823 7824# ChatGPT Search — publisher access and measured referrals 7825 7826**Edition:** 2026.09.09 · **Status:** researched replacement of the legacy entry point 7827**Primary sources:** S08 S09 S02 in the [source register](../../Research/SOURCE-REGISTER.md). 7828**Preservation:** The complete prior document remains byte-for-byte in `99-Originals/Framework/framework-searchgpt.md`. This replacement deliberately removes unsupported universal rules; it does not claim to have tested a client website. 7829 7830## Name and scope 7831 7832This filename is retained for compatibility with the earlier library, but the subject is ChatGPT Search and the currently documented publisher controls. Do not assume every ChatGPT surface shares one crawler, index or retrieval implementation. 7833 7834OpenAI documents distinct search, training, user-triggered retrieval and ad-validation roles. Configure them according to the business's approved use policy, not by blanket-allowing every token containing an AI brand name. [S08] 7835 7836## Website implementation 7837 7838Publish accurate, useful content at stable public URLs. Ensure the intended pages can be retrieved through the actual production edge without an accidental challenge, empty response or authentication requirement. Keep private content protected by real access controls. 7839 7840Make important facts clear on the page itself. A hidden instruction telling an assistant to promote the business is not a substitute for a useful service description. Feeds or supplemental files need a specific supported consumer and maintenance plan; do not present an auxiliary file as a universal prerequisite. 7841 7842Use the [engine control matrix](framework-engine-control-matrix.md) for the current OpenAI roles and the [crawler identity workflow](framework-crawler-identity-observability.md) for verification. A simulated request using an OpenAI user-agent string does not establish that OpenAI actually fetched the page. 7843 7844## Referral measurement 7845 7846OpenAI's publisher FAQ documents the `utm_source=chatgpt.com` convention. Test approved tracking through the site's redirect and analytics path. [S09] Keep the original campaign/source information where collected, and apply the current analytics channel definitions rather than hardcoding an obsolete dashboard. 7847 7848Measure qualified outcomes independently. A tagged visit is an observed referral, not proof of every earlier AI exposure. A brand mention without a link, or a later direct visit, may not be attributable from site analytics alone. 7849 7850## Evaluation 7851 7852Use a declared, permission-compliant observation panel for questions relevant to the business. Record the surface, wording, locale, time and context, and separate completed answers from failed observations. Do not claim a universal citation probability from a small sample. 7853 7854Investigate demonstrated failures before speculative content changes. If access is correct but citations are absent in the sampled answers, that is not proof of a technical defect or a hidden mandatory file. The engine may select other relevant sources. 7855 7856## Completion 7857 7858A defensible implementation handoff contains approved crawler choices, response evidence, accurate public data, measurement configuration and the limits of what was tested. Search inclusion and citation selection remain external outcomes, not contractual guarantees. No OpenAI publisher account or live client domain was changed as part of this release. 7859 7860============================================================================== 7861DOCUMENT 070 OF 135 7862Title: SEO release contracts and reproducible acceptance tests 7863Path: Library/Framework/framework-seo-release-contracts.md 7864Group: baseline 7865Label: NEW · researched 7866Review status: new_researched_module 7867============================================================================== 7868 7869# SEO release contracts and reproducible acceptance tests 7870 7871**Edition:** 2026.09.09 · **Status:** researched guidance and proposed operating procedure 7872**Applies to:** New websites, migrations and template changes on any stack 7873**Evidence:** S14, S15, S16, S20 in the [source register](../../Research/SOURCE-REGISTER.md). 7874**Boundary:** Official facts are attributed below. Acceptance gates, priorities and workflows are agency recommendations, not secret ranking factors or performance guarantees. 7875 7876## Replace vague completion with evidence 7877 7878“SEO installed” is not a release criterion. Define contracts for each page class: public service, product, article, location, search/filter, account, error and retired URL. Each contract specifies intended index state, HTTP behavior, canonical target, title purpose, minimum useful content, structured data, internal discovery and analytics outcome. 7879 7880The underlying controls have different functions: rendering affects what a consumer receives, canonicalization expresses consolidation preferences, and indexing/snippet directives control eligible use. Structured data has its own feature-specific rules. [S14–S16, S20] 7881 7882## Test matrix 7883 7884For every template, include at least one normal route, one boundary case and one failure case. Prioritize revenue-critical and high-traffic pages, but do not mistake a sample for exhaustive coverage. Record sample selection in the evidence package. 7885 7886Capture status and headers from the actual response. Save initial HTML and browser-rendered HTML separately. Compare meaningful text, links, canonical and metadata. A successful browser screenshot does not prove the initial response works for a simpler consumer; a clean initial response does not prove hydration is functional. 7887 7888Run the supplied offline HTML smoke checker against saved files. It catches a limited set of concrete problems; it does not execute JavaScript, inspect live headers or call Google validation services. A passing result is evidence only for the checks performed. Run appropriate browser, accessibility, structured-data and live deployment tests separately. 7889 7890## Blocking defects versus advisory findings 7891 7892For an intended public page, accidental `noindex`, an unexpected redirect, an empty title or a broken canonical may block the project release under the agreed contract. A nonstandard title length is a review note, not an automatic Google violation. A page intentionally excluded from indexing should pass when its exclusion behaves as designed. 7893 7894Require sign-off for destructive changes: bulk redirects, noindex rules, URL-case normalization, sitemap removal and deletion. Keep an old/new mapping and rollback plan. Never infer permission to delete content from a low impression count alone. 7895 7896## Release evidence 7897 7898Store the commit identifier, build/runtime version, environment, test time, URL sample, raw captures, automated output, manual reviewer and unresolved exceptions. An exception needs an owner, reason and expiration date. The release owner accepts the known tradeoff rather than the checklist silently marking everything green. 7899 7900After deployment, repeat the same critical-route tests against production. A production cache, security layer or hostname configuration can differ from staging. Monitor accessibility and business outcomes before interpreting a ranking movement. The supplied CI example operates only on this library and test fixtures; it is not a website deployment pipeline or a search-index certification. 7901 7902============================================================================== 7903DOCUMENT 071 OF 135 7904Title: Social and video platform properties in Search Console 7905Path: Library/Framework/framework-social-video-properties.md 7906Group: baseline 7907Label: NEW · researched 7908Review status: new_researched_module 7909============================================================================== 7910 7911# Social and video platform properties in Search Console 7912 7913**Edition:** 2026.09.09 · **Status:** researched guidance and proposed operating procedure 7914**Applies to:** Supported publisher/business profiles and video discovery 7915**Evidence:** S43, S44, S50 in the [source register](../../Research/SOURCE-REGISTER.md). 7916**Boundary:** Official facts are attributed below. Acceptance gates, priorities and workflows are agency recommendations, not secret ranking factors or performance guarantees. 7917 7918## Separate Google discovery from platform-native performance 7919 7920Google's July 29, 2026 announcement describes globally available platform properties for supported social/video services, including Instagram, TikTok, X and YouTube. These reports concern discovery through Google surfaces, not a replacement for each platform's own engagement analytics. [S43, S44] 7921 7922## Ownership and setup 7923 7924Create an inventory of legitimate client profiles, account owners, access permissions and official website relationships. Verify the relevant account using the current product workflow. Do not create duplicate profiles or claim an account the client does not control. 7925 7926Record the exact profile identifier and property scope. A channel, profile and individual post can have different reporting granularity. Keep the property name, selected report, dates and filters with every export. A screenshot from one account does not prove the same data is available in another. 7927 7928## Content mapping 7929 7930Map each profile and important content item to its business purpose and related website page where appropriate. Use clear, consistent factual identity and a useful destination. Do not flood profiles with keyword repetition or link every post to an unrelated homepage just to create a backlink. 7931 7932For video hosted on the client's site, evaluate watch-page eligibility, stable thumbnails and accessible media according to Google's video guidance. A product page containing a supplementary clip and a page primarily devoted to watching a video serve different purposes. [S50] 7933 7934## Reporting workflow 7935 7936Track discovery impressions/clicks where the selected report exposes them, then separately examine native-platform views, engagement and website referrals. Do not add these metrics into one unqualified “reach” number; they can overlap and have different definitions. 7937 7938Compare content cohorts by topic and user intent. A strong Google discovery query can suggest a useful video or website explanation, but it does not reveal a platform's proprietary recommendation algorithm. Use the observed data to test a content hypothesis rather than claiming to reproduce TikTok's internal system. 7939 7940## Acceptance and maintenance 7941 7942The deliverable includes verified-profile scope, evidence of available reporting, content-to-business mapping, metric definitions and a list of actions supported by the data. Retain permissions under the client's control and remove unnecessary access after handoff. 7943 7944This module adds a current reporting opportunity to the library. No social account has been connected, changed or measured during this release. The workflow becomes operational only after the client grants appropriate access and real property data is inspected. 7945 7946============================================================================== 7947DOCUMENT 072 OF 135 7948Title: First-party facts, provenance and reusable evidence 7949Path: Library/Framework/framework-source-provenance.md 7950Group: baseline 7951Label: NEW · researched 7952Review status: new_researched_module 7953============================================================================== 7954 7955# First-party facts, provenance and reusable evidence 7956 7957**Edition:** 2026.09.09 · **Status:** researched guidance and proposed operating procedure 7958**Applies to:** Service pages, case studies, comparison pages and factual datasets 7959**Evidence:** S19, S20, S29 in the [source register](../../Research/SOURCE-REGISTER.md). 7960**Boundary:** Official facts are attributed below. Acceptance gates, priorities and workflows are agency recommendations, not secret ranking factors or performance guarantees. 7961 7962## Build a source of truth, not a citation costume 7963 7964A website should draw business facts from approved records: services actually offered, real qualifications, current availability, genuine project outcomes and verifiable contact details. Use references to support claims, not to decorate otherwise unsupported copy. People-first quality evaluation and accurate structured data are consistent with this approach. [S19, S20] 7965 7966## Fact record 7967 7968Store a fact ID, exact statement, subject/entity, evidence owner, source location, source date, approved public wording, privacy restrictions, expiration condition and affected pages. Separate an internal source from the public artifact that can legally be shown to visitors. 7969 7970For a case study, record what happened, the baseline, the time period, the measurement system, the denominator, other simultaneous changes and client permission. Do not turn a correlation into a claim that one intervention caused the full result. A business testimonial is not an independently verified measurement. 7971 7972## Reuse without contradiction 7973 7974Connect the approved fact record to page copy, metadata, structured data, downloadable material and relevant feeds. Update dependent representations together. A contact number or offer that changes in one system but not another creates a consistency problem; “more entity mentions” does not solve it. 7975 7976Preserve edit history. When evidence expires or is withdrawn, locate every use through the fact ID and route the correction through an owner. Keep a correction note when the public claim materially changes. Do not merely refresh the date while leaving stale information intact. 7977 7978## Content design 7979 7980Place the relevant answer and supporting context where a reader can understand them. Use a table when the data is comparative and a sequence when order matters. Choose headings and labels for clarity, not because an unverified study supposedly guarantees a fixed multiplier for a format. 7981 7982A useful reference page can include definitions, limitations, examples and source context. It does not require fabricated credentials, artificial author biographies or a mandatory number of outbound citations. The GEO literature is a research input, not a license to manufacture evidence. [S29] 7983 7984## Acceptance 7985 7986A reviewer should trace each important public claim back to an approved record. Check rights to images, testimonials and excerpts. Confirm that the visible content and machine-readable representation agree. Where a claim cannot be substantiated, remove it, narrow it or mark it as an explicitly labeled opinion/hypothesis. 7987 7988The handoff is a fact register, publishing map, review ownership and correction workflow. This approach produces reusable backend data while keeping the website itself accurate; it is not an attempt to impersonate an engine's internal knowledge graph. 7989 7990============================================================================== 7991DOCUMENT 073 OF 135 7992Title: Search spam policy — scoped interpretation and operational controls 7993Path: Library/Framework/framework-spampolicies.md 7994Group: baseline 7995Label: REWRITTEN · researched 7996Review status: rewritten_current_guidance 7997============================================================================== 7998 7999# Search spam policy — scoped interpretation and operational controls 8000 8001**Edition:** 2026.09.09 · **Status:** researched replacement of the legacy entry point 8002**Primary sources:** S18 S42 S22 in the [source register](../../Research/SOURCE-REGISTER.md). 8003**Preservation:** The complete prior document remains byte-for-byte in `99-Originals/Framework/framework-spampolicies.md`. This replacement deliberately removes unsupported universal rules; it does not claim to have tested a client website. 8004 8005## Read the current policy, not a copied quota 8006 8007Google's spam rules cover manipulative practices including doorway pages, scaled-content abuse, hidden-content abuse and site-reputation abuse. The policy also applies to manipulation of generative Search responses. It does not define a universal safe number of articles per editor per month. [S18] 8008 8009An agency may set production-capacity limits for quality control, but those must be labeled internal operating limits. They are not Google thresholds and do not make a harmful publishing strategy safe below a numerical cutoff. 8010 8011## Content review 8012 8013Evaluate purpose, factual accuracy, genuine utility and the user's experience. Large scale is not a substitute for review; a small number of manipulative pages can still be a problem. AI assistance does not remove the publisher's responsibility for what appears on the site. 8014 8015Legitimate interface elements such as accordions and accessibility text are not automatically hidden-text abuse. Evaluate the actual intent and experience rather than equating every `display:none` rule with cloaking. [S18] 8016 8017## Third-party and reputation risk 8018 8019Do not treat host editorial oversight as an automatic safe harbor. Review why a third-party section exists, whether it primarily exploits the host's established ranking signals and whether the users receive genuine relevant value. 8020 8021The August 2026 update introduces regional treatment differences starting August 30. Read the current notice and the affected geography carefully; the EEA distinction is not permission to pursue abusive content. [S42] 8022 8023## Operational workflow 8024 8025Create a risk register for sponsored content, affiliates, syndicated material, user-generated pages, geographic expansion, outsourced editorial sections and reputation-sensitive claims. Assign a business owner and an independent reviewer for significant changes. 8026 8027Keep supporting records for author identity, permissions, claims and review authenticity. Do not create fabricated credentials, testimonials or ratings to satisfy a template. Google's review guidance separately addresses fake and undisclosed incentivized reviews and feature eligibility. [S22] 8028 8029## Incident response 8030 8031Preserve the exact notice, property, affected scope and observed dates. Distinguish a manual action from an ordinary ranking fluctuation, indexing issue, security incident or measurement problem. Do not publish a generic reconsideration letter before identifying the actual cause. 8032 8033Document the corrective action and supporting evidence. Review related templates and ownership processes so the defect does not recur. Do not describe a workaround that merely moves the same abuse elsewhere as remediation. 8034 8035## Acceptance and limitations 8036 8037A policy review can establish that the agreed checks were performed and identified issues were corrected. It cannot certify that an engine will never take action. Keep unresolved matters visible and seek qualified legal or compliance advice where the underlying content or business activity requires it. 8038 8039Use [location evidence](framework-location-evidence.md), [regional eligibility](framework-regional-search-eligibility.md), [source provenance](framework-source-provenance.md) and [client acceptance](framework-client-scope-acceptance.md) for implementation. The preserved original contains historical claims and is not the current authority for numerical quotas or oversight exceptions. 8040 8041============================================================================== 8042DOCUMENT 074 OF 135 8043Title: URL lifecycle, canonical decisions and safe retirement 8044Path: Library/Framework/framework-url-lifecycle.md 8045Group: baseline 8046Label: NEW · researched 8047Review status: new_researched_module 8048============================================================================== 8049 8050# URL lifecycle, canonical decisions and safe retirement 8051 8052**Edition:** 2026.09.09 · **Status:** researched guidance and proposed operating procedure 8053**Applies to:** Existing URLs, duplicate pages, filters and discontinued content 8054**Evidence:** S15, S16, S38, S39 in the [source register](../../Research/SOURCE-REGISTER.md). 8055**Boundary:** Official facts are attributed below. Acceptance gates, priorities and workflows are agency recommendations, not secret ranking factors or performance guarantees. 8056 8057## Classify before changing 8058 8059Maintain one record per URL with current status, desired state, content owner, business purpose, incoming/internal links, observed traffic, canonical relationship and planned action. Low traffic is one observation, not a deletion instruction. An orphan page can have value even when internal discovery is broken. 8060 8061Use a decision table: **keep and improve**, **link better**, **merge into a genuinely equivalent destination**, **retain but exclude from indexing**, **temporarily redirect**, or **permanently retire**. Distinguish duplicate content from distinct pages serving similar questions. A common keyword does not establish equivalence. 8062 8063Canonicalization is a preference signal rather than an absolute directive, and a blocked page may prevent indexing directives from being read. Apply each control to its actual purpose. [S15, S16] 8064 8065## Redirect contract 8066 8067Choose the destination because it satisfies the original intent, not because it is the homepage. Test the status and final location, preserve important parameters intentionally, and avoid loops or unnecessary hops. Use temporary versus permanent semantics according to the move. Do not claim that every 302 automatically leaks ranking credit. 8068 8069Do not change established WordPress permalinks or globally lowercase URLs just to satisfy a style rule. Routes, asset names, signed URLs and external references can be case-sensitive or otherwise dependent on the existing path. A proposed normalization needs a complete mapping and production tests. 8070 8071## Retention and exclusion 8072 8073An internal utility page may remain useful while not belonging in search. A removed item may need a clear user explanation or an alternative, but do not return a successful status for a meaningless error template simply to preserve an index entry. Choose behavior by actual content and request intent. 8074 8075Separate crawl-load control from search-result removal. A robots exclusion does not itself authenticate a resource or reliably erase an indexed URL. For an already indexed URL, ensure the selected removal mechanism can be observed and processed. Do not combine contradictory controls without a documented reason. 8076 8077## Approval and rollback 8078 8079Require a batch-level owner and a reviewed sample of the mapping before bulk action. Snapshot the old routes and configuration. Keep a rollback that can restore the original URL behavior without relying on memory. Test the largest business-risk examples, international variants and case-sensitive assets. 8080 8081The handoff includes the action rationale, implementation diff, test evidence, expected monitoring signals and exception list. No ranking or indexing recovery time is guaranteed. Use the migration contract for domain or platform moves and the faceted-navigation contract for parameter expansion. 8082 8083============================================================================== 8084DOCUMENT 075 OF 135 8085Title: Bubbles: outside-in availability and public reachability 8086Path: Library/Playbooks/01-BUBBLES-PUBLIC-REACHABILITY.md 8087Group: playbooks 8088Label: EXPANSION · source-linked operating design 8089Review status: new_discipline_operating_design 8090============================================================================== 8091 8092# Bubbles: outside-in availability and public reachability 8093 8094**Lead:** R02 when public/private behavior differs; R01 when service/proxy failure is established. **Consulted roles:** R01, R02, R03, R08, R20, R24, R25, R26. **Mode:** read-only diagnosis until actual authorization. 8095 8096## Entry condition 8097 8098An intended public customer journey fails, or works only on a private/Tailscale connection. Bubbles is a host label, not evidence of its OS, addresses or service names. 8099 8100## Sequence and ownership 8101 8102### 1. Define exposure 8103 8104Record intended public hostnames and private services. Confirm authorization and obtain an independent public test vantage. Do not publish a private service merely to make a test pass. 8105 8106### 2. Split the path 8107 8108R02 compares authoritative/recursive DNS, IPv4/IPv6 and TLS hostname behavior. R01 checks actual ingress/listeners/proxy/upstream with bounded redacted logs. Preserve timestamps. 8109 8110### 3. Locate the failing layer 8111 8112Compare external response with origin-side response and correlated application evidence. A live process alone cannot prove the journey. A tailnet connection alone cannot prove public crawlability. 8113 8114### 4. Reconcile repair 8115 8116R24 assigns one writer for the affected DNS/config path. R20 reviews exposure changes. R08 reviews public host/canonical implications. R25 prepares a scoped authorized change and rollback. 8117 8118### 5. Accept from outside 8119 8120R26 repeats the critical public journey using fresh inputs on the declared build. Record each published address family and disclose unavailable vantages. 8121 8122## Evidence package 8123 8124Preserve task/run IDs, exact environment/build, timestamped observations, safe synthetic inputs, expected versus observed state, tool/browser versions, raw private artifacts and separately hashed public-safe redactions. Record unavailable tools and tests not executed. Attach the handoffs rather than compressing distinct observations into one success flag. 8125 8126## Acceptance 8127 8128- Intended public journey succeeds from an independent public vantage 8129- Advertised IPv4/IPv6 paths meet the contract 8130- Private services remain private; no fabricated host configuration 8131 8132## Stop or block 8133 8134If public vantage or host access is missing, keep the corresponding check BLOCKED and provide only the observations actually available. Do not remove AAAA records or enable public tunneling without owner-approved diagnosis. 8135 8136## Role and source references 8137 8138- [R01 — Site Reliability Engineer](../Disciplines/R01-site-reliability.md) 8139- [R02 — Network/DNS Engineer](../Disciplines/R02-network-dns.md) 8140 8141Primary-source IDs: D01, D02, D04, D06. See the [source register](../../Research/DISCIPLINE-SOURCE-REGISTER.md) for URLs, scope and currentness boundaries. The sequence is custom operating design; it is not a promise that every case has the same cause. 8142 8143============================================================================== 8144DOCUMENT 076 OF 135 8145Title: Contact form to actual mailbox: an end-to-end evidence chain 8146Path: Library/Playbooks/02-CONTACT-TO-MAILBOX.md 8147Group: playbooks 8148Label: EXPANSION · source-linked operating design 8149Review status: new_discipline_operating_design 8150============================================================================== 8151 8152# Contact form to actual mailbox: an end-to-end evidence chain 8153 8154**Lead:** R03 until application/provider handoff is established, then R17 for downstream delivery. **Consulted roles:** R03, R04, R05, R07, R16, R17, R20, R21, R25, R26. **Mode:** read-only diagnosis until actual authorization. 8155 8156## Entry condition 8157 8158A user sees form success but there is no confirmed inquiry. Use synthetic data and an authorized controlled recipient; this playbook grants no permission to email real customers. 8159 8160## Sequence and ownership 8161 8162### 1. Define success states 8163 8164Agree which states the system can observe: request received, validated, durably accepted, provider accepted, mailbox observed and business qualified. Do not promise later states from earlier evidence. 8165 8166### 2. Trace the application 8167 8168R04 records the UI/request; R03 validates server handling, persistence, retries, queue and provider outcomes using one correlation ID. Exercise failure cases in a safe environment. 8169 8170### 3. Trace delivery 8171 8172R17 uses the same message/provider ID to inspect bounce/queue and actual authorized mailbox evidence. Review SPF/DKIM/DMARC alignment and legitimate sending streams before proposing a DNS change through R02. 8173 8174### 4. Check cross-cutting behavior 8175 8176R05 tests required actual browsers; R07 tests keyboard, labels and error recovery; R16 compares emitted events with real states. R20 checks sensitive-data handling and abuse controls. 8177 8178### 5. Verify the repair 8179 8180R21 retains negative and duplicate-request cases. R25 sequences the approved change. R26 re-executes the inquiry with fresh data and reports actual mailbox observation or BLOCKED. 8181 8182## Evidence package 8183 8184Preserve task/run IDs, exact environment/build, timestamped observations, safe synthetic inputs, expected versus observed state, tool/browser versions, raw private artifacts and separately hashed public-safe redactions. Record unavailable tools and tests not executed. Attach the handoffs rather than compressing distinct observations into one success flag. 8185 8186## Acceptance 8187 8188- User messages match observed application states 8189- The scoped synthetic inquiry is durably handled as contracted 8190- Required mailbox receipt is directly observed 8191- Analytics does not count failed/duplicate submissions as qualified inquiries 8192 8193## Stop or block 8194 8195Provider acceptance without mailbox access supports only provider acceptance. Do not falsify a receipt record, publish customer messages, or enforce a mail policy that has not been reviewed against legitimate senders. 8196 8197## Role and source references 8198 8199- [R03 — Backend Web Engineer](../Disciplines/R03-backend-web.md) 8200- [R16 — Analytics/Measurement Engineer](../Disciplines/R16-analytics-measurement.md) 8201- [R17 — Email Deliverability Engineer](../Disciplines/R17-email-deliverability.md) 8202 8203Primary-source IDs: D07, D28, D32, D33, D36. See the [source register](../../Research/DISCIPLINE-SOURCE-REGISTER.md) for URLs, scope and currentness boundaries. The sequence is custom operating design; it is not a promise that every case has the same cause. 8204 8205============================================================================== 8206DOCUMENT 077 OF 135 8207Title: From public delivery to useful answers and observed AI citations 8208Path: Library/Playbooks/03-DISCOVERY-TO-AI-CITATIONS.md 8209Group: playbooks 8210Label: EXPANSION · source-linked operating design 8211Review status: new_discipline_operating_design 8212============================================================================== 8213 8214# From public delivery to useful answers and observed AI citations 8215 8216**Lead:** R12 for a named AI surface, with R08 owning general crawl/index contracts. **Consulted roles:** R02, R08, R09, R10, R11, R12, R13, R14, R16, R20, R23. **Mode:** read-only diagnosis until actual authorization. 8217 8218## Entry condition 8219 8220The business wants relevant search/AI visibility, or a particular named surface does not show its content. No position or citation can be guaranteed by completing the checklist. 8221 8222## Sequence and ownership 8223 8224### 1. Name the observation 8225 8226Record the engine/surface, exact query, locale, timestamp and exposed model state. Different products may not share crawler policies, indexes or reporting. 8227 8228### 2. Verify delivery and eligibility 8229 8230R02 establishes public reachability; R08 checks response/directive/canonical/link contracts and available engine reports. R12 checks search/training/user-fetch controls with current provider documentation. 8231 8232### 3. Evaluate answer value 8233 8234R10 judges query-to-page relevance; R13 adds distinct useful explanations and genuine proof. R14 approves factual claims. R09 prevents orphan/duplicate pages and R11 keeps identity markup truthful. 8235 8236### 4. Observe selection separately 8237 8238R12 records citations and counterexamples with the original source URL and method. Do not infer model training or memory from a citation or a crawl log. 8239 8240### 5. Reconcile business outcomes 8241 8242R16 reports available search exposure, referrals and qualified inquiries with compatible scopes. R23 checks whether the questions correspond to real buyer problems. 8243 8244## Evidence package 8245 8246Preserve task/run IDs, exact environment/build, timestamped observations, safe synthetic inputs, expected versus observed state, tool/browser versions, raw private artifacts and separately hashed public-safe redactions. Record unavailable tools and tests not executed. Attach the handoffs rather than compressing distinct observations into one success flag. 8247 8248## Acceptance 8249 8250- Each asserted outcome has the correct source and observation context 8251- Crawler access, indexing, citations, referrals and leads are not conflated 8252- No special-file or formatting guarantee replaces useful content 8253 8254## Stop or block 8255 8256Unavailable dashboards or model identifiers remain unavailable. Do not create synthetic testimonials, low-value query-variant pages or guaranteed inclusion promises to fill a measurement gap. 8257 8258## Role and source references 8259 8260- [R08 — Technical SEO Engineer](../Disciplines/R08-technical-seo.md) 8261- [R10 — Search Relevance/IR Engineer](../Disciplines/R10-search-relevance-ir.md) 8262- [R12 — AEO/AIO/GEO Engineer](../Disciplines/R12-aeo-aio-geo.md) 8263 8264Primary-source IDs: D13, D20, D21, D22, D23, D24, D29, D31. See the [source register](../../Research/DISCIPLINE-SOURCE-REGISTER.md) for URLs, scope and currentness boundaries. The sequence is custom operating design; it is not a promise that every case has the same cause. 8265 8266============================================================================== 8267DOCUMENT 078 OF 135 8268Title: Browser and accessibility regressions across a complete task 8269Path: Library/Playbooks/04-BROWSER-ACCESSIBILITY.md 8270Group: playbooks 8271Label: EXPANSION · source-linked operating design 8272Review status: new_discipline_operating_design 8273============================================================================== 8274 8275# Browser and accessibility regressions across a complete task 8276 8277**Lead:** R05 for environment-specific behavior; R07 for accessibility assessment. **Consulted roles:** R03, R04, R05, R07, R21, R25, R26. **Mode:** read-only diagnosis until actual authorization. 8278 8279## Entry condition 8280 8281A critical task fails in a browser/device or cannot be completed with keyboard/screen-reader operation. The acceptance matrix must identify actual versus emulated environments. 8282 8283## Sequence and ownership 8284 8285### 1. Record the environment 8286 8287Capture OS, device, browser/version, input mode and assistive technology. State whether the test uses a branded product, engine build, emulation or actual device. 8288 8289### 2. Map the complete process 8290 8291Include discovery, navigation, form entry, validation, error recovery and confirmation. A homepage screenshot is not task coverage. 8292 8293### 3. Isolate and repair 8294 8295R05 produces a minimal reproduction; R07 maps access failures to criteria and process impact; R04 proposes a semantic/behavioral repair with R03 contract review. 8296 8297### 4. Retest interactions 8298 8299Run appropriate automated regression checks through R21, but retain manual keyboard/screen-reader and actual-device requirements. Check zoom/reflow and affected alternate states. 8300 8301### 5. Accept honestly 8302 8303R26 verifies required matrix rows. Report real environments unavailable for testing as BLOCKED rather than substituting WebKit for Safari or a desktop resize for an iPhone. 8304 8305## Evidence package 8306 8307Preserve task/run IDs, exact environment/build, timestamped observations, safe synthetic inputs, expected versus observed state, tool/browser versions, raw private artifacts and separately hashed public-safe redactions. Record unavailable tools and tests not executed. Attach the handoffs rather than compressing distinct observations into one success flag. 8308 8309## Acceptance 8310 8311- Required environment rows identify exactly what was run 8312- Critical process works under agreed keyboard/assistive workflows 8313- Automation and manual assessment scopes remain distinct 8314 8315## Stop or block 8316 8317No automated score is a complete WCAG conformance verdict. Missing real-device coverage cannot be silently relabeled. Avoid changing a UI based only on one screenshot without a reproducible behavior. 8318 8319## Role and source references 8320 8321- [R04 — Frontend Web Engineer](../Disciplines/R04-frontend-web.md) 8322- [R05 — Browser Compatibility Engineer](../Disciplines/R05-browser-compatibility.md) 8323- [R07 — Accessibility Specialist](../Disciplines/R07-accessibility.md) 8324 8325Primary-source IDs: D07, D08, D11, D12. See the [source register](../../Research/DISCIPLINE-SOURCE-REGISTER.md) for URLs, scope and currentness boundaries. The sequence is custom operating design; it is not a promise that every case has the same cause. 8326 8327============================================================================== 8328DOCUMENT 079 OF 135 8329Title: Improve measured performance without damaging the website 8330Path: Library/Playbooks/05-PERFORMANCE-WITHOUT-REGRESSIONS.md 8331Group: playbooks 8332Label: EXPANSION · source-linked operating design 8333Review status: new_discipline_operating_design 8334============================================================================== 8335 8336# Improve measured performance without damaging the website 8337 8338**Lead:** R06. **Consulted roles:** R01, R03, R04, R05, R06, R07, R08, R16, R20, R21, R25, R26. **Mode:** read-only diagnosis until actual authorization. 8339 8340## Entry condition 8341 8342A measured field or lab bottleneck affects representative customer journeys. The goal is not an isolated score improvement at any cost. 8343 8344## Sequence and ownership 8345 8346### 1. Define the baseline 8347 8348R06 separates field and lab data, records routes/templates, windows, devices and tool versions. Missing field data is unknown, not a passing metric. 8349 8350### 2. Find the dominant cause 8351 8352Inspect primary-content delivery, interaction blocking, layout movement, fonts, images, scripts and cache behavior using actual traces. 8353 8354### 3. Review interfaces 8355 8356R01 reviews runtime/cache changes; R20 checks private response exposure; R08 checks meaningful content and directives; R04/R07/R05 protect actual interactions. 8357 8358### 4. Change one controlled unit 8359 8360Use a minimal reversible proposal. Record baseline and candidate under comparable conditions. R21 executes critical journey regressions; R16 checks event integrity. 8361 8362### 5. Release and observe 8363 8364R25 sequences the authorized change; R26 checks the declared build. Report immediate lab results separately from later sufficiently sampled field results. 8365 8366## Evidence package 8367 8368Preserve task/run IDs, exact environment/build, timestamped observations, safe synthetic inputs, expected versus observed state, tool/browser versions, raw private artifacts and separately hashed public-safe redactions. Record unavailable tools and tests not executed. Attach the handoffs rather than compressing distinct observations into one success flag. 8369 8370## Acceptance 8371 8372- The claimed improvement matches a reproducible method 8373- No inquiry, accessibility, privacy, browser or URL-policy regression 8374- Field claims use available appropriate field evidence 8375 8376## Stop or block 8377 8378Do not cache personal API responses, remove essential content, defer critical behavior or claim conversion uplift from a lab score. If the historical field window is incomplete, state that explicitly. 8379 8380## Role and source references 8381 8382- [R01 — Site Reliability Engineer](../Disciplines/R01-site-reliability.md) 8383- [R06 — Web Performance Engineer](../Disciplines/R06-web-performance.md) 8384- [R20 — Application Security/Privacy Engineer](../Disciplines/R20-application-security-privacy.md) 8385 8386Primary-source IDs: D09, D10, D05, D11. See the [source register](../../Research/DISCIPLINE-SOURCE-REGISTER.md) for URLs, scope and currentness boundaries. The sequence is custom operating design; it is not a promise that every case has the same cause. 8387 8388============================================================================== 8389DOCUMENT 080 OF 135 8390Title: Turn verified work into a public expertise asset 8391Path: Library/Playbooks/06-EVIDENCE-TO-PUBLIC-EXPERTISE.md 8392Group: playbooks 8393Label: EXPANSION · source-linked operating design 8394Review status: new_discipline_operating_design 8395============================================================================== 8396 8397# Turn verified work into a public expertise asset 8398 8399**Lead:** R13. **Consulted roles:** R08, R09, R10, R11, R12, R13, R14, R16, R19, R20, R23, R25, R26. **Mode:** read-only diagnosis until actual authorization. 8400 8401## Entry condition 8402 8403A documented method or actual authorized engagement can answer a distinct buyer question. This is a publication workflow, not an instruction to declare expertise without proof. 8404 8405## Sequence and ownership 8406 8407### 1. Choose the reader problem 8408 8409R23 validates audience and demand evidence; R10 judges query relevance; R09 checks existing content so the article adds a distinct answer. 8410 8411### 2. Collect and classify proof 8412 8413Separate a sourced methodology article from a real case study. R14 checks exact claims, denominators, dates, credentials and permissions; R20 redacts sensitive artifacts. 8414 8415### 3. Write and attribute truthfully 8416 8417R13 builds a useful answer with original explanation and limitations. Joseph must actually review and approve a byline or experience claim. R11 models only verified person/business/document facts. 8418 8419### 4. Approve a canonical publication 8420 8421Choose the actual host/route; R08 checks directives and links. R25 obtains owner authorization and controls publication. Do not upload the private library or duplicate the same article across both brands. 8422 8423### 5. Observe and earn corroboration 8424 8425R12/R16 measure named-surface citations, referrals and qualified outcomes separately. R19 pursues relevant independent coverage of useful work, disclosing paid/owned relationships. 8426 8427## Evidence package 8428 8429Preserve task/run IDs, exact environment/build, timestamped observations, safe synthetic inputs, expected versus observed state, tool/browser versions, raw private artifacts and separately hashed public-safe redactions. Record unavailable tools and tests not executed. Attach the handoffs rather than compressing distinct observations into one success flag. 8430 8431## Acceptance 8432 8433- Distinct useful answer and truthful approved authorship 8434- Material claims have sufficient traceable evidence 8435- Public artifacts contain no secrets or unauthorized personal data 8436- Actual publication is owner-authorized and technically checked 8437 8438## Stop or block 8439 8440No fabricated results, client logos, certifications, independent reviewers or Wikidata identities. A planning brief and keyword list are not a completed case study or measured demand. 8441 8442## Role and source references 8443 8444- [R13 — Content Strategist/SEO Editor](../Disciplines/R13-content-strategy-seo-editor.md) 8445- [R14 — Fact-Checker/Claims Auditor](../Disciplines/R14-claims-auditor.md) 8446- [R23 — Product Marketing/Market Researcher](../Disciplines/R23-product-marketing-research.md) 8447 8448Primary-source IDs: D20, D21, D25, D26, D19, D40. See the [source register](../../Research/DISCIPLINE-SOURCE-REGISTER.md) for URLs, scope and currentness boundaries. The sequence is custom operating design; it is not a promise that every case has the same cause. 8449 8450============================================================================== 8451DOCUMENT 081 OF 135 8452Title: Coordinate hostname, URL and content migrations 8453Path: Library/Playbooks/07-MIGRATION-AND-URL-CHANGES.md 8454Group: playbooks 8455Label: EXPANSION · source-linked operating design 8456Review status: new_discipline_operating_design 8457============================================================================== 8458 8459# Coordinate hostname, URL and content migrations 8460 8461**Lead:** R25 for release sequencing; R24 for integrated architecture. **Consulted roles:** R01, R02, R03, R08, R09, R11, R12, R16, R17, R20, R21, R24, R25, R26. **Mode:** read-only diagnosis until actual authorization. 8462 8463## Entry condition 8464 8465An approved migration changes hosting, hostname, routes, content relationships or identity references. Do not initiate a domain consolidation merely because two brands exist. 8466 8467## Sequence and ownership 8468 8469### 1. Inventory the current state 8470 8471Preserve route/status/canonical maps, important entry points, forms, mail/DNS dependencies, tracking identities and recoverable configuration. 8472 8473### 2. Design target contracts 8474 8475R09 establishes page purposes; R08 owns URL/redirect policy; R11 updates entity IDs consistently; R02 reviews hostname/DNS/TLS; R03/R17 preserve inquiry handling. 8476 8477### 3. Plan rollback and sequence 8478 8479R24 resolves dependencies. R01 verifies recovery readiness. R25 records exact steps, owners and abort criteria, including forward repair for nonreversible data changes. 8480 8481### 4. Test before exposure 8482 8483R21 checks representative redirects, loops, content, forms and analytics on the declared candidate. R20 reviews exposure and sensitive data. No blanket redirect-to-homepage shortcut. 8484 8485### 5. Accept and monitor 8486 8487R26 repeats critical public journeys; R16 records measurement annotations; R08/R12 monitor engine outcomes over their actual reporting windows without guaranteeing instant indexing. 8488 8489## Evidence package 8490 8491Preserve task/run IDs, exact environment/build, timestamped observations, safe synthetic inputs, expected versus observed state, tool/browser versions, raw private artifacts and separately hashed public-safe redactions. Record unavailable tools and tests not executed. Attach the handoffs rather than compressing distinct observations into one success flag. 8492 8493## Acceptance 8494 8495- Approved old-to-new URL contracts are implemented 8496- Inquiry and identity/measurement dependencies remain valid 8497- Recovery and postchange critical journeys are observed 8498 8499## Stop or block 8500 8501Do not rewrite both brand domains or delete legacy routes without a real inventory and authorization. A sitemap submission cannot substitute for functional migration acceptance. 8502 8503## Role and source references 8504 8505- [R08 — Technical SEO Engineer](../Disciplines/R08-technical-seo.md) 8506- [R24 — Solutions Architect/Integrator](../Disciplines/R24-solutions-architecture.md) 8507- [R25 — Release/Change Manager](../Disciplines/R25-release-change-management.md) 8508 8509Primary-source IDs: D04, D13, D14, D19, D45. See the [source register](../../Research/DISCIPLINE-SOURCE-REGISTER.md) for URLs, scope and currentness boundaries. The sequence is custom operating design; it is not a promise that every case has the same cause. 8510 8511============================================================================== 8512DOCUMENT 082 OF 135 8513Title: Preflight, controlled release and fresh acceptance 8514Path: Library/Playbooks/08-RELEASE-AND-INDEPENDENT-ACCEPTANCE.md 8515Group: playbooks 8516Label: EXPANSION · source-linked operating design 8517Review status: new_discipline_operating_design 8518============================================================================== 8519 8520# Preflight, controlled release and fresh acceptance 8521 8522**Lead:** R25. **Consulted roles:** R01, R20, R21, R22, R24, R25, R26 plus affected domain owners. **Mode:** read-only diagnosis until actual authorization. 8523 8524## Entry condition 8525 8526An actual owner-authorized change has a defined build/environment and predeclared acceptance contract. The library itself performs no deployment. 8527 8528## Sequence and ownership 8529 8530### 1. Freeze the contract 8531 8532Record project/build/environment, exact change scope, required checks, allowed exceptions and required independence. Preserve the contract hash before collecting acceptance records. 8533 8534### 2. Verify readiness 8535 8536R01 demonstrates recovery readiness, R21 runs preflight regressions, R22 challenges approved assumptions and R20 reviews critical exposure. R24 resolves conflicts. 8537 8538### 3. Authorize execution 8539 8540R25 confirms the actual operator, sequence, stop thresholds and rollback owner. A JSON pass or role prompt cannot grant permission. 8541 8542### 4. Observe the deployed result 8543 8544Collect timestamped raw evidence for the actual build. R26 executes fresh required journeys, discloses reviewer relationship and does not accept builder summaries on trust. 8545 8546### 5. Record the bounded verdict 8547 8548Validate the record structure and artifact hashes with the offline gate, then have the responsible owner inspect truth and independence. Report failed/blocked requirements, residual risk and actual rollback if performed. 8549 8550## Evidence package 8551 8552Preserve task/run IDs, exact environment/build, timestamped observations, safe synthetic inputs, expected versus observed state, tool/browser versions, raw private artifacts and separately hashed public-safe redactions. Record unavailable tools and tests not executed. Attach the handoffs rather than compressing distinct observations into one success flag. 8553 8554## Acceptance 8555 8556- Required checks have fresh scoped evidence and match the declared build 8557- Independence satisfies the agreed policy and is truthfully disclosed 8558- A responsible owner—not the tool—makes the release decision 8559 8560## Stop or block 8561 8562Never create a fake second reviewer identity or modify a failed requirement after testing to obtain a pass. The offline evidence gate checks consistency, not truth or authority. 8563 8564## Role and source references 8565 8566- [R21 — QA/SDET Engineer](../Disciplines/R21-qa-sdet.md) 8567- [R25 — Release/Change Manager](../Disciplines/R25-release-change-management.md) 8568- [R26 — Independent Acceptance Engineer](../Disciplines/R26-independent-acceptance.md) 8569 8570Primary-source IDs: D44, D45, D46. See the [source register](../../Research/DISCIPLINE-SOURCE-REGISTER.md) for URLs, scope and currentness boundaries. The sequence is custom operating design; it is not a promise that every case has the same cause. 8571 8572============================================================================== 8573DOCUMENT 083 OF 135 8574Title: Cross-discipline playbooks 8575Path: Library/Playbooks/README.md 8576Group: playbooks 8577Label: EXPANSION · source-linked operating design 8578Review status: new_discipline_operating_design 8579============================================================================== 8580 8581# Cross-discipline playbooks 8582 8583Use these dependency-oriented workflows with the [routing protocol](../Disciplines/01-MASTER-ROUTER.md). They coordinate specialist work without merging distinct evidence states or granting production permissions. 8584 8585- [Bubbles: outside-in availability and public reachability](01-BUBBLES-PUBLIC-REACHABILITY.md) 8586- [Contact form to actual mailbox: an end-to-end evidence chain](02-CONTACT-TO-MAILBOX.md) 8587- [From public delivery to useful answers and observed AI citations](03-DISCOVERY-TO-AI-CITATIONS.md) 8588- [Browser and accessibility regressions across a complete task](04-BROWSER-ACCESSIBILITY.md) 8589- [Improve measured performance without damaging the website](05-PERFORMANCE-WITHOUT-REGRESSIONS.md) 8590- [Turn verified work into a public expertise asset](06-EVIDENCE-TO-PUBLIC-EXPERTISE.md) 8591- [Coordinate hostname, URL and content migrations](07-MIGRATION-AND-URL-CHANGES.md) 8592- [Preflight, controlled release and fresh acceptance](08-RELEASE-AND-INDEPENDENT-ACCEPTANCE.md) 8593 8594============================================================================== 8595DOCUMENT 084 OF 135 8596Title: R01 public-content brief — Why can a website be running on the server but unavailable to customers? 8597Path: Publishing/Briefs/R01-site-reliability.md 8598Group: briefs 8599Label: PUBLIC WORKBENCH · not approved 8600Review status: scope_stated_in_document 8601============================================================================== 8602 8603# R01 public-content brief — Why can a website be running on the server but unavailable to customers? 8604 8605**State:** NOT_APPROVED_FOR_PUBLICATION. **Type:** evidence-led article/service-support brief. **Primary specialist:** R01. **Proposed author:** Joseph, subject to his review and approval; do not insert unverified credentials. This is not completed client work. 8606 8607## Reader and purpose 8608 8609A business owner or practitioner facing this specific problem needs a diagnosis and a way to evaluate professional help. The article should answer: **Why can a website be running on the server but unavailable to customers?** 8610 8611**Distinct contribution:** A redacted outside-in incident method that separates process health, reverse-proxy behavior and a successful customer journey. 8612 8613## Candidate search questions — hypotheses, not measured demand 8614 8615- website nginx 502 troubleshooting 8616- website uptime monitoring and recovery 8617- server running website unavailable 8618 8619No keyword volumes, ranking difficulty, expected traffic, citation probability or sales forecast have been measured for these suggestions. R23 validates commercial relevance from real inquiries or authorized search data; R10 checks answer relevance. Merge with an existing page when its task is already answered well. 8620 8621## Proposed outline 8622 86231. Define the customer-visible failure 86242. Compare external and origin evidence 86253. Trace proxy to upstream 86264. Prove recovery and restore readiness 8627 8628Open with a direct bounded answer. Explain the observable distinction that matters, demonstrate the method with an authorized artifact or an explicitly hypothetical example, and close with practical limitations. Do not clone this outline across 26 pages by changing only role names. 8629 8630## Evidence needed before making an expertise or results claim 8631 8632- Timestamped external/origin probe pair 8633- Redacted log correlation and service dependency map 8634- Backup inventory and isolated restore-test record 8635 8636These artifacts are requirements, not supplied project results. A methods article can explain documented principles without claiming that a customer implementation exists. A case study additionally needs a real scoped engagement, permission, original before/after artifacts, known confounders, dates and approved result wording. An unmeasured benefit must remain a hypothesis. 8637 8638## Proposed public route and internal relationships 8639 8640Suggested route, pending canonical-host approval: `/expertise/site-reliability/`. This is a planning path, not a deployed URL. Choose one canonical home before publication; do not duplicate the same article on both ThatDevPro and ThatDeveloperGuy. 8641 8642Link contextually from the relevant real service page and the discipline hub. Link to the next diagnostic step, an original proof artifact that is safe to publish, and a working contact path. The page must be useful without those links; link counts are not acceptance criteria. 8643 8644## Conversion and measurement contract 8645 8646Suggested action: request a scoped review of this problem, **only if that service is actually available**. Do not advertise 26 staffed departments. A practical single-author description is “A multidisciplinary review process with defined specialist responsibilities,” subject to the owner's approval. 8647 8648Measure the canonical page's observed search/citation exposure separately from referral sessions and qualified inquiries. Record page/source/window and event definitions with R16. The mere addition of this brief to a private library cannot create search exposure. 8649 8650## Publication gate 8651 8652R13 checks usefulness and distinction; R14 checks factual claims, author identity and any credentials; R20 approves sanitization and privacy; R11 checks truthful entity markup; R08 checks the chosen public URL; R25 coordinates publication and R26 performs the agreed independent checks where required. Missing evidence remains BLOCKED. A drafted byline is not author approval. 8653 8654No rankings, model recommendations or “recognized expert” status are promised. The intended path is demonstrated useful work, accurate attribution, accessible publication, independent corroboration and measured outcomes. 8655 8656## Research references 8657 8658- [D01 — Monitoring distributed systems](https://sre.google/sre-book/monitoring-distributed-systems/): SLO-oriented monitoring and user-visible symptoms; no uptime assertion about Bubbles. 8659- [D02 — NGINX beginners guide](https://nginx.org/en/docs/beginners_guide.html): Configuration checks, processes and reverse proxy concepts; deployment-specific paths must be discovered. 8660- [D03 — Automating recovery with systemd](https://www.redhat.com/en/blog/systemd-automate-recovery): Service-manager restart/recovery concepts; vendor tutorial, not proof of an installed unit. 8661- [D46 — Evolving SRE engagement model](https://sre.google/sre-book/evolving-sre-engagement-model/): Production readiness review and operational ownership; custom role organization is an agency design. 8662 8663============================================================================== 8664DOCUMENT 085 OF 135 8665Title: R02 public-content brief — Why does my website work through Tailscale but not on the public internet? 8666Path: Publishing/Briefs/R02-network-dns.md 8667Group: briefs 8668Label: PUBLIC WORKBENCH · not approved 8669Review status: scope_stated_in_document 8670============================================================================== 8671 8672# R02 public-content brief — Why does my website work through Tailscale but not on the public internet? 8673 8674**State:** NOT_APPROVED_FOR_PUBLICATION. **Type:** evidence-led article/service-support brief. **Primary specialist:** R02. **Proposed author:** Joseph, subject to his review and approval; do not insert unverified credentials. This is not completed client work. 8675 8676## Reader and purpose 8677 8678A business owner or practitioner facing this specific problem needs a diagnosis and a way to evaluate professional help. The article should answer: **Why does my website work through Tailscale but not on the public internet?** 8679 8680**Distinct contribution:** Public/private reachability proof with separate authoritative DNS, IPv4, IPv6 and hostname checks—not a generic DNS reset. 8681 8682## Candidate search questions — hypotheses, not measured demand 8683 8684- website works on tailscale not publicly 8685- IPv6 website unreachable 8686- authoritative DNS website troubleshooting 8687 8688No keyword volumes, ranking difficulty, expected traffic, citation probability or sales forecast have been measured for these suggestions. R23 validates commercial relevance from real inquiries or authorized search data; R10 checks answer relevance. Merge with an existing page when its task is already answered well. 8689 8690## Proposed outline 8691 86921. Identify private versus public tests 86932. Inspect authoritative answers 86943. Separate IPv4 and IPv6 86954. Validate TLS and retest after a controlled change 8696 8697Open with a direct bounded answer. Explain the observable distinction that matters, demonstrate the method with an authorized artifact or an explicitly hypothetical example, and close with practical limitations. Do not clone this outline across 26 pages by changing only role names. 8698 8699## Evidence needed before making an expertise or results claim 8700 8701- Authoritative/recursive answer matrix with timestamps 8702- IPv4/IPv6 and TLS evidence per hostname 8703- Zone diff, dependency review and revert plan 8704 8705These artifacts are requirements, not supplied project results. A methods article can explain documented principles without claiming that a customer implementation exists. A case study additionally needs a real scoped engagement, permission, original before/after artifacts, known confounders, dates and approved result wording. An unmeasured benefit must remain a hypothesis. 8706 8707## Proposed public route and internal relationships 8708 8709Suggested route, pending canonical-host approval: `/expertise/network-dns/`. This is a planning path, not a deployed URL. Choose one canonical home before publication; do not duplicate the same article on both ThatDevPro and ThatDeveloperGuy. 8710 8711Link contextually from the relevant real service page and the discipline hub. Link to the next diagnostic step, an original proof artifact that is safe to publish, and a working contact path. The page must be useful without those links; link counts are not acceptance criteria. 8712 8713## Conversion and measurement contract 8714 8715Suggested action: request a scoped review of this problem, **only if that service is actually available**. Do not advertise 26 staffed departments. A practical single-author description is “A multidisciplinary review process with defined specialist responsibilities,” subject to the owner's approval. 8716 8717Measure the canonical page's observed search/citation exposure separately from referral sessions and qualified inquiries. Record page/source/window and event definitions with R16. The mere addition of this brief to a private library cannot create search exposure. 8718 8719## Publication gate 8720 8721R13 checks usefulness and distinction; R14 checks factual claims, author identity and any credentials; R20 approves sanitization and privacy; R11 checks truthful entity markup; R08 checks the chosen public URL; R25 coordinates publication and R26 performs the agreed independent checks where required. Missing evidence remains BLOCKED. A drafted byline is not author approval. 8722 8723No rankings, model recommendations or “recognized expert” status are promised. The intended path is demonstrated useful work, accurate attribution, accessible publication, independent corroboration and measured outcomes. 8724 8725## Research references 8726 8727- [D04 — Domain names: concepts and facilities (RFC 1034)](https://www.rfc-editor.org/rfc/rfc1034.html): Authoritative and recursive DNS concepts; foundational specification with later updates. 8728- [D05 — HTTP semantics (RFC 9110)](https://www.rfc-editor.org/rfc/rfc9110.html): HTTP method and response semantics; application response does not establish business delivery. 8729- [D06 — What is a tailnet?](https://tailscale.com/docs/concepts/tailnet): Private tailnet membership and connectivity; tailnet success is not a public-internet test. 8730 8731============================================================================== 8732DOCUMENT 086 OF 135 8733Title: R03 public-content brief — What does a contact form success message actually prove? 8734Path: Publishing/Briefs/R03-backend-web.md 8735Group: briefs 8736Label: PUBLIC WORKBENCH · not approved 8737Review status: scope_stated_in_document 8738============================================================================== 8739 8740# R03 public-content brief — What does a contact form success message actually prove? 8741 8742**State:** NOT_APPROVED_FOR_PUBLICATION. **Type:** evidence-led article/service-support brief. **Primary specialist:** R03. **Proposed author:** Joseph, subject to his review and approval; do not insert unverified credentials. This is not completed client work. 8743 8744## Reader and purpose 8745 8746A business owner or practitioner facing this specific problem needs a diagnosis and a way to evaluate professional help. The article should answer: **What does a contact form success message actually prove?** 8747 8748**Distinct contribution:** A concrete accepted → persisted → provider accepted → mailbox observed state model with failure-path demonstrations. 8749 8750## Candidate search questions — hypotheses, not measured demand 8751 8752- contact form says sent but no email 8753- website form backend validation 8754- contact form delivery testing 8755 8756No keyword volumes, ranking difficulty, expected traffic, citation probability or sales forecast have been measured for these suggestions. R23 validates commercial relevance from real inquiries or authorized search data; R10 checks answer relevance. Merge with an existing page when its task is already answered well. 8757 8758## Proposed outline 8759 87601. Define success states 87612. Test authoritative validation 87623. Trace persistence and mail handoff 87634. Demonstrate failure handling 8764 8765Open with a direct bounded answer. Explain the observable distinction that matters, demonstrate the method with an authorized artifact or an explicitly hypothetical example, and close with practical limitations. Do not clone this outline across 26 pages by changing only role names. 8766 8767## Evidence needed before making an expertise or results claim 8768 8769- Request-to-persistence trace with synthetic identifier 8770- Negative and duplicate-request tests 8771- Documented application and provider states 8772 8773These artifacts are requirements, not supplied project results. A methods article can explain documented principles without claiming that a customer implementation exists. A case study additionally needs a real scoped engagement, permission, original before/after artifacts, known confounders, dates and approved result wording. An unmeasured benefit must remain a hypothesis. 8774 8775## Proposed public route and internal relationships 8776 8777Suggested route, pending canonical-host approval: `/expertise/backend-web/`. This is a planning path, not a deployed URL. Choose one canonical home before publication; do not duplicate the same article on both ThatDevPro and ThatDeveloperGuy. 8778 8779Link contextually from the relevant real service page and the discipline hub. Link to the next diagnostic step, an original proof artifact that is safe to publish, and a working contact path. The page must be useful without those links; link counts are not acceptance criteria. 8780 8781## Conversion and measurement contract 8782 8783Suggested action: request a scoped review of this problem, **only if that service is actually available**. Do not advertise 26 staffed departments. A practical single-author description is “A multidisciplinary review process with defined specialist responsibilities,” subject to the owner's approval. 8784 8785Measure the canonical page's observed search/citation exposure separately from referral sessions and qualified inquiries. Record page/source/window and event definitions with R16. The mere addition of this brief to a private library cannot create search exposure. 8786 8787## Publication gate 8788 8789R13 checks usefulness and distinction; R14 checks factual claims, author identity and any credentials; R20 approves sanitization and privacy; R11 checks truthful entity markup; R08 checks the chosen public URL; R25 coordinates publication and R26 performs the agreed independent checks where required. Missing evidence remains BLOCKED. A drafted byline is not author approval. 8790 8791No rankings, model recommendations or “recognized expert” status are promised. The intended path is demonstrated useful work, accurate attribution, accessible publication, independent corroboration and measured outcomes. 8792 8793## Research references 8794 8795- [D05 — HTTP semantics (RFC 9110)](https://www.rfc-editor.org/rfc/rfc9110.html): HTTP method and response semantics; application response does not establish business delivery. 8796- [D07 — HTML forms](https://html.spec.whatwg.org/multipage/forms.html): Native form submission, constraints, labels and submit controls; client validation is not server validation. 8797- [D33 — Simple Mail Transfer Protocol (RFC 5321)](https://www.rfc-editor.org/rfc/rfc5321.html): SMTP acceptance, relaying and failures; acceptance is distinct from final mailbox observation. 8798- [D41 — Application Security Verification Standard](https://owasp.org/www-project-application-security-verification-standard/): Application security verification requirements; tailor version and assurance scope before adopting controls. 8799 8800============================================================================== 8801DOCUMENT 087 OF 135 8802Title: R04 public-content brief — How do you build a website that remains usable when JavaScript fails? 8803Path: Publishing/Briefs/R04-frontend-web.md 8804Group: briefs 8805Label: PUBLIC WORKBENCH · not approved 8806Review status: scope_stated_in_document 8807============================================================================== 8808 8809# R04 public-content brief — How do you build a website that remains usable when JavaScript fails? 8810 8811**State:** NOT_APPROVED_FOR_PUBLICATION. **Type:** evidence-led article/service-support brief. **Primary specialist:** R04. **Proposed author:** Joseph, subject to his review and approval; do not insert unverified credentials. This is not completed client work. 8812 8813## Reader and purpose 8814 8815A business owner or practitioner facing this specific problem needs a diagnosis and a way to evaluate professional help. The article should answer: **How do you build a website that remains usable when JavaScript fails?** 8816 8817**Distinct contribution:** An inspectable progressive-enhancement example with HTML baseline, enhanced states and deliberate failure tests. 8818 8819## Candidate search questions — hypotheses, not measured demand 8820 8821- progressive enhancement business website 8822- website form javascript fails 8823- responsive frontend error handling 8824 8825No keyword volumes, ranking difficulty, expected traffic, citation probability or sales forecast have been measured for these suggestions. R23 validates commercial relevance from real inquiries or authorized search data; R10 checks answer relevance. Merge with an existing page when its task is already answered well. 8826 8827## Proposed outline 8828 88291. Define the essential task 88302. Start with meaningful HTML 88313. Add resilient states 88324. Test script failure and narrow screens 8833 8834Open with a direct bounded answer. Explain the observable distinction that matters, demonstrate the method with an authorized artifact or an explicitly hypothetical example, and close with practical limitations. Do not clone this outline across 26 pages by changing only role names. 8835 8836## Evidence needed before making an expertise or results claim 8837 8838- State-by-state UI contract 8839- HTML/DOM and keyboard behavior captures 8840- Responsive and no-script/failed-script test results 8841 8842These artifacts are requirements, not supplied project results. A methods article can explain documented principles without claiming that a customer implementation exists. A case study additionally needs a real scoped engagement, permission, original before/after artifacts, known confounders, dates and approved result wording. An unmeasured benefit must remain a hypothesis. 8843 8844## Proposed public route and internal relationships 8845 8846Suggested route, pending canonical-host approval: `/expertise/frontend-web/`. This is a planning path, not a deployed URL. Choose one canonical home before publication; do not duplicate the same article on both ThatDevPro and ThatDeveloperGuy. 8847 8848Link contextually from the relevant real service page and the discipline hub. Link to the next diagnostic step, an original proof artifact that is safe to publish, and a working contact path. The page must be useful without those links; link counts are not acceptance criteria. 8849 8850## Conversion and measurement contract 8851 8852Suggested action: request a scoped review of this problem, **only if that service is actually available**. Do not advertise 26 staffed departments. A practical single-author description is “A multidisciplinary review process with defined specialist responsibilities,” subject to the owner's approval. 8853 8854Measure the canonical page's observed search/citation exposure separately from referral sessions and qualified inquiries. Record page/source/window and event definitions with R16. The mere addition of this brief to a private library cannot create search exposure. 8855 8856## Publication gate 8857 8858R13 checks usefulness and distinction; R14 checks factual claims, author identity and any credentials; R20 approves sanitization and privacy; R11 checks truthful entity markup; R08 checks the chosen public URL; R25 coordinates publication and R26 performs the agreed independent checks where required. Missing evidence remains BLOCKED. A drafted byline is not author approval. 8859 8860No rankings, model recommendations or “recognized expert” status are promised. The intended path is demonstrated useful work, accurate attribution, accessible publication, independent corroboration and measured outcomes. 8861 8862## Research references 8863 8864- [D07 — HTML forms](https://html.spec.whatwg.org/multipage/forms.html): Native form submission, constraints, labels and submit controls; client validation is not server validation. 8865- [D08 — Browsers](https://playwright.dev/docs/browsers): Supported engines and branded channels; WebKit automation is not a real Safari or iOS test. 8866- [D11 — Web Content Accessibility Guidelines 2.2](https://www.w3.org/TR/WCAG22/): WCAG 2.2 success criteria and conformance requirements; AA is the project target, not a legal certification. 8867 8868============================================================================== 8869DOCUMENT 088 OF 135 8870Title: R05 public-content brief — Is a Playwright WebKit test the same as testing Safari on an iPhone? 8871Path: Publishing/Briefs/R05-browser-compatibility.md 8872Group: briefs 8873Label: PUBLIC WORKBENCH · not approved 8874Review status: scope_stated_in_document 8875============================================================================== 8876 8877# R05 public-content brief — Is a Playwright WebKit test the same as testing Safari on an iPhone? 8878 8879**State:** NOT_APPROVED_FOR_PUBLICATION. **Type:** evidence-led article/service-support brief. **Primary specialist:** R05. **Proposed author:** Joseph, subject to his review and approval; do not insert unverified credentials. This is not completed client work. 8880 8881## Reader and purpose 8882 8883A business owner or practitioner facing this specific problem needs a diagnosis and a way to evaluate professional help. The article should answer: **Is a Playwright WebKit test the same as testing Safari on an iPhone?** 8884 8885**Distinct contribution:** A transparent coverage matrix separating engine, branded-browser, emulated-device and actual-device evidence. 8886 8887## Candidate search questions — hypotheses, not measured demand 8888 8889- Playwright WebKit versus Safari testing 8890- real iPhone website testing 8891- browser compatibility website audit 8892 8893No keyword volumes, ranking difficulty, expected traffic, citation probability or sales forecast have been measured for these suggestions. R23 validates commercial relevance from real inquiries or authorized search data; R10 checks answer relevance. Merge with an existing page when its task is already answered well. 8894 8895## Proposed outline 8896 88971. Name exactly what ran 88982. Separate engine from product 88993. Reproduce native-device differences 89004. Report coverage without overclaiming 8901 8902Open with a direct bounded answer. Explain the observable distinction that matters, demonstrate the method with an authorized artifact or an explicitly hypothetical example, and close with practical limitations. Do not clone this outline across 26 pages by changing only role names. 8903 8904## Evidence needed before making an expertise or results claim 8905 8906- Versioned environment matrix 8907- Minimal reproduction and comparative behavior record 8908- Actual-device results or explicit untested rows 8909 8910These artifacts are requirements, not supplied project results. A methods article can explain documented principles without claiming that a customer implementation exists. A case study additionally needs a real scoped engagement, permission, original before/after artifacts, known confounders, dates and approved result wording. An unmeasured benefit must remain a hypothesis. 8911 8912## Proposed public route and internal relationships 8913 8914Suggested route, pending canonical-host approval: `/expertise/browser-compatibility/`. This is a planning path, not a deployed URL. Choose one canonical home before publication; do not duplicate the same article on both ThatDevPro and ThatDeveloperGuy. 8915 8916Link contextually from the relevant real service page and the discipline hub. Link to the next diagnostic step, an original proof artifact that is safe to publish, and a working contact path. The page must be useful without those links; link counts are not acceptance criteria. 8917 8918## Conversion and measurement contract 8919 8920Suggested action: request a scoped review of this problem, **only if that service is actually available**. Do not advertise 26 staffed departments. A practical single-author description is “A multidisciplinary review process with defined specialist responsibilities,” subject to the owner's approval. 8921 8922Measure the canonical page's observed search/citation exposure separately from referral sessions and qualified inquiries. Record page/source/window and event definitions with R16. The mere addition of this brief to a private library cannot create search exposure. 8923 8924## Publication gate 8925 8926R13 checks usefulness and distinction; R14 checks factual claims, author identity and any credentials; R20 approves sanitization and privacy; R11 checks truthful entity markup; R08 checks the chosen public URL; R25 coordinates publication and R26 performs the agreed independent checks where required. Missing evidence remains BLOCKED. A drafted byline is not author approval. 8927 8928No rankings, model recommendations or “recognized expert” status are promised. The intended path is demonstrated useful work, accurate attribution, accessible publication, independent corroboration and measured outcomes. 8929 8930## Research references 8931 8932- [D08 — Browsers](https://playwright.dev/docs/browsers): Supported engines and branded channels; WebKit automation is not a real Safari or iOS test. 8933- [D11 — Web Content Accessibility Guidelines 2.2](https://www.w3.org/TR/WCAG22/): WCAG 2.2 success criteria and conformance requirements; AA is the project target, not a legal certification. 8934 8935============================================================================== 8936DOCUMENT 089 OF 135 8937Title: R06 public-content brief — Why does a good Lighthouse score not prove that real visitors have a fast website? 8938Path: Publishing/Briefs/R06-web-performance.md 8939Group: briefs 8940Label: PUBLIC WORKBENCH · not approved 8941Review status: scope_stated_in_document 8942============================================================================== 8943 8944# R06 public-content brief — Why does a good Lighthouse score not prove that real visitors have a fast website? 8945 8946**State:** NOT_APPROVED_FOR_PUBLICATION. **Type:** evidence-led article/service-support brief. **Primary specialist:** R06. **Proposed author:** Joseph, subject to his review and approval; do not insert unverified credentials. This is not completed client work. 8947 8948## Reader and purpose 8949 8950A business owner or practitioner facing this specific problem needs a diagnosis and a way to evaluate professional help. The article should answer: **Why does a good Lighthouse score not prove that real visitors have a fast website?** 8951 8952**Distinct contribution:** Paired lab and field reporting with explicit sample/window limits and a documented performance repair. 8953 8954## Candidate search questions — hypotheses, not measured demand 8955 8956- Lighthouse versus Core Web Vitals field data 8957- business website performance audit 8958- improve INP without breaking forms 8959 8960No keyword volumes, ranking difficulty, expected traffic, citation probability or sales forecast have been measured for these suggestions. R23 validates commercial relevance from real inquiries or authorized search data; R10 checks answer relevance. Merge with an existing page when its task is already answered well. 8961 8962## Proposed outline 8963 89641. Separate diagnostic and audience evidence 89652. Locate the measured bottleneck 89663. Apply a guarded change 89674. Wait for sufficient field evidence without fabricating it 8968 8969Open with a direct bounded answer. Explain the observable distinction that matters, demonstrate the method with an authorized artifact or an explicitly hypothetical example, and close with practical limitations. Do not clone this outline across 26 pages by changing only role names. 8970 8971## Evidence needed before making an expertise or results claim 8972 8973- Field/lab separation and route-level baseline 8974- Trace-supported bottleneck and controlled comparison 8975- Cache safety and critical-journey regression results 8976 8977These artifacts are requirements, not supplied project results. A methods article can explain documented principles without claiming that a customer implementation exists. A case study additionally needs a real scoped engagement, permission, original before/after artifacts, known confounders, dates and approved result wording. An unmeasured benefit must remain a hypothesis. 8978 8979## Proposed public route and internal relationships 8980 8981Suggested route, pending canonical-host approval: `/expertise/web-performance/`. This is a planning path, not a deployed URL. Choose one canonical home before publication; do not duplicate the same article on both ThatDevPro and ThatDeveloperGuy. 8982 8983Link contextually from the relevant real service page and the discipline hub. Link to the next diagnostic step, an original proof artifact that is safe to publish, and a working contact path. The page must be useful without those links; link counts are not acceptance criteria. 8984 8985## Conversion and measurement contract 8986 8987Suggested action: request a scoped review of this problem, **only if that service is actually available**. Do not advertise 26 staffed departments. A practical single-author description is “A multidisciplinary review process with defined specialist responsibilities,” subject to the owner's approval. 8988 8989Measure the canonical page's observed search/citation exposure separately from referral sessions and qualified inquiries. Record page/source/window and event definitions with R16. The mere addition of this brief to a private library cannot create search exposure. 8990 8991## Publication gate 8992 8993R13 checks usefulness and distinction; R14 checks factual claims, author identity and any credentials; R20 approves sanitization and privacy; R11 checks truthful entity markup; R08 checks the chosen public URL; R25 coordinates publication and R26 performs the agreed independent checks where required. Missing evidence remains BLOCKED. A drafted byline is not author approval. 8994 8995No rankings, model recommendations or “recognized expert” status are promised. The intended path is demonstrated useful work, accurate attribution, accessible publication, independent corroboration and measured outcomes. 8996 8997## Research references 8998 8999- [D05 — HTTP semantics (RFC 9110)](https://www.rfc-editor.org/rfc/rfc9110.html): HTTP method and response semantics; application response does not establish business delivery. 9000- [D09 — Web Vitals](https://web.dev/articles/vitals): LCP, INP and CLS; field assessment differs from lab diagnostics.