Fix Untitled titles: convert all YAML frontmatter to org-style headers
This commit is contained in:
Hermes
@@ -3,6 +3,7 @@
|
||||
:CREATED: [2026-05-11 Mon]
|
||||
:ID: 7cb7df45-982f-4f5a-afee-36cd5595c25c
|
||||
:END:
|
||||
#+title: The Symbolic Engine
|
||||
* The Symbolic Engine
|
||||
|
||||
- [[file:the-five-architecture-options.org][The Five Architecture Options]] — The symbolic engine must relate to the human memex. The relationship is not obvi
|
||||
|
||||
@@ -1,16 +1,8 @@
|
||||
---
|
||||
title: Abstract Fact Store Interface — Modular by Design
|
||||
type: reference
|
||||
tags: :passepartout:architecture:
|
||||
---
|
||||
|
||||
* Abstract Fact Store Interface — Modular by Design
|
||||
:PROPERTIES:
|
||||
:ID: 64be38aa-56ca-4960-92e1-f3fc4cb51a2e
|
||||
:ID: design-fact-interface
|
||||
:CREATED: [2026-05-10 Sun]
|
||||
:WEIGHT: 40
|
||||
:CREATED: [2026-06-04 Thu]
|
||||
:END:
|
||||
#+title: Abstract Fact Store Interface — Modular by Design
|
||||
#+filetags: :passepartout:architecture:
|
||||
|
||||
The fact store is accessed through an abstract API. The Merkle DAG (or any future backing store) is an implementation behind this interface, not a dependency that code throughout the system calls directly.
|
||||
|
||||
|
||||
@@ -1,16 +1,8 @@
|
||||
---
|
||||
title: Cardinality Policies — Singular, Dual, and Plural Facts
|
||||
type: reference
|
||||
tags: :passepartout:architecture:
|
||||
---
|
||||
|
||||
* Cardinality Policies — Singular, Dual, and Plural Facts
|
||||
:PROPERTIES:
|
||||
:ID: f23e5518-bf2a-459e-8d2e-a9645fad76ac
|
||||
:ID: design-cardinality
|
||||
:CREATED: [2026-05-08 Fri]
|
||||
:WEIGHT: 40
|
||||
:CREATED: [2026-06-04 Thu]
|
||||
:END:
|
||||
#+title: Cardinality Policies — Singular, Dual, and Plural Facts
|
||||
#+filetags: :passepartout:architecture:
|
||||
|
||||
Classical logic requires consistency. A contradiction implies everything (=ex contradictione quodlibet=). Screamer, as a constraint solver, also requires consistency — a contradictory constraint set has no solutions. But the symbolic engine operates across domains where the meaning of contradiction is fundamentally different. The correct question is not "is this consistent?" but "what cardinality of truth does this domain support?"
|
||||
|
||||
|
||||
@@ -1,16 +1,8 @@
|
||||
---
|
||||
title: Ephemeral First, Persistent Later
|
||||
type: reference
|
||||
tags: :passepartout:architecture:
|
||||
---
|
||||
|
||||
* Ephemeral First, Persistent Later
|
||||
:PROPERTIES:
|
||||
:ID: 1b88cec6-76d8-4496-ae36-1bf16b5bc962
|
||||
:ID: design-ephemeral-first
|
||||
:CREATED: [2026-05-10 Sun]
|
||||
:WEIGHT: 40
|
||||
:CREATED: [2026-06-04 Thu]
|
||||
:END:
|
||||
#+title: Ephemeral First, Persistent Later
|
||||
#+filetags: :passepartout:architecture:
|
||||
|
||||
The architecture note's Option 5 (ephemeral facts, no disk persistence) is the correct first implementation. Three reasons:
|
||||
|
||||
|
||||
@@ -1,16 +1,8 @@
|
||||
---
|
||||
title: How Categories Grow — The Organic Ontology
|
||||
type: reference
|
||||
tags: :passepartout:architecture:
|
||||
---
|
||||
|
||||
* How Categories Grow — The Organic Ontology
|
||||
:PROPERTIES:
|
||||
:ID: ce124de6-6777-4dca-aaf3-57e842c1855b
|
||||
:ID: design-organic-ontology
|
||||
:CREATED: [2026-05-08 Fri]
|
||||
:WEIGHT: 40
|
||||
:CREATED: [2026-06-04 Thu]
|
||||
:END:
|
||||
#+title: How Categories Grow — The Organic Ontology
|
||||
#+filetags: :passepartout:architecture:
|
||||
|
||||
Whitehead's /Principia Mathematica/ took over 300 pages to define the logical foundations before it could prove that one plus one equals two. Every category introduced carried a burden of justification. Every inference rule had to be demonstrated sound. This is the classical approach to ontology: define everything upfront, exhaustively, formally.
|
||||
|
||||
|
||||
@@ -1,16 +1,8 @@
|
||||
---
|
||||
title: Knowledge Graph Type Hierarchy — Structural Anti-Self-Reference (v3.0.0)
|
||||
type: reference
|
||||
tags: :passepartout:architecture:
|
||||
---
|
||||
|
||||
* Knowledge Graph Type Hierarchy — Structural Anti-Self-Reference (v3.0.0)
|
||||
:PROPERTIES:
|
||||
:ID: 699de53a-06ff-4815-9f9d-70b006d372b8
|
||||
:ID: design-kg-type-hierarchy
|
||||
:CREATED: [2026-05-14 Thu]
|
||||
:WEIGHT: 40
|
||||
:CREATED: [2026-06-04 Thu]
|
||||
:END:
|
||||
#+title: Knowledge Graph Type Hierarchy — Structural Anti-Self-Reference (v3.0.0)
|
||||
#+filetags: :passepartout:architecture:
|
||||
|
||||
The same type-theoretic principle that governs the gate stack can be applied to the knowledge graph itself. When VivaceGraph ships (v3.0.0), every entity carries a ~:pm-type-level~ metadata field. Queries cannot return entities of the same level as the querying function. Self-referential knowledge becomes structurally impossible — no "this entity defines its own type level."
|
||||
|
||||
|
||||
@@ -1,16 +1,8 @@
|
||||
---
|
||||
title: Merkle DAG for Version History
|
||||
type: reference
|
||||
tags: :passepartout:architecture:
|
||||
---
|
||||
|
||||
* Merkle DAG for Version History
|
||||
:PROPERTIES:
|
||||
:ID: d08f4f7b-6800-4625-a8f6-f91b3231ae2e
|
||||
:ID: design-merkle-dag
|
||||
:CREATED: [2026-05-10 Sun]
|
||||
:WEIGHT: 40
|
||||
:CREATED: [2026-06-04 Thu]
|
||||
:END:
|
||||
#+title: Merkle DAG for Version History
|
||||
#+filetags: :passepartout:architecture:
|
||||
|
||||
Every fact is versioned. Every =(:entity :relation)= pair forms its own independent chain in a Merkle DAG. This is not new infrastructure — it is a new occupant of Passepartout's existing Merkle-tree memory system (v0.2.0).
|
||||
|
||||
|
||||
@@ -1,16 +1,8 @@
|
||||
---
|
||||
title: Ontology Versioning — How Worldviews Change Without Losing Perspective
|
||||
type: reference
|
||||
tags: :passepartout:architecture:
|
||||
---
|
||||
|
||||
* Ontology Versioning — How Worldviews Change Without Losing Perspective
|
||||
:PROPERTIES:
|
||||
:ID: 49104db7-0c41-4507-8755-42b4a48b7cc9
|
||||
:ID: design-ontology-versioning
|
||||
:CREATED: [2026-05-10 Sun]
|
||||
:WEIGHT: 40
|
||||
:CREATED: [2026-06-04 Thu]
|
||||
:END:
|
||||
#+title: Ontology Versioning — How Worldviews Change Without Losing Perspective
|
||||
#+filetags: :passepartout:architecture:
|
||||
|
||||
Ontology refactoring is not a schema migration. It is a worldview change. When you split =:secret-file= into =:crypto-secret= and =:plaintext-secret=, you are not renaming columns. You are reclassifying what a file *is* — and every Screamer deduction that crossed the old category boundary now means something different under the new distinction.
|
||||
|
||||
|
||||
@@ -1,16 +1,8 @@
|
||||
---
|
||||
title: The Awakening — Sufficiency Criterion
|
||||
type: reference
|
||||
tags: :passepartout:architecture:
|
||||
---
|
||||
|
||||
* The Awakening — Sufficiency Criterion
|
||||
:PROPERTIES:
|
||||
:ID: 5788ad0f-45fb-4b2d-a3ab-09a4d95f351c
|
||||
:ID: design-awakening
|
||||
:CREATED: [2026-05-08 Fri]
|
||||
:WEIGHT: 40
|
||||
:CREATED: [2026-06-04 Thu]
|
||||
:END:
|
||||
#+title: The Awakening — Sufficiency Criterion
|
||||
#+filetags: :passepartout:architecture:
|
||||
|
||||
The symbolic index begins its life as a lossy construct. The initial extraction from prose — LLM proposals verified by Screamer — is built from an uncertain foundation. Some facts are correct. Some are missing. Some are wrong.
|
||||
|
||||
|
||||
@@ -1,16 +1,8 @@
|
||||
---
|
||||
title: The Chosen Path: Option 4, Starting with Option 5
|
||||
type: reference
|
||||
tags: :passepartout:architecture:
|
||||
---
|
||||
|
||||
* The Chosen Path: Option 4, Starting with Option 5
|
||||
:PROPERTIES:
|
||||
:ID: b21917d8-cb6e-4959-96c0-9326b0611134
|
||||
:ID: design-chosen-path
|
||||
:CREATED: [2026-05-08 Fri]
|
||||
:WEIGHT: 40
|
||||
:CREATED: [2026-06-04 Thu]
|
||||
:END:
|
||||
#+title: The Chosen Path: Option 4, Starting with Option 5
|
||||
#+filetags: :passepartout:architecture:
|
||||
|
||||
The one-memex-two-indices architecture (Option 4) is the correct long-term architecture. The prose is the ground truth. The symbolic index is a derived view that can be rebuilt. The neural index handles what the symbolic index cannot — semantic search, fuzzy matching, associative leaps.
|
||||
|
||||
|
||||
@@ -1,16 +1,8 @@
|
||||
---
|
||||
title: The Five Architecture Options
|
||||
type: reference
|
||||
tags: :passepartout:architecture:
|
||||
---
|
||||
|
||||
* The Five Architecture Options
|
||||
:PROPERTIES:
|
||||
:ID: e9c7a384-b42d-4dff-8da7-d4b62bb69956
|
||||
:ID: design-five-options
|
||||
:CREATED: [2026-05-08 Fri]
|
||||
:WEIGHT: 40
|
||||
:CREATED: [2026-06-04 Thu]
|
||||
:END:
|
||||
#+title: The Five Architecture Options
|
||||
#+filetags: :passepartout:architecture:
|
||||
|
||||
The symbolic engine must relate to the human memex. The relationship is not obvious because knowledge lives in two incompatible forms: natural language prose (what the human reads and writes) and formal facts (what the symbolic engine reasons about). The translation between them is lossy by nature. The architecture is defined by how it handles that lossiness.
|
||||
|
||||
|
||||
@@ -1,16 +1,8 @@
|
||||
---
|
||||
title: The Gate-to-Fact Bootstrap — Extracting the First Ontology from Code
|
||||
type: reference
|
||||
tags: :passepartout:architecture:
|
||||
---
|
||||
|
||||
* The Gate-to-Fact Bootstrap — Extracting the First Ontology from Code
|
||||
:PROPERTIES:
|
||||
:ID: 28a8caf7-c0a1-4154-8ca3-3a0d11cf121a
|
||||
:ID: design-gate-bootstrap
|
||||
:CREATED: [2026-05-08 Fri]
|
||||
:WEIGHT: 40
|
||||
:CREATED: [2026-06-04 Thu]
|
||||
:END:
|
||||
#+title: The Gate-to-Fact Bootstrap — Extracting the First Ontology from Code
|
||||
#+filetags: :passepartout:architecture:
|
||||
|
||||
The Dispatcher gate stack already encodes an implicit ontology. Every gate vector asserts the existence of a category of things:
|
||||
|
||||
|
||||
@@ -1,16 +1,8 @@
|
||||
---
|
||||
title: The LLM as Proposer — Verified Extraction
|
||||
type: reference
|
||||
tags: :passepartout:architecture:
|
||||
---
|
||||
|
||||
* The LLM as Proposer — Verified Extraction
|
||||
:PROPERTIES:
|
||||
:ID: 02798a39-c12b-4835-bc61-34f57a860cdb
|
||||
:ID: design-llm-proposer
|
||||
:CREATED: [2026-05-08 Fri]
|
||||
:WEIGHT: 40
|
||||
:CREATED: [2026-06-04 Thu]
|
||||
:END:
|
||||
#+title: The LLM as Proposer — Verified Extraction
|
||||
#+filetags: :passepartout:architecture:
|
||||
|
||||
The LLM cannot be trusted to populate the symbolic index directly. Its outputs are sampled, not proven. A probabilistic extraction feeding a deterministic engine defeats the purpose of being deterministic.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user