💡 Life OS: A Vision for PAI as Your Personal AI Operating System

[mellanon]

Your Personal AI Operating System

"You stay focused. The layers handle the noise."

---

The Problem

Modern life drowns us in noise:

Domain	The Noise
💬 Communication	Emails, Slack, WhatsApp, calls, video conferences, notifications
💼 Work	Context switching, multiple projects, colleagues, deadlines
🏠 Life Admin	Vehicle maintenance, insurance, subscriptions, documents
🧠 Knowledge	Ideas captured but lost, conversations forgotten, learning that fades

Result: Important things get missed. Context is lost. Promises slip through. Your brain wasn't designed for this volume.

---

The Vision

Life OS puts four operational domains between you and the chaos, guided by a strategic layer that keeps you aligned with who you're becoming.

Each operational domain answers a fundamental question. The strategic layer keeps you aligned. Identity and Legacy aren't stored—they're derived from the digital trail you leave as you operate.

"This is more than productivity. It's about helping us be the best version of ourselves."

---

🧱 The Foundation: Markdown + Tags + Interoperability

Life OS is built on the same foundation as the Knowledge Domain:

Plain Text Forever

• Everything lives in Markdown files with YAML frontmatter
• No vendor lock-in, no proprietary databases
• Your data is yours—readable in any editor, forever

Tags Are the API

• Multi-dimensional taxonomy encodes metadata
• Enables queries, analytics, and AI assistance
• Works across all five domains

Tool Interoperability

• Telegram as universal capture gateway
• Obsidian for rich interaction
• Git for version control
• PAI for AI assistance
• Swap any tool without losing data

---

🧭 The Strategic Layer

Above the operational domains sits a strategic layer—three cross-cutting concerns that span everything you do. These aren't separate systems; they're lenses through which all activity flows.

🎯 Aspiration: "Who am I becoming?" (Direction)

The compass that gives meaning to everything else.

What It Holds	Examples
Goals	"Launch my product by Q2"
Values	"Family first", "Deep work over shallow"
Vision	"Financial independence by 50"

Why Aspiration matters: It tells you which awareness matters, which attention to prioritize, which commitments to make, and which knowledge to cultivate.

🪞 Identity: "What makes me me?" (Present)

Derived from your digital trail, not stored explicitly. Your patterns reveal who you are:

Source	What It Reveals
Writing style	How you express ideas—voice memos, notes, messages
Tag choices	How you categorize and organize
Connection patterns	How you link concepts together
Recurring frameworks	Your mental models for analysis
Meeting transcripts	How you communicate and collaborate
Decisions over time	Your values in action

Identity enables:

• Style consistency — System knows your voice, applies it
• Framework application — Analyze through your lens
• Bias recognition — Surface your assumptions
• Growth challenges — "Have you considered the opposite view?"

Identity isn't decoration—it's how your AI becomes yours. As PAI puts it: "Your AI, knowing how you work, learning from your patterns, serving your goals."

🏛️ Legacy: "What trail am I leaving?" (Proof)

Derived from your operational outputs—the receipts of your journey:

Domain	What Becomes Legacy
📋 Commitment	Delivered work → status reports, CV, portfolio
🧠 Knowledge	Cultivated notes → evolved documents, frameworks
All domains	Activity history → the archive of your journey

Legacy outputs (when appropriate):

• Expanded and refined notes and documents
• Blog posts, articles, presentations
• Talks, workshops, videos
• Portfolio items and case studies

Not every cultivation session becomes a blog post. Sometimes you're simply expanding existing notes, refining frameworks, or evolving your thinking. All of this IS the trail—the digital footprint you leave as you honor your commitments and aspirations.

Legacy answers: "What have I actually done?" It keeps you honest, helps you course-correct, and creates proof of your intellectual journey.

This aligns with PAI Principle 12 (Custom History System): "Memory makes intelligence compound. Without history, every session starts from zero."

---

⚙️ The Operational Domains

🚨 Awareness: "What's happening?"

Monitors signals from your world—work and personal.

Scope	What It Monitors
💼 Work	Dashboards, system alerts, project status, deadlines approaching
🏠 Home	Security cameras, water tank levels, power consumption
🚗 Vehicles	WOF due, service reminders, insurance renewals
🧠 Vault	Inbox age, orphan notes, cultivation cadence

Predictions: "At current usage, water runs out in 4 weeks" / "You haven't cultivated in 3 weeks"

