Pattern Catalog

Private or user-provided source material may be acquired into local source packets only for reviewed handoff. Raw private sources, private PDFs, account identifiers, location-bearing materials, screenshots, and personal identifiers must not be published.

v1.1 source packets must preserve raw source artifacts, metadata, extraction receipts, source indexes, and visual indexes when applicable before downstream HTML or infographic artifacts are produced.

Codex owns source acquisition and packet packaging. ChatGPT owns final interpretation and artifact generation. Gemini is optional fallback extraction only, never a required upstream dependency.

Private or user-provided source material may inform the final public-safe narrative only after review, redaction, and owner approval. Raw private sources, identity-sensitive documents, account material, compensation data, and private chronological ledgers must not be published.

Pattern-controlled artifacts should be checked for self-contained static HTML posture, absence of remote dependencies and runtime services, registry consistency, public-safe source profile, and visible credibility boundary language.

The authority path and template define the reusable standard. The Tony Career Arc page is an existing public-safe example and does not redefine the pattern or publish source material.

SharePlane artifacts must remain public-safe. Raw source packets, transcripts, subtitles, media, screenshots, private source material, normalization handoffs, and temporary files must not be committed or published.

The standard package is validated by validation/scripts/check_shareplane_artifact_standard_v01.py. Future artifacts should add focused deterministic validators scaled to artifact risk without retrofitting existing pages unless explicitly scoped.

The standard defines a shared shell and quality contract while allowing custom artifact skins. It does not create a new artifact, redesign existing artifacts, or migrate all current artifacts.

Pattern-controlled artifacts must stay public-safe. Public pages explain origin thesis, source backing, claim posture, and public evidence trail without exposing local filenames, validator paths, receipt paths, raw packets, transcripts, screenshots, private source material, temporary files, or repo hygiene.

Pattern-controlled work should validate required reader modes, premium light/dark parity, prompt suite copy-readiness, public-safe provenance, static implementation boundaries, registry/catalog consistency, and absence of prohibited materials or public implementation internals.

The authority path defines the reusable pattern. The Agent-Readable Web page is the approved reference implementation and catalog example, but it does not redefine the locked pattern or publish any new artifact in this lane.

Pattern-controlled op-ed artifacts must remain public-safe. Public pages may include owner-approved opinion, public-source links, claim posture, and reader-facing provenance, but must not publish raw packets, transcripts, screenshots, private source material, confidential records, local paths, implementation internals, or workflow-only receipts as reader content.

Pattern-controlled artifacts should validate article-first flow, single-file HTML posture, local CSS, source theme and desktop TOC preservation when present, minimal footer/source/provenance additions, registry/catalog consistency, no boxed dashboard conversion, no article-copy compression or rewriting, and absence of prohibited runtime/build/private material.

The authority path defines the reusable pattern. The AI Underclass page is the first proven implementation and catalog example, but future artifacts must reuse the preservation rules rather than copying the visible shell or mutating the published op-ed artifact.

Pattern-controlled artifacts must stay public-safe. Public pages may explain owner-approved or repo-derived thesis origin, source backing, claim posture, and caveats, but must not publish raw packets, transcripts, screenshots, media, private source material, confidential records, local staging paths, or implementation internals as reader content.

Pattern-controlled artifacts should validate required section order, near-top origin clarity, compact mobile navigation, article-lane completeness, source spine, source dossier, claim ledger, related artifacts, visual prompt suite, footer receipt readability, static-first behavior, registry scope, and absence of prohibited private/runtime/build material.

The authority path defines the reusable pattern. The Subscription Is Tuition page is the first proven implementation and catalog example, but future artifacts must use this standard rather than copying the visible shell or mutating the published artifact.

Pattern-controlled artifacts must remain public-safe. Public pages may include owner-approved thesis language, public-source links, source posture, claim/evidence ledgers, and reader-facing provenance, but must not publish raw source packets, transcripts, screenshots, private source material, confidential records, local paths, implementation internals, or workflow-only receipt details as reader content.

