Normalize all passepartout-economics to inline wiki links
Replaced every bottom-of-section 'See also:' block with inline Org-mode file: links at the first natural mention in body text. All 29 files across the economics directory now use wiki-style inline cross-references rather than standalone reference blocks.
This commit is contained in:
@@ -10,7 +10,7 @@ Three standard dialects: CLIF (Common Logic Interchange Format), CGIF (Conceptua
|
||||
|
||||
**Relevance to Passepartout**
|
||||
|
||||
The fact store interchange format. Passepartout's fact store uses plists internally — fast, native to Lisp, zero serialization cost. But between instances (Agora sync, backup/restore, export), a standardized format is needed. CLIF is a strong candidate because its first-order logic is a direct match for the gate rules ACL2 verifies. A CLIF-to-ACL2 translator is mechanically straightforward — both operate on first-order formulas.
|
||||
The fact store interchange format. Passepartout's fact store uses plists internally — fast, native to Lisp, zero serialization cost. But between instances (Agora sync, backup/restore, export), a standardized format is needed. CLIF is a strong candidate because its first-order logic is a direct match for the [[file:gate-rule-encoding.org][gate rules]] ACL2 verifies. A CLIF-to-ACL2 translator is mechanically straightforward — both operate on first-order formulas.
|
||||
|
||||
The dialect architecture mirrors Passepartout. CL's defining insight: define abstract semantics, let any concrete syntax map to it, get interoperability for free. This is the exact same pattern as Passepartout's "one gate stack, many skills" — the gate stack defines the security ontology (abstract semantics), and skills (dialects) map their operations to it. CL's approach validates Passepartout's design choice and provides a theoretical framework for it.
|
||||
|
||||
@@ -43,9 +43,4 @@ Common Logic is relevant not as something to implement or replace, but as:
|
||||
4. A bridge to RDF/OWL data sources
|
||||
5. A cautionary example for the CIC prover design (careful about higher-order scope)
|
||||
|
||||
The right time to integrate it: when Agora Notes need a standard knowledge interchange format for inter-instance communication. Before that, it is a reference worth reading but not implementing.
|
||||
|
||||
See also:
|
||||
[[file:sufficiency-flip.org][Sufficiency flip]]
|
||||
[[file:gate-rule-encoding.org][Gate rule encoding]]
|
||||
[[file:cost-structure.org][Cost structure]]
|
||||
The right time to integrate it: when Agora Notes need a standard knowledge interchange format for inter-instance communication. Before that, it is a reference worth reading but not implementing. The CL approach informs the [[file:sufficiency-flip.org][sufficiency flip]] strategy and the [[file:cost-structure.org][cost structure]] of encoding domain knowledge.
|
||||
|
||||
Reference in New Issue
Block a user