📥 Attention: "Who needs me?"

Your AI gatekeeper screens all inbound—work and personal. Attention is how you get notified.

Telegram as Control Plane: Just like Knowledge uses Telegram for ingestion, Attention uses Telegram for notification delivery. One interoperable channel, event-driven, with filters you control.

Priority	Who/What	Treatment
⭐ VIP	Family, boss, key clients	Always notify immediately
🔴 Urgent	Deadlines today, emergencies	Notify within minutes
🟡 Important	Requires response	Batch hourly
🟢 Normal	FYI, general updates	Daily digest
⚪ Low	Newsletters, promotions	Weekly or ignore

Event Sources: Emails, phone calls, monitoring alerts, calendar reminders (from Commitment), system notifications—all flow through the Attention filter before reaching you.

Focus Modes: Deep Work, Personal, Sleep—like your iPhone's Focus modes, but for your entire digital life.

📋 Commitment: "What do I owe?"

Tracks everything you've committed to—work and personal.

Scope	What It Tracks
💼 Work	Meetings, sprint deliverables, client deadlines
🏠 Personal	Family events, life admin, promises to friends
🧠 Self	Cultivation sessions, review cadence, learning goals

Promise Tracking: "I'll send that by Monday" → tracked automatically.

Capacity: All calendars unified. Conflicts detected. "You're overcommitted this week."

🧠 Knowledge: "What do I know?"

Your second brain—everything captured, processed, searchable.

Layer	What It Does
Capture	Zero-friction input via Telegram
Store	Organized by actionability (PARA)
Connect	Ideas link and compound (Zettelkasten + AI)
Create	New insights emerge from connections

The CONNECT layer is where knowledge compounds. Without it, you have a filing cabinet. With it, you have a thinking partner.

---

🔄 How Domains Connect

The domains don't operate in isolation—they flow into each other:

Key distinction:

• Awareness = What's happening (monitors state, detects changes)
• Attention = How you get notified (filters, priorities, delivery)

Example Flow:

1. Awareness detects: "47 notes older than 7 days in inbox"
2. Attention surfaces: "Your vault needs you"
3. Commitment schedules: "Cultivation session - Saturday 9am"
4. Knowledge grows: Session produces synthesized insights
5. Aspiration served: Insights compound toward your goals

---

🔄 The Meta Loop: Systems That Improve Themselves

Life OS doesn't just manage your life—it improves how it manages your life.

This aligns with three PAI principles working together:

Principle	What It Means	Life OS Application
P7: ENG/SRE	Treat systems as infrastructure	Git-tracked configs, version-controlled domains
P10: Meta/Self-Update	Systems should improve themselves	Practices become automation
P12: Custom History	Memory makes intelligence compound	Session history becomes source material

The Loop:

    ┌─────────────────────────────────────────────────────────────┐
    │                                                             │
    │   📝 Manual Practice                                        │
    │      (operating Life OS daily)                              │
    │              │                                              │
    │              ▼ capture patterns                             │
    │   📋 Documented Workflow                                    │
    │      (how you use each domain)                              │
    │              │                                              │
    │              ▼ SpecFirst methodology                        │
    │   📐 OpenSpec                                               │
    │      (requirements for automation)                          │
    │              │                                              │
    │              ▼ implementation                               │
    │   🤖 PAI Skills                                             │
    │      (automated assistance)                                 │
    │              │                                              │
    │              ▼ dogfooding                                   │
    │   ✨ Better Manual Practice ───────────────────────┐        │
    │                                                    │        │
    │              ◀────────────────────────────────────┘        │
    │                     continuous improvement                  │
    └─────────────────────────────────────────────────────────────┘

Real Example: The SpecFirst + Jira skills were built in 4 hours by:

1. Ingesting research into Knowledge Domain
2. Loading context with obs search
3. Building with PAI + Claude Code
4. Validating methodology while building

The Knowledge Domain enabled rapid development. The same pattern applies to all domains.

---

🏗️ Built on PAI

Life OS extends Personal AI Infrastructure (PAI)—the open-source foundation from Daniel Miessler.

Why PAI's Principles Matter

PAI Principle	Life OS Application
Scaffolding > Model	The five domains ARE the scaffolding
CLI-First	Each domain gets deterministic tools
Unix Philosophy	Small tools compose into pipelines
Code Before Prompts	Processing pipelines are testable code
Skills as Containers	Each domain becomes a self-contained skill
Spec / Test / Evals First	SpecFirst methodology for domain development

