Fix Untitled titles: convert all YAML frontmatter to org-style headers

projects/passepartout/architecture/design/foundation/_index.org

@@ -3,6 +3,7 @@
 :CREATED:  [2026-05-11 Mon]
 :ID:       2c880b7d-e97f-459a-88d1-61fac760a0dd
 :END:
+#+title: Foundation
 * Foundation
 
 - [[file:non-negotiable-identity.org][Non-Negotiable Identity]] — - Pure Common Lisp + Org-mode. No JSON. No YAML. No external databases.

projects/passepartout/architecture/design/foundation/homoiconicity-as-foundation.org

@@ -1,16 +1,8 @@
----
-title: Homoiconicity as Foundation
-type: reference
-tags: :passepartout:architecture:
----
-
-* Homoiconicity as Foundation
 :PROPERTIES:
-:ID:       7dee11bc-72b0-43a3-9bc8-2f022b59ba49
-:ID:       design-homoiconicity
-:CREATED:  [2026-05-07 Wed]
-:WEIGHT:  40
+:CREATED:  [2026-06-04 Thu]
 :END:
+#+title: Homoiconicity as Foundation
+#+filetags: :passepartout:architecture:
 
 Common Lisp is homoiconic: code and data share the same representation. A Lisp program is a list, and a list is a Lisp program. This is usually presented as a curiosity, an interesting property that enables macros. In Passepartout, it is the foundational enabling property of the entire self-modification architecture.
 

projects/passepartout/architecture/design/foundation/non-negotiable-identity.org

@@ -1,16 +1,8 @@
----
-title: Non-Negotiable Identity
-type: reference
-tags: :passepartout:architecture:
----
-
-* Non-Negotiable Identity
 :PROPERTIES:
-:ID:       0a33bd83-ff3c-4eac-bc97-83eb6702051a
-:ID:       design-identity
-:CREATED:  [2026-05-07 Wed]
-:WEIGHT:  40
+:CREATED:  [2026-06-04 Thu]
 :END:
+#+title: Non-Negotiable Identity
+#+filetags: :passepartout:architecture:
 
 - Pure Common Lisp + Org-mode. No JSON. No YAML. No external databases.
 - Single-address-space memory (Lisp hash tables in RAM — the agent IS the memory).

projects/passepartout/architecture/design/foundation/one-single-agent.org

@@ -1,16 +1,8 @@
----
-title: One Single Agent
-type: reference
-tags: :passepartout:architecture:
----
-
-* One Single Agent
 :PROPERTIES:
-:ID:       92e314a1-a650-4878-958a-9646aef4e032
-:ID:       design-multi-agent-default
-:CREATED:  [2026-05-07 Wed]
-:WEIGHT:  40
+:CREATED:  [2026-06-04 Thu]
 :END:
+#+title: One Single Agent
+#+filetags: :passepartout:architecture:
 
 The AI industry has developed an intuition toward multi-agent systems as the default solution to hard problems. Multiple agents spawn, delegate, coordinate, debate, and consensus their way toward solutions. This pattern is compelling in demos and genuinely useful in specific contexts — but it has become a default assumption that warrants scrutiny.
 

projects/passepartout/architecture/design/foundation/org-mode-as-unified-ast.org

@@ -1,16 +1,8 @@
----
-title: Org-Mode as Unified AST
-type: reference
-tags: :passepartout:architecture:
----
-
-* Org-Mode as Unified AST
 :PROPERTIES:
-:ID:       4bf2264c-db97-4d7b-9972-5a5d052d80be
-:ID:       design-org-unified-ast
-:CREATED:  [2026-05-07 Wed]
-:WEIGHT:  40
+:CREATED:  [2026-06-04 Thu]
 :END:
+#+title: Org-Mode as Unified AST
+#+filetags: :passepartout:architecture:
 
 Passepartout makes a bet that most systems consider too expensive to place: that humans and machines should share the same file format. That bet is Org-mode.
 

projects/passepartout/architecture/design/foundation/the-unified-memory-argument.org

@@ -1,16 +1,8 @@
----
-title: The Unified Memory Argument
-type: reference
-tags: :passepartout:architecture:
----
-
-* The Unified Memory Argument
 :PROPERTIES:
-:ID:       1076101b-6201-4461-81e5-38d7886b66af
-:ID:       design-unified-memory
-:CREATED:  [2026-05-07 Wed]
-:WEIGHT:  40
+:CREATED:  [2026-06-04 Thu]
 :END:
+#+title: The Unified Memory Argument
+#+filetags: :passepartout:architecture:
 
 If single-agent architecture is the decision, unified memory becomes the mechanism that makes it viable. The critical question is not "how many agents" but "how does the agent manage context without saturating."