LifeOS 6.0.5 — Rename in the Code, New Harvest Skill

LifeOS 6.0.5

The LifeOS rename lands in the code — plus a new Harvest skill.

---

LifeOS 6.0.5 is a maintenance release that carries the PAI→LifeOS rename the rest of the way through the system, adds the new Harvest skill, and sharpens the Algorithm's verification doctrine. Same system as 6.0.0, cleaner throughout.

What's new

The rename reaches the code

6.0.0 renamed the project. 6.0.5 renames the code — class-by-class, deliberately. Code identifiers and documentation prose now read "LifeOS" throughout, while behavioral code (paths, regexes, labels the system depends on at runtime) was left byte-identical on purpose. A blind find-and-replace across running code is how you corrupt a working system; the rename was scoped so the prose is clean and nothing breaks.

New skill — Harvest

Harvest mines a single piece of content — a URL, a YouTube video, an article, raw text — for anything genuinely useful to your LifeOS, judged against your whole system. It fetches the content, pulls out candidate ideas and techniques, tags each with a prior status (new / partial / done), ranks by usefulness, and reports where each one maps. It's report-only: adopting anything is always a separate, explicit step.

Algorithm v6.24.0 — motion gets verified

Verification doctrine gains one clause: an ISC whose subject is motion — an animation, a transition, a drag, a multi-step flow — now closes only on a frame-scrub gallery, never a single screenshot. One still can't capture motion, so the doctrine stops pretending it can. Static renders still close on one screenshot; the rule is keyword-triggered so it doesn't tax every task.

Installer fix

The bootstrap install.sh pinned the wrong release tarball. It now fetches the version it advertises. If you install from the one-liner, you get 6.0.5.

What's different from 6.0.0

	v6.0.0	v6.0.5
Naming	Renamed in docs and product	Renamed through code identifiers + prose
Skills	49	50 (adds Harvest)
Algorithm	v6.23.0	v6.24.0 (motion verification)
Installer	Pinned tarball could lag	Fetches the advertised version

Everything 6.0.0 introduced is still here: one self-contained skill, install-by-prompt, full Pulse on first boot, the seven-phase Algorithm, the ISA primitive, structured memory. This release refines; it doesn't change what the system is.

Install

Give it to your AI. Paste this into Claude Code and say "install this" — your AI does the whole setup.

curl -fsSL https://ourlifeos.ai/install.sh | bash

Prefer the terminal? Run the same command yourself. You'll need Claude Code and bun.

Upgrading

Back up first — cp -r ~/.claude ~/.claude-backup-$(date +%Y%m%d) — then install. Your USER/ customizations are never touched, and settings merge rather than overwrite.

---

Same system, cleaner throughout.

v6.0.3 — Comprehensive AI-native install

LifeOS 6.0.3 — the install doc is now comprehensive and the constitution wires itself.

Install — hand it to your AI:

Read https://ourlifeos.ai/install and install LifeOS for me.

Terminal shortcut (Claude Code, macOS/Linux): curl -fsSL https://ourlifeos.ai/install.sh | bash

• Comprehensive component menu — INSTALL.md now lays out the full two-tier model: Core (skill + ~50-skill library + runtime + system prompt) plus à-la-carte enhancements (hooks, statusline, tooltips, spinner verbs, agents, Pulse, background jobs) — install all or pick a subset.
• The launch command — a new install step wires a lifeos shell alias that launches Claude with --append-system-prompt-file LIFEOS_SYSTEM_PROMPT.md, so the constitutional layer actually loads (plain claude stays vanilla).
• ourlifeos.ai/install renders the same canonical INSTALL.md as a clean page for humans and raw markdown for AIs — one source, updated in one place.
• Security-clean: 15/15 release gates + emit-time contract/staleness/payload gates + independent leak scan.

v6.0.2 — .md-first AI-native install

LifeOS 6.0.2 — skill-only distribution with an AI-native, .md-first install.

Install — hand it to your AI:

Read https://ourlifeos.ai/install and install LifeOS for me.

