Skill: levineam/personal-ontology (version 1.0.0)

--- name: personal-ontology description: Help users build and maintain a Personal Ontology - a Palantir-style graph of Objects (identity, beliefs, predictions, goals) and Links (relationships between them) that enables AI-driven decision-making and life alignment. --- # Personal Ontology Skill A framework for organizing your life as a knowledge graph. **Objects** are the entities (beliefs, goals, projects). **Links** are the relationships between them (serves, supports, contradicts). The agent uses this graph to make decisions aligned with who you are. ## Quick Start (Example) You tell the agent: "Moltbot bootstrap personal ontology." It scans your notes, proposes candidate Objects (e.g., a Belief about AI, a Goal for health, a Project for a newsletter), and presents them for review - nothing is auto-committed. You confirm or edit those candidates. The agent then creates/updates your ontology files and links Projects → Goals → Core Self, flagging any orphans or contradictions for your decision. From that point on, the agent runs a light daily scan: it watches for new beliefs, predictions, goals, and projects, and surfaces only high-confidence candidates or conflicts so you stay aligned without extra maintenance. ## The Object Hierarchy Objects are organized from most abstract/stable to most concrete/changeable: 1. **Higher Order** - The highest organizing principle (God, universe, truth). Acknowledged, not defined. 2. **Beliefs** - Foundational assumptions about reality. What you hold to be true. *Generally unfalsifiable.* 3. **Predictions** - Your model of what will happen. *Testable, time-bound, updateable.* 4. **Core Self** - Who you are: Mission, Values, Strengths. 5. **Goals** - Time-bound objectives serving your Core Self. *Outcomes you want to achieve.* 6. **Projects** - Organized efforts toward goals. *Bounded work with beginning and end.* 7. **Tasks** - Atomic units of work. *(Live elsewhere: daily notes, Kanban, reminders.)* ## Link Types Every Object (except Higher Order) should link to other Objects. Standard link types: | Link | Meaning | Example | |------|---------|---------| | `serves` | Directly supports an outcome | "This Project **serves** Goal X" | | `supports` | Provides evidence/foundation for | "This Prediction **supports** Belief Y" | | `contradicts` | In tension with | "This Belief **contradicts** Prediction Z" | | `relates-to` | General association | "This Goal **relates-to** Value W" | | `depends-on` | Requires for completion | "Project A **depends-on** Project B" | | `evolved-from` | Updated version of | "Prediction 2.0 **evolved-from** Prediction 1.0" | **Validation rule:** Every Project must `serve` at least one Goal. Every Goal must `serve` Core Self. Orphan Objects are flagged for review. ## File Structure **Live ontology (canonical):** `[User's Notes Folder]/My_Personal_Ontology/` ``` My_Personal_Ontology/ ├── 1-higher-order.md ├── 2-beliefs.md ├── 3-predictions.md ├── 4-core-self.md ├── 5-goals.md └── 6-projects.md ``` Each file contains multiple Objects of that type, each with a `## Links` section. **Suggestions queue:** `Ontology_Suggestions.md` Use this file to capture all candidate updates (bootstrap + ongoing). --- ## For AI Agents ### Deployment Modes **Interactive Mode:** Direct conversation. User asks for help, agent references ontology for context. - "Should I take this job?" → Check against Goals, Values, Mission - "What should I work on?" → Surface high-priority Projects serving active Goals **Embedded Mode:** Agent uses ontology to inform all decisions without explicit reference. - Email triage → Prioritize based on Goals/Projects - Task suggestions → Only suggest what serves active Projects - Calendar optimization → Protect time for Goal-aligned work **Automated Mode:** Passive scanning and maintenance without user prompting. - Daily scan for new/changed Objects - Flag contradictions and orphans - Surface stale Predictions ### When to Reference the Ontology 1. **Making decisions** - Check proposed action against Values, Goals, Mission 2. **Prioritizing** - Use Goal hierarchy to rank options 3. **Explaining** - Connect tasks to higher purpose ("This serves your goal of...") 4. **Flagging misalignment** - "This task doesn't connect to any active Goal" 5. **Surfacing insights** - "Your Prediction about X has a time horizon of Q1 - any update?" ### Integration Recipes (optional) For users who want the ontology to shape daily behavior, integrate it into: - **Morning briefing**: restate Mission + top Goal + active Project, then suggest the next concrete output. - **Task sanity checks**: flag tasks that don't clearly map to a Project → Goal. - **End-of-day closure**: reflect on what served the Mission/Goals, then close the loop so the user can disconnect. - **Wind-down**: brain dump + tiny alignment cue for tomorrow. #### Adaptive prompts ("magic in the background") If higher layers are missing (Higher Order, Predictions), do **not** nag daily. Instead: - Ask **one** tiny, optional prompt at most once every N days. - Track last-asked timestamps in a small local state file (example: `memory/ontology-nudges.json`). - Only surface prompts at natural transitions (work start or wind-down), and skip on overloaded days. These can be implemented via scheduled prompts (cron) that read the ontology files + the user's task board/journal + the nudge state file. ### How to Use It ``` 1. Read Core Self first for value judgments 2. Read Goals for current priorities 3. Read Projects for tactical context 4. Read Beliefs/Predictions for worldview grounding 5. Reference explicitly when helpful ("This aligns with your mission to...") 6. Flag when something doesn't fit ``` --- ## Daily Passive Scan Agents should perform a lightweight scan of recent activity to maintain the ontology. ### What to Scan - **New notes** (last 24h) - Look for ontology-relevant content - **Modified files** (last 24h) - Check if existing Objects need updates - **Task completions** - Do they affect Project status? - **Calendar/journal** - Any events that validate/invalidate Predictions? ### Extraction Patterns When scanning, look for these signals: | Pattern | Candidate Object | |---------|------------------| | "I believe...", "I think...", "I'm convinced..." | Belief | | "I predict...", "By 20XX...", "will happen", "I expect..." | Prediction | | "My goal is...", "I want to achieve...", "I'm working toward..." | Goal | | "I'm working on...", "Project:", "I'm building..." | Project | | Mission statements, value lists, "What matters to me..." | Core Self | ### When to Act | Signal | Action | |--------|--------| | New Object candidate (high confidence) | Queue for user review | | New Object candidate (low confidence) | Note in daily memory, don't surface yet | | Existing Object contradicted | Surface immediately with evidence | | Prediction time horizon passed | Prompt for resolution | | Project completed | Prompt to update Goals | ### Contradiction Detection When new content conflicts with existing ontology: 1. Note the specific contradiction 2. Surface to user with both sides 3. Don't auto-resolve - user decides which to update 4. Track resolution in Prediction Log or Object history --- ## Intelligence Layer The ontology isn't just storage - it drives insights. Regularly surface: ### Orphan Detection - **Orphan Project** - Doesn't serve any Goal → "This project isn't connected to your goals. Is it still relevant?" - **Orphan Goal** - Doesn't connect to Core Self → "What mission/value does this goal serve?" - **Orphan Task** - Doesn't belong to any Project → "Is this task important enough to track?" ### Staleness Checks - **Stale Prediction** - Time horizon passed, no update → "Your prediction that X would happen by Q1 2026 - did it?" - **Stale Project** - No activity in 30+ days → "Is [Project] still active?" - **Stale Goal** - No serving Projects → "What's the next project for [Goal]?" ### Alignment Checks - **Task audit** - "These 5 tasks from today don't connect to any Project. Intentional?" - **Time allocation** - "You spent 80% of this week on Goal 2 but marked Goal 1 as top priority" - **Value drift** - "Your recent decisions seem to prioritize X over Y, but your values list Y first" ### Pattern Recognition - **Recurring themes** - "You've mentioned 'AI safety' in 5 notes this month. Should this be a Belief or Goal?" - **Implicit Objects** - "You act as if you believe X, but it's not in your Beliefs. Add it?" - **Prediction clusters** - "These 3 predictions are related. What's the underlying model?" --- ## Review Cadence ### Weekly (Agent-initiated) - Are current tasks serving projects? - Are projects serving goals? - Any new Objects to add from the week's notes? ### Monthly (User-prompted) - Do goals still serve Core Self? - New predictions to add? Existing ones to update? - Any completed Projects to close out? ### Quarterly (Deep review) - What surprised you? What does that reveal? - Has Core Self shifted? - Full Prediction Log review - what were you right/wrong about? --- ## Temporal Tracking Objects evolve. Track when and why: ```markdown ## History - 2026-01-28: Created - 2026-03-15: Updated based on [evidence/event] - 2026-06-01: Marked resolved/completed ``` For Predictions specifically, track: - **Created:** When you made the prediction - **Timeframe:** When you expected resolution - **Resolved:** Date + outcome (confirmed/disconfirmed/modified) - **Learning:** What the outcome revealed --- ## Setup ### How to Run Bootstrap (User-Facing) Say: **"Moltbot bootstrap personal ontology."** The agent will: 1) Scan your notes for candidate Objects 2) Present candidates for your review (no auto-commit) 3) Write/merge confirmed Objects into your ontology files **Default location (Obsidian):** `Vault v3/ontology/` (pretty-formatted, readable Markdown) ### For New Users 1. Run the bootstrap process (see `bootstrap.md`) to extract candidate Objects from existing notes 2. Review and confirm/edit candidates 3. Work through `prompts.md` to fill gaps 4. Agent begins daily passive scans ### For Existing Users 1. Copy templates to your ontology folder 2. Fill in what you know 3. Agent maintains and extends over time ### Reference Implementation See templates/ for starter files. The user's ontology will be created in their notes folder. ## Files - `SKILL.md` - This file (agent instructions) - `heuristics.md` - Rules for categorization and validation - `bootstrap.md` - Initial extraction from existing vault - `prompts.md` - Guided questions for building each layer - `templates/` - Starter files for each Object type

