• English
      • English

      Usage

      Basic can refer to the following steps:

      1. Example Vault Selection
      2. Scenario 2
      3. Scenario 3

      After extracting the complete package, the main folders are:

      LifeOS Pro/
├── Example Vault/
│   ├── LifeOS Pro Memos Vault/
│   ├── LifeOS Pro Memos Blank Vault/
│   ├── LifeOS Pro IPO Vault/
│   ├── LifeOS Pro IPO Blank Vault/
│   ├── LifeOS Pro GTD Vault/
│   ├── LifeOS Pro GTD Blank Vault/
│   ├── LifeOS Pro PARA Vault/
│   ├── LifeOS Pro PARA Blank Vault/
│   ├── OPC LifeOS Vault/
│   └── OPC LifeOS Blank Vault/
└── Plugin/

      According to your usage scenario, select one of the scenarios, and follow the steps one by one!

      Example Vault Selection

      After extracting the complete package, enter LifeOS Pro/Example Vault/. It contains five filled examples, from easiest to hardest: LifeOS Pro Memos Vault, LifeOS Pro IPO Vault, LifeOS Pro GTD Vault, LifeOS Pro PARA Vault, and OPC LifeOS Vault. Each has a matching Blank Vault beside it for your own main vault after learning the workflow.

      Choose by the bottleneck you need to remove, not by the longest feature list:

      1. No stable daily capture habit; you only want bullets and tasks -> Memos.
      2. You want the fewest categories needed to turn sources into useful output -> IPO.
      3. Tasks are scattered; next actions and waiting-for items are unclear -> GTD.
      4. Projects, responsibilities, and reusable knowledge all need structure -> PARA.
      5. Products, customers, revenue, and delivery need one system -> OPC.

      The recommended order is Memos -> IPO -> GTD -> PARA -> OPC, from lowest to highest upkeep. It is not a mandatory migration path: start with the simplest structure that solves the current problem, or skip ahead when the need is clear.

      Templates share Markdown, periodic notes, and task syntax, but they are not one-click skins. Memos can keep every old daily note while growing into IPO, GTD, or PARA. Conversions among those three require reviewed reclassification. OPC normally starts in its Blank Vault and receives selected material. Never overwrite working settings with a Blank Vault's .lifeos/settings.json. See Upgrade from Memos.

      After installing the LifeOS Skill, an agent can run the migration. For example:

      Migrate this vault from GTD to PARA. Move only historical material that is useful now.
