# SourceMesh Source-Derived Pattern Register Template V01

Issue: #54

Status: copy-ready operator template. Pattern registration does not promote the pattern into doctrine, package authority, production approval, vendor approval, model approval, tool approval, security assurance, compliance assurance, pricing or limits authority, benchmark or performance proof, source registry mutation, or source-of-record replacement.

## Purpose

Capture source-derived patterns after a Source Claim Verification Harness review so operators can route weak, caveated, verified, or rejected source material into the correct handling lane without accidentally promoting it into doctrine.

## Handling Lanes

Every row must map to one or more target lanes:

- Shared Core
- AI Capability Discipline
- WESS
- EA Assistant
- SourceMesh

The lane is a handling destination for review. It is not approval.

## Register Table

| pattern ID | source ID | source title | source type | source verification status | extracted pattern | claim IDs supporting the pattern | target lane | reuse category | caveat | owner review requirement | decision status | follow-up issue | retirement or refresh trigger |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| `PATTERN-001` | `SOURCE-001` | `source title` | transcript, practitioner video, podcast, article, repo, vendor documentation, or vendor-promoted material | verified, mostly verified, plausible but unverified, partially supported, contradicted, outdated, not independently verifiable, or opinion | concise pattern statement | `CLAIM-001`, `CLAIM-002` | Shared Core, AI Capability Discipline, WESS, EA Assistant, or SourceMesh | doctrine input after verification, pattern input with caveats, perspective signal only, terminology signal only, backlog candidate only, or no reuse | limitation, source class caveat, sponsor caveat, version caveat, evidence gap, or not applicable | owner validation required, owner review recommended, not required for perspective-only use, or not applicable | include, include with caveats, perspective-only, hold pending verification, exclude | issue number or not opened | date trigger, version trigger, source update, product change, model release, sponsor disclosure change, repo commit drift, or not applicable |

## Required Row Rules

- `pattern ID` must be stable inside the register.
- `source ID` must link to a completed verification packet or an explicit `hold pending verification` decision.
- `source verification status` must use the harness status set.
- `claim IDs supporting the pattern` must name the reviewed claims. Do not cite the source as a whole when only one claim supports the pattern.
- `target lane` must be one or more of Shared Core, AI Capability Discipline, WESS, EA Assistant, and SourceMesh.
- `reuse category` must be one of doctrine input after verification, pattern input with caveats, perspective signal only, terminology signal only, backlog candidate only, or no reuse.
- `owner review requirement` must be explicit when the pattern could affect doctrine, governance, source authority, tool behavior, model behavior, security, compliance, GxP, production interpretation, pricing, metrics, or package promotion.
- `decision status` must be include, include with caveats, perspective-only, hold pending verification, or exclude.
- `retirement or refresh trigger` must be present for stale-or-version-sensitive, vendor-claim, sponsor-claim, self-promotional-claim, practitioner-commentary, pricing, model capability, tool capability, product, security, and metric claims.

## Claim Reuse Labels

Apply evidence posture labels as needed:

- verified-source-supported
- source-supported-with-caveat
- perspective-only
- weak-signal
- vendor-claim
- sponsor-claim
- self-promotional-claim
- practitioner-commentary
- needs-independent-verification
- do-not-promote
- stale-or-version-sensitive
- unsafe-for-doctrine
- safe-for-pattern-intake
- owner-validation-required

These are evidence posture labels, not truth certification.

## Non-Promotion Rule

Pattern registration does not promote the pattern into doctrine.

Promotion requires a separate owner-approved change with evidence suited to the claim, validation coverage, receipt evidence, and explicit package-boundary review.

## Forbidden Use

The register must not create or imply:

- arbitrary web search
- browser-side source fetching
- provider calls
- package authority mutation
- source registry mutation
- production approval
- vendor approval
- model approval
- tool approval
- GxP approval
- security assurance
- compliance assurance
- pricing or limits authority
- benchmark or performance proof
- source-of-record replacement