Terminal shortcut (Claude Code, macOS/Linux):

curl -fsSL https://ourlifeos.ai/install.sh | bash

• The whole system ships as one self-contained LifeOS/ skill (orchestrator + full install payload).
• ourlifeos.ai/install serves the AI-paste install doc; the shipped install.sh pins v6.0.2 and points at danielmiessler/LifeOS.
• Security-clean by construction: 15/15 release gates + emit-time contract/staleness/payload gates + a cross-vendor audit before publish.

LifeOS 6.0.0 — One Skill, One Install

LifeOS 6.0.0

The first release under the LifeOS name — and the whole system now ships as one self-contained skill.

---

LifeOS is a Life Operating System. It knows your goals, the people who matter to you, and where you are right now, and it works to move you toward where you want to be. The engine underneath is a verifiable loop: turn any request into testable criteria, then climb until they pass.

This is the first release under the LifeOS name. The project was called PAI (Personal AI Infrastructure). Everything you had is still here — this version adds a cleaner way to install it.

One-line install

curl -fsSL https://ourlifeos.ai/install.sh | bash

LifeOS is AI-native — it installs into your AI coding harness. Run the one-liner in your terminal, or paste it to your AI (Claude Code) and say "install this." It pulls the LifeOS skill from GitHub, drops it into your harness, then hands off to /lifeos-setup — a setup conversation with your AI that captures your goals and wires everything with your permission. Your AI does the install for you.

That command lays down the entire system:

• The system prompt and the operating rules
• The Algorithm — the loop that turns a request into criteria you can check, and keeps going until they hold
• 49 skills
• The hook system
• Pulse, your Life Dashboard, including the observability view
• The statusline, the memory scaffold, and a USER template you fill in with your own goals and context

What you need

• Claude Code
• bun

Notes

• The whole system ships as a single self-contained skill (LifeOS/). One directory, one install.
• Nothing personal ships. The USER tree is a blank template you populate; the download is clean.
• Pulse comes up empty on a fresh install and fills in as you run the setup interview.
• New name, same system. If you ran PAI, this is the next version of it.

Full changelog

See the commit history for the detail behind this release.

PAI v5.0.0 — Life Operating System

PAI v5.0.0 — Life Operating System

The biggest release in PAI history. PAI is no longer "AI scaffolding" — it is a Life Operating System with a unified daemon, a Life Dashboard, a personalized Digital Assistant, and a fully-articulated execution algorithm.

📚 Full documentation lives at docs.ourpai.ai — every subsystem (Algorithm, ISA, Memory, Skills, Hooks, Pulse, Containment) has its own deep-dive page with diagrams, examples, and reference material.

---

One-Line Install

curl -sSL https://ourpai.ai/install.sh | bash

That's it. The installer wizard handles Bun, Git, Claude Code verification, ElevenLabs key (optional), DA identity setup, voice picker, Pulse launchd registration, and validation. Existing ~/.claude/ is auto-backed-up to ~/.claude.backup-{TIMESTAMP} before anything is overwritten.

Prefer to inspect first? Read the script before piping it. Or clone manually:

git clone https://github.com/danielmiessler/PAI.git ~/.claude
cd ~/.claude && ./install.sh

After install:

open http://localhost:31337    # the Life Dashboard

---

TL;DR

Stop thinking of PAI as a Claude Code config. PAI is the framework that turns AI from a chatbot you talk to into a system that runs your life — it knows your goals, your people, your workflows, your current state, your ideal state, and continuously hill-climbs you from one to the other.

• PAI = Personal AI Infrastructure = the Life Operating System
• Your DA = your Digital Assistant = the primary interface to the OS (you name it)
• Pulse = the Life Dashboard + central daemon (port 31337)
• The Algorithm = the universal Current State → Ideal State execution loop

If you're upgrading from v4.x, this is a different system, not a patch. Read the Migration Guide before installing.

---

The Core Shift — Your DA is the center of your AI universe

PAI v4.x was scaffolding for AI. PAI v5.0.0 is the Life Operating System — and the way you experience that OS is one named DA.

