Source of truth
docs/patterns/pattern-registry.json remains the source of truth for reusable patterns.
Reusable publishing standards
A generated public teaching surface for reusable SharePlane standards: how finished work keeps provenance, claim posture, receipts, validation, and source-of-truth boundaries visible.
How to read this catalog
Patterns explain repeatable ways to produce SharePlane artifacts, handoffs, prompts, receipts, and validation posture. They keep the discipline portable while topics vary across technical explainers, community materials, career evidence, operating models, calculators, essays, and other finished public-safe work.
docs/patterns/pattern-registry.json remains the source of truth for reusable patterns.
Pattern standards are authority. Generated catalog cards and example artifact pages explain or demonstrate them; they do not redefine them.
Pattern registry metadata is public. Authority docs may be mirrored later in a separate public-safe pattern-source lane; this page does not link private GitHub docs paths as public pages.
This page is generated from registry metadata. Update the registry and renderer, then rerender, rather than hand-editing individual pattern cards.
Source boundary
The catalog renders names, status, family, version, summaries, authority paths, template paths, example paths, privacy posture, validation posture, governance notes, and version boundaries from the pattern registry.
Paths under site/pages/ become public static links when they resolve to a public page. Repo-internal docs, templates, examples, and authority paths are displayed as code paths for now.
Public pattern-source mirroring is intentionally deferred to a future scoped lane so the public surface can be reviewed for source safety before docs become public pages.
Generated catalog
Each card shows the registry-backed pattern summary and the current public-link decision for templates, examples, and catalog pages.
Pattern standard
Locked MVP pattern for converting high-fidelity source material into a self-contained teaching artifact, reusable source packet, correction ledger, and thesis-focused infographic prompt suite.
locked
source-to-teaching-artifact
v1.0
source-to-teaching-artifact-v1.0
docs/patterns/source-to-teaching-artifact/v1.0/source_to_teaching_artifact_mvp_standard_v1.md
docs/patterns/source-to-teaching-artifact/v1.0/templates/source_packet_harness_v1.md Repo path onlydocs/patterns/source-to-teaching-artifact/v1.0/templates/html_artifact_spec_v1.md Repo path onlydocs/patterns/source-to-teaching-artifact/v1.0/templates/infographic_prompt_rules_v1.md Repo path onlydocs/patterns/source-to-teaching-artifact/v1.0/templates/final_processor_checklist_v1.md Repo path onlydocs/patterns/source-to-teaching-artifact/v1.0/templates/publication_manifest_template_v1.json Repo path onlyexamples/source-to-teaching-artifact/peer-preservation/README.md Repo path onlyexamples/source-to-teaching-artifact/peer-preservation/artifact.html Repo path onlyexamples/source-to-teaching-artifact/peer-preservation/source_extraction_packet.md Repo path onlyexamples/source-to-teaching-artifact/peer-preservation/infographic_prompt_suite.md Repo path onlyexamples/source-to-teaching-artifact/peer-preservation/mainline_dense_technical_infographic_pattern_harness.md Repo path onlyPrivate or user-provided source material may inform a generated artifact only after redaction and review. Raw private sources, private PDFs, account identifiers, location-bearing materials, screenshots, and personal identifiers must not be published.
Pattern-controlled artifacts must preserve source chain, correction history, validation posture, credibility notes, and publication-gate receipts before public catalog publication.
The authority path and templates are the controlled standard. Example files and catalog pages demonstrate the pattern but do not define or silently modify it.
v1.0 is locked. Corrections to examples or publication metadata may be proposed separately, but changes to the reusable pattern semantics require a new version such as v1.1.
Pattern standard
Locked MVP pattern for Codex-acquired source packets that preserve raw source artifacts before ChatGPT creates the final teaching artifact and infographic prompt suite.
locked
source-to-teaching-artifact
v1.1
source-to-teaching-artifact-v1.1
docs/patterns/source-to-teaching-artifact/v1.1/source_to_teaching_artifact_mvp_standard_v1_1.md
docs/patterns/source-to-teaching-artifact/v1.1/lanes/codex_source_acquisition_lane.md Repo path onlydocs/patterns/source-to-teaching-artifact/v1.1/templates/source_packet_harness_v1_1.md Repo path onlyPrivate 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.
v1.1 supersedes v1.0 for Codex source acquisition and no raw-source omission posture. Changes to required packet structure, raw-source preservation, or tool responsibilities require a later version such as v1.2.
Pattern standard
Draft reusable pattern for creating self-contained public-safe executive career, professional arc, or life-arc HTML artifacts without publishing raw private source material.
draft
executive-career-arc
v1.0
executive-career-arc-html-v1.0
docs/patterns/executive-career-arc/v1.0/executive_career_arc_html_pattern_v1.md
docs/patterns/executive-career-arc/v1.0/templates/executive_career_arc_outline_v1.md Repo path onlyPrivate 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.
v1.0 is the initial draft standard. Corrections that do not change source-handling, privacy, runtime, or credibility semantics may stay in v1.0; semantic changes require a later version such as v1.1.
Pattern standard
Draft reusable baseline for SharePlane artifact shells, reading lanes, visual prompt suites, provenance receipts, public-safe boundaries, and implementation prompts.
draft
shareplane-artifact-standard
v01
shareplane-artifact-standard-v01
docs/patterns/shareplane-artifact-standard-v01.md
docs/patterns/shareplane-visual-prompt-suite-standard-v01.md Repo path onlydocs/patterns/shareplane-provenance-receipt-standard-v01.md Repo path onlydocs/patterns/shareplane-artifact-implementation-prompt-v01.md Repo path onlySharePlane 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.
v01 is the first draft baseline for future artifact implementation prompts. Changes to shell expectations, reading lanes, prompt-suite requirements, provenance boundaries, or prohibited-material rules require a later standard version or explicit owner approval.
Pattern standard
Locked reusable pattern for premium editorial technical explainers with executive scan, thesis reading view, guided explainer, evidence and implementation mode, and paired mainline white and dark expressive prompt variants.
locked
premium-editorial-technical-explainer
v01
premium-editorial-technical-explainer-v01
docs/patterns/premium-editorial-technical-explainer-v01.md
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.
v01 is locked from the approved Agent-Readable Web PR #73 reference implementation. Changes to required reader modes, palette posture, provenance model, prompt-suite requirements, or static constraints require a later version such as v02.
Pattern standard
Locked reusable pattern for packaging SharePlane artifact and pattern handoffs with a manifest, Codex prompt, implementation ticket, Creative Lock Gate blueprint, optional pattern follow-up, checksums, exclusions, validation, and stop/report conditions.
locked
shareplane-complete-handoff-capsule
v01
shareplane-complete-handoff-capsule-v01
docs/patterns/shareplane-complete-handoff-capsule-v01.md
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.
v01 is locked as the first complete handoff capsule standard. Changes to required inventory, manifest fields, source handling, checksum rules, task separation, prohibited-material posture, or validation posture require a later version such as v02.