Entity Architecture is the lab proof for the structured publishing method behind this site. The work is simple to describe and hard to execute well: define the real entities, make their relationships explicit, and publish content in a way that human readers, search engines, and AI systems can interpret without guesswork.
What changed in this build
- The site now separates public proof, guides, knowledge, entities, catalog, and machine-readable endpoints into distinct route families.
- The WordPress theme owns content, routing, SEO, templates, and media while Vercel hosts only decorative Replit-source animation embeds.
- Recovered legacy proof and guide media are used in article support slots instead of being exposed as generic asset-inventory blocks.
- Receipts and evidence now record source truth, rollback anchors, route checks, content decisions, and remaining gaps.
Why this is proof
A visual site can look finished while still being structurally weak. This lab entry documents the opposite target: a public site whose content types, internal links, source receipts, and machine-readable surfaces are organized enough to keep future additions from breaking the architecture.
Architecture surfaces
Recovered support visuals