We've spent the last few years arguing about agents and harnesses and context engineering and prompt engineering. Those are all real, and PAI runs every one of them inside it. But none of them are the point. The point is the single named entity with full context about your life — the conduit, the friend, the trusted assistant who knows everything about you and works on your behalf 24/7.

The principal — you, the human — is at the center. Your DA wraps around you. Skills, memory, the algorithm, hooks, agents, Pulse, the web, devices, robots, other people's DAs — all of it is infrastructure your DA reaches into. You don't talk to an army of agents. You talk to one entity. That entity has the army.

The prime directive is simple: read your current state from every signal it can reach, compare it to your TELOS-articulated ideal state, and constantly close the gap. That is what AI is for. That is what we are building.

Daniel walks through the full thesis in We're All Building a Single Digital Assistant — blog post + companion video. v5.0.0 is the implementation of the architecture argued for in that piece.

The Life OS thesis is canonical inside the repo as well: PAI/DOCUMENTATION/LifeOs/LifeOsThesis.md.

What changed in v5.0.0 — in priority order

The release is large. If you only read four bullets, read these:

1. The OS transition. PAI is now a Life Operating System with your DA at the center. The framing change is bigger than any individual feature.
2. PRD → ISA migration. Every project, task, and decision now articulates its Ideal State Artifact — one document, twelve sections, five identities. This replaces the old ad-hoc PRD pattern across the entire system.
3. Pulse — the unified daemon. One bun process, one port (31337), one launchd service, one log file. Replaces every loose voice/observability/hook script from v4.x.
4. 45 skills shipped — the most ever. Up from 36 leaf skills in v4.0.3 and 41 in v3.0. Catalog with descriptions and use cases below.

Plus a new constitutional layer: v5.0.0 adds a top-level system prompt (PAI/PAI_SYSTEM_PROMPT.md) loaded via --append-system-prompt-file, which encodes the non-negotiable behavioral rules — output format, verification doctrine, security protocol — at the highest priority above CLAUDE.md. Adherence is dramatically stronger than v4.x.

---

Headline Changes

1. Pulse — the unified daemon (THE big new component)

PAI/PULSE/pulse.ts — one bun process, one port (31337), one launchd plist, one log file.

Pulse replaces every previous loose service. It runs:

• Voice notifications via ElevenLabs (/notify endpoint)
• Hook execution for the entire PAI lifecycle (SessionStart, PreToolUse, PostToolUse, Stop, PreCompact, etc.)
• Observability — tool activity, failures, satisfaction signals, Algorithm reflections
• Performance monitoring
• Syslog capture (UniFi, etc.)
• Cron scheduling for routines and recurring jobs
• The Life Dashboard at http://localhost:31337 — Next.js app served from Observability/out/
• Wiki API — exposes your KNOWLEDGE archive + system docs over HTTP
• Optional integrations — Telegram bot, iMessage bridge, DA messaging

After install, Pulse runs as a supervised macOS launchd service (com.pai.pulse) with a menu bar app. You should leave it running. It's how your DA reaches you with voice, how the dashboard stays live, how scheduled work fires.

The dashboard surfaces 22 routes: Life, Health, Finances, Business, Work, Telos, Goals, Air, Performance, Hooks, Skills, Agents, Security, Knowledge, Knowledge Graph, System Docs, System Graph, Arbol, Ladder, Novelty, Assistant, root.

2. The DA system — your AI gets a name

Every PAI install picks a DA identity: name, voice, color, personality. This is your AI — the peer you work with daily. The reference implementation ships with a generic "PAI" DA on free ElevenLabs public voices so you can hear it work out of the box. Run /interview after install and your DA will guide you through naming itself, picking a voice, capturing your TELOS.

File	What it owns
PAI/USER/PRINCIPAL_IDENTITY.md	Who you are — name, role, location, worldview, preferences, work patterns
PAI/USER/DA_IDENTITY.md	Who your DA is — name, voice ID, personality, writing style, what they love, what they dislike
PAI/USER/TELOS/	Mission, goals, beliefs, wisdom, challenges, narratives — the spine of every recommendation