path: README.md
content: # Personal Ontology

**Your own Palantir — a knowledge graph of who you are.**

A framework for organizing your life as interconnected Objects (beliefs, goals, projects) and Links (relationships between them). Your AI assistant uses this graph to make decisions aligned with who you are.

## What It Does

- **Extracts** your beliefs, predictions, goals, and projects from existing notes
- **Organizes** them into a 6-layer hierarchy (Higher Order → Beliefs → Predictions → Core Self → Goals → Projects)
- **Visualizes** relationships as an interactive Mermaid graph
- **Validates** alignment (flags orphan projects, stale predictions, contradictions)
- **Integrates** into daily briefings as invisible "meaning guardrails"

## The Hierarchy

```
Layer 1: Higher Order     — What you orient toward (God, truth, universe)
Layer 2: Beliefs          — What you hold true about reality
Layer 3: Predictions      — Testable bets about the future
Layer 4: Core Self        — Mission, Values, Strengths
Layer 5: Goals            — Time-bound objectives
Layer 6: Projects         — Organized efforts toward goals
```

Every Project must serve a Goal. Every Goal must serve Core Self. Orphans get flagged.

## Quick Start

### 1. Bootstrap from existing notes
```
"Bootstrap my personal ontology"
```
The agent scans your notes, extracts candidate Objects, and presents them for review. Nothing auto-commits.

### 2. Review and confirm
For each candidate, you can:
- **Accept** — add as-is
- **Edit** — modify before adding
- **Skip** — don't add

### 3. Fill gaps manually
Work through `prompts.md` for anything the bootstrap missed.

### 4. Daily integration (optional)
Add ontology checks to your briefings:
- Morning: "What goal should I advance today?"
- Evening: "Did today's work serve my mission?"

## File Structure

After setup, your ontology lives in your notes folder:

```
My_Personal_Ontology/
├── index.md           ← Mermaid visualization + navigation
├── 1-higher-order.md  ← Transcendent orientation
├── 2-beliefs.md       ← Foundational assumptions
├── 3-predictions.md   ← Testable, time-bound bets
├── 4-core-self.md     ← Mission, Values, Strengths
├── 5-goals.md         ← Time-bound objectives
└── 6-projects.md      ← Organized efforts
```

## Link Types

| Link | Meaning |
|------|---------|
| `serves` | Directly supports an outcome |
| `supports` | Provides evidence/foundation |
| `contradicts` | In tension with |
| `depends-on` | Requires for completion |

## Visualization

The index.md includes a Mermaid diagram showing all Objects and their relationships:

```mermaid
graph TD
    subgraph "Core Self"
        M[Mission]
    end
    subgraph "Goals"
        G1[Goal 1]
        G2[Goal 2]
    end
    subgraph "Projects"
        P1[Project 1]
        P2[Project 2]
    end
    M --> G1
    M --> G2
    G1 --> P1
    G2 --> P2
```

## Agent Integration

Once your ontology exists, your AI assistant can:
- Reference it when helping you make decisions
- Flag tasks that don't serve any goal
- Surface stale predictions for review
- Detect contradictions between beliefs and actions

### Adaptive Prompts

If key layers are empty (Higher Order, Predictions), the agent will occasionally ask a single, optional question — at most once per week. No nagging.

## Requirements

- Clawdbot (or any AI agent that can read markdown)
- Obsidian (recommended) or any markdown-based notes system

## Install

```bash
clawdhub install personal-ontology
```

Or manually copy the skill folder to your Clawdbot skills directory.

## Philosophy

This isn't about productivity — it's about alignment. The goal is to ensure your daily actions connect to what actually matters to you.

A project without a goal is drift. A goal without connection to your core self is someone else's priority. This system makes those disconnects visible.

---

*"Know thyself" — now machine-readable.*


path: SETUP.md
content: # Personal Ontology — Setup

## Quick Start

### Option 1: Bootstrap from existing notes (recommended)

If you have an existing notes/journal collection:

```
"Bootstrap my personal ontology"
```

