The Second Brain PARA Method for AI-Assisted Work

The second brain PARA method organizes saved material into Projects, Areas, Resources, and Archives, according to how you expect to use it. For AI-assisted work, keep that reference structure alongside a short record of current goals, decisions, and next steps. fenbs can hold the active work record while the source files stay in your chosen notes or document app.

Start with a current project rather than reorganizing every file you own. You need to see whether the method helps you find useful evidence and resume work. A tidy archive is pleasant, but it does not tell an assistant what a person has approved.

How do you set up the four PARA categories?

Tiago Forte’s PARA explanation↗ (opens in a new tab) defines the categories around active efforts, continuing responsibilities, subjects of interest, and inactive material. Create four clearly named locations in the tool you already use. These can be folders, pages, or another simple grouping that the tool supports.

1. Create Projects for work with a specific intended result. Name each project after that result, such as “Submit the neighborhood grant proposal.”
2. Create Areas for responsibilities that continue, such as maintaining community partnerships. Describe the standard you need to maintain.
3. Create Resources for material you may reuse across several efforts, such as interview guidance or examples of grant narratives.
4. Create Archives for completed or inactive material you still need to retain. Preserve useful references when you move something out of active work.

Use one real item to test the distinction. An application checklist for the proposal belongs with that project; a general interviewing guide may belong in Resources. You can reference the guide from the project without maintaining two complete copies.

How do you tell a project from an area?

Ask what would make the work complete. “Submit an approved proposal” has an end state. “Maintain relationships with partner organizations” continues after one proposal is finished. Keeping them separate helps you see both the next deliverable and the responsibility it supports.

A single subject can appear in several categories without being a mistake. The difference is the job the information does. A current accessibility review is a project; maintaining accessible communications is an area; a useful technical guide is a resource.

If you cannot place an item quickly, ask which upcoming action needs it. Leave it in a temporary incoming location if you do not yet know. Repeated difficulty is a reason to simplify the structure rather than invent more categories.

Where should sources and reusable notes live?

Keep each substantial source in a dependable home, then link to it from the places that use it. Include a short explanation of the connection. “Use this interview guide for the consent wording” is easier to act on than a bare attachment with no context.

For a note-based setup, Obsidian supports links between notes and links to specific headings, as its internal link documentation↗ (opens in a new tab) explains. That is one implementation option. It does not mean another tool or an AI assistant can automatically open a private local file.

Save the source title, owner or author, location, and the relevant section. When material changes, note which version supported your conclusion. A new webpage may look authoritative while differing from the page that a person originally reviewed.

For tool-specific organization, use the Obsidian setup or Notion setup; the general second brain guide explains the broader concept. PARA supplies a filing approach, while those pages cover their own implementation questions.

What context should an AI read before starting?

Give the assistant a current work summary rather than asking it to infer the project from every folder. State the goal, what is already settled, which sources matter, what remains uncertain, and the next task. Specify any file that is a draft or has been replaced.

Project: Submit the neighborhood grant proposal
Goal: A reviewed application ready for submission
Current sources: Application instructions; checked interview notes
Decided: Use the approved service area definition
Open question: Confirm which partner will supply the final letter
Next action: Draft the evidence section with source references
Source archive: Keep complete documents in the existing project folder

This is the distinction between an archive and a work record. The archive preserves material; the record tells a reader what to do with it now. An AI second brain can support reusable knowledge, while an AI brain keeps the context needed to continue work.

fenbs shows agreed rules before current work context, so the assistant can read the boundaries and next step without treating a folder name as an instruction.

How do you keep PARA current as work changes?

Review Projects when work pauses or finishes. Save the outcome, what remains open, and which decisions still matter before archiving the supporting material. Make sure links used by ongoing work still lead to the correct location.

If an inactive project resumes, bring forward its relevant sources and check them again. Do not assume an earlier contact, instruction, or approval still applies. Preserve the earlier record and write down what changed so the next reader can distinguish continuity from a new decision.

For coursework, the study method explains how practice fits around saved material. In work projects, use a similarly practical test: can someone identify the current goal, the governing decision, and the next action without reading the whole archive?

How to do this with fenbs

1. Create a free account and add one active project on your kanban board. fenbs is free for one person, no credit card.
2. Add current tasks and an AI context note with the goal, source locations, and unresolved questions. Keep your PARA source structure in its existing app.
3. Record the choices people made in Decisions and rules. Identify which instructions keep applying so an assistant does not turn an old suggestion into a rule.
4. Connect a supported assistant, ask it to read context before acting, and save progress when you stop. Recheck the project summary when source files move or work resumes.

fenbs does not create or synchronize a PARA folder tree in your notes app. It is not the right fit when all you need is file organization. Use it when ongoing decisions and assistant handoffs need a clearer home, and explore related workflows in the second brain hub.