# Ward6 / Ward7 Skill Reference Documents

This folder is the master home for the Ward6 and Ward7 reference and source
documents used across the skills. Some of these files are loaded by skills at
runtime; the rest are human-maintained source documents that no skill loads
directly. The two groups are listed separately below.

## Group A: Loaded by skills at runtime

These files are uploaded to the `Skill references/` folder of the skills S3
bucket and fetched at runtime via the `get_skill_reference` tool. No retrieval,
no RAG. The skill reads the whole file deterministically.

Proof Check (Skill 1), used by both `ward6-proof-check` and `ward7-proof-check`:

- `Ward6 Rules Checklist.md`, `Ward7 Rules Checklist.md` — the canonical rule
  list the Proof Checker walks every document against. Loaded on every run. This
  file replaces runtime parsing of the house style documents and is the primary
  control on run-to-run consistency.
- Brand Approved Terms (loaded only for the detected brand):
  - `Maviret Approved Terms.md` (Ward 6 brand)
  - `Veltassa Approved Terms.md` (Ward 6 brand)
  - `Kesimpta Approved Terms.md` (Ward 7 brand)
  - `Kisqali Approved Terms.md` (Ward 7 brand)

Reference & Claim Checker (Skill 2), used by both `ward6-reference-and-claim-checker`
and `ward7-reference-and-claim-checker`:

- `Ward6 References Style.docx`, `Ward7 References Style.docx`. The references style,
  loaded on every run to check citation and reference formatting. These are also the
  source authors use to maintain the Proof Check Rules Checklists.
- Brand Approved Claims, the approved claims library (loaded only for the detected brand):
  - `Maviret Approved Claims.docx` (Ward 6 brand). Fictional placeholder, pending a real library.
  - `Veltassa Approved Claims.docx` (Ward 6 brand). Fictional placeholder, pending a real library.
  - `Kesimpta Approved Claims.docx` (Ward 7 brand). Fictional placeholder, pending a real library.
  - `Kisqali Approved Claims.docx` (Ward 7 brand). Real, sourced from Novartis KISQALI Core Claims (NOKI29007M).

Email Drafter (Skill 4), `ward-email-drafter` (one brand-agnostic skill; detects the brand at run time):

- **Mandatory:** the brand's `<Brand> Approved Claims.docx` and `<Brand> Approved Terms.md`, plus the ward's `Ward6/7 House Style.docx` and `Ward6/7 References Style.docx`.
- **Optional (graceful fall-back):** `<Brand> Email Templates.docx` (built-in standard template if missing), `Ward6/7 Voice & Tone.docx` (default register if missing), and `<Brand> Audiences.docx` (standard HCP archetypes if missing).

Word Document Formatter (Skill 5), `ward-word-document-formatter` (one brand-agnostic skill):

- **Mandatory:** the brand's `<Brand> Brand Values.md` — sponsor name, address, phone, website, ABN and the fallback mandatory disclaimer. The visual spec is baked into the skill, so no other file is loaded.
  - `Maviret Brand Values.md` (Ward 6), `Veltassa Brand Values.md` (Ward 6), `Kesimpta Brand Values.md` (Ward 7), `Kisqali Brand Values.md` (Ward 7). A `Brand Values TEMPLATE.md` fill-in template is also here.

Note: S4 and S5 load from this shared folder via `get_skill_reference` (the earlier brand-knowledge-base / RAG approach is retired). The Approved Claims Library Builder (Skill 6) produces the brand Approved Claims files above; it loads nothing from this folder itself.

To deploy: place these files in the `Skill references/` folder of the skills
S3 bucket. Do NOT place them in the brand knowledge bases (a different bucket),
and do NOT upload the `.skill` packages here.

## Group B: Source and reference documents (not loaded at runtime)

These are human-maintained. No skill loads them directly. They are the
source-of-truth authors use to maintain the Group A files, plus the wider house
style system.

- `Ward6 House Style.docx`, `Ward7 House Style.docx`. The source documents authors use
  to maintain the Rules Checklists. Not loaded at runtime by Proof Check; if a rule is in
  the docx but not in the checklist, the skill does not enforce it by design. References
  Style is also a checklist source, but it sits in Group A because Skill 2 loads it at runtime.
- `Ward6 Voice & Tone.docx`, `Ward7 Voice & Tone.docx`;
  `Ward6 Compliance & Regulatory Framing.docx`, `Ward7 Compliance & Regulatory Framing.docx`;
  `Ward6 Digital Writing.docx`, `Ward7 Digital Writing.docx` — proposed documents
  (starter content for team review), not yet adopted and not enforced.
- `Ward6 Production Workflow.docx`, `Ward7 Production Workflow.docx` — reference for
  file paths, templates, EndNote setup, and version control.
- `Ward6 Style Architecture & Skill Map.docx`, `Ward7 Style Architecture & Skill Map.docx`
  — the index of the six-document house style system: ownership, decay rates, and the
  skill-application matrix.

## Updating a runtime file

To change a rule or a term, update the relevant Group A file and re-upload it to
the `Skill references/` folder of the S3 bucket, overwriting the previous version.
The next skill invocation loads the new content. No `.skill` repackaging is needed.

## Naming convention

All brand and ward reference files use Title Case with spaces (e.g. `Kisqali Approved Claims.docx`, `Kisqali Approved Terms.md`, `Kisqali Brand Values.md`). The brand-values files were renamed from the earlier lower-case `kisqali-brand-values.md` form on 27 May 2026 to match.

## Related files kept elsewhere

- `<Brand> Email Templates.docx` is an optional Skill 4 input and belongs in this shared folder when a brand supplies one; until then the Email Drafter uses its built-in standard template. Platform-structure notes (`VAE Email Conventions.md`, `eWizard Email Conventions.md`) also live here.