48 lines
2.8 KiB
Org Mode
48 lines
2.8 KiB
Org Mode
#+TITLE: PRD: Org-Agent Memex (Knowledge Management Standards)
|
|
#+STATUS: FROZEN
|
|
#+AUTHOR: Agent
|
|
#+CREATED: [2026-03-31 Tue 11:45]
|
|
|
|
* 1. Purpose
|
|
Define the functional and technical requirements for an integrated Org-mode workflow that synchronizes Atomic Notes (Zettelkasten) and GTD task management. This PRD serves as the foundational specification for the "Memex Agent" skill.
|
|
|
|
* 2. User Needs
|
|
|
|
** 2.1 Unified Knowledge & Task Capture
|
|
As a user (Amr), I need a single entry point for all information.
|
|
- All new captures MUST land in `memex/inbox.org`.
|
|
- No other files are permitted for general inbox capture.
|
|
|
|
** 2.2 Strict Metadata Compliance
|
|
I need my PKM system to maintain high structural integrity.
|
|
- Every Org item must have a `:PROPERTIES:` drawer with a `:CREATED:` property in `[YYYY-MM-DD Day HH:MM]` format.
|
|
- Collaborative items must use `:AUTHOR:` and `:ASSIGNED:` properties.
|
|
- State changes MUST be tracked in a `:LOGBOOK:` drawer following the `:PROPERTIES:` drawer.
|
|
|
|
** 2.3 Automated Task Lifecycle
|
|
I need the agent to manage the "boring" parts of GTD.
|
|
- **Automatic NEXT Promotion:** When a `NEXT` item in a sequential project is marked `DONE`, the agent MUST automatically promote the subsequent `TODO` item to `NEXT`.
|
|
- **Agenda Coordination:** The agent must place items requiring my attention as `TODO` (planned) or `NEXT` (immediate) in my agenda.
|
|
|
|
** 2.4 Mobile Sovereignty
|
|
I need to interact with my Memex on the go.
|
|
- The system must remain compatible with Markor (for text editing) and Orgzly (for agenda management) on Android.
|
|
- Sync must be handled via a Git-based state machine (commits as source of truth).
|
|
|
|
** 2.5 Agentic Distillation (The Scribe)
|
|
I need my daily logs transformed into timeless knowledge.
|
|
- The agent must read from immutable daily logs (`daily/`).
|
|
- It must extract "Evergreen" concepts and write them to `notes/` as atomic notes.
|
|
- Atomic notes must have descriptive snake_case filenames (no dates) and a `Source:` backlink.
|
|
|
|
* 3. Success Criteria
|
|
- [ ] **Promotion Logic:** Agent successfully identifies a completed `NEXT` task and promotes its successor in a sequential project.
|
|
- [ ] **Metadata Audit:** Agent can identify and flag any Org item missing `:CREATED:` or `:LOGBOOK:` headers.
|
|
- [ ] **Scribe Accuracy:** Agent extracts a concept from a daily log and creates a correctly formatted atomic note in `notes/` without user intervention.
|
|
- [ ] **Git Synchronization:** All changes are automatically committed to the local repository for versioning and state tracking.
|
|
|
|
* 4. Constraints
|
|
- **Single User/Single Agent:** Designed exclusively for Amr and his Assistant. No multi-user conflict resolution.
|
|
- **Environment Driven:** All identity and path values must be pulled from `.env` (e.g., `$MEMEX_USER`, `$MEMEX_NOTES`).
|
|
- **Org-mode Native:** No external databases. The `.org` files ARE the database.
|