The agent will:
1. Scan your notes for beliefs, predictions, goals, and projects
2. Present candidates for your review (nothing auto-commits)
3. Create your ontology files with confirmed items

### Option 2: Start fresh

Copy the templates to your notes folder:

```
My_Personal_Ontology/
├── index.md           ← copy from templates/
├── 1-higher-order.md
├── 2-beliefs.md
├── 3-predictions.md
├── 4-core-self.md
├── 5-goals.md
└── 6-projects.md
```

Then work through `prompts.md` to fill in each layer.

---

## Configuration

By default, the agent looks for your ontology at:
- `[Your Notes Folder]/My_Personal_Ontology/`

To customize, set in your agent config or workspace:
```
ONTOLOGY_DIR=/path/to/your/ontology
```

---

## After Setup

### Daily integration (optional)

Add ontology references to your briefings:
- Read Core Self + Goals before suggesting tasks
- Flag work that doesn't map to any Project/Goal
- Occasionally prompt for missing layers (Higher Order, Predictions)

### Maintenance

The agent can run periodic checks:
- **Weekly**: Are tasks serving projects? Projects serving goals?
- **Monthly**: Any new predictions? Existing ones to update?
- **Quarterly**: Has Core Self shifted? Full review.

---

## Visualization

The `index.md` includes a Mermaid diagram. As you add Objects, update the diagram to show relationships.

For command-line rendering:
```bash
node scripts/render-ontology.js           # Output Mermaid code
node scripts/render-ontology.js --ascii   # ASCII art (requires beautiful-mermaid)
node scripts/render-ontology.js --svg out.svg  # SVG export
```

---

## Troubleshooting

**Agent can't find ontology files**
- Check the path in your config
- Ensure files exist and are readable markdown

**Bootstrap found nothing**
- Your notes may not have explicit statements
- Try the manual prompts instead

**Mermaid not rendering**
- Ensure your markdown viewer supports Mermaid (Obsidian does)
- Check syntax in the code block

---

## Next Steps

1. Complete the bootstrap or manual setup
2. Review the Mermaid visualization in `index.md`
3. Use the ontology daily — let it inform your decisions
4. Update as you learn more about yourself


path: bootstrap.md
content: # Bootstrap — Extracting Objects from Existing Notes

Instructions for agents to scan a user's vault and extract candidate ontology Objects.

---

## Overview

The bootstrap process converts unstructured notes into structured ontology Objects. It's a one-time (or periodic) deep scan that surfaces what the user already believes, predicts, and is working toward — even if they've never explicitly organized it.

**Key principle:** Always surface for user confirmation. Never auto-commit Objects to the ontology.

---

## Pre-requisites

1. Access to user's notes/vault (Obsidian, markdown files, etc.)
2. Empty or partially filled ontology folder
3. User consent to scan and extract

---

## Phase 1: Scan

### Target Locations
Prioritize these in order:
1. **Journal/daily notes** — Recent thoughts, decisions, reflections
2. **Project docs** — Active work, goals mentioned
3. **About/bio pages** — Mission, values, self-description
4. **Drafts and rough notes** — Unfiltered thinking
5. **Archived/old notes** — Historical context (lower priority)

### Extraction Patterns

#### Beliefs (generally unfalsifiable, about "what is")

```
High confidence triggers:
- "I believe..."
- "I think that..."
- "I'm convinced..."
- "It's clear to me that..."
- "The truth is..."
- "Fundamentally,..."

Medium confidence triggers:
- "Reality is..."
- "Human nature is..."
- "The world works by..."
- Lists of principles or axioms
```

**Extract as:** Statement of what is true, categorized by domain (reality, human nature, how world works, my place in it)

#### Predictions (falsifiable, time-bound)

```
High confidence triggers:
- "I predict..."
- "By [year/date]..."
- "Within [timeframe]..."
- "will happen..."
- "My bet is..."
- "I expect..."

Medium confidence triggers:
- "Probably going to..."
- "Trends suggest..."
- "It's only a matter of time..."
- "The future will..."
```

**Extract as:** What will happen + timeframe + confidence level

#### Goals (outcomes desired)

```
High confidence triggers:
- "My goal is..."
- "I want to achieve..."
- "I'm working toward..."
- "Success looks like..."
- "By [date] I want to have..."

Medium confidence triggers:
- "I should..."
- "I need to..."
- "The objective is..."
- "I'm aiming for..."
```

**Extract as:** Desired outcome + timeframe + what it serves

#### Projects (organized efforts)

```
High confidence triggers:
- "I'm working on..."
- "Project:"
- "I'm building..."
- "[Name] project"
- "Currently shipping..."

Medium confidence triggers:
- Active to-do lists with theme
- "The [X] thing I'm doing..."
- Recurring topic with tasks attached
```

**Extract as:** Project name + goal it serves + current status

#### Core Self (mission, values, strengths)

```
Mission triggers:
- "My mission is..."
- "I'm here to..."
- "My purpose is..."
- "What I want to do with my life..."

Values triggers:
- "What matters to me..."
- "I value..."
- "I prioritize..."
- "I'd sacrifice X for Y..."
- Lists of principles

Strengths triggers:
- "I'm good at..."
- "People come to me for..."
- "My superpower is..."
- "What energizes me..."
```

#### Higher Order (transcendent orientation)

```
Triggers:
- References to God, universe, meaning, truth
- "What grounds everything for me..."
- "The deepest level..."
- Philosophical or spiritual foundations
```

---

## Phase 2: Compile Candidates

**Default output:** `[User's Notes Folder]/Ontology_Suggestions.md` (or dated file: `Bootstrap Candidates — YYYY-MM-DD.md`)

Create a suggestions file organized by Object type:

```markdown
# Ontology Suggestions — [Date]

## Beliefs (X candidates)

### B1: [Statement]
- **Source:** [file/location]
- **Confidence:** High/Medium
- **Quote:** "[exact text]"
- **Suggested category:** Reality / Human Nature / World / My Place

### B2: ...

## Predictions (X candidates)

### P1: [What will happen]
- **Source:** [file/location]
- **Confidence:** High/Medium
- **Quote:** "[exact text]"
- **Timeframe:** [extracted or "unclear"]
- **Domain:** [area of prediction]

### P2: ...

## Goals (X candidates)

### G1: [Desired outcome]
- **Source:** [file/location]  
- **Confidence:** High/Medium
- **Quote:** "[exact text]"
- **Timeframe:** [if mentioned]
- **Potential links:** [what Core Self element it might serve]

### G2: ...

## Projects (X candidates)

### PJ1: [Project name]
- **Source:** [file/location]
- **Confidence:** High/Medium
- **Quote:** "[exact text]"
- **Status:** Active / Paused / Unclear
- **Potential Goal:** [what goal it might serve]

### PJ2: ...

## Core Self (X candidates)

### Mission candidates:
- ...

### Values candidates:
- ...

### Strengths candidates:
- ...

## Higher Order

### Candidates:
- ...

---

## Duplicates / Conflicts

[Note any contradictions or duplicate concepts found]

## Missing

[Note any obvious gaps — e.g., "No clear mission statement found"]

---

**Save to:** `Ontology_Suggestions.md`
```