Current Implementation Status

Domain	PAI Skill	Status
🧠 Knowledge	Context Skill (ingest, obs)	✅ Built
📋 Commitment	Jira Skill (work commitments)	🟡 Partial
🎯 Aspiration	(To be designed)	🔲 Planned
🚨 Awareness	(To be designed)	🔲 Planned
📥 Attention	(To be designed)	🔲 Planned

The Pattern: Capture → Process → Store → Retrieve

Every domain follows this pattern:

Domain	Capture	Process	Store	Retrieve
🧠 Knowledge	Notes, voice, docs	Transcribe, tag, embed	Vault	"What do I know about X?"
📥 Attention	All messages	AI triage, priority	Inbox	"What needs me?"
📋 Commitment	Calendars, tasks	Promise detection	Obligations	"What do I owe?"
🚨 Awareness	Sensors, APIs	Predictions	State	"What's happening?"

---

📋 Life OS In Action

The Weekly Presidential Briefing

Instead of checking 10 apps every morning, you get one briefing:

┌─────────────────────────────────────────────────────────────────┐
│                   MONDAY MORNING BRIEFING                        │
├─────────────────────────────────────────────────────────────────┤
│                                                                  │
│  "Good morning. Here's your week:                                │
│                                                                  │
│   🎯 ASPIRATION                                                  │
│      Your Q1 goal: Launch MVP. 6 weeks remaining.                │
│                                                                  │
│   🚨 AWARENESS                                                   │
│      💼 Sprint review Wednesday — 3 tickets still open           │
│      🏠 Water tank at 35% (~4 weeks). WOF due in 14 days.        │
│      🧠 Inbox has 23 notes older than 7 days.                    │
│                                                                  │
│   📥 ATTENTION                                                   │
│      💼 Sarah's contract needs response (urgent)                 │
│      🏠 2 personal items can wait until weekend                  │
│                                                                  │
│   📋 COMMITMENT                                                  │
│      💼 5 work meetings. Sprint ends Wednesday.                  │
│         You promised Mike the proposal by Thursday.              │
│      🏠 Saturday: Help with the move (you promised)              │
│      🧠 Weekly cultivation session scheduled Sunday 9am          │
│                                                                  │
│   🧠 KNOWLEDGE                                                   │
│      You captured 8 notes last week. Henderson project           │
│      has the most context if you need to review.                 │
│                                                                  │
│   Suggestion: Block 2 hours Tuesday for the proposal."           │
│                                                                  │
└─────────────────────────────────────────────────────────────────┘

Work + Personal + Home + Knowledge—all in one view.

---

🔐 The Four Pillars

Life OS is built on four foundational pillars:

Pillar	Promise	What It Means
📱 Access	Anywhere	Mobile, web, CLI, voice, API—same data, any surface
👁️ Observable	See it	Activity feed, system health, audit trail
🔐 Secure	Trust it	Work/private separation, sensitivity levels
🌐 Open	Own it	Open source, open standards, data portability

Security: Context × Sensitivity

Data has two dimensions:

	Public	Internal	Sensitive	Highly Sensitive
Work	Company blog	Internal wiki	Client contracts	M&A docs
Private	Social posts	Personal notes	Financial statements	Medical records

The rule: More sensitive = more friction to access. Highly sensitive data never goes to AI.

---

✨ The Promise

With Life OS, you will:

1. 🎯 Stay aligned — Aspiration guides every decision
2. 🚨 Know what's happening — Awareness monitors your world
3. 📥 Control your attention — AI gatekeeper filters the noise
4. 📋 Keep your promises — Nothing slips through
5. 🧠 Compound your knowledge — Every insight builds on the last
6. 🔓 Own your data — Plain text, no vendor lock-in
7. 🪞 Know yourself — Identity surfaces your patterns and challenges your biases
8. 🏛️ Leave a trail — Legacy captures proof of your journey

Like having a chief of staff for your life.

But this is more than productivity. It's about helping you be the best version of yourself.

You stay focused. The layers handle the noise. The trail proves you honored your commitments.

---

📖 Learn More

Foundational Methods:

• Zettelkasten.de — The original slip-box method
• Forte Labs - PARA — Organize by actionability
• How to Take Smart Notes — Sönke Ahrens' book on Zettelkasten
• Building a Second Brain — Tiago Forte's book on PARA

PAI Foundation:

