Second Brain: Alur Kerja

What It Is

The ebook bundle describes a modern second brain stack with three roles:

Component	Role	What It Should Not Become
Obsidian	Source of truth for Markdown notes, links, templates, and human-readable context	A decorative dashboard project
Hermes	AI operator for summarizing, cleaning, extracting action items, drafting decisions, and reviews	Replacement for judgment or note structure
GBrain	Retrieval and knowledge graph layer for finding relevant notes, old decisions, and patterns	Primary place to edit or store notes

The core loop is:

Capture -> Organize -> Connect -> Retrieve -> Think -> Act

The ebook’s strongest principle is simple: a second brain is not an archive. It should help turn information into decisions, action, output, and reusable understanding.

Source Material Covered

• Second-Brain-Modern.pdf
• 60-Minute-Quick-Start-Guide.pdf
• 30-Day-Second-Brain-Checklist.pdf
• Template-and-Prompt-Library.pdf
• Apple-Workflow-Pack.pdf
• VPS-Mobile-Sync-Playbook.pdf
• Hermes-Cron-Recipe-Pack.pdf
• README - START HERE.md

Core Principles

Start Small

The ebook repeatedly warns against building a beautiful system that is too heavy to use. Start with a few folders, a few templates, and a weekly review. Add complexity only when a real workflow asks for it.

Practical rule:

• If a folder, tag, template, plugin, or automation does not make capture, retrieval, review, or action easier this month, skip it.

Retrieval Beats Aesthetics

Good notes are findable. A note should have:

• A clear title.
• Context near the top.
• Structured sections.
• Links to genuinely related notes.
• Action items or follow-up when relevant.

The ebook’s point is not “make every note pretty”; it is “make future-you able to recover the right context quickly.”

Context Makes Notes Durable

Weak note:

Use option 2. Safer.

Useful note:

For the website migration project, option 2 is safer for long-term maintenance.
Option 1 is faster now, but creates more technical risk later.

Minimum context checklist:

• What is this about?
• Why does it matter?
• What project, area, source, or decision does it belong to?
• What should happen next?

Raw Notes And Processed Notes Are Different

Raw notes belong in quick capture spaces like daily notes or an inbox. Processed notes belong in project, area, resource, meeting, or decision contexts.

The ebook’s workflow is:

Capture fast. Process later. Review weekly.

The System Should Produce Action

A useful note may become:

• A decision.
• A task.
• A project update.
• A reference.
• A learning summary.
• A content outline.
• A research synthesis.

Not every note needs action, but important notes should be reviewed for action.

Recommended Vault Structure From The Ebook

The ebook recommends this beginner structure:

Inbox/
Daily Notes/
Projects/
Areas/
Resources/
Decisions/
Templates/
Archive/

Folder roles:

Folder	Purpose
Inbox	Temporary capture for unclear or unprocessed notes
Daily Notes	Daily focus, quick notes, actions, short reflection
Projects	Active outcomes with status, context, references, risks, and next actions
Areas	Long-running responsibilities without a fixed end
Resources	Reusable references, summaries, tutorials, frameworks, research
Decisions	Important decisions with context, options, rationale, risk, follow-up
Templates	Reusable note formats
Archive	Inactive or completed material that should not clutter active work

Note Types

Daily Note

Use for daily focus, quick capture, action items, and short review.

Recommended sections:

## Focus
## Quick Notes
## Action Items
## Review

Project Note

Use for active work with an outcome.

Recommended sections:

## Outcome
## Context
## Status
## References
## Decisions
## Risks
## Next Actions

Decision Note

Use for decisions that are important, hard to reverse, or likely to be revisited.

Recommended sections:

## Context
## Options
## Decision
## Rationale
## Tradeoffs
## Risks
## Follow-up

Reference Note

Use for external sources like books, videos, docs, articles, and reports.

Recommended sections:

## Source
## Summary
## Key Points
## Interpretation
## Relevance
## Related Notes

Meeting Note

Use to separate discussion, decisions, and action items.

Recommended sections:

## Details
## Agenda
## Notes
## Decisions
## Action Items
## Follow-up