---

## Phase 3: User Review

Present candidates to user in conversational format:

### Review Script

```
I've scanned your notes and found [N] candidate Objects for your ontology.
Let me walk through them by category.

**Beliefs** — I found [X] statements about what you hold to be true:

1. "[Statement]" — Found in [source]. Add this? [Yes / Edit / Skip]
2. ...

**Predictions** — I found [X] testable predictions:

1. "[Prediction]" by [timeframe] — Found in [source]. Add this? [Yes / Edit / Skip]
2. ...

[Continue through all categories]

**I also noticed:**
- [Contradictions found]
- [Missing elements]
- [Potential duplicates]

Would you like me to commit the confirmed Objects to your ontology?
```

### User Actions

For each candidate:
- **Yes** — Add as-is to ontology
- **Edit** — User provides corrected version, then add
- **Skip** — Don't add (too uncertain, not accurate, etc.)
- **Merge** — Combine with another candidate

---

## Phase 4: Commit

After user review:

1. Add confirmed Objects to `1 - Notes/My_Personal_Ontology/` files
2. Generate Links:
   - Connect Projects to Goals
   - Connect Goals to Core Self
   - Note any Predictions that support Beliefs
3. Add `## History` entry: "Added from Ontology_Suggestions [date]"
4. Move resolved items out of Ontology_Suggestions (or mark as processed)

---

## Output Format

Each committed Object should include:

```markdown
### [Object Name/Statement]

[Description or elaboration]

**Timeframe:** [if applicable]
**Status:** Active / Completed / Paused [if applicable]

## Links
- serves: [[Goal Name]] [for Projects]
- supports: [[Belief Name]] [for Predictions]
- relates-to: [[Other Object]] [general associations]

## History
- [Date]: Bootstrapped from [source file]
```

---

## Re-bootstrap

Run bootstrap again when:
- User has added significant new notes (months of content)
- User requests "what have I been thinking about?"
- Major life change suggests ontology review
- Annual deep review

On re-run:
- Focus on new/modified files since last bootstrap
- Cross-reference against existing ontology
- Surface only net-new candidates
- Flag potential updates to existing Objects

---

## Example Output

### Input (from user's journal):

> "I really think AI is going to change everything about work. By 2027, most knowledge workers will be using AI tools daily — that's my bet. What I care about is helping people navigate this transition, especially the meaning crisis part. I've been working on this Swarm Theory thing to articulate my worldview, and the Moltbot skills to build distribution."

### Extracted Candidates:

**Belief (High confidence):**
- "AI is going to change everything about work"
- Source: Journal entry
- Category: How the world works

**Prediction (High confidence):**
- "Most knowledge workers will use AI tools daily by 2027"
- Source: Journal entry
- Timeframe: 2027

**Core Self - Mission (Medium confidence):**
- "Helping people navigate the AI transition, especially the meaning crisis"
- Source: Journal entry

**Project (High confidence):**
- "Swarm Theory" — articulating worldview
- "Moltbot skills" — building distribution
- Source: Journal entry
- Status: Active

---

## Failure Modes

**Too aggressive:** Extracting weak signals as Objects
- Fix: Raise confidence threshold, only surface High confidence

**Too passive:** Missing obvious Objects
- Fix: Lower threshold, surface more candidates for review

**Duplicate detection failure:** Same concept extracted multiple times
- Fix: Cross-reference candidates before surfacing

**Missing context:** Object extracted without enough context to evaluate
- Fix: Include larger quote, link to source

**User fatigue:** Too many candidates to review
- Fix: Batch by category, allow "skip category" option


path: examples/demo-ontology/1-higher-order.md
content: # Higher Order

*The highest organizing principle. What you orient toward.*

---

## Orientation

**Truth / Understanding**

I orient toward understanding reality as clearly as possible. Not truth as dogma, but truth as the ongoing process of seeing things as they actually are.

This isn't something I "believe in" — it's the ground from which beliefs emerge. Everything else in my ontology serves or is measured against this orientation toward clarity and understanding.

---

## Notes

This layer is deliberately minimal. You can leave it blank or acknowledge it without defining it precisely.

Some people put: God, the universe, love, humanity, family, service, beauty.

The key is acknowledging that *something* sits above your mission — something you don't fully control or define, but orient toward.

---

## History

- 2026-01-29: Created (demo)


path: examples/demo-ontology/2-beliefs.md
content: # Beliefs

*Foundational assumptions about reality. Generally unfalsifiable.*

---

## B1 — Technology amplifies human capability
- **Status:** Active
- **Confidence:** High
- **Quote:** "Tools don't replace thinking — they extend it."

### Links
- `supports` → Core Self Mission

---

## B2 — Clear thinking is a learnable skill
- **Status:** Active
- **Confidence:** High
- **Quote:** "Most people never learn to think well because no one teaches it explicitly."

### Links
- `supports` → Core Self Mission
- `supports` → PJ1 (Weekly Newsletter)
- `supports` → PJ2 (Online Course)

---

## B3 — Small teams can have outsized impact
- **Status:** Active
- **Confidence:** High
- **Quote:** "You don't need a big company to make a big difference."

### Links
- `supports` → G2 (Create sustainable indie income)
- `supports` → PJ3 (Consulting Practice)

---

## History

- 2026-01-29: Created (demo)


path: examples/demo-ontology/3-predictions.md
content: # Predictions

*Time-bound, testable predictions about the future.*

---

## P1 — AI assistants will be mainstream by 2027
- **Status:** Active
- **Confidence:** High
- **Timeframe:** End of 2027
- **Quote:** "Most knowledge workers will use AI tools daily within 2 years."

### Links
- `supports` → PJ2 (Online Course) — course should incorporate AI thinking tools
- `tests` → B1 (Technology amplifies human capability)

### Resolution
- **Outcome:** TBD
- **Evidence:** TBD

---

## P2 — Remote work stays dominant
- **Status:** Active
- **Confidence:** Medium
- **Timeframe:** Through 2028
- **Quote:** "The office-first model won't come back for knowledge work."

### Links
- `supports` → G2 (Create sustainable indie income) — location-independent work enables consulting

### Resolution
- **Outcome:** TBD
- **Evidence:** TBD

---

## History

- 2026-01-29: Created (demo)


path: examples/demo-ontology/4-core-self.md
content: # Core Self

*Who you are: Mission, Values, Strengths.*

---

## Mission
**Help people think more clearly**
- **Confidence:** High
- **Why:** Clear thinking is the foundation of good decisions, and most people never learn how.

### Links
- `served-by` → G1 (Build audience of clear thinkers)
- `served-by` → G2 (Create sustainable indie income)
- `served-by` → PJ1 (Weekly Newsletter)
- `served-by` → PJ2 (Online Course)

