#+TITLE: PSF PRD v2.0: The Sovereign Software House #+AUTHOR: PM-Agent #+DATE: 2026-03-22 #+ID: psf-prd-v2 #+STARTUP: content * Executive Summary The Personal Software Foundry (PSF) is an end-to-end, proactive "virtual software house" embedded within the user's workspace. It is tasked with the entire lifecycle of software creation—from proactive need-discovery to autonomous maintenance—all while adhering to the philosophical and technical rigor of a native Lisp Machine. * 1. Scope & Boundaries ** 1.1. In-Scope (Foundry Responsibility) - Proactive identification of software needs within the Memex. - Demand Interviews and PRD generation. - Full SDLC: Architecture, TDD, Implementation, Chaos QA, and Gitea PR management. - Long-term code grooming and technical debt reduction. ** 1.2. Out-of-Scope (Prohibitions) - Interference with non-technical Org subtrees (Journals, Personal Records). - Irreversible deletions without multi-step user confirmation. - Adding external dependencies without Architect vetting and User approval. * 2. Personas & Interaction ** 2.1. The Sovereign Executive (User) - Focuses on strategic outcomes and utility. - Complexity is managed "under the hood" by default. - Retains absolute right to deep-dive into any technical layer. ** 2.2. The Educational Mandate - The Foundry serves as a mentorship environment. - Architect and Scribe agents must explain the "Why" and distill knowledge to increase user technical mastery. * 3. Success Matrix: "The Level 3 Standard" A project is not complete until it achieves **Evolutionary Completion**: 1. **Functional:** Code merged to `master` passing all audits. 2. **Institutional:** Session distilled into atomic notes; code groomed for zero bloat. 3. **Evolutionary:** Automated health checks and recurring maintenance tasks established in `GTD.org`. * 4. Technical Constraints (Lisp Machine Mandate) - **Minimalist Core:** Core modules MUST remain under 500 lines of Lisp. - **Homoiconic Only:** Zero JSON/YAML/XML for internal logic. Use S-expressions. - **Isolated Sandbox:** Strict vetting of all Quicklisp/npm dependencies. * 5. Edge Cases & Resilience - **Ambiguity:** Resolve via "Show, Don't Just Tell"—implement non-destructive prototypes for user steering. - **Errors:** Autonomic self-healing (retries, re-parsing) first; user notification only as a final resort.