Find your starting point first, then make Priotrix last
This is not a list of articles. It is a reading entry organized around real user situations. Start by identifying where you are now, then enter through the path that fits best.
If you are new to Priotrix, begin with the understanding path. If your system already feels heavy, jump straight to the reset path.
- A path for understanding the product logic and structural boundaries.
- A path for building a minimal workable starting system.
- A path for rollback, subtraction, and long-term stability when the system gets heavy.
Which situation sounds most like you right now?
You do not need to read everything first. Pick the situation closest to where you are now, then start from that entry point.
If you only read a few pieces first, start with these six
This is not the full list. It is the highest-value entry set for understanding, starting, using, and sustaining Priotrix with the clearest path possible.
What problem Priotrix is actually solving
Best for people discovering Priotrix for the first time
Understand what problem it is actually solving.
Where to start the first time
Best for people whose first step is still unclear
Helps you decide how to begin.
How to build a minimal workable setup
Best for people who tend to overbuild too early
Helps you start with a minimal workable structure.
How to turn capture into action
Best for people who capture a lot but still lack a reliable execution loop
Helps you connect capture to action.
How to do a light and effective weekly review
Best for people already using Priotrix who want a steadier rhythm
Helps you build a lighter weekly review.
How to make Priotrix a long-term system
Best for people who want Priotrix to become a lasting system
Helps you place local practice inside a long-term method.
If you already know the problem you want to solve, follow one of these paths
Each path is organized around a real situation. You do not need to read all 18 articles from the top. Start with the one path that fits your current state.
Best for people who are new to the product and still do not know how it differs from traditional task tools.
Build the right mental model first, then move into usage and setup.
- 1What problem Priotrix is actually solving
- 2Why Priotrix is not a traditional task app
- 3Why capture, action, and projects belong in one structure
Best for people who understand the direction and now need a starting structure and a usable daily loop.
Set up the system first, then connect capture to action.
- 1Where to start the first time
- 2How to build a minimal workable setup
- 3How to turn capture into action
- 4When to use notes, items, and projects
Best for people already using Priotrix whose system is getting heavier and less trustworthy.
Step back, reduce weight, restore rhythm, and return to long-term stability.
- 1How to reset an overbuilt system
- 2How to do a light and effective weekly review
- 3How to keep the system light and stable
- 4What to check daily, weekly, and monthly
If you want the full picture, continue by category
Once the overall structure is clear, browsing all articles by category becomes much easier. This keeps the complete view available without making it the first decision you must make.
Understand what Priotrix is solving and why capture, action, and projects are organized this way.
Best for people who are new to Priotrix or want the right product boundaries first.
Start small, then learn how to reorganize when the system gets heavy or low-frequency work accumulates.
Best for people who are beginning, building structure, or stepping back from an overbuilt setup.
Connect capture to action, handle review, and make better decisions around pause, exit, and reactivation.
Best for people already using Priotrix who want clearer day-to-day judgment and execution.
Long-term sustainability comes from better review, lighter maintenance, and clearer rhythm decisions.
Best for people who already believe in the structure and want to make it last.
Priotrix is not about managing more. It is about moving important work forward more steadily
If you only look at it as a feature set, it can seem similar to many other tools. Its value becomes clearer when you understand it as a structured path from capture to progress.
These are not three isolated modules. They are one connected path. Much of the usual chaos comes from letting context, action, and progress drift apart.
The easiest mistake at the beginning is to build too much structure. A sustainable method starts small, then grows only where real use makes it necessary.
Many execution problems are not really about effort. They come from missing context. Notes, items, and projects need to work together before progress starts to feel natural.
A burst of organizing energy is easy. What matters is turning structure into habit. Guide is meant to help you keep this workable over time, not just make it feel complete at the beginning.
Ready to start with Priotrix?
If the overall model now makes sense, the recommended order is simple: read the key pieces first, then install and begin using the app. Go to Help when you need answers to specific issues.
It is easier to begin well when the product model and starting point are clear before you build anything.
Once you know what the first step should be, the download page becomes more than an install page. It becomes the next practical move.
Help is better for setup guidance, subscription questions, and practical issues after installation. It does not replace Guide.
Not the main reading path, but useful when needed
If you are only looking for download, updates, policy, or account information, use these links directly. They belong to the standard information layer, not the main Guide narrative.
Once the overall model is clear, the most relevant next pages are download and feature overview.
If you want to see what has changed and what is already public, start here.
These are standard policy and account routes. You may not need them often, but they should be easy to find when you do.