3e32ea9959
All 31 files from ideas/passepartout-economics/ promoted to ideas/ root. - Subfolder's passepartout-economics.org (42-line index) renamed to triad-index.org to avoid collision with root-level full doc - index.org removed (redundant — triad-index.org replaces it) - Root-level passepartout-economics.org: stripped file:passepartout-economics/ prefix from all cross-references (now simple file:foo.org links) - compliance-framework-mapping.org: same prefix cleanup - All internal file: links within the economics docs already used simple names (no prefix) — they resolve correctly from ideas/ root
18 lines
1.5 KiB
Org Mode
18 lines
1.5 KiB
Org Mode
:PROPERTIES:
|
|
:ID: 45ea493b-94ad-5885-aa65-0c846e5c3c1d
|
|
:END:
|
|
#+title: Gate Rule Encoding from Codified Domains
|
|
#+filetags: :passepartout:gates:rules:encoding:llm:translation:
|
|
|
|
Laws, regulations, standards, procedures, and technical specifications are already written down in structured text. The LLM does not need to *reason* about them — it needs to *translate* them into gate rules and ACL2 theorems.
|
|
|
|
Example: The US Federal Acquisition Regulation (FAR) is ~2,000 pages. A frontier LLM can ingest the FAR and produce a plist of gate rules:
|
|
- (if contract > $250K AND not small-business-set-aside → :deny)
|
|
- (if sole-source AND no justification-documented → :deny, produce-justification)
|
|
|
|
ACL2 verifies the rule set for internal consistency. Screamer checks against existing compliance facts. The human reviews the bootstrap output and approves or corrects individual rules.
|
|
|
|
The key distinction: the LLM is not *extracting knowledge from prose* — it is *translating a known rule system into a formal representation.* The result is not "the LLM's best guess" but "the rule set as stated in the source document, mechanically transcribed."
|
|
|
|
For codified domains, the encoding cost drops from weeks to hours. The only bottleneck is human review of the 5% ambiguous rules. This is what makes the [[file:sufficiency-flip.org][sufficiency flip]] economically viable — once gates are encoded, verification is near-free. The resulting rules are packaged into [[file:domain-gate-packages.org][domain gate packages]] that can be reused across deployments.
|