# Personalization Inputs — Derived Data Only

No real Discover Packet or Soul Quiz result is bundled. Hermes must not invent one.

The build kit includes compatibility input schemas copied from the validated baseline:

- `input-schemas/discover-packet-input.schema.json` for `NAIO-DISCOVER-PACKET-ADAPTER-1`
- `input-schemas/soul-profile-input.schema.json` for `NAIO-SOUL-PROFILE-ADAPTER-1`

Only derived, reviewed, nonsensitive results may use those adapters. Raw interview notes, transcripts, raw quiz answers and raw Hermes `SOUL.md` are prohibited.

`STEWARD-Mission-Profile.schema.json` defines the target editable profile created from approved derived inputs and minimum first-run answers. It is distinct from the Hermes Soul. Every proposed field requires visible provenance and user approval before persistence.

The target profile preserves global and per-workspace priorities/goals, strengths and growth areas, situation context, working/presentation/accessibility preferences, authority context, AI and memory boundaries, and recommended STEWARD assets. Recommendations are candidates only: they activate nothing and tool recommendations remain empty until real capability discovery.

Use `../implementation/STEWARD-Personalization-Mapping-Crosswalk.md` for the exact JSON-pointer, enum, conflict, role/workspace and legacy-workflow rules. Use `../implementation/STEWARD-Starter-Workspace-Crosswalk.md` for deterministic per-workspace Starter creation. Do not invent a mapping outside those contracts.

The two example inputs and one Mission Profile example are unmistakably synthetic. They demonstrate shape only and must never be silently adopted as user data, authority, competence, preferences or goals.

Hermes must implement a versioned mapping with tests for:

1. valid Discover-only input;
2. valid Soul-only input;
3. both inputs with consistent fields;
4. conflicting inputs requiring user resolution;
5. neither input, using minimum first-run questions;
6. unknown roles or schema versions;
7. prohibited/sensitive content rejection;
8. preview/edit/reject/approve/export/delete; and
9. field-level provenance, uncertainty and last-updated time.

Adapter imports may recommend workspaces or presentation. They cannot grant authority, activate an agent, weaken EDENA/CHART rules, enable memory or prove competence.