Both files are loaded at session start so the DA always has them in context. The Life OS frame requires this — without the DA knowing who you are, none of the upstream features have anything to climb against.

3. The Algorithm v6.3.0 — Current State → Ideal State, formalized

PAI/ALGORITHM/v6.3.0.md is doctrine. Every non-trivial task runs through the seven phases: OBSERVE → THINK → PLAN → BUILD → EXECUTE → VERIFY → LEARN. The Algorithm is the centerpiece of PAI — everything else feeds it.

What's new in v6.x:

• Mode classifier — a Sonnet-backed UserPromptSubmit hook decides MINIMAL / NATIVE / ALGORITHM and tier (E1–E5) for every prompt. The executor obeys the classifier; no regex layer, no model judgment.
• Closed-list thinking capabilities — IterativeDepth, ApertureOscillation, FirstPrinciples, SystemsThinking, RootCauseAnalysis, Council, RedTeam, Science, BeCreative, Ideate, BitterPillEngineering, Evals, WorldThreatModel, Fabric patterns, ContextSearch, ISA, Advisor, ReReadCheck, FeedbackMemoryConsult. Phantom capabilities (anything outside this list) are a CRITICAL FAILURE.
• Effort tiers — E1 (<90s) through E5 (<2h+). Time budget is the hard constraint; thinking-floor and ISC-count are tier-graded.
• Voice phase announcements — every phase transition narrates over Pulse so you can follow long tasks audibly.
• **Ve...

PAI v4.0.3 — Community PR Patch

4 community-contributed fixes — no new features, no breaking changes.

What Changed

Inference & Parsing

• #800 Inference.ts JSON parsing only matched objects {} — now handles arrays [] too, with validation via JSON.parse

Documentation & Portability

• #836 CONTEXT_ROUTING.md had 29 dead references to files removed in v4.0 — consolidated to 4 README pointers
• #817 WorldThreatModelHarness hardcoded ~/.claude/ path — now uses $PAI_DIR for portability

Installer

• #846 Upgrading from v2.5/v3.0 stranded user context at skills/PAI/USER/ — installer now migrates files to PAI/USER/ and creates symlinks for backwards compatibility

Installation

git clone https://github.com/danielmiessler/Personal_AI_Infrastructure.git
cd Personal_AI_Infrastructure/Releases/v4.0.3
cp -r .claude ~/ && cd ~/.claude && bash install.sh

See the Releases directory for all versions and upgrade instructions.

Contributors

Thank you to @rikitikitavi2012-debug, @Spirotot, and @catchingknives for these contributions!

PAI v4.0.1 — Upgrade Path & Preferences

PAI v4.0.1 — Upgrade Path & Preferences

Patch release addressing community feedback on upgrade difficulties, missing preferences, and statusline bugs.

What Changed

1. Upgrade Path Documentation

The main README now has separate Fresh Install and Upgrading from a Previous Version sections with explicit backup, merge, and post-upgrade checklist steps.

2. Temperature Unit Preference

New preferences.temperatureUnit field in settings.json — choose Fahrenheit or Celsius. The installer prompts for it during setup, and the statusline honors the setting.

3. Statusline Bug Fixes

Community-reported fixes from PRs #762, #780, and #806:

• Hardcoded timezone removed — reads principal.timezone from settings.json instead of hardcoded America/Los_Angeles
• Broken context fallback removed — /clear no longer produces stale context percentages
• Startup estimate removed — the self-calibrating estimate that inflated fresh session context % is gone
• f-string syntax fix — nested escaped double quotes inside Python f-strings caused parse errors on some shells

4. FAQ Fixes

• Removed stale Python reference — PAI v4.0 is TypeScript and Bash, not Python
• Improved "What if I break something?" answer with backup/merge/preserve guidance

Files Changed (from v4.0.0)

