egohygiene Create Personal Model Document
Repository continuity composition
For repository-scoped work, compose maintain-repository-continuity in
Resume mode before selecting work. After an authorized repository change
passes domain validation, compose Refresh and Verify immediately before
presenting the pull request, and include the reconciled root CONTINUITY.md in
the same change. A policy-permitted no-change or exemption result must be
documented instead of fabricating an edit.
- Contribute: Conceptual assumptions, boundaries, cited evidence, validation, and privacy-safe unknowns
- Never claim: That private context is publishable or an inferred personal model is approved fact
Purpose
Create or update PERSONAL_MODEL.md in conformance with architecture-personal-model.
The document must answer:
How does this project understand the people it serves while preserving agency, dignity, privacy, complexity, and change?
Use This Skill When
- the canonical document is missing
- terminology or assumptions are inconsistent
- upstream architecture has changed
- a repository is establishing or repairing its domain model
- downstream architecture needs a stable canonical reference
Required Inputs
Resolve the governing specification, upstream architecture, relevant evidence, existing terminology or assumptions, and downstream consumers.
Missing evidence must be recorded rather than invented.
Workflow
- inventory explicit and implicit assumptions about people
- separate evidence from preference and inference
- define agency, autonomy, identity, context, and change
- distinguish people from system representations
- define consent, privacy, and inference boundaries
- define correction and contestability expectations
- challenge universal and normative assumptions
- record limitations and unknowns
- report downstream design and AI implications
Output Contract
Produce:
PERSONAL_MODEL.md- governing specification identifier and version
- assumptions and unresolved questions
- validation results
- downstream migration or review recommendations
Constraints
- Preserve canonical terminology.
- Separate evidence, assumptions, and inference.
- Do not fabricate domain or human knowledge.
- Do not silently resolve contradictions.
- Do not leak implementation structure into canonical concepts.
- Do not claim completion when required evidence is missing.
Validation
Use:
references/validation-checklist.md
and the acceptance criteria in:
architecture-personal-model
Completion Criteria
- The governing specification is identified.
- Required upstream artifacts have been read.
- The primary question is answered.
- Boundaries are respected.
- Assumptions and open questions are visible.
- Structural, semantic, relationship, and evidence checks pass.
- Downstream impacts are reported.