---

## Values

**Honesty** — Say what you actually think, even when uncomfortable
- **Confidence:** High

**Curiosity** — Follow interesting questions wherever they lead
- **Confidence:** High

**Craft** — Do the work well, not just done
- **Confidence:** High

---

## Strengths

**Simplifying complex ideas** — Taking dense concepts and making them accessible
- **Confidence:** High

**Writing** — Clear, direct prose
- **Confidence:** Medium

**Building systems** — Creating processes that work without constant attention
- **Confidence:** Medium

---

## History

- 2026-01-29: Created (demo)


path: examples/demo-ontology/5-goals.md
content: # Goals

*Time-bound objectives serving Core Self.*

---

## G1 — Build audience of clear thinkers
- **Status:** Active
- **Confidence:** High
- **Timeframe:** 2026
- **Success looks like:** 10,000 engaged subscribers who apply clear thinking

### Links
- `serves` → Core Self Mission
- `served-by` → PJ1 (Weekly Newsletter)
- `served-by` → PJ2 (Online Course)

---

## G2 — Create sustainable indie income
- **Status:** Active
- **Confidence:** Medium
- **Timeframe:** End of 2026
- **Success looks like:** $10k/month from products + consulting

### Links
- `serves` → Core Self Mission
- `serves` → Core Self Values (Craft, independence)
- `served-by` → PJ2 (Online Course)
- `served-by` → PJ3 (Consulting Practice)

---

## History

- 2026-01-29: Created (demo)


path: examples/demo-ontology/6-projects.md
content: # Projects

*Organized efforts toward goals.*

---

## PJ1 — Weekly Newsletter
*Clear thinking essays, delivered weekly*
- **Status:** Active
- **Confidence:** High

### Links
- `serves` → G1 (Build audience of clear thinkers)
- `supported-by` → B2 (Clear thinking is learnable)

---

## PJ2 — Online Course
*"Think Better" — a cohort-based course on clear thinking*
- **Status:** Planning
- **Confidence:** Medium

### Links
- `serves` → G1 (Build audience of clear thinkers)
- `serves` → G2 (Create sustainable indie income)
- `supported-by` → P1 (AI assistants mainstream by 2027)

---

## PJ3 — Consulting Practice
*1:1 advising for founders on strategy and clear thinking*
- **Status:** Active
- **Confidence:** High

### Links
- `serves` → G2 (Create sustainable indie income)
- `supported-by` → B3 (Small teams can have outsized impact)

---

## History

- 2026-01-29: Created (demo)


path: examples/demo-ontology/index.md
content: # Personal Ontology — Demo

*Example ontology showing the structure and relationships.*

---

## Ontology Map

```mermaid
graph TD
    subgraph L1["Layer 1: Higher Order"]
        HO["Truth / Understanding"]
    end

    subgraph L2["Layer 2: Beliefs"]
        B1["Technology amplifies human capability"]
        B2["Clear thinking is a learnable skill"]
        B3["Small teams can have outsized impact"]
    end

    subgraph L3["Layer 3: Predictions"]
        P1["AI assistants mainstream by 2027"]
        P2["Remote work stays dominant"]
    end

    subgraph L4["Layer 4: Core Self"]
        M["Mission: Help people think more clearly"]
        V["Values: Honesty, Curiosity, Craft"]
        S["Strength: Simplifying complex ideas"]
    end

    subgraph L5["Layer 5: Goals"]
        G1["Build audience of clear thinkers"]
        G2["Create sustainable indie income"]
    end

    subgraph L6["Layer 6: Projects"]
        PJ1["Weekly Newsletter"]
        PJ2["Online Course"]
        PJ3["Consulting Practice"]
    end

    %% Beliefs → Core Self
    B1 --> M
    B2 --> M
    
    %% Core Self → Goals
    M --> G1
    M --> G2
    
    %% Goals → Projects
    G1 --> PJ1
    G1 --> PJ2
    G2 --> PJ2
    G2 --> PJ3
    
    %% Predictions support projects
    P1 -.-> PJ2
    B3 -.-> PJ3
```

---

## Layer Details

| Layer | File |
|------:|------|
| 1. Higher Order | [[1-higher-order]] |
| 2. Beliefs | [[2-beliefs]] |
| 3. Predictions | [[3-predictions]] |
| 4. Core Self | [[4-core-self]] |
| 5. Goals | [[5-goals]] |
| 6. Projects | [[6-projects]] |

---

*This is a demo. Your ontology will reflect your actual beliefs, goals, and projects.*


path: heuristics.md
content: # Heuristics — Object Categorization & Validation

Rules for classifying ontology Objects and ensuring graph integrity.

---

## Object Classification

### Belief vs Prediction

| Criterion | Belief | Prediction |
|-----------|--------|------------|
| **Falsifiable?** | Generally no | Yes — can be proven wrong |
| **Time horizon?** | Timeless or indefinite | Specific timeframe |
| **Evidence changes it?** | Slowly, with significant counter-evidence | Directly — outcome resolves it |
| **Format** | "X is true" / "I believe X" | "X will happen by Y" |

**Examples:**
- ✅ Belief: "AI will transform society" (directional, no specific timeline)
- ✅ Prediction: "AI agents will be mainstream by end of 2026" (testable, dated)
- ✅ Belief: "People are meaning-seeking creatures" (about human nature)
- ✅ Prediction: "Twitter will add agent integration within 6 months" (specific, falsifiable)

**Edge case:** "AI will cause job displacement" 
- As-is: Belief (vague, unfalsifiable)
- Better as Prediction: "50% of knowledge workers will use AI daily by 2027"

**Rule:** If you can imagine a specific date where you'd know if you were right or wrong, it's a Prediction.

---

### Goal vs Project vs Task

| Criterion | Goal | Project | Task |
|-----------|------|---------|------|
| **Nature** | Outcome | Effort | Action |
| **Question answered** | What do I want? | How will I get it? | What's the next step? |
| **Timeframe** | Months to years | Weeks to months | Hours to days |
| **Completion** | Achieved or not | Delivered or abandoned | Done or not done |
| **Scope** | Could have multiple projects | Has multiple tasks | Atomic |
| **Lives in** | ontology/5-goals.md | ontology/6-projects.md | Daily notes / task manager |

**Examples:**
- ✅ Goal: "Build distribution via Moltbot ecosystem"
- ✅ Project: "Ship personal-ontology skill" (serves the Goal)
- ✅ Task: "Write SKILL.md" (part of the Project)

**Edge cases:**
- "Launch newsletter" — Goal if it's the outcome you want; Project if it serves a larger Goal (like "Build audience")
- "Learn Spanish" — Goal if you want fluency; Project if it serves "Move to Spain" Goal

**Rule:** Goals are about *having* something. Projects are about *building* something. Tasks are about *doing* something.

---

### Core Self Components