• PAI README — The 13 founding principles
• SpecFirst Methodology — How to build domains

Implementation:

• Context Skill PR #183 — Knowledge Domain implementation
• Jira Skill PR #190 — Commitment Domain (work, partial)

Tools:

• Obsidian — Local-first Markdown knowledge base
• Telegram — Control plane for ingestion and notifications

---

"The purpose of technology is to serve humans—not the other way around. These new AI frameworks should be available to everyone, so that regular people can use it to help them flourish." — Daniel Miessler

[smolcompute]

Nice. Sounds great.

[smolcompute]

I think Daniel has added a lot of tools and procedures to the repo that he uses himself to disentangle his own private PAI from what he makes publicly available.

Perhaps you can package it was a skill with some scripts that use env vars instead of full hard paths.

I'm curious about the Telegram integration.

[mellanon]

Hey @smolcompute PR created for knowledge layer. Feel free to take it for a spin.
I've done my best to document how to get it up and running but please get PA to record all the things you have to do to get it going and push any feedback my way.

[smolcompute]

Thanks ! I haven't had a chance to read up and experiment with it yet but I'm looking forward to it.

[mellanon]

Context Skill PR Status Update

Following up on the Knowledge Domain implementation — the Context Management Skill PR is now submitted and ready for review.

PR Status

PR: #183
Status: Open — Ready for review
Files: 51 files (Context skill, ingest CLI, obs CLI, iOS shortcuts)

What's Included

✅ Complete Knowledge Layer Implementation:

• ingest CLI: Multi-device capture via Telegram (voice, photos, docs, URLs)
• obs CLI: Vault operations — search, semantic search, context loading
• iOS Shortcuts: Mobile capture templates
• Skill definition: Workflow routing for Claude

✅ Release Engineering:

• Formal release framework (RELEASE-FRAMEWORK.md) for future skill contributions
• Comprehensive file inventory (51 files explicitly approved)
• Sanitization process (PII removed, personal config excluded)
• Tag-before-PR workflow for audit trail

✅ Documentation:

• Quick start guide
• CLI reference
• Capture tips
• iOS shortcuts setup
• Release framework (reusable process)

Test Coverage

• Unit/Integration/CLI Tests: 92% pass rate (135/147 tests)
• Manual Acceptance Testing: All core workflows verified
• Test Framework: 4-layer pyramid exists in private repo (sanitized version to follow)

Release Process Highlights

This contribution follows a formal release process that could serve as a template:

1. File Inventory Approach: Every file explicitly decided in RELEASE-v1.0.0.md before cherry-pick
2. 3-Repo Workflow: Private dev → Fork staging → Upstream PR
3. Tag-Before-PR: Tag marks exact tested code, cherry-pick ensures PR matches tests
4. Sanitization: Comprehensive PII removal and scope validation

What's Next

• Awaiting Review: PR is ready for community feedback
• If Changes Needed: Will iterate with v1.0.1 following the same process
• After Approval: Tag v1.0.0 and merge

Related

• PR: [Your new PR - update with actual number/URL]
• Original Discussion: #147 - Knowledge Layer
• Life OS Vision: #157 - Four Domains (this discussion)

The Knowledge domain is now ready for the community. Looking forward to feedback and seeing how others extend PAI with additional Life OS domains! 🚀

[mellanon]

📣 Progress Update: Four Domains → Five Domains + Knowledge Stack

Some evolution on this thinking after a few more days of building:

Framework Evolution: Adding Aspiration

After running LifeOS past a friend he pointed out that there's something missing... Aspirations.
He's right, I realised the original four domains are all reactive and external — they handle what's happening TO you, what others need FROM you, what you OWE, and what you HAVE. But there was a missing dimension: who you're becoming.

I've added 🎯 Aspiration as a fifth domain — the compass that gives meaning to the other four:

• Which awareness matters → aligned with your goals
• Which attention to prioritise → serves your purpose
• Which commitments to make → reflects your values
• Which knowledge to cultivate → supports who you're becoming

Updated the main post above to reflect this.

[1activegeek]

I don't have much to add at the moment - I'm just starting to try and implement PAI myself now. I see the vision as you do of what Daniel has built here (which is phenomenal!). Interestingly, I'm not surprised - as I know of him, Jason, and many other of the leading thinkers in the Cyber Security space (I too work in InfoSec, on the vendor side). That aside, I am very much aligned with your thinking here as well and mentality around the knowledge piece of things.