Learning Note

Use when studying a topic.

Recommended sections:

## Source
## Summary
## Key Concepts
## Insights
## Open Questions
## How To Apply

Weekly Review

Use to keep the system alive.

Recommended sections:

## Summary
## Active Projects
## Decisions
## Insights
## Inbox Review
## Open Actions
## Focus Next Week

Linking Rules

The ebook’s linking model is:

• Folders answer: where does this note live?
• Tags answer: what status or broad category applies?
• Links answer: what is this note related to?

Good links have context:

This decision supports Project - Website Migration because the platform choice affects maintenance cost.

Avoid:

• Linking every repeated word.
• Creating links only to make the graph look busy.
• Using tags as a substitute for real relationships.
• Creating orphan notes with no context.

Hermes Workflow

Hermes is most useful when a prompt includes:

1. Context.
2. Source material.
3. Specific task.
4. Output format.

Use Hermes for:

• Summarizing long notes.
• Cleaning raw notes.
• Extracting action items.
• Creating decision briefs.
• Comparing notes.
• Drafting weekly or monthly reviews.
• Turning research notes into outlines.

Reusable prompt pattern:

Context:
[why this matters]
 
Source:
[paste note, path, or selected material]
 
Task:
[what to do]
 
Output format:
[sections, bullets, table, checklist]
 
Constraints:
[do not invent facts; mark unknowns as TBD]

GBrain Workflow

GBrain is the retrieval layer. Use it when keyword search is not enough or when the question is contextual.

Use GBrain for:

• Finding relevant notes by topic.
• Finding old decisions.
• Discovering relationships between topics.
• Finding recurring patterns.
• Building research context from existing notes.

Good GBrain prompt:

Find notes relevant to this topic:
[topic]
 
Group results by theme, explain why each note matters, and suggest which notes to read first.
Only use notes in the vault. If context is missing, say what is missing.

Daily And Weekly Operating System

Daily, 5-10 Minutes

• Open or create today’s daily note.
• Write the focus for the day.
• Capture quick notes into daily note or inbox.
• Mark action items.
• At the end of the day, move only important items.

Weekly, 20-30 Minutes

• Review daily notes.
• Clean inbox.
• Update active project notes.
• Extract decisions.
• Add useful links.
• Use Hermes to draft a weekly review.
• Pick 1-3 focuses for next week.

This weekly review is the heartbeat of the system. Without it, the vault becomes storage.

30-Day Implementation Roadmap

The ebook’s 30-day plan can be compressed for this vault because much of the base already exists.

Week	Ebook Focus	Adapted Focus For This Vault
Week 1	Obsidian, folders, daily note, inbox, first project note	Confirm existing PARA flow, start lightweight daily capture only if useful
Week 2	Better titles, context, decision notes, reference notes, links	Add decision capture and improve context on active project notes
Week 3	Hermes setup and prompts	Build a small prompt library note and use Hermes for weekly review/action extraction
Week 4	GBrain retrieval and system audit	Add GBrain only after notes have enough structure; audit templates before automation

Minimum useful version:

1. Keep project notes current.
2. Capture decisions.
3. Run weekly review.
4. Save the 3-5 prompts that actually get reused.
5. Add retrieval only when keyword search and wikilinks start feeling insufficient.

Sync, Mobile, VPS, And Automation

The bonus guides are conservative about sync and automation. The main warnings:

• Sync is not backup.
• Pick one source of truth.
• Mobile should mostly capture, not restructure.
• Hermes should write only to controlled locations.
• Automation must not overwrite human notes.
• Cron jobs need logs, timezone, dedupe, and backup.

Safe automation candidates:

• Daily note scaffold.
• Session archival.
• Weekly review draft.
• GBrain sync.
• Backup reminder.
• Sync health check.

Do not automate:

• Mass delete.
• Mass rename.
• Overwrite project notes.
• Move decisions without human review.

Current Vault Implementation

Observed current structure:

00 - Dashboard/
01 - Projects/
02 - Areas/
03 - Resources/
04 - Archives/
templates/

