You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Decouple identity files from their source: let PROJECTS.md / CONTACTS.md be projections of the tool you already use
#2579
The problem: two places to maintain the same facts
Most people who adopt LifeOS already keep their projects, people and research areas in a notes system, task tool or folder of markdown. LifeOS then asks for the same facts again in hand-maintained USER files: PROJECTS.md, CONTACTS.md, and the areas I work in. Within a few weeks the two copies drift apart, and the DA reasons over the copy I update less often.
Migrate solves the first day by importing once. It doesn't solve day 30, when the external system has moved on.
The idea: let LifeOS read a projection instead of holding a copy
The user's existing system stays the single source of truth, whatever it is. LifeOS gets a generated, read-only projection of it.
LifeOS already does this in one place. People treats Apple Contacts, Gmail and calendars as sources and merges them into the USER store on a schedule. This proposal extends that pattern to the other hand-maintained identity files.
A minimal shape:
A [[sources]] table in LIFEOS_CONFIG.toml. Each entry names the kind (projects, people or areas), an adapter, adapter-specific settings, and a target under LIFEOS/USER.
An adapter is a small read-only module that reads entries out of the external system. Examples: a markdown or Obsidian folder, a Logseq graph, a Notion export, a GitHub Projects board.
A renderer turns those entries into the existing target file format.
Generated files carry the existing derived_from / generator frontmatter (as PRINCIPAL_TELOS.md does), so Interview, the memory reviewer and humans know to edit the source rather than the projection.
The sync is one-way. The generated file is rewritten only when the content changes, and a scheduled or watched job keeps it current.
What I have running
I built a working prototype in my fork using one adapter: a markdown/Obsidian folder. It's in VaultSync.ts and documented in Config/VaultSync.md.
It reads note frontmatter: status, priority, aliases, path, url.
From that it generates three files:
PROJECTS.md, with an Active table, the remaining projects grouped by status, and routing aliases;
CONTACTS.md;
an areas list.
A watch job rewrites them within seconds of a note change.
After a few days of use, the DA's project routing stays current with no double entry.
The only Obsidian-specific part is the obsidian:// links. The reader works on any folder of markdown notes with YAML frontmatter. The reader and the renderers are already separate functions, but they are not yet behind a formal adapter interface. That interface is what I'm asking about below.
Questions for the maintainers
Direction. Does "the user's own system is the source of truth, LifeOS holds a projection" fit where the Life OS schema is going? Or is the intent that LifeOS itself becomes the source, with Migrate as the bridge?
Seam. If it does fit, where should it live?
(a) A generic [[sources]] + adapter contract in SYSTEM, with adapters shipped or community-provided.
(b) An extension of People's source model to projects and areas.
(c) Nothing in SYSTEM; forks and USER-side tools only.
Write path. Should the memory reviewer and Interview stay out of generated files and propose edits to the source instead, or is one-way enough?
Contribution. If (a) or (b), would a PR that adds the contract plus one markdown-folder adapter be welcome? Or would you rather design the contract on your side?
I'm not attached to Obsidian. The goal is to stop maintaining the same facts in two places, whatever tool someone already uses.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
The problem: two places to maintain the same facts
Most people who adopt LifeOS already keep their projects, people and research areas in a notes system, task tool or folder of markdown. LifeOS then asks for the same facts again in hand-maintained USER files:
PROJECTS.md,CONTACTS.md, and the areas I work in. Within a few weeks the two copies drift apart, and the DA reasons over the copy I update less often.Migratesolves the first day by importing once. It doesn't solve day 30, when the external system has moved on.The idea: let LifeOS read a projection instead of holding a copy
The user's existing system stays the single source of truth, whatever it is. LifeOS gets a generated, read-only projection of it.
LifeOS already does this in one place. People treats Apple Contacts, Gmail and calendars as sources and merges them into the USER store on a schedule. This proposal extends that pattern to the other hand-maintained identity files.
A minimal shape:
[[sources]]table inLIFEOS_CONFIG.toml. Each entry names thekind(projects, people or areas), anadapter, adapter-specific settings, and atargetunderLIFEOS/USER.derived_from/generatorfrontmatter (asPRINCIPAL_TELOS.mddoes), so Interview, the memory reviewer and humans know to edit the source rather than the projection.What I have running
I built a working prototype in my fork using one adapter: a markdown/Obsidian folder. It's in
VaultSync.tsand documented inConfig/VaultSync.md.status,priority,aliases,path,url.PROJECTS.md, with an Active table, the remaining projects grouped by status, and routing aliases;CONTACTS.md;After a few days of use, the DA's project routing stays current with no double entry.
The only Obsidian-specific part is the
obsidian://links. The reader works on any folder of markdown notes with YAML frontmatter. The reader and the renderers are already separate functions, but they are not yet behind a formal adapter interface. That interface is what I'm asking about below.Questions for the maintainers
Migrateas the bridge?[[sources]]+ adapter contract in SYSTEM, with adapters shipped or community-provided.I'm not attached to Obsidian. The goal is to stop maintaining the same facts in two places, whatever tool someone already uses.
Context
LifeOS 8.761.0 · Windows (x64) · claude-code
All reactions