The decision
SharePlane Next will be compiled before deployment and inert afterward. A small Python standard-library tool will produce the catalog, graph, metadata, discovery files, and receipts. The browser receives finished HTML and CSS rather than a catalog that assembles itself after arrival.
The artifact is the product. Provenance proves it. Governance should not obscure it.
One artifact, one authority
Each artifact owns one canonical structured record and one locked page source. Catalogs, topic pages, agent indexes, graph projections, sitemaps, feeds, and receipts are generated from that record. Humans get a coherent reading surface. Agents get explicit structure. Neither has to reconcile several competing truths.
What remains
Static publishing, public-safe boundaries, source posture, independent artifacts, deterministic validation.
Authority, taxonomy, receipts, validators, and publication mechanics.
Browser-built catalogs, central-registry overload, untyped relationship arrays.
Accounts, comments, RAG, graph databases, managed hosting, and other expensive hobbies.
Evidence without visual punishment
Sources, claim posture, caveats, and receipts remain available from every artifact. They are structured and visible, but they are not allowed to dominate the page unless the artifact is specifically about those controls. The thesis leads. The evidence follows close enough to be trusted.