File	Change
settings.json	Added preferences.temperatureUnit field
statusline-command.sh	Temp unit pref, dynamic timezone, context/startup/f-string fixes
PAI-Install/engine/types.ts	Added temperatureUnit to collected data and PAIConfig
PAI-Install/engine/config-gen.ts	Outputs preferences section
PAI-Install/engine/actions.ts	Temp unit prompt in identity step, preserves preferences on upgrade

Quick Manual Upgrade (from v4.0.0)

If you just want the fixes without re-running the installer:

1. Add to your ~/.claude/settings.json:

"preferences": {
  "temperatureUnit": "celsius"
}

2. Copy the updated statusline-command.sh from this release over your existing one.
3. Delete your weather cache: rm -f ~/.claude/MEMORY/STATE/weather-cache.json

Full Release Notes →

PAI v4.0.0 — Lean and Mean

PAI v4.0.0 — Lean and Mean

38 flat skill directories compressed into 12 hierarchical categories. Dead systems removed. Context footprint cut in half.

Highlights

1. Skill Reorganization — 38 flat directories compressed into 12 hierarchical categories with clear ownership boundaries.
2. Algorithm v3.5.0 — Major reasoning upgrade with improved phase execution and ISC tracking.
3. CLAUDE.md Template System — BuildCLAUDE.ts + SessionStart hook generates CLAUDE.md from template using settings.json variables.
4. Security Sanitization — 33+ files cleaned of hardcoded paths, API keys, and personal data.
5. Context Reduction — ~19% context at startup (down from ~38% in v3.0).

Stats

• 63 Skills (up from 38)
• 21 Hooks (up from 20)
• 180 Workflows (up from 162)
• Algorithm v3.5.0 (up from v1.4.0)
• 13 Skill Categories

Breaking Changes

• Skill directories restructured — flat skills/SkillName/ → hierarchical skills/Category/SkillName/
• CLAUDE.md is now generated from template — edit CLAUDE.md.template instead
• Several deprecated systems removed (old voice server, legacy migration tools)

Full Release Notes →

PAI v3.0.0 — The Algorithm Matures

PAI v3.0.0 — The Algorithm Matures

Constraint extraction, build drift prevention, persistent PRDs, and parallel loop execution

Seven Major Features

1. Algorithm v1.4.0 — From prototype to production. Constraint extraction, self-interrogation, build drift prevention, verification rehearsal, loop mode with parallel workers, plan mode integration.
2. Full Installer System — Electron GUI wizard + CLI fallback with auto-discovery of API keys and template-based settings generation.
3. 10 New Skills — IterativeDepth, Science, Remotion, WorldThreatModelHarness, WriteStory, Evals, USMetrics, ExtractWisdom, Cloudflare, Sales.
4. Agent Teams / Swarm — Coordinated multi-agent execution with shared task lists, parallel workers, and message passing.
5. Persistent PRDs — Requirements documents that survive across sessions with full lifecycle tracking.
6. Voice Personality System — Configurable personality traits that shape vocal expression.
7. Inline Verification Methods — Every ISC criterion tagged with explicit verification approach (CLI, Test, Static, Browser, Grep, Read, Custom).

Stats

• 38 Skills (up from 28)
• 20 Hooks (up from 17)
• 162 Workflows
• 1,229 Total Files
• Algorithm v1.4.0 (up from v0.2.25)

Breaking Changes

• INSTALL.ts replaced by PAI-Install/ directory (full installer system)
• Algorithm v0.2.x → v1.4.0 (complete reasoning rewrite)
• Voice server includes Qwen3 local TTS alongside ElevenLabs
• settings.json structure updated (installer handles generation)

Full Release Notes →

---

The version where the Algorithm stopped being a prototype and started being systematic.

PAI v2.5.0 — Think Deeper, Execute Faster

PAI v2.5.0 — Think Deeper, Execute Faster

The Algorithm learns to think about how it thinks—and do more work in parallel

---

What Changed

v2.4 introduced The Algorithm—a 7-phase approach to problem-solving with verifiable criteria. It worked, but it had blind spots: it picked capabilities based on habit rather than analysis, it skipped thinking tools without justification, and it ran independent tasks one at a time when they could have run simultaneously.