Pattern-controlled artifacts should validate source SHA, target slug/path, article body preservation, author/origin attribution, public-safe disclaimer, source index and claim/evidence ledger when present, SharePlane navigation and footer receipt, registry/catalog consistency, JavaScript-disabled completeness, no hidden core content, no external dependencies, no raw/private/source-packet material, and no unrelated artifact mutation.

The authority file defines the reusable pattern. The Do Not Outsource the Brain page is the first proven implementation and catalog example, but future artifacts must reuse the preservation and validation rules rather than copying the visible shell wholesale or mutating the published artifact.

Pattern-controlled artifacts must remain public-safe. Public pages may include owner-origin or curated thesis language, public-source links, source posture, claim/evidence ledgers, related artifact meaning, and reader-facing provenance, but must not publish raw source packets, transcripts, screenshots, private source material, confidential records, local paths, implementation internals, issue or PR mechanics, validator names, or workflow-only receipt details as reader content.

Pattern-controlled artifacts should validate first proven implementation identity, article-first structure, executive scan, visual metaphor module, operational test/checklist, claim/evidence ledger when applicable, source index when applicable, related artifacts when applicable, JavaScript-disabled completeness, no external dependencies, no raw/private/source-packet material, no reader-facing implementation internals, and valid TOC anchors and source links in implementation validators.

The authority file defines the reusable pattern. Demo Debt is the first proven implementation and catalog example, but future artifacts must abstract the premium editorial ledger thesis grammar rather than copying the visible shell or mutating the published artifact.

Handoff capsules must remain public-safe inside the SharePlane repo. Raw packets, transcripts, subtitles, media, screenshots, private source material, normalization handoffs, temporary files, account identifiers, location-bearing materials, __pycache__, and .pyc files must not be committed.

Capsules should validate required inventory, manifest fields, Codex prompt fields, implementation ticket fields, Creative Lock Gate fields, checksum coverage, artifact-versus-pattern separation, public/private material exclusions, naming conventions, acceptance criteria, and stop/report conditions.

The authority path defines the reusable handoff package standard. The Agent-Readable Web and Premium Editorial Technical Explainer workflows are references only; this pattern does not publish a new artifact or redefine those outputs.

Pattern-controlled artifacts must remain public-safe. Public pages may explain expert-source framing, claim posture, caveats, and SharePlane interpretation, but must not publish raw packets, transcripts, subtitles, screenshots, media, private source material, confidential records, local paths, implementation internals, or workflow-only receipts as reader content.

Pattern-controlled artifacts should validate article-led structure, source posture, expert-source boundary, source-role table, claim/evidence/caveat/interpretation ledger, caveat rail, source spine, reader-facing receipt, visual prompt-suite claim boundaries where scoped, absence of internal process language, static-first behavior, registry scope, and absence of prohibited raw/private/runtime/build material.

The authority path defines the reusable pattern. Copyable Agency is the first proven implementation and catalog example, but future artifacts must abstract the source-claim governance grammar rather than copying the visible shell or mutating the published artifact.

Pattern-controlled prompt suites must remain public-safe. Prompt bodies may include owner-approved thesis language, public-source framing, visible labels, and teaching-graphic instructions, but must not publish raw packets, transcripts, screenshots, media, private source material, confidential records, local paths, implementation internals, exploit instructions, or workflow-only receipts as reader content.

Pattern-controlled artifacts should validate self-contained prompt bodies, paired Mainline White and Dark Expressive variants, collapsed native prompt drawers, terminal-style prompt boxes, copy controls that copy prompt bodies only, JavaScript-disabled prompt availability, page-aesthetic separation, and absence of prohibited private/runtime/build material.

The authority path and template define the reusable prompt-package pattern. The Worm Is in the Workflow page is the first proven implementation and catalog example, but future artifacts must reuse the prompt-package structure rather than copying the visible page aesthetic or mutating the published artifact.