amr/memex
1
0
Fork 0
Code Issues 12 Pull Requests Actions Packages Projects 1 Releases Wiki Activity

feat(arch): implement 'Code as Thought' architecture and formalize PSF Consensus Loop

Browse Source
This commit is contained in:
Amr Gharbeia
2026-03-31 13:03:26 -04:00
parent 5a9129132e
commit 1712b1e4a9
114 changed files with 3652 additions and 2581 deletions
Download Patch File Download Diff File Expand all files Collapse all files

46
system/skills/org-skill-gtd.org
View File

@@ -1,46 +0,0 @@
#+TITLE: SKILL: Getting Things Done (GTD) (Execution Hub)
#+ID: skill-gtd
#+STARTUP: content
#+FILETAGS: :gtd:execution:workflow:
* Overview
This skill defines the **GTD Execution Hub**, the single source of truth for all commitments within the Memex. It governs how the `org-agent` perceives priorities and tracks the progress of the [[file:personal-software-foundry.org][Personal Software Foundry (PSF)]] Consensus Loop.
* Philosophy
The Memex follows the **Allen-Sovereign Methodology**:
- **Capture:** No friction. If a thought exists, it must be in the `inbox.org`.
- **Clarify:** Every item is either trash, reference, or a commitment with a defined "Next Action."
- **DAG Structure:** Following the **`org-gtd` v4.0 standard**, projects are not linear lists but graphs of dependencies managed via `:TRIGGER:` and `:BLOCKER:` properties.
* The Modular GTD Structure
To prevent "Context Rot," the GTD system is partitioned across specialized files:
- [[file:../../inbox.org][inbox.org]]: High-frequency capture.
- [[file:../../gtd.org][gtd.org]]: Active projects and the current DAG of commitments.
- [[file:org-skill-scribe.org][Scribe Agent]]: Automatically moves items from Dailies into the knowledge graph.
* Operational Lifecycle
** 1. Perception (The Weekly Review)
The agent assists the Sovereign Executive in scanning `gtd.org`. It identifies "Stalled" projects—those marked as `NEXT` but with no active sub-tasks or blocked by legacy items.
** 2. Shadow Orchestration
The PSF uses the `:PSF-STATE:` property within `gtd.org` to track the engineering lifecycle without polluting the standard GTD keywords. The agent monitors this property to decide which "Safety Gate" to trigger next.
** 3. Evolution
Completed projects are not simply deleted; they are processed by the Scribe to extract permanent learnings into [[file:../institutional-memory.org][Institutional Memory (SOUL)]] before the GTD headline is marked `DONE`.
* Symbolic Implementation
The following logic defines how the agent interacts with the `org-gtd` system.
#+begin_src lisp
(defun gtd-perceive-commitments ()
"Returns a list of all active NEXT actions across the agenda files."
(let ((gtd-file (expand-file-name "~/memex/gtd.org")))
(kernel-log "GTD - Scanning commitments in ~a" gtd-file)
;; Implementation of org-gtd v4.0 DAG perception
(org-agent:run-shell-command (format nil "grep '^\*\* NEXT' ~a" gtd-file))))
#+end_src
* See Also
- [[file:org-gtd-v4-migration.org][org-gtd v4.0 Migration Guide]]
- [[file:personal-software-foundry.org][Personal Software Foundry]]

1
system/skills/org-skill-gtd.org Symbolic link
View File

@@ -0,0 +1 @@
/home/user/memex/notes/org-skill-gtd.org