memex/projects/org-skill-architect/PROTOCOL.org

PROTOCOL: Skill - Architect Agent

• 1. Architectural Intent
• 2. Semantic Interfaces
  • 2.1 Requirements Perception
  • 2.2 Blueprint Actuation
  • 2.3 Memory Retrieval
• 3. Integration with PSF Lifecycle

1. Architectural Intent

This protocol defines the shared Lisp interfaces for the Architect skill. It ensures a rigorous "Consensus Loop" by defining how the Architect perceives requirements and actuates blueprints.

Following the Literate Mandate, the Architect skill's own implementation must be generated from its Org-mode source.

2. Semantic Interfaces

2.1 Requirements Perception

(defun architect-perceive-frozen-prd (project-name)
  "Checks if a project has a FROZEN PRD.
   Returns a plist: (:status :frozen :path \"path/to/PRD.org\") or NIL."
  )

2.2 Blueprint Actuation

(defun architect-actuate-protocol (project-name blueprint-content)
  "Physically writes the PROTOCOL.org file.
   Input: project name and generated Org content.
   Returns a success message or error signal."
  )

2.3 Memory Retrieval

(defun architect-query-institutional-memory (context-tags)
  "Retrieves relevant architectural patterns from notes/institutional-memory.org.
   Input: tags like :emacs:gtd:psf.
   Returns a list of relevant patterns/learnings."
  )

3. Integration with PSF Lifecycle

The Architect is triggered when a project transitions from `:DEMAND` to `:BLUEPRINT`. Its output (a SIGNED Protocol) is the "Safety Gate" for the Analyst phase.