USER/ layout: PascalCase-flat schema (LifeOsSchema.md) vs ALL_CAPS TELOS/ split files the tooling reads — which is intended?

[tzioup]

While setting up on a fresh install I hit a structural question I couldn't resolve from the repo, and wanted to check intent rather than assume a bug.

LifeOsSchema.md (Draft v1.0) specifies a PascalCase-flat USER/ layout — e.g. Goals.md, Wisdom.md at root, Telos/Mission.md. But the shipped install templates and the deterministic TELOS tooling (GenerateTelosSummary.ts, InterviewScan.ts, TelosFreshness.ts) create and read ALL_CAPS split files under a TELOS/ directory (MISSION.md, GOALS.md, …). I couldn't find tooling that migrates between the two shapes.

Trying to understand the intended direction:

1. Is PascalCase-flat the forward target, with the ALL_CAPS TELOS/ split files as supported legacy? If so, is a migration path planned?
2. Or has the schema doc drifted ahead of the shipping tooling, and ALL_CAPS is the de-facto current convention?

Happy to help (docs or a migration shim) if useful. Entirely possible I'm missing context.

[danielmiessler]

Direct answer: LifeOsSchema.md is a Draft that never shipped as implementation — no tooling reads the PascalCase-flat layout. The de-facto convention is the unified TELOS/TELOS.md (single file, H2 sections), which all three tools you named read first; the ALL_CAPS split files exist only as a back-compat fallback for pre-migration installs. So: option 2, with the nuance that the real target post-dates both shapes. We'll mark the schema doc as aspirational so it stops reading as current. Thanks for checking intent instead of assuming a bug — and no migration shim is needed for a fresh install (the interview writes unified TELOS.md directly).