Free deep guide

    Graph Engineering
    for a working Second Brain.

    Connect decisions, tasks, people, projects, sources, and feedback. Then give your AI a repeatable way to recall, act, learn, and keep the system clean.

    The central idea

    A graph is the connective layer behind an operating brain.

    A folder of notes can store context. A working Second Brain knows what changed, what connects, what is uncertain, and what deserves attention next.

    work → recall context
    feedback → proposed learning
    maintenance → cleaner memory
    evaluation → proof of improvement
    Inside the guide
    01
    Design the relationship layer
    Nodes, edges, evidence, time, and confidence.
    02
    Build the operating loop
    Daily updates, tasks, decisions, and preparation.
    03
    Make learning reviewable
    Corrections, promotion, retirement, and evals.
    04
    Package automation honestly
    Recipes, providers, runtimes, and setup evidence.
    Get the full guide

    Build one operating graph.

    Free templates, schemas, examples, evaluation questions, and the Second Brain 2.1 reference map.

    The five layers

    The graph becomes useful when it runs your work.

    01

    Connected memory

    Link people, projects, decisions, commitments, sources, and feedback.

    02

    Daily operations

    See what changed, what is open, and what deserves attention today.

    03

    Evidence-gated learning

    Turn corrections into proposed updates that stay reviewable.

    04

    Task and decision truth

    Keep active work connected to the context behind it.

    05

    Honest automation

    Track what is manual, suggested, active, blocked, or unsupported.

    The Second Brain 2.1 reference architecture

    See the connection between memory and operations.

    The guide uses Second Brain 2.1 as a reference implementation. Its operating layer connects current truth, timelines, commitments, risks, decisions, action queues, feedback events, memory maintenance, and daily rituals.

    /overview and /daily-update
    /begin and /end rituals
    /correct and evidence-gated /learn
    /review-memory and weekly reports
    GitHub Issues as task truth
    Provider and automation manifests
    A useful rule

    If the brain cannot show what changed, why it changed, and what evidence supports it, call it memory maintenance. Not self-learning.

    Included

    Start with artifacts, not theory.

    01Graph Design Canvas
    02Starter Ontology Worksheet
    03Relationship and Confidence Template
    04Graph-Lite Markdown/Postgres Schema
    0510-Question Evaluation Pack
    06Second Brain 2.1 Architecture Map
    Iwo Szapar
    Why I made this

    I spent years adding more notes, skills, and prompts. The useful breakthrough was connecting what the brain knew to what I needed to do next.

    This guide turns that operating pattern into something you can inspect, adapt, and build in your own stack.

    The graph is the beginning.

    The operating layer turns connected context into daily work. See the full Second Brain approach when you are ready to go further.

    Explore Second Brain