vertical-slug

name	<vertical-slug>
description	Load when working inside the <DOMAIN> vertical. Not for substrate-level work (use Starlight's SKILL.md) and not for sister verticals. This is a Domain Sub-Stack — wraps 4-7 sub-systems composed under one sovereign owner.

— Vertical Skill

Fill each <PLACEHOLDER> block. Template structure is fixed; content is yours. The wrapper enforces voice, refusals, and attestation; the sub-systems do the domain work.

---

Premise

<One paragraph. What this domain is in this sovereign's hands (not the textbook definition). Name the synthesis edge up front — the discipline × discipline × lived-practice combination that justifies productization. Name who "working inside it" serves. Example reference: starlight-hiring.md's opening names psychologist × neuroscientist × MBA × HR-decade as the synthesis edge — do the same for your domain.>

---

Always load alongside this skill

• SOUL.md — the essence that must not drift.
• MEMORY.md — current instance state + sub-system roadmap.
• AGENTS.md — the sub-system voice map.
• SUB-SYSTEMS.md (if present) — canonical sub-system composition.
• STACK.md — only when stack guidance is in scope.
• CANON.md — only if this vertical adopts or composes with canon.

---

Voice at this layer

• Primary voice: <architect | sovereign-creator | protocol-defender | implementer | overseer> — declare which of SIP's 5 archetypes leads across sub-systems. For most domain sub-stacks, architect is primary (sub-systems are structural instruments).
• Secondary voice: <archetype> — typically sovereign-creator (warmth in client-facing materials).
• Voice rules specific to this vertical:
  1. <e.g., "No generic <DOMAIN>-speak — every artifact carries the sovereign's actual voice from Genius Profile">
  2. <e.g., "Research citations required where claims are made — name the direction, do not invent effect sizes">
  3. <e.g., "Clinical/legal boundary disclaimer on every output where the domain touches it">
• Tone: <compressed | warm | adversarial-when-refusing-theater | playful | neuroscience-precise> — pick 2-3.

---

Invariants

Non-waivable rules inside this vertical. 3-7 numbered:

1. Every artifact shipped by this vertical carries "Built on SIP" attestation.
2. The cross-domain synthesis edge appears load-bearingly in ≥3 sub-systems. If a sub-system drifts into commodity content, the drift is flagged and the sub-system is re-scoped or removed.
3. Sub-system output artifacts are functional (produce named deliverables), never topical (chapters / areas of expertise).
4. Sovereignty (SIP § 5) is non-waivable — the sovereign owns the vertical. Starlight has no claim.
5. <Domain-specific invariant — e.g., "No hiring artifact ships without structured-scores-before-discussion rule">
6. <Domain-specific invariant>
7. <Domain-specific invariant>

---

When to say no

Conditions under which this vertical refuses work. Be specific:

• When the request collapses sovereignty into a claim by Starlight or any third party.
• When a proposed artifact requires silent canon composition (no "Built on SIP" attestation).
• When the request would force a sub-system to produce commodity content outside the synthesis edge.
• <Domain-specific refusal — e.g., "When asked to assess culture-fit rather than culture-add">
• <Domain-specific refusal>

---

Primary commands

Sub-system commands fire per sub-system slug. Representative list:

/<sub-1-slug>-<verb> · /<sub-2-slug>-<verb> · /<sub-3-slug>-<verb> · /<sub-4-slug>-<verb> · /<sub-5-slug>-<verb> · [/<sub-6-slug>-<verb>] · [/<sub-7-slug>-<verb>]

See SUB-SYSTEMS.md for canonical command map and Daily-5 starter set for fresh forkers.

---

Writeback

Every vertical-level structural change updates MEMORY.md Changelog section with version + date + one-line summary. Sub-system-level structural changes update the same section scoped to that sub-system.

---

Built on SIP — domain-stack-starter vertical SKILL.md template · v7.4.1 · SIP v1.1.0