Life Domains Vision
Vision
Uvilo’s life domains are the foundational taxonomy that underpins every quiz, scoring model, and analytics surface in the product. Each domain represents a major area of human experience — Body, Mind, Home, Intimacy, Community, School, Work, Business, Money, Parenting, Caregiving, Play, Growth, and Purpose — and carries the metadata that downstream systems use to generate quizzes, interpret results, and produce recommendations.
The 14 domains and their metadata already exist in draft form (Output/Life_Domains.json), evolved from an earlier 13-domain CSV. This project formalizes that work: promoting the domain definitions from draft to published, enforcing a clear metadata schema, validating tag coverage for quiz authoring, and establishing a repeatable process for reviewing and updating domain data as Uvilo’s methodology evolves.
Background
The life domains originated outside the Forge project framework. A v2 CSV defined 13 domains; the current JSON expanded to 14 (adding Business and Caregiving, renaming Connection→Community, merging Meaning+Legacy→Purpose). The existing life-domains skill focuses on quiz authoring and review, referencing domain data but not managing domain metadata itself. Downstream consumers — Domain Quiz (Spec_Completed), Onboarding Quiz (Spec_Eval_Started), and Analytics (Spec_Eval_Blocked) — all depend on a stable, validated domain reference.
Requirements
R1: Canonical domain set
Publish the canonical set of 14 life domains with complete, consistent metadata. Each domain must have a stable identifier, title, subtitle, description, icon, and ordering. All domains must be promoted from draft to published status. The set must be stable — existing domain identifiers must not change without a versioned migration.
R2: Domain metadata schema
Define and enforce a schema for domain metadata. Fields include: id, domainId, number, title, subtitle, icon, imageId (optional), description, tags, conditional, and status. The schema must be validated programmatically so that malformed or incomplete domain definitions are caught before publication.
R3: Tag coverage for quiz authoring
Each domain must carry a tags array that defines the minimum coverage boundary for quiz questions. Tags represent the sub-areas and constructs within a domain that quiz authors must address. The Domain Quiz spec already enforces that every tag is covered by at least one question; the domain definitions must provide a complete, well-scoped tag set for each domain.
R4: Conditional domains
Support conditional domains that only apply to users based on life circumstances. Five domains are currently conditional: School, Work, Business, Parenting, and Caregiving. The conditional flag and the logic for determining applicability must be clearly defined so that downstream systems can skip non-applicable domains during onboarding and quiz flows.
R5: Machine-readable output
Produce a validated JSON output file (Life_Domains.json) that downstream systems — Domain Quiz, Onboarding Quiz, and Analytics — can consume directly. The output must be the single source of truth for domain definitions, replacing ad-hoc references and ensuring all consumers work from the same data.
R6: Update process and skill
Maintain a skill for creating, reviewing, and updating domain data. The skill must cover: adding new domains, modifying existing domain metadata, updating tags, promoting status from draft to published, and validating changes against the schema. The existing life-domains skill focuses on quiz authoring; domain metadata management must be clearly documented as a distinct workflow or separated into its own skill.
Success Criteria
| # | Criterion | Measured by |
|---|---|---|
| V1 | All 14 domains have complete metadata and published status | JSON output has status: "published" for every domain; no missing required fields |
| V2 | Domain metadata conforms to a defined schema with programmatic validation | A schema validator (TypeScript/Zod or equivalent) passes on the output JSON |
| V3 | Every domain has a non-empty tags array with well-scoped sub-areas | Manual review confirms tags are distinct, comprehensive, and aligned with quiz content |
| V4 | Conditional domains are clearly flagged with documented applicability logic | Each conditional domain has a documented condition; non-conditional domains have conditional: false |
| V5 | Output JSON is consumable by Domain Quiz, Onboarding Quiz, and Analytics | Downstream projects reference the canonical output path; no duplicated or stale domain definitions |
| V6 | A skill exists for creating, reviewing, and updating domain metadata | Skill documented with workflows for add, modify, validate, and publish operations |
Out Of Scope
- Quiz question authoring and scoring (Domain Quiz project)
- Onboarding quiz format and content (Onboarding_Quiz project)
- Analytics implementation and dashboards (Analytics project)
- User-facing UI for domain selection or display
- Database or API infrastructure for serving domain data at runtime
- Taxonomy system beyond domain-level tags (Taxonomy project)
Charter Considerations
- Stewardship — Life domains directly affect every Uvilo user who takes a quiz. Changes to domain definitions ripple through quiz content, scoring, and analytics. This project must ensure changes are versioned, validated, and communicated to downstream consumers. A corresponding requirement (R1: stable identifiers, versioned migration) has been added above.