| Component | Question | Changes | Example |
|-----------|----------|---------|---------|
| **Mission** | Why am I here? | Rarely (years) | "Help people find meaning" |
| **Values** | What matters most? | Slowly (major life events) | "Family first", "Intellectual honesty" |
| **Strengths** | What am I good at? | Moderately (skill development) | "Synthesizing ideas", "Clear writing" |

**Rule:** If it feels changeable month-to-month, it's probably not Core Self — it might be a Goal or current interest.

---

## Link Validation Rules

### Required Links

| Object Type | Must Link To | Link Type |
|-------------|--------------|-----------|
| Project | At least one Goal | `serves` |
| Goal | Core Self (mission, value, or strength) | `serves` |
| Prediction | Optionally a Belief | `supports` or `tests` |
| Belief | Nothing required | — |

### Orphan Detection

An Object is **orphaned** if:
- Project with no `serves → Goal` link
- Goal with no `serves → Core Self` link
- Task (in daily notes) mentioned 3+ times without Project assignment

**Agent action:** Surface orphans in weekly review. Ask user to link or archive.

### Contradiction Detection

A **contradiction** exists when:
- Two Beliefs make incompatible claims
- A Prediction contradicts a Belief
- A Goal conflicts with a stated Value
- Two Goals require mutually exclusive resource allocation

**Agent action:** Surface immediately. Present both sides. User resolves.

---

## Validation Checklist

Run periodically (weekly or on-demand):

### Structural Integrity
- [ ] Every Project has at least one `serves → Goal` link
- [ ] Every Goal has at least one `serves → Core Self` link
- [ ] No orphan Projects (linked nowhere)
- [ ] No orphan Goals (linked nowhere)

### Temporal Integrity
- [ ] All Predictions have timeframes
- [ ] No overdue Predictions without resolution
- [ ] Completed Projects marked with completion date
- [ ] Parked items have pause reason

### Content Integrity
- [ ] No duplicate Objects (same thing named differently)
- [ ] Beliefs are belief-shaped (not predictions)
- [ ] Predictions are prediction-shaped (not beliefs)
- [ ] Goals are outcomes, not activities

---

## Confidence Levels (for Bootstrap)

When extracting candidate Objects from text:

| Level | Confidence | Action |
|-------|------------|--------|
| **High** | Clear, explicit statement matching pattern | Queue for user review |
| **Medium** | Implicit or partial match | Note in candidates, ask for clarification |
| **Low** | Possible interpretation | Don't surface unless asked |

**Patterns by confidence:**

**High confidence:**
- "I believe..." / "I think that..." / "I'm convinced..."
- "I predict..." / "By [date]..." / "My bet is..."
- "My goal is..." / "I want to achieve..."
- "I'm working on [Project name]..."

**Medium confidence:**
- "It seems like..." / "Probably..."
- "I should..." / "I need to..."
- Bulleted lists of priorities or values

**Low confidence:**
- General discussion of topics
- Quotes from other sources
- Historical statements ("I used to think...")

---

## Migration Rules

### When to Upgrade an Object
- Task mentioned 5+ times → Consider promoting to Project
- Project that's really about an outcome → Promote to Goal
- Prediction that became timeless → Convert to Belief
- Goal achieved → Archive with learnings

### When to Downgrade an Object
- Goal too vague → Clarify or demote to aspiration
- Project too small → Demote to task
- Belief too specific → Convert to Prediction

### When to Archive
- Goal completed
- Prediction resolved (confirmed/disconfirmed)
- Project delivered or abandoned
- Belief no longer held

---

## Object Naming Conventions

- **Goals:** Verb-noun phrase ("Build distribution", "Publish book")
- **Projects:** Specific deliverable ("personal-ontology skill", "Newsletter Q1")
- **Beliefs:** Statement form ("AI will transform work")
- **Predictions:** Dated statement ("AI agents mainstream by 2026")

Keep names short. Details go in description.


path: prompts.md
content: # Personal Ontology — Guided Prompts

Work through these from top to bottom. Take your time. The upper layers inform everything below.

---

## 1. Higher Order / Power

*What sits at the apex of your worldview? This isn't something you define so much as acknowledge.*

- What do you orient toward? God? The universe? Truth? Humanity? Something else?
- If you had to name the "ground" from which everything else derives meaning, what would it be?
- You can leave this implicit if that feels right. Just acknowledge it exists.

---

## 2. Beliefs

*What do you hold to be true about reality? These are foundational assumptions, not opinions.*

- What do you believe about the nature of reality?
- What do you believe about human nature?
- What do you believe about how the world works?
- What do you believe about your place in it?
- What beliefs shape what seems possible, valuable, or worth pursuing for you?

---

## 3. Predictions

*What do you expect to happen? These are testable — you'll find out if you're right.*

- What trends do you see continuing? Reversing?
- What do you expect to happen in your domains of interest over the next 1, 5, 10 years?
- What would genuinely surprise you? (And what would that surprise reveal about your model?)
- What are you betting on — with your time, money, or attention?

---

## 4. Core Self

### Mission / Purpose
- Why are you here? What's your enduring reason for being?
- What contribution do you want to make?
- If you succeeded completely, what would be different in the world?

### Values
- What matters most to you?
- What would you sacrifice for?
- What qualities do you want to embody?
- When you make hard decisions, what principles do you fall back on?

### Strengths
- What are you genuinely good at?
- What energizes you rather than drains you?
- What do people come to you for?
- What capabilities can you deploy in service of your mission?

---

## 5. Goals

*Time-bound objectives that serve your Core Self.*

- What concrete outcomes are you working toward?
- How do these connect to your mission?
- What would "done" look like?
- What's the timeframe?

---

## 6. Projects

*Organized efforts toward goals.*

- What projects are currently active?
- Which goal does each project serve?
- What's the scope and expected end state?

---

## Review Questions

### Weekly
- Are my current tasks actually serving my projects?
- Are my projects moving toward my goals?

### Monthly
- Do my goals still serve my Core Self?
- Any new predictions to add? Any to update?

### Quarterly
- What surprised me this quarter?
- What does that reveal about my beliefs or predictions?
- Has my Core Self shifted? (Mission, values, strengths)


path: scripts/render-ontology.js
content: #!/usr/bin/env node
/**
 * Render Personal Ontology as Mermaid diagram
 * 
 * Usage: node render-ontology.js [--ascii] [--svg output.svg]
 * 
 * Reads ontology files from the configured location and generates
 * a Mermaid graph visualization.
 */

const fs = require('fs');
const path = require('path');

// Default ontology location - customize via ONTOLOGY_DIR env var
const ONTOLOGY_DIR = process.env.ONTOLOGY_DIR || 
  path.join(process.cwd(), 'My_Personal_Ontology');

