Discovery work is useful only when it makes the research easier to find, understand, verify, quote, and revisit. Built To Resist treats SEO, AEO, GEO, accessibility, and agent readiness as different layers of the same evidence-first publishing discipline.
Use stable canonical URLs, descriptive titles, useful visible text, normal crawlable links, sitemaps, truthful structured data, accessible markup, and strong page experience. Dates change when content changes—not to simulate freshness.
Concise answer units lead into deeper evidence. Definitions and direct answers stay quotable while keeping limitations nearby. The answer index exists to route systems and people to the canonical evidence page, not to replace it.
Generative systems benefit from clear entities, stable terminology, original analysis, provenance, source diversity, section anchors, currentness labels, and claim-to-source routing. The site does not publish unsupported “AI ranking” markup or cloaked machine-only claims.
AG-UI is the Agent–User Interaction protocol. Built To Resist currently exposes public machine-readable research interfaces but no live AG-UI endpoint. A future endpoint must be observable, source-routed, public-context-only by default, and human-approved for material actions.
Core evidence remains readable without client-side execution. Performance, accessibility, and security are release criteria.
| Layer | Built To Resist rule |
|---|---|
| HTML | Semantic landmarks, descriptive headings, native controls, accessible media, explicit language, meaningful links, stable canonical metadata, and reserved media dimensions. |
| JavaScript | Progressive enhancement, deferred/non-blocking loading, first-party code, bounded DOM updates, keyboard-safe interactions, graceful network failure, and no dependency on social-network SDKs. |
| CSS | Responsive/mobile-first layout, visible focus, WCAG 2.2 AA contrast target, reduced-motion support, modest critical CSS, and no visual optimization that hides indexable or accessible content. |
| PHP / future server code | Use a supported PHP branch, strict typing where practical, PHP-FIG style/autoloading, prepared database access, context-correct escaping, CSRF/session protections, least privilege, and secrets outside the public tree. |
These files help software navigate public research. They are not a license to expose private project memory or internal control state.
Optional machine-readable route map for the public research surface.
Open →AEOConcise public answers with canonical routes and evidence boundaries.
Open →RetrievalCollection-level machine index for public pages and source readers.
Open →Agent readinessStates explicitly that the site is content-ready but does not yet expose a live AG-UI endpoint.
Open →Current implementation is checked against Google Search Central guidance, Schema.org, W3C WCAG 2.2, MDN Web Docs, PHP supported-version guidance / PHP-FIG coding standards, and the AG-UI protocol specification.
Publishing is public; it is not a promise of search ranking, AI citation, or approval by an advertising platform.
Paid distribution is separate from organic discovery. This site has no newly deployed ad pixels, remarketing, audience profiling, paid campaigns, or conversions in this release. Any future campaign should use accurate claims, a transparent sponsor, a suitable landing page, and required political-ad review where applicable.
Public answer pages and JSON entries route each concise answer to its source-backed analysis. The answer index exposes uncertainty and source boundaries; a short answer is not an independent new citation.
Published provenance, evidence boundaries, original reports, stable canonical URLs, and machine-readable discovery files make research easier to evaluate. No special schema or automated ingestion guarantee is claimed.
Built To Resist serves a static, public, read-only retrieval layer. It does not operate an AG-UI streaming endpoint, execute tools, or accept private user state. A future runtime would need authentication, authorization, consent, and an actual AG-UI implementation.
Video visibility trade-off: locally hosted preview artwork and opt-in YouTube players prioritize privacy. The watch-page videos do not include unverified upload dates or durations, so eligibility for Google's enhanced video presentation is not asserted. A static video sitemap provides verified watch-page, thumbnail, title, and player URLs.
See the machine-readable audit and the read-only agent interface statement. Official references: Google AI Search optimization, video structured data, AG-UI events, and Google political advertising policy.