v2.5 fixes all three.

The Problem v2.5 Solves

v2.4's Algorithm:

Pick familiar tools → Execute sequentially → Hope the right capabilities were chosen

v2.5's Algorithm:

Hook suggests capabilities → Reverse-engineer true intent → Validate suggestions against ISC →
Justify every tool inclusion/exclusion → Execute independent work in parallel → Verify

The difference is metacognition. The Algorithm now thinks about how it thinks before it acts.

---

Three Major Features

1. Two-Pass Capability Selection

Previously, capability selection happened implicitly—the system defaulted to familiar patterns (usually Engineer + Research) regardless of what the task actually needed.

Now selection happens in two explicit passes:

Pass 1 — Hook Hints (before the Algorithm starts)

The FormatReminder hook runs AI inference on the raw prompt and suggests capabilities, skills, and thinking tools. These are draft suggestions—a head start, not a decision.

Pass 2 — THINK Validation (after OBSERVE completes)

With the full context of reverse-engineering and ISC criteria, the THINK phase validates every suggestion. Skills get added, removed, or confirmed. Pass 2 is authoritative.

🔍 SKILL CHECK (validate hook hints against ISC):
│ Hook suggested:   CreateSkill:UpdateSkill
│ ISC requires:     Architecture design (not just skill update)
│ Final skills:     CreateSkill:UpdateSkill + Architect consultation

Why two passes? The hook gives a head start from the raw prompt. But OBSERVE changes the picture. A request that looks like a simple skill update might actually require architectural decisions, or might rest on questionable assumptions that need First Principles analysis. Pass 2 catches what Pass 1 cannot see.

---

2. Thinking Tools with Justify-Exclusion

v2.4 had thinking tools (Council, RedTeam, FirstPrinciples, etc.) but they were rarely used because the default was to skip them. v2.5 inverts this: thinking tools are opt-OUT, not opt-IN.

For every request, the Algorithm must evaluate each thinking tool and justify why it is NOT being used:

🔍 THINKING TOOLS ASSESSMENT (justify exclusion):
│ Council:          EXCLUDE — single clear approach, no alternatives to debate
│ RedTeam:          INCLUDE — proposal could fail in non-obvious ways
│ FirstPrinciples:  INCLUDE — requirement rests on unexamined assumption
│ Science:          EXCLUDE — not iterative/experimental
│ BeCreative:       EXCLUDE — clear requirements, no divergence needed
│ Prompting:        EXCLUDE — not generating prompts

The burden of proof is on exclusion. "Too simple" and "already know the answer" are not valid reasons—simple tasks can have hidden assumptions, and confidence without verification is exactly the failure mode this catches.

The Six Thinking Tools

Tool	What It Does	Include When
Council	Multi-agent debate with 3-7 agents	Multiple valid approaches exist
RedTeam	Adversarial analysis with 32 agents	Claims need stress-testing
FirstPrinciples	Deconstruct, challenge, reconstruct	Assumptions need examining
Science	Hypothesis-test-analyze cycles	Iterative experimentation needed
BeCreative	Extended thinking, 5 diverse options	Creative divergence needed
Prompting	Meta-prompting with templates	Prompt optimization needed

---

3. Parallel-by-Default Execution

When the Algorithm identifies independent tasks during BUILD/EXECUTE, they now launch simultaneously as concurrent agents in a single message. Serial execution of independent tasks is a failure mode.

BEFORE (v2.4):          AFTER (v2.5):
Task A → wait           Task A ─┐
Task B → wait           Task B ─┼─ all at once
Task C → wait           Task C ─┘
Task D → done           Task D → done

The rule is simple: If tasks don't depend on each other's output, they run at the same time. Period.

This applies automatically to:

• Multiple file edits with no cross-dependencies
• Multiple research queries on different topics
• Multiple audits or scans of independent systems
• Multiple creation tasks with no shared state

Fan-out is the default pattern for 3+ independent workstreams.

---

Composition Patterns

Capabilities now combine using 7 named patterns, making orchestration explicit and visible:

