# DISCIPLINE_SKELETON_OVERLAY -- Overlay Protocol for 11 Disciplines

**Owner:** Epistemic Output Layer (S4). **Library:** Private RAM. **Consumers:** S4 only.

The 11 inherited Librarian discipline output skeletons live in `../../../_public/discipline-skeletons/`. This file defines how to overlay the three-axis block, Surprise Register, and Search Ledger onto any native skeleton at Phase D.

---

## 1. The 11 Inherited Disciplines

- systematic-review
- scoping-review
- realist-review
- content-analysis
- qualitative-synthesis
- secondary-data-analysis
- competitive-intelligence
- comparative-analysis
- discourse-analysis
- historiography
- research-auditor

Each skeleton is a read-only scaffold. The overlay rules below apply uniformly regardless of discipline.

---

## 2. Overlay Rules

### 2.1 Claim-level overlay
For every claim slot in the native skeleton (whatever the discipline calls it -- "finding," "theme," "CMO configuration," "code," "category," etc.):
1. Attach the three-axis block (evidence / transportability / decision) at the claim.
2. Render the axes in canonical order, separately displayed, with slot label visible on transportability.
3. Render the type-coded caveat inline if the claim type is normative or interpretive.

### 2.2 Top-level sections (added uniformly)
Every overlaid artifact gains three top-level sections (inserted in this order near the end, before any appendix):
- **Surprise Register section** -- top-level, not nested in a claim. Render every entry per `RAM_SEARCH_LEDGER_RENDER_SPEC.md` and Cross-Cutting artifact spec.
- **Search Ledger section** -- top-level. Render every record kind (every-query / every-accepted / every-rejected / every-skipped).
- **Methodology trace** -- which discipline ran (by name), which corpora, which methods, warrant rationale from Warrant Governor, any discipline-specific method tags.

### 2.3 Multi-discipline merge
If the Orchestrator invoked more than one discipline on a single question:
- Merge native skeletons by claim. Each claim appears once.
- The three-axis block appears once per claim.
- The methodology trace lists every invoked discipline with its own method-tag block.
- Native section headings that differ between disciplines (e.g., realist-review "CMO" vs systematic-review "Effect estimate") are preserved per-claim under the unified block.

### 2.4 Discipline-specific preservation
Do NOT strip discipline-native structure. The caller invoked the discipline deliberately; its output skeleton carries the reader expectations. For example:
- **systematic-review**: preserve PRISMA flow, eligibility, risk-of-bias summary per included study.
- **scoping-review**: preserve mapping tables and evidence-type inventories.
- **realist-review**: preserve CMO configurations; the three-axis block attaches to each configuration as a claim.
- **content-analysis**: preserve codebook and intercoder reliability; three-axis block attaches per category.
- **qualitative-synthesis**: preserve thematic structure; three-axis block per theme.
- **secondary-data-analysis**: preserve dataset provenance and hypothesis structure.
- **competitive-intelligence**: preserve entity profiles; three-axis block per comparative claim.
- **comparative-analysis**: preserve dimension matrix; three-axis block per dimension claim.
- **discourse-analysis**: preserve framing/subject-position findings; three-axis block per interpretive claim.
- **historiography**: preserve temporal narrative; three-axis block per causation claim.
- **research-auditor**: preserve audit-by-audit structure; three-axis block per adjudicated finding.

---

## 3. Emit Validation
Before Phase E emit, confirm:
- Every claim slot in the native skeleton has a three-axis block (or `axis-not-computable` record).
- Surprise Register and Search Ledger are top-level sections.
- Methodology trace is present with at least one discipline named.
- Native discipline structure is recognizable (a systematic-review artifact should still look like a systematic-review, just augmented).

If any check fails -> HALT with E7 (methodology trace) or E1/E2/E3/E4/E5 as appropriate.

---

## 4. Design Constraint
The overlay never REPLACES native structure; it AUGMENTS it. A reader who knows the discipline should recognize the native skeleton at first glance and find the three-axis block + Register + Ledger as additive sections, not as replacements.
