# Input Precedence and Conflict Resolution

Apply the most specific applicable rule and the stricter safe boundary. A lower-priority source may add detail but may not weaken a higher-priority requirement.

## Order of precedence

1. Applicable law, regulation, emergency procedure, current approved institutional and clinical-site policy, contracts and licenses, and a currently authorized human decision within that person's actual scope.
2. This kit's absolute learner-data, PHI, patient, live-care, secure-assessment, privacy, accessibility, no-surveillance, no-fabrication, no-secret, authority, and no-in-app-consequential-action controls.
3. Canonical complete program `NAIO-NEID-COMPLETE-TEACH-1.0`, foundation `NAIO-NE-LPEF-1.0`, overlay `NAIO-NEID-TEACH-1.0`, and namespace `neid_teach.*`.
4. The resolved educator functional-build master prompt.
5. Product, architecture, governance, personalization, routing, capability, Guide, security, matrix, ledger, and handoff contracts in this kit.
6. The working Mission Control baseline as engineering material only.
7. Approved user preferences and approved derived Mission Profile fields.
8. Synthetic examples and Starter content, which never establish user facts, authority, eligibility, competence, or badge evidence.

## Nonwaivable narrowing rules

- The shipped personal application accepts no learner/student records or individual assessment payloads.
- Names removed from a submission, feedback item, clinical narrative, event, recording, or record do not make it safe.
- A future separately provisioned institutional workspace may accept only an exact separately approved non-person course/curriculum object or exact separately approved aggregate created outside TEACH, plus minimum routing metadata and opaque official-system references, under current purpose-matched authority.
- PHI, patient/event narratives, learner/person/row/submission data, grades/evaluations, accommodations, conduct/integrity records, secure items, secrets, and unclassified sensitive content remain prohibited.
- Real teaching release, grading, LMS change, learner communication, clinical action, institutional decision, publication, or other consequential execution occurs outside TEACH through an accountable human and approved official system.
- `edena_tier` and `absolute_stop` are independent. An absolute stop is never waived by acknowledgment, preference, role, or institutional context.
- Stopped content is never summarized, redacted, transformed, or reused. A permitted clean sandbox starts from new generic or synthetic information.
- Private life, health scheduling, family, financial, relationship, recovery, and career material never becomes institutional analytics, badge evidence, or learner-facing content.

## Conflict handling

When two sources conflict:

1. stop the affected operation before persistence, provider transmission, release, or external action;
2. identify the conflicting statements and the affected object or scope;
3. apply a nonwaivable higher-priority rule when one clearly controls;
4. otherwise retain the conflict as unresolved and name the authorized human or source required;
5. mark dependent recommendations, approvals, badges, and release states stale when applicable;
6. do not average, silently harmonize, or invent a rule.

Access, title, technical capability, a selected role adapter, an AI recommendation, or a completed checklist never proves authority.