Current strengths:

• PARA is already in place.
• There is a clear dashboard and vault guide.
• There are short templates for project, meeting, reference, documentation, area, and journal notes.
• Archive rules already exist.
• The productivity area already names this vault as the second brain.
• The system already prefers short notes, searchability, wikilinks, and avoiding unnecessary folders.

Current gaps versus the ebook:

Ebook Recommendation	Current Vault	Gap
Inbox for raw capture	Not present as a top-level folder	No obvious capture queue
Daily Notes	Journal template exists, but no visible daily note folder	Daily habit is optional/undefined
Decisions	No decision template or folder	Decisions may remain buried in project/meeting notes
Learning Notes	No dedicated learning template	Learning can use Reference, but application/questions are not prompted
Weekly Review	No weekly review template	Review workflow is described but not templatized
Prompt Library	No dedicated Hermes/GBrain prompt note	Prompts may be recreated ad hoc
GBrain	Not visible in vault rules	Retrieval layer not implemented yet
Automation	Not visible	Correctly absent until manual workflow proves useful

Recommendations For This Vault

1. Do Not Rebuild The Folder Structure

The ebook recommends Inbox, Daily Notes, and Decisions, but this vault already uses PARA and explicitly says not to create new folders unless asked.

Use the current PARA system first. Add folders only if weekly review proves a recurring pain.

2. Add A Decision Template

This is the highest-value missing piece.

Store project-specific decisions near the project note. Store cross-cutting productivity/system decisions under 03 - Resources/Productivity/.

Suggested template:

title:
created:
type: resource
status: active
tags: [decision]
summary:
 
# Decision - [Title]
 
## Context
 
## Options
 
## Decision
 
## Rationale
 
## Risks
 
## Follow-up

3. Add A Weekly Review Template

This turns the vault from storage into a working system.

Suggested template:

title: Weekly Review - YYYY-MM-DD
created: YYYY-MM-DD
type: resource
status: active
tags: [weekly-review]
summary:
 
# Weekly Review - YYYY-MM-DD
 
## Summary
 
## Active Projects
 
## Decisions
 
## Open Actions
 
## Notes To Clean Up
 
## Focus Next Week

4. Create One Prompt Library Note

Do not create many prompt notes yet. One note is enough.

Sections to include:

• Summarize note.
• Extract action items.
• Clean raw note.
• Decision brief.
• Weekly review.
• Find relevant notes with GBrain.
• Find old decisions with GBrain.

5. Treat Daily Notes As Optional

The ebook pushes daily notes, but this vault is work-knowledge focused. Daily notes are useful only if you will actually review them.

Lazy version:

• Use the existing Journal.md template only on days with real capture.
• Do not create automatic daily notes yet.

6. Add GBrain Later

GBrain is useful after the vault has enough structured notes and decisions. Right now, the easiest retrieval improvements are:

• Better titles.
• More context at the top of project/resource notes.
• More wikilinks between projects, decisions, and references.

Add GBrain when search starts missing context you know exists.

7. Avoid Cron Until Review Is Manual And Stable

The ebook’s cron pack is useful, but automation should come after a working manual loop.

Safe future order:

1. Weekly review prompt.
2. Manual weekly review note.
3. Manual prompt library.
4. Optional GBrain indexing.
5. Optional automation for weekly review draft or backup reminder.

8. Add Mobile Capture Only If Needed

If mobile capture becomes important, start with one capture note rather than a folder migration.

Possible note:

03 - Resources/Productivity/Mobile Capture Inbox.md

Process it during weekly review.

Practical Next Changes

Best next three changes:

1. Add templates/Decision Note.md.
2. Add templates/Weekly Review.md.
3. Create 03 - Resources/Productivity/Second Brain Prompt Library.md.

Skip for now:

• New top-level Inbox/, Daily Notes/, or Decisions/ folders.
• VPS setup.
• Cron jobs.
• Mobile sync redesign.
• GBrain until the vault has more explicit decisions and weekly reviews.

Links

• Vault Guide
• Area Dashboard
• Project Management Workflow Guide - Kevin