One side angle I'll offer, is that I don't think this is universal for all people - but some personalities like my own REALLY struggle with the idea of lost information or things falling through that gap. It's IMO the biggest thing holding me back from really exploring my own potential and expanding my own entrepreneurial ventures to gain back some time freedom in my life. I really like the idea of PAI for 3 main things:

• Time Freedom - gaining back valuable time spend doing mundane things, sort of the idea of an executive assistant on steroids more tightly tuned and more capable than any actual EA that exists (kind like having 5 different assistants on staff all great at different things rolled into 1 PAI).
• Knowledge Enhancement - plays in here with what you are advertising and focuses in on being able to wrangle all the thoughts, ideas, information, etc that I consume and process
• Life Enhancement - level up our life capabilities - along the lines of the core that Daniel preaches. I want to be able to do more and go farther and be better than I am, with AI enabling it I can do that faster and be more to the people in my life and this world.

I write all this to share the positive vibes with what you've created, and let you know I'll come back and share some feedback later when I get things running. I'm really loving the idea of telegram as the way to start capturing things to process - this is my biggest issue getting stuff out of my head. Linked directly with PAI? Fantastic!

Keep ideating. Feedback to come.

[mellanon]

I don't have much to add at the moment - I'm just starting to try and implement PAI myself now. I see the vision as you do of what Daniel has built here (which is phenomenal!). Interestingly, I'm not surprised - as I know of him, Jason, and many other of the leading thinkers in the Cyber Security space (I too work in InfoSec, on the vendor side). That aside, I am very much aligned with your thinking here as well and mentality around the knowledge piece of things.

One side angle I'll offer, is that I don't think this is universal for all people - but some personalities like my own REALLY struggle with the idea of lost information or things falling through that gap. It's IMO the biggest thing holding me back from really exploring my own potential and expanding my own entrepreneurial ventures to gain back some time freedom in my life. I really like the idea of PAI for 3 main things:

• Time Freedom - gaining back valuable time spend doing mundane things, sort of the idea of an executive assistant on steroids more tightly tuned and more capable than any actual EA that exists (kind like having 5 different assistants on staff all great at different things rolled into 1 PAI).
• Knowledge Enhancement - plays in here with what you are advertising and focuses in on being able to wrangle all the thoughts, ideas, information, etc that I consume and process
• Life Enhancement - level up our life capabilities - along the lines of the core that Daniel preaches. I want to be able to do more and go farther and be better than I am, with AI enabling it I can do that faster and be more to the people in my life and this world.

I write all this to share the positive vibes with what you've created, and let you know I'll come back and share some feedback later when I get things running. I'm really loving the idea of telegram as the way to start capturing things to process - this is my biggest issue getting stuff out of my head. Linked directly with PAI? Fantastic!

Keep ideating. Feedback to come.

Thanks for taking the time to share this — really appreciate the thoughtful response.

We are definitely aligned on your three pillars (Time Freedom, Knowledge Enhancement, Life Enhancement). They map almost directly to what I've been calling the "five domains" and hearing how you frame it adds more colour to the vision.

The "lost information anxiety" you describe — that's exactly what drove me to build the Knowledge Domain first. The feeling that thoughts are slipping through the cracks, that you had an insight last week but can't find it now. Telegram as the "single front door" was my solution to that: capture in 3 seconds, process later, never lose the thread.

