4c38127b45
Merged: - verification-monopoly + evaluation-harness + collective-regression-suite - licensing + patent-strategy → strategy/ - moats + infrastructure-lock-in - lisp-economics + cost-structure - domain-gate-packages + gate-rule-encoding - revenue-table + first-mover-window → revenue.org Moved: sufficiency-flip, upgrade-lifecycle → strategy/ native-org-knowledge-base → architecture/ Renamed: revenue-hub.org → revenue.org Deleted: passepartout-economics.md orphan
37 lines
2.5 KiB
Org Mode
37 lines
2.5 KiB
Org Mode
:PROPERTIES:
|
|
:CREATED: [2026-05-24 Sun]
|
|
:ID: c34940cc-090e-57c4-8020-e78b1d32b96c
|
|
:ID: 45ea493b-94ad-5885-aa65-0c846e5c3c1d
|
|
:END:
|
|
#+title: Domain Gate Packages — Encoding and Products
|
|
#+filetags: :passepartout:revenue:gate-rules:compliance:subscription:encoding:llm:translation:
|
|
|
|
* Encoding — How Rules Are Translated from Codified Domains
|
|
|
|
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 sufficiency flip economically viable — once gates are encoded, verification is near-free. The resulting rules are packaged into domain gate packages that can be reused across deployments.
|
|
|
|
* Products — How Rules Are Packaged and Sold
|
|
|
|
Pre-verified gate rule packages for specific compliance domains. Translated from published regulations by the LLM, verified by ACL2, reviewed by a human for the 5% ambiguous edge cases.
|
|
|
|
- HIPAA package: $50K/yr
|
|
- SOC2 package: $50K/yr
|
|
- GDPR package: $50K/yr
|
|
- FedRAMP package: $100K/yr
|
|
- Combined enterprise: $250K/yr
|
|
|
|
Switching costs are high — changing packages means re-verifying the fact store against new rules. The infrastructure lock-in compounds: a hospital at $250K/yr in year one grows to $500K-$1M by year five as more packages are added and the fact store becomes more valuable than the software itself.
|
|
|
|
20 subscriptions in year one = $1M-$5M. These packages each wrap the social protocol Note primitive into a domain-specific authorization boundary. These packages are verified using the verification appliance and scored by the evaluation harness.
|