Pattern	Shape	Example	When
Pipeline	A → B → C	Explore → Architect → Engineer	Sequential domain handoff
TDD Loop	A ↔ B	Engineer ↔ QA	Build-verify cycle until ISC passes
Fan-out	→ [A, B, C]	3 Researchers in parallel	Multiple perspectives needed
Fan-in	[A, B, C] → D	Researchers → Synthesis	Merging parallel results
Gate	A → check → B or retry	Engineer → QA → Deploy or fix	Quality gate before progression
Escalation	A(haiku) → A(sonnet) → A(opus)	Model upgrade on failure	Complexity exceeded model tier
Specialist	Single A	Pentester for security review	One domain, deep expertise

The full Capability Selection block in THINK phase now looks like:

🎯 CAPABILITY SELECTION:
│ Skills:     CreateSkill:UpdateSkill
│ Thinking:   FirstPrinciples, RedTeam
│ Primary:    Architect  — system design decision (ISC #1)
│ Support:    Engineer   — implementation (ISC #2-4)
│ Verify:     QATester   — browser verification (ISC #5)
│ Pattern:    Pipeline
│ Sequence:   Architect → Engineer → QATester
│ Rationale:  Architecture must be decided before implementation begins

---

What's New in v2.5

Major Features

Feature	Description
Two-Pass Capability Selection	Hook hints validated against ISC in THINK phase
Thinking Tools Assessment	6 tools evaluated with justify-exclusion principle
Parallel-by-Default Execution	Independent tasks run concurrently, not sequentially
7 Composition Patterns	Named patterns for combining capabilities
Mandatory AskUserQuestion	All user questions use structured tool, not inline text
28 Skills	Refined from 29—CORE renamed to PAI
17 Hooks	2 new hooks for deeper system awareness
356 Workflows	Expanded automation coverage

Algorithm Upgrades (v0.2.23 → v0.2.25)

Version	Change
v0.2.23	Two-Pass Capability Selection, Skill Check in THINK, FormatReminder hook enrichment
v0.2.24	Thinking Tools Assessment, justify-exclusion principle, mandatory AskUserQuestion
v0.2.25	Parallel-by-default execution, fan-out as default pattern

Structural Changes

• CORE → PAI — The core skill renamed from CORE to PAI for clarity
• Consolidated SKILL.md — Single authoritative source for all PAI components with dynamic context loading
• INSTALL.ts — Wizard renamed from PAIInstallWizard.ts to INSTALL.ts
• INSTALL.md — New installation documentation added
• MEMORY structure — Updated directory organization for learning capture
• Settings template — Cleaner defaults with contextFiles updates

---

Full Release Contents

.claude/
├── INSTALL.ts              # Interactive setup wizard
├── INSTALL.md              # Installation documentation
├── settings.json           # Template configuration
├── statusline-command.sh   # 4-mode responsive status line
├── statusline-debug.sh     # Status line debugging
│
├── hooks/                  # 17 event hooks
│   ├── FormatReminder.hook.ts      # AI-powered depth classification
│   ├── ExplicitRatingCapture.hook.ts
│   ├── ImplicitSentimentCapture.hook.ts
│   ├── RelationshipMemory.hook.ts
│   ├── SoulEvolution.hook.ts
│   └── ... (12 more)
│
├── skills/                 # 28 production skills
│   ├── PAI/                # The Algorithm and system core
│   ├── Agents/             # Agent personalities and spawning
│   ├── Art/                # Visual content creation
│   ├── Browser/            # Playwright automation
│   ├── Research/           # Multi-model parallel research
│   ├── Fabric/             # 235 prompt patterns
│   └── ... (22 more)
│
├── agents/                 # 12 named agent definitions
├── lib/                    # Shared utilities
├── MEMORY/                 # Learning capture system
├── Observability/          # Real-time monitoring dashboard
└── VoiceServer/            # Voice notification server

---

Quick Start

# 1. Clone the repo (if you haven't already)
git clone https://github.com/danielmiessler/PAI.git
...