// Parse ontology files and extract objects + links
function parseOntologyFiles() {
  const objects = [];
  const links = [];
  
  const files = [
    '1-higher-order.md',
    '2-beliefs.md', 
    '3-predictions.md',
    '4-core-self.md',
    '5-goals.md',
    '6-projects.md'
  ];
  
  for (const file of files) {
    const filePath = path.join(ONTOLOGY_DIR, file);
    if (!fs.existsSync(filePath)) continue;
    
    const content = fs.readFileSync(filePath, 'utf-8');
    const type = file.replace(/^\d+-/, '').replace('.md', '');
    
    // Extract objects (## headers with IDs)
    const objectRegex = /^## ([A-Z0-9]+) — (.+)$/gm;
    let match;
    while ((match = objectRegex.exec(content)) !== null) {
      objects.push({
        id: match[1],
        name: match[2].substring(0, 30) + (match[2].length > 30 ? '...' : ''),
        type: type
      });
    }
    
    // Extract links from ### Links sections
    const linkRegex = /`(serves|supports|contradicts|relates-to|depends-on|served-by|supported-by)`\s*→\s*(?:\[\[#)?([A-Z0-9]+)?/gm;
    let currentObject = null;
    const lines = content.split('\n');
    
    for (let i = 0; i < lines.length; i++) {
      const line = lines[i];
      const objMatch = line.match(/^## ([A-Z0-9]+) — /);
      if (objMatch) {
        currentObject = objMatch[1];
      }
      
      if (currentObject) {
        const linkMatch = line.match(/`(serves|supports|contradicts|relates-to|depends-on|served-by|supported-by)`\s*→\s*(?:\[\[#)?([A-Z0-9]+)?/);
        if (linkMatch) {
          const linkType = linkMatch[1];
          const target = linkMatch[2];
          if (target) {
            // Normalize link direction
            if (linkType === 'served-by' || linkType === 'supported-by') {
              links.push({ from: target, to: currentObject, type: linkType.replace('-by', '') });
            } else {
              links.push({ from: currentObject, to: target, type: linkType });
            }
          }
        }
      }
    }
  }
  
  // Add Core Self as a special node
  objects.push({ id: 'CORE', name: 'Core Self (Mission)', type: 'core-self' });
  
  return { objects, links };
}

// Generate Mermaid syntax
function generateMermaid(objects, links) {
  const lines = ['graph TD'];
  
  // Define node styles by type
  const typeStyles = {
    'higher-order': ':::higherOrder',
    'beliefs': ':::belief',
    'predictions': ':::prediction',
    'core-self': ':::coreSelf',
    'goals': ':::goal',
    'projects': ':::project'
  };
  
  // Add subgraphs by type
  const byType = {};
  for (const obj of objects) {
    if (!byType[obj.type]) byType[obj.type] = [];
    byType[obj.type].push(obj);
  }
  
  // Add nodes
  for (const obj of objects) {
    const shape = obj.type === 'core-self' ? `((${obj.name}))` : `[${obj.name}]`;
    lines.push(`    ${obj.id}${shape}`);
  }
  
  lines.push('');
  
  // Add links
  for (const link of links) {
    const arrow = link.type === 'contradicts' ? '-.->|contradicts|' : 
                  link.type === 'supports' ? '-->|supports|' :
                  link.type === 'serves' ? '-->|serves|' :
                  '-->';
    lines.push(`    ${link.from} ${arrow} ${link.to}`);
  }
  
  // Add style definitions
  lines.push('');
  lines.push('    classDef coreSelf fill:#f9f,stroke:#333,stroke-width:2px');
  lines.push('    classDef belief fill:#bbf,stroke:#333');
  lines.push('    classDef goal fill:#bfb,stroke:#333');
  lines.push('    classDef project fill:#fbb,stroke:#333');
  
  return lines.join('\n');
}

// Main execution
async function main() {
  const args = process.argv.slice(2);
  const useAscii = args.includes('--ascii');
  const svgIndex = args.indexOf('--svg');
  const svgOutput = svgIndex !== -1 ? args[svgIndex + 1] : null;
  
  const { objects, links } = parseOntologyFiles();
  const mermaidCode = generateMermaid(objects, links);
  
  if (useAscii) {
    try {
      const { renderMermaidAscii } = require('beautiful-mermaid');
      const ascii = renderMermaidAscii(mermaidCode);
      console.log(ascii);
    } catch (e) {
      console.log('ASCII rendering requires beautiful-mermaid');
      console.log('\nMermaid code:\n');
      console.log(mermaidCode);
    }
  } else if (svgOutput) {
    try {
      const { renderMermaid, THEMES } = require('beautiful-mermaid');
      const svg = await renderMermaid(mermaidCode, THEMES['tokyo-night']);
      fs.writeFileSync(svgOutput, svg);
      console.log(`SVG written to ${svgOutput}`);
    } catch (e) {
      console.error('SVG rendering failed:', e.message);
      console.log('\nMermaid code:\n');
      console.log(mermaidCode);
    }
  } else {
    // Just output the Mermaid code
    console.log(mermaidCode);
  }
}

main().catch(console.error);


path: templates/1-higher-order.md
content: # Higher Order / Power

*The highest organizing principle of your life. This isn't something you define so much as acknowledge — it's the ground from which everything else derives meaning.*

---

## My Higher Order

[What do you orient toward? God? The universe? Truth? Humanity? Nature? Something else? You can leave this implicit if that feels right — just acknowledge it exists.]

---

## Notes

[How did you arrive at this? What does it mean for how you live?]

---

## Links

*Higher Order typically doesn't link to other Objects — other Objects link up to it.*

---

## History

- [Date]: Created


path: templates/2-beliefs.md
content: # Beliefs

*What you hold to be true about reality, human nature, how the world works, and your place in it. These are foundational assumptions — generally unfalsifiable, slowly-changing.*

---

## About Reality

- [What do you believe about the nature of existence?]

## About Human Nature

- [What do you believe about people?]

## About How the World Works

- [What do you believe about systems, society, change?]

## About My Place In It

- [What do you believe about your role and potential?]

---

## Links

*Beliefs ground everything else. Link from Predictions that support or test specific Beliefs.*

| Object | Link Type | Notes |
|--------|-----------|-------|
| | supports / contradicts | |

---

## History

- [Date]: Created


path: templates/3-predictions.md
content: # Predictions

*Your model of what will happen. Testable, time-bound, updateable. Where your worldview meets reality and gets feedback.*

---

## Short-term (< 1 year)

### [Prediction Name]
- **Statement:** [What will happen]
- **Timeframe:** [By when]
- **Confidence:** High / Medium / Low
- **What would prove me wrong:** [Falsification criteria]

## Medium-term (1-5 years)

### [Prediction Name]
- **Statement:** 
- **Timeframe:** 
- **Confidence:** 
- **What would prove me wrong:** 

## Long-term (5+ years)

### [Prediction Name]
- **Statement:** 
- **Timeframe:** 
- **Confidence:** 
- **What would prove me wrong:** 

---

## What Would Surprise Me

*Inversions of your model. If these happened, what would it reveal?*

- 

---

## Prediction Log

| Date | Prediction | Timeframe | Outcome | What I Learned |
|------|------------|-----------|---------|----------------|
| | | | Confirmed / Disconfirmed / Modified | |

---

## Links

| Prediction | Link Type | Target | Notes |
|------------|-----------|--------|-------|
| [Name] | supports | [[Belief]] | This prediction tests whether [Belief] is true |
| [Name] | contradicts | [[Belief]] | If true, challenges [Belief] |
| [Name] | relates-to | [[Goal]] | Outcome affects my [Goal] |

---

## History

- [Date]: Created


path: templates/4-core-self.md
content: # Core Self

*The heart of the system. Who am I?*

---

## Mission / Purpose

*What you're here to do. Your enduring reason for being.*

[What contribution do you want to make? If you succeeded completely, what would be different?]

---

## Values

*What matters to you. The principles you prioritize when making decisions.*

1. **[Value]** — [Why / what it means in practice]
2. **[Value]** — 
3. **[Value]** — 
4. **[Value]** — 
5. **[Value]** — 

---

## Strengths

*What you're good at and energized by. Capabilities you deploy in service of your mission.*

1. **[Strength]** — [How you use it]
2. **[Strength]** — 
3. **[Strength]** — 
4. **[Strength]** — 
5. **[Strength]** — 

---

## The Synthesis

*How Mission, Values, and Strengths combine into your unique contribution.*

[Your values tell you what's worth doing. Your strengths tell you how you can uniquely contribute. Your mission is the synthesis — the specific way YOU will create value given who you are.]

---

## Links

| Component | Link Type | Target | Notes |
|-----------|-----------|--------|-------|
| Mission | serves | [[Higher Order]] | Grounded in [orientation] |
| Mission | relates-to | [[Belief]] | Built on belief that [X] |
| Value: [X] | informs | [[Goal]] | This value drives [Goal] |
| Strength: [Y] | enables | [[Project]] | I use this in [Project] |

---

## History

- [Date]: Created


path: templates/5-goals.md
content: # Goals

*Time-bound objectives that serve your Core Self. Concrete enough to achieve, specific enough to measure, but connected upward to your mission.*

*A goal without connection to your Core Self is just busyness. A Core Self without goals is just aspiration.*

---

## Active Goals

### Goal 1: [Name]
- **Description:** [What outcome you want]
- **Timeframe:** [By when]
- **Success looks like:** [How you'll know you've achieved it]

#### Links
| Link Type | Target | Notes |
|-----------|--------|-------|
| serves | [[Core Self#Mission]] | How this serves your mission |
| serves | [[Core Self#Values]] | Which value(s) this honors |
| enabled-by | [[Core Self#Strengths]] | What strength you're deploying |

#### Projects
- [[Project 1]] — [status]
- [[Project 2]] — [status]

---

### Goal 2: [Name]
- **Description:** 
- **Timeframe:** 
- **Success looks like:** 

#### Links
| Link Type | Target | Notes |
|-----------|--------|-------|
| serves | | |

#### Projects
- 

---

### Goal 3: [Name]
- **Description:** 
- **Timeframe:** 
- **Success looks like:** 

#### Links
| Link Type | Target | Notes |
|-----------|--------|-------|
| serves | | |

#### Projects
- 

---

## Completed Goals

| Goal | Completed | Outcome | What I Learned |
|------|-----------|---------|----------------|
| | | | |

---

## Parked Goals

*Goals you've considered but aren't pursuing now.*

| Goal | Parked | Reason | Reactivate If |
|------|--------|--------|---------------|
| | | | |

---

## History

- [Date]: Created


path: templates/6-projects.md
content: # Projects

*Organized efforts toward goals. Each project has a beginning and end, a defined scope, and requires multiple tasks to complete.*

*Projects are how goals get operationalized.*

---

## Active Projects

### [Project Name]
- **Scope:** [What you're building/delivering]
- **Status:** Active / In Progress / Blocked
- **Next milestone:** [Immediate target]
- **Key tasks:** [Link to task list or bullet key items]

#### Links
| Link Type | Target | Notes |
|-----------|--------|-------|
| serves | [[5-goals#Goal Name]] | This project directly advances [Goal] |
| depends-on | [[Other Project]] | Blocked until [X] |
| relates-to | [[Belief/Prediction]] | Informed by [worldview element] |

---

### [Project Name]
- **Scope:** 
- **Status:** 
- **Next milestone:** 
- **Key tasks:** 

#### Links
| Link Type | Target | Notes |
|-----------|--------|-------|
| serves | | |

---

## Completed Projects

| Project | Goal | Completed | Outcome | Learnings |
|---------|------|-----------|---------|-----------|
| | | | | |

---

## Paused Projects

| Project | Goal | Paused | Reason | Reactivate If |
|---------|------|--------|--------|---------------|
| | | | | |

---

## Notes

*Tasks are the atomic units of work. They don't live here — they live in daily notes, Kanban boards, or task managers. Tasks are where intention meets reality.*

---

## History

- [Date]: Created


path: templates/index.md
content: # Personal Ontology

*A compact map of what matters — your "meaning guardrails."*

---

## Ontology Map

```mermaid
graph TD
    subgraph L1["Layer 1: Higher Order"]
        HO["? - not yet articulated"]
    end

    subgraph L2["Layer 2: Beliefs"]
        B1["(add your beliefs)"]
    end

    subgraph L3["Layer 3: Predictions"]
        PR["(add your predictions)"]
    end

    subgraph L4["Layer 4: Core Self"]
        M["Mission: (your mission)"]
        V["Values: (your values)"]
        S["Strength: (your strengths)"]
    end

    subgraph L5["Layer 5: Goals"]
        G1["(add your goals)"]
    end

    subgraph L6["Layer 6: Projects"]
        PJ1["(add your projects)"]
    end

    %% Connect as you build out your ontology
    %% B1 --> M
    %% M --> G1
    %% G1 --> PJ1

    %% Style placeholders as dim
    classDef empty fill:#444,stroke:#666,color:#999
    class HO,PR,B1,G1,PJ1 empty
```

*Update this diagram as you add Objects. Connect them with arrows to show relationships.*

---

## Layer Details

| Layer | File |
|------:|------|
| 1. Higher Order | [[1-higher-order]] |
| 2. Beliefs | [[2-beliefs]] |
| 3. Predictions | [[3-predictions]] |
| 4. Core Self | [[4-core-self]] |
| 5. Goals | [[5-goals]] |
| 6. Projects | [[6-projects]] |

---

## Getting Started

1. Work through the layers top-to-bottom using the prompts
2. Or run a bootstrap scan on your existing notes
3. Update the Mermaid diagram above as you add Objects
4. Every Project should connect to a Goal; every Goal to Core Self

---

## Related

- [[Ontology_Suggestions]] — Candidates waiting for review

---

*Created: [date]*


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal:  | SkillSpector: suspicious (HIGH)