Files
hermes-brain/ideas/passepartout-economics/upgrade-lifecycle.org
Hermes 9b2be10c77 Restructure economics doc into 27 org-roam interlinked nodes
Replace monolithic passepartout-economics.org with directory of
org-roam style nodes, each with :ID: property and cross-references
using [[id:uuid][title]] format.

27 nodes organized by theme:
- Core: index, triad overview, agora, stoa
- Revenue: verification appliance, domain gate packages, evaluation
  harness, skill marketplace, agora usernames, PDS service, compute marketplace
- Strategy: investment thesis, moats, licensing, patents, AI industry impact
- Analysis: lisp economics, sufficiency flip, time estimates, cost structure,
  gate rule encoding, upgrade lifecycle, biology parallels, symbolics comparison
- Big money: verification monopoly, infrastructure lock-in

Old file kept as archive with redirect links to new structure.
2026-05-21 19:36:02 +00:00

1.7 KiB

Upgrade and Distribution Lifecycle

Once instances diverge in both code and knowledge, naive git pull breaks things. Passepartout's architecture already has the primitives for safe upgrades:

  • Ontology versioning: every fact stores the ontology version at assertion. On upgrade, facts with old versions are flagged for re-verification.
  • Degradation, not crash: if an upgrade breaks the fact store, the system degrades to the pre-macro state (hash-table fallback, text-scan fallback). Still works — just proves less.
  • Reversible upgrades (Phase 0 undo): every upgrade produces a Merkle snapshot before applying.
  • Delta distribution: upgrades delivered as diffs against the current ontology version. Migration script runs automatically.

The upgrade is verified by the upgraded system before committing. The distributor ships the new gate vector; ACL2 reports which rules are compatible and which need review. The operator reviews only the incompatible subset.

Business model for upgrades:

  • Code upgrades: free (AGPL)
  • Migration scripts: subscription. The verified migration path from current ontology version to new one.
  • Domain knowledge package upgrades: subscription. When HIPAA updates, the healthcare package updates.
  • Verification appliance firmware: bundled with hardware. Signed and verified against hardware root of trust.

See also: Infrastructure lock-in, Verification appliance, Domain gate packages