Show the folder and settings-field diff first. Do not overwrite settings or move files yet.

      The agent records the scope, preserves periodic notes and custom templates, merges only confirmed structural settings, and proposes destinations in bounded batches. Files stay in place when links, attachment ownership, or name collisions are unsafe. The profile manifest changes only after target entry points, task queries, and links have been checked.

      LifeOS Pro PARA Vault

      A complete CODE/PARA practice for users who already need to manage projects, ongoing responsibilities, and reusable knowledge together. Start with Memos instead when daily capture is not stable yet.

      LifeOS Pro IPO Vault

      In knowledge management, IPO typically refers to the process of Input, Processing, and Output. This model describes the entire journey of knowledge from acquisition and processing to application.

      In the IPO model:

      1. Input: This marks the starting point of knowledge management, involving the collection and acquisition of information. Input can include data, documents, research, personal experiences, external information, etc. The quality of input is crucial to the entire knowledge management process.

      2. Processing: At this stage, the input information is analyzed and refined to make it useful and applicable. Processing activities may include analysis, synthesis, evaluation, interpretation, storage, and sharing of knowledge. The goal of this phase is to transform raw data and information into valuable knowledge.

      3. Output: This is the final stage of knowledge management, where processed knowledge is applied to real-world problems to create value. Output can include decisions, solutions, new products, improved processes, training materials, etc.

      Can be simply understood as a simplified version of the CODE/PARA practice, it greatly reduces the entry threshold for beginners. Users only need to focus on input, output, and themes, and easily record, organize, and use notes.

      At the same time, you can also base this on it to design your own note system and workflow without PARA, which is a very imaginative feature!

      LifeOS Pro GTD Vault

      GTD is better for users who want the vault to answer "what is the next action?" before anything else. It keeps the project concept, but separates execution into inbox, next actions, waiting-for items, someday/maybe, reviews, and archive.

      Choose this vault when:

      1. Your day contains many small tasks, follow-ups, and delegated items.
      2. You want to stabilize the task system first, then grow the knowledge base later.
      3. You already understand the GTD Capture → Clarify → Organize → Engage → Review loop and want to use it directly in LifeOS.

      The GTD vault uses tags such as #gtd/next, #gtd/waiting, #gtd/someday, and #ctx/*. Project notes remain the source of truth; action pages aggregate what should be done or followed up now.

      OPC LifeOS Vault

      Best for one-person companies, side businesses, consulting services, or indie products. It organizes operations through a CEO dashboard, seven departments, input/output pipelines, and .AI.md pages.

      LifeOS Pro Memos Vault

      Recommended for Logseq, flomo, and usememos users. It enables periodic notes only and disables PARA and theme notes by default. The filled version demonstrates bullets, tasks, and review with two daily notes and one weekly note; the daily template stays empty while weekly-to-yearly templates keep task and record queries.

      After learning, open LifeOS Pro Memos Blank Vault as your own main vault instead of clearing the example.

      Scenario 1: Upgrade from LifeOS to LifeOS Pro

      If you have used the Basic, simply enable the new plugin in the existing repository, PRO version is compatible with all functions of the Basic:

      1. Copy the 'plugin/lifeos-pro' directory to the ' .obsidian/plugins' directory
      Warning

      .obsidian directory is a hidden folder, if you cannot see it, you need to display it through the following method

      1. MacBook: Use the shortcut key Command + Shift + .
      2. Windows: In the current folder, select "View > Show", then select "Hidden items" to view hidden files and folders

      1. Copy the existing LifeOS configuration file from ' .obsidian/plugins/periodic-para/data.json' to ' .obsidian/plugins/lifeos-pro/data.json'

      2. Find the Basic LifeOS plugin in the third-party plugin list and disable it first to avoid conflicts caused by running LifeOS and LifeOS Pro at the same time

      3. Find LifeOS Pro in the third-party plugin list and enable it

      • Open the LifeOS Pro plugin configuration page in the 'third-party plugin'

      1. Click the 'activate upgrade' panel, input the email and activation code (usually in the email you received), and click the 'upgrade now' button at the bottom to upgrade to the latest version of the plugin

      1. Restart Obsidian

      2. The left sidebar will show the 'calendar', 'home', 'file new' icons, click to experience

      3. Go to Pro Version to view more usage instructions

      Scenario 2: Use Existing Example Repository

      1. Open Obsidian, choose "Open local repository", enter the extracted LifeOS Pro/Example Vault/ folder, and use the Memos -> IPO -> GTD -> PARA -> OPC easiest-to-hardest order to open one of the five filled examples: LifeOS Pro Memos Vault, LifeOS Pro IPO Vault, LifeOS Pro GTD Vault, LifeOS Pro PARA Vault, or OPC LifeOS Vault. Remember to select "Trust repository author and enable plugins".

      2. Open the LifeOS Pro plugin configuration page in the 'third-party plugin'

      1. Restart Obsidian

      2. The left sidebar will show the 'calendar', 'home', 'file new' icons, click to experience

      3. Go to Pro Version to view more usage instructions

      After learning the workflow, do not manually erase the sample content. Open the matching LifeOS Pro Memos Blank Vault, LifeOS Pro IPO Blank Vault, LifeOS Pro GTD Blank Vault, LifeOS Pro PARA Blank Vault, or OPC LifeOS Blank Vault as your own main vault. Blank vaults do not duplicate plugin binaries; if the plugins are not installed yet, copy them from the complete package's top-level Plugin/ folder into .obsidian/plugins/.

      Scenario 3: Use LifeOS Pro in an Existing Repository

      1. Copy .obsidian/plugins/lifeos-pro from any LifeOS Pro example vault to the .obsidian/plugins directory of your existing repository
      Warning

      .obsidian directory is a hidden folder, if you cannot see it, you need to display it through the following method

      1. MacBook: Use the shortcut key Command + Shift + .
      2. Windows: In the current folder, select "View > Show", then select "Hidden items" to view hidden files and folders
      1. Find LifeOS Pro in the third-party plugin list and enable it

      1. Prefer opening the matching Blank Vault as a new main vault. If you must merge with an existing repository, copy .lifeos, templates, and the folder structure from the selected blank vault. PARA, IPO, GTD, and OPC use different structures, so choose only one instead of mixing them together.

      2. If you did not copy the full .obsidian settings, make sure the community plugins used by that example vault are installed and enabled. The GTD vault mainly relies on Tasks queries; older templates may still use Dataview or Templater.

      3. Open the LifeOS Pro plugin configuration page in the 'third-party plugin'

      1. Click the 'activate upgrade' panel, input the email and activation code (usually in the email you received), and click the 'upgrade now' button at the bottom to upgrade to the latest version of the plugin

      1. Restart Obsidian

      2. The left sidebar will show the 'calendar', 'home', 'file new' icons, click to experience

      3. Go to Pro Version to view more usage instructions

      After installation, plugin activation, and the example vault check are done, read these case studies. They are not extra setup steps. They show how to use LifeOS Pro in daily work, projects, research, and reviews.

      Next Step

      Expand the left 'knowledge base directory', continue to read the current manual!

      Reference Material

      How to Migrate to LifeOS/Obsidian

      See How to Migrate to LifeOS/Obsidian.

      Main System and Sub System of LifeOS

      See Main System and Sub System.