Decisions
User Tasks
Summary
Connect Opus to the Atlas personal vault (Tempus, Orbis, Actus, Mentis) for personal life management features.
Problem / Motivation
Personal data (calendar, tasks, projects, knowledge) lives in a separate Atlas vault.
This includes personal projects and goals like language learning, music instruments,
courses, egg freezing, and other life pursuits tracked in Actus/Orbis.
Opus needs access to this data for briefings, task management, and personal assistant
features — but should not own or restructure it.
Proposed Solution
A read/write bridge between Opus and Atlas. Opus treats Atlas as an external data
source with its own conventions.
Atlas Vault — “My Life Lab”
Path: C:\Users\marij\Vaults\My Life Lab
Section Structure Opus Integration 0. Inbox new/ Shared capture pipeline 1. Tempus Templates, Past, Now, Future Daily briefings, scheduling 2. Actus Tasks, Projects, Workflows, Trackers, Intentions, Practices, Lifestyles, Traditions Task sync, action items, project status 3. Orbis Health, Social, Work, Growth, Adventures, Systems Life area dashboards in briefings 4. Mentis Database, Ideas, Notes, References, Resources Knowledge bridge with vault/20_knowledge/
Implementation : Consider using the Filesystem MCP server to access the personal Obsidian vault outside the project directory.
Open Questions
⇒
No open questions.
Phase Overview
Phase Description Status Phase 1 Configuration — Phase 2 Read Integration — Phase 3 Write Integration —
Phase 1: Configuration —
Goal: Define how Opus accesses Atlas vault and document conventions.
File / Feature Details Owner Status Atlas vault path config Define Atlas vault path in Opus config opus — Vault bridge config Create config for which Atlas sections Opus can access opus — Read-only access Read-only access first opus — Atlas conventions doc Document Atlas folder structure, naming conventions, and integration rules so Opus respects them opus —
Phase 2: Read Integration —
Goal: Pull data from Atlas into Opus for briefings and overviews.
File / Feature Details Owner Status Calendar pull Daily briefings pull calendar from Tempus opus — Project status Status overview includes active projects from Orbis opus — Task overview Briefing includes open tasks from Actus opus — Personal goals Surface personal projects (courses, language, music, health) from Actus/Orbis opus —
Phase 3: Write Integration —
Goal: Enable Opus to create and update entries in Atlas.
File / Feature Details Owner Status Create tasks Opus can create tasks in Actus opus — Calendar entries Opus can add calendar entries to Tempus opus — File knowledge Opus can file knowledge in Mentis opus — Two-way sync Two-way sync for shared concepts opus —
Prerequisites / Gap Analysis
Requirements
Requirement Description REQ-1 Opus can read Atlas data without modifying its structure REQ-2 Daily briefing includes Atlas calendar and task data REQ-3 Atlas vault continues to work independently in Obsidian
Current State
Component Status Details Atlas vault done Exists at C:\Users\marij\Vaults\My Life Lab VPS access — FR-019 needed for always-on access Daily briefings — FR-003 as consumer
Gap (What’s missing?)
Gap Effort Blocker? Vault bridge config Med No Filesystem MCP server setup Low No
Test
Manual tests
Test Expected Actual Last Read Atlas calendar from Tempus Returns upcoming events pending - Read open tasks from Actus Returns task list pending - Atlas vault unchanged after read No modifications to Atlas files pending -
AI-verified tests
Scenario Expected behavior Verification method … … …
E2E tests
Integration tests
Unit tests
Component Tests Coverage … … …
History
Date Event Details 2026-02-26 Created Created from brain dump 2026-02-27 Renumbered From FR-048 to FR-025 2026-02-28 Rewritten Aligned to feature-request template
References
Atlas is the personal vault; Opus is the technical vault. Keep separation clean.
Original “Personal Vault” FR (old FR-028) was deleted and superseded by this — Atlas IS the personal vault.
Depends on: FR-019 (VPS, for always-on access)