Would love to collaborate as you get things running. The best way to improve these tools is having more people use them and share what works (and what doesn't). The Context Skill PR #183 is ready for testing if you want to try the Knowledge Domain implementation.

And if you hit friction points getting it set up — that's valuable feedback. Document what's confusing, what's missing, what you had to figure out. That becomes the roadmap for making it easier for the next person.

Looking forward to your feedback. Great things happen when people like you bring fresh perspectives to the table!

[mellanon]

📣 Update: Life OS Vision Enhanced

Just completed a major knowledge cultivation session that enhanced the Life OS vision with new concepts and diagrams. Key updates to the main post above:

What's New

1. Domain Interconnections Diagram

• Shows how the five domains flow into each other
• Aspiration feeds priorities down to all domains
• Knowledge feeds insights back up to Aspiration
• Key distinction: Awareness = what's happening; Attention = how you get notified

2. Foundation Section

• Markdown + Tags as "the glue" that enables everything
• Plain text forever (no vendor lock-in)
• Tags are the API (multi-dimensional taxonomy)
• Tool interoperability (Telegram, Obsidian, Git, PAI — all swappable)

3. Meta Loop Section

• Shows how PAI Principles 7, 10, 12 work together
• P7 (ENG/SRE): Treat systems as infrastructure
• P10 (Meta/Self-Update): Systems improve themselves
• P12 (Custom History): Memory makes intelligence compound
• Visual diagram of the continuous improvement cycle

4. Implementation Status Table

• Knowledge Domain: ✅ Built (PR feat(context): Add Context Skill for knowledge capture and retrieval #183)
• Commitment Domain: 🟡 Partial (PR feat(jira): Add Jira skill with Filters API, Quick Filters, and Ordering #190 — Jira for work)
• Other domains: 🔲 Planned

The Process

This update came from practicing the 8-phase cultivation workflow:

LOAD → SURVEY → EXTRACT → CONNECT → DRAFT → CREATE → ARCHIVE → COMMUNITY

We processed 18 research documents into the updated vision, with HITL checkpoints at each phase. The cultivation plan and worked example are documented in my fork.

Related Updates

• Knowledge Domain Vision — Deep dive on the "What do I know?" domain (see #147)
• SpecFirst Methodology — How we're building skills spec-first (see #187)

The session also generated 67 OpenSpec requirements for the next Context Skill version (cultivation workflow support, session management, graph commands, lineage tracking).

---

This is Phase 8 (Community) of the cultivation workflow — sharing back what we learned.

[mellanon]

🌱 Update: Strategic Layer with Identity and Legacy

I've expanded the Life OS vision based on cultivation sessions exploring the deeper purpose of personal AI systems.

What Changed

Before: 5 domains with Aspiration as a special "compass" domain
After: Strategic Layer (Aspiration + Identity + Legacy) guiding 4 Operational Domains

The Key Insight

"This is more than productivity. It's about helping us be the best version of ourselves."

Identity and Legacy aren't separate domains—they're emergent properties derived from the digital trail you leave across all operational activity:

• 🪞 Identity emerges from patterns in your writing, tags, connections, voice recordings, and decisions
• 🏛️ Legacy accumulates from delivered commitments, cultivated knowledge, and the archive of your journey

Why This Matters

Identity enables growth:

• Your AI learns your style and can apply it
• More importantly, it can surface your biases and challenge your assumptions
• "Have you considered the opposite view?"

Legacy provides proof:

• Status reports, CV, portfolio from delivered work
• Blog posts, presentations from cultivated knowledge
• Not everything becomes a blog post—sometimes you're just expanding notes
• All of this IS the trail

New Sections Added

1. 🧭 The Strategic Layer — Aspiration + Identity + Legacy explained in depth
2. ⚙️ The Operational Domains — Expanded detail on each domain
3. 🔄 How Domains Connect — Flow diagram showing interconnections
4. 🔄 The Meta Loop — P7 + P10 + P12 working together
5. 🏗️ Built on PAI — Implementation status and patterns
6. 📋 Life OS In Action — Presidential Briefing example
7. 🔐 The Four Pillars — Access, Observable, Secure, Open
8. ✨ The Promise — Now 8 items including Identity and Legacy

Connection to PAI Principle 12

"Memory makes intelligence compound. Without history, every session starts from zero."

The History System isn't just about remembering—it's the foundation for Legacy. Every captured thought, every completed commitment, every cultivated note becomes part of your proof.

---

This update came from cultivation sessions integrating insights about the deeper purpose of personal AI systems. The vault document is the source of truth.

[systemccg]

I couldn't believe when I saw this! I built out a similar system except I also use neo4j with graphiti for graph rag to connect Concepts that are searchable when this gets up to millions of documents. I also have a vector store in Supabase as well as the number of tables to handle things like my vision and goals in okrs. I'm going to build it so that we could share workspaces together where we have shared knowledge in addition to our personal knowledge. I'd love to get together if you're interested

[mellanon]

That sound like we've been down the same rabbit hole! I have explored knowledge graphs over the last few years and have experience with neo4j but I'm trying to keep the skill as basic as possible so that you don't end up needing lots of infrastructure to run PAI.

Keen to collaborate. Would be awesome if you could help out with some early testing so we can get a feedback loop going if you are interested?

There's likely a place for more tooling around this i.e. having knowledge graph powered insights to support making connections that aren't obvious or surfacing up things similar to Spotify wrapped etc but I decided to start simple and build from there since.