#Usage

Basic can refer to the following steps:

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

Unzip the attachment, the file list is as follows

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

#Example Vault Selection

#LifeOS Pro PARA Vault

Complete CODE/PARA practice, the process is relatively complete and standardized, generally recommended to use this example repository!

#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.

#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

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

3. 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

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

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

5. 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

6. Restart Obsidian

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

8. Go to Pro Version to view more usage instructions

#Scenario 2: Use Existing Example Repository

1. Open Obsidian, follow the steps in the images, choose "Open local repository", and select Example Vault/LifeOS Pro PARA Vault, Example Vault/LifeOS Pro IPO Vault, or Example Vault/LifeOS Pro GTD Vault based on the template you chose above. Remember to select "Trust repository author and enable plugins".

   

   

   

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

3. 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

4. Restart Obsidian

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

6. Go to Pro Version to view more usage instructions

#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

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

3. Copy the folders from the selected example vault, except the .obsidian directory, into your repository. PARA, IPO, and GTD use different structures, so copy only one of them instead of mixing them together.

4. 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.

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

6. 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

7. Restart Obsidian

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

9. Go to Pro Version to view more usage instructions

#Read next after setup

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.

• A Day with Obsidian LifeOS — plan the morning, execute during the day, and close the loop
• Manage a Full Project with LifeOS Pro — use theme notes to hold project context
• A Research Workflow with Obsidian LifeOS — collect sources and turn them into output
• Make Obsidian Notes Askable with DeepAsk — connect AI after your notes are already working
• Run a Useful Weekly Review with LifeOS — bring daily notes, tasks, and projects back together

#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.