All 117 inter-node links now use [[file:node-name.org][title]] format which renders as clickable hyperlinks in both Emacs (C-c C-o) and web-based org renderers (Gitea, GitHub). Each node retains its :ID: UUID property for Emacs org-roam database features (backlinks, capturing, node-find). Prev format: [[id:uuid][title]] — Emacs only, dead text on web New format: [[file:name.org][title]] — works everywhere
20 lines
1.1 KiB
Org Mode
20 lines
1.1 KiB
Org Mode
:PROPERTIES:
|
|
:ID: c34940cc-090e-57c4-8020-e78b1d32b96c
|
|
:END:
|
|
#+title: Domain Gate Rule Subscriptions
|
|
#+filetags: :passepartout:revenue:gate-rules:compliance:subscription:
|
|
|
|
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.
|
|
|
|
See also: [[file:gate-rule-encoding.org][Gate rule encoding]], [[file:verification-appliance.org][Verification appliance]], [[file:evaluation-harness.org][Evaluation harness]], [[file:infrastructure-lock-in.org][Infrastructure lock-in]]
|