# Source Notes and Provenance

## Purpose

This build kit preserves the supplied material as immutable evidence and distinguishes source authority from implementation-generated decisions. A source file that calls itself implementation-ready is still a specification; it does not prove that a runnable educator application exists.

The target begins `not_operational_build_required`.

## Pinned source families

### Functional-build contract

- `Mission-Control-Functional-Build-Master-Prompt.md`
- SHA-256: `ce884cfc6345cc93a6baec0852cf44feb44d859234ef1dc2b5ac2138df18ebe2`

### Working Mission Control engineering baseline

- Baseline archive SHA-256: `69a4dd86659b41136ce9ceb2ceb52512ab567637ab0be29fdc6f6ab6573223c1`
- Baseline release-manifest SHA-256: `22fed55fd789c933f4e7eb50266f88f8dda47f9fba91ebbe9c2cbe4f0ab99702`
- Baseline checksum-file SHA-256: `e178993d6185b126cc915f0d3026ddb3b07e7c5c7dd432aaf581152db8a5a40e`

The baseline is an engineering reference. It is not Nurse Educator domain authority and must be copied before editing.

### Standalone educator foundation

- `Nursing-Educator-Life-and-Practice-Hermes-Program.md`
  - SHA-256: `ee424bcd15c66ee01b706ce5697d7f188d3f49562aa79a43093374d899487e2f`
- `Nursing-Educator-AI-OS-Life-and-Practice-Guide.docx`
  - SHA-256: `c5ddfac2c161161257603d9e4d91c68226a921e350c70a14f895222ee684481d`

### Integrated TEACH distribution

- Complete Hermes program SHA-256: `d16b693d5a28b706e8f20b1b1f1b8941f2e81d93ce2f70cf00b151833b22f035`
- Setup guide Markdown SHA-256: `fd90028796a066f7854baf456fa761ba212979a584ba18088dc123df4915967a`
- Setup guide DOCX SHA-256: `12a1176b4c08cbab842204d9c24228e76809383a16c05b02817273e45b526e16`
- Prior outer ZIP SHA-256: `841e4b363d1de91560a786e37811c28011b3ee33741e8bfebe1670d30a3e8c92`

The prior ZIP contains the complete program and two setup guides. It does not contain an operational application, release manifest, checksum file, or standalone inner TEACH ZIP.

### Canonical TEACH source tree

- Files: 13
- Bytes: 44,430
- Deterministic tree digest: `b2738d9abedafe0c6b3ebe0ba05c8241b57bb316badd42ae2da482f5ddf5711e`

The digest is SHA-256 over sorted rows in this exact form:

```text
<file-sha256><two spaces><relative-path><newline>
```

There was no standalone inner TEACH ZIP. `SOURCE-INVENTORY.json` therefore records every relative file and hash plus this deterministic digest. The complete program embeds the 12 substantive TEACH files, omits only the development README, and adds the foundation. After removing wrapper blank lines, the embedded component text matches the standalone sources.

## Canonical versus build-layer identifiers

Canonical:

- `NAIO-NEID-COMPLETE-TEACH-1.0`
- `NAIO-NE-LPEF-1.0`
- `NAIO-NEID-TEACH-1.0`
- `neid_teach.*`
- source role names, power titles, workflow titles, template titles, and test IDs

Implementation-generated:

- Build kit `NAIO-NEID-TEACH-FUNCTIONAL-BUILD-KIT-1.0.0`
- Product ID `nurse-educator-instructional-designer-mission-control`
- Lane `nurse_educator_instructional_designer`
- Route `/nurse-educators-designers/dashboard`
- Home `My TEACH Command Studio`
- `TEACH-DATA-*`, executable schema, agent, permission, and stable catalog IDs

Implementation-generated identifiers must remain traceable to their source mapping and may not rewrite canonical titles.

## What is intentionally absent

This kit contains no real Discover Packet, Soul Quiz response, raw `SOUL.md`, learner record, learner work, grade, evaluation, accommodation, conduct record, secure assessment, patient information, employee file, institutional authorization, provider credential, API secret, live Hermes capability result, or earned badge evidence.

Personalization files are synthetic shape examples. They do not establish facts, authority, identity, competence, preference, or achievement.

## Existing validation versus runtime proof

The historical educator source-package validator passed its document checks. Those checks confirm file presence, embedded components, counts, guide coverage, and DOCX integrity. They do not verify the target runtime, persistence, authentication, streaming, cancellation, learner-data rejection, accessibility enforcement, backup/restore, clean installation, or Operational readiness.
