Uvilo Method Vision
Vision
The Uvilo Method is Uvilo’s core methodology — the structured self-improvement process that guides users through assessing their life domains, setting priorities, and taking action. This project establishes the method as a living, versioned document within the Uvilo OS, with a repeatable release process that produces consistent output formats (Markdown, PDF, DOCX) from a single source, maintains an archive of previous versions, and keeps the method content current as Uvilo’s product features evolve.
The method document is comprehensive — covering the 360° Life Review, coach matching, interviews, persistent memory, the taxonomy system, self-help resources, goals, habits, metrics, and programs. As the product grows, the method must grow with it. This project ensures there is one authoritative source, a reliable pipeline to produce distributable outputs, and a clear version history that traces how the methodology has evolved.
Background
The Uvilo Method document (The_Uvilo_Method.md) is a large, structured markdown document that serves as the canonical description of Uvilo’s coaching methodology. It is both an internal reference and a customer-facing artifact. The project already contains an output prompt (Prompts/Output_Prompt.md) used as a template for generating the method, a release skill (Skills/Uvilo_Method_Release/) with an automated script that generates PDF and DOCX outputs via pandoc and weasyprint, and an archive of two previous versions (2025-10-01, 2026-02-07) plus older whitepapers.
Several sections of the current method are marked “[Work In Progress]” (Goals, Metrics, Programs), reflecting features still under development in the product. The release skill has dependencies on external tools (pandoc, weasyprint) and font assets that must be present for PDF generation to succeed.
Requirements
R1: Single Source of Truth
The Uvilo Method must be maintained as a single canonical markdown document that is the authoritative source for all method content. Duplicate copies must be eliminated or clearly subordinated to the canonical source. The source document must be versioned with a date stamp on each release.
R2: Repeatable Release Pipeline
The project must provide a reliable, automated release process that generates consistent output formats — Markdown (with generated table of contents), PDF (styled with Uvilo branding), and DOCX — from the single source document. The release process must handle version stamping, TOC generation, and multi-format output in a single invocation. All external dependencies (pandoc, weasyprint, fonts) must be documented and verifiable.
R3: Version Archive
Each released version of the method must be archived with its date, preserving the full document and all generated outputs (PDF, DOCX) for historical reference and traceability. The archive must clearly distinguish between method versions and earlier standalone whitepapers.
R4: Content Currency
The method content must be kept current with the product’s feature evolution. Sections marked as work-in-progress must be updated as the corresponding product features are completed. The output prompt must be maintained alongside the method document so that AI-assisted generation remains aligned with the current methodology.
R5: Knowledge System Integration
The Uvilo Method must be discoverable within the Uvilo OS knowledge system. This includes Typesense indexing for search, sidebar navigation entries, and cross-references to related knowledge such as Life Domains and Domain Quiz. The method document should be referenceable from other parts of the OS without ambiguity.
R6: Content Review Workflow
Because the Uvilo Method is customer-facing content that describes how Uvilo coaches users, changes to the method must go through a review workflow. The document status (draft → review → approved → published) must be enforced, and significant content changes should be reviewed before release.
Success Criteria
| # | Criterion | Measured by |
|---|---|---|
| V1 | A single canonical markdown file exists as the source of truth, with no unmanaged duplicates | File audit confirms one canonical source; other copies are clearly archived or removed |
| V2 | The release script produces Markdown, PDF, and DOCX outputs in a single run without manual intervention | Successful release run with all three outputs generated and valid |
| V3 | Each release creates a dated archive entry containing the full document and all output formats | Archive folder contains dated entries with .md, .pdf, and .docx files |
| V4 | Work-in-progress sections are updated or annotated with current status | No stale “[Work In Progress]” markers for shipped features; in-progress features clearly annotated |
| V5 | The method document is indexed in Typesense and appears in the OS sidebar with working navigation | Typesense search returns the method; sidebar entry navigates to the document |
| V6 | Document status frontmatter reflects the current review state | Status field is draft, review, approved, or published — never stale or missing |
Out Of Scope
- Building or modifying the Uvilo product features described in the method (coaching, habits, taxonomy, etc.) — those are product engineering tasks, not this project
- Creating new methodology content or domains beyond what already exists in the current method document
- Building a web-based editor or CMS for the method — the source remains a markdown file managed in the OS repo
- Translating the method into languages other than English
- Migrating the older standalone whitepapers (Book Database, Taxonomy System) into the method — they remain in the archive as historical artifacts
Charter Considerations
- Stewardship — The Uvilo Method is customer-facing content that directly guides how users are coached. Content accuracy and currency affect user trust and outcomes. R6 (Content Review Workflow) addresses this.
- Privacy — The method document describes systems that handle user data (persistent memory, factoids), but the document itself contains no user data. No additional requirement needed.
- Performance tracking — The release process involves automation (scripts, pandoc, weasyprint). R2 (Repeatable Release Pipeline) includes dependency verification. No additional requirement needed.