303e8c6306
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
1.8 KiB
Competitive Moats
Re-evaluated: time is not the primary moat. A Phase 4+ Passepartout fed on Wikipedia + Wikidata can build a general ontology in two weeks. The organic growth advantage collapses for general knowledge.
Actual moats (weaker than initially assumed):
- Domain-specific gate rules — thin. A few hundred lines of Lisp data. Write once, trivial to copy. Not a real moat.
- Empirical decision history — every HITL decision is a Merkle fact. A fresh instance has none. Makes your instance more valuable but doesn't prevent competition — it's a switching cost, not a barrier to entry.
- Evaluation harness (regression suite) — thousands of test cases accumulated from every bug fix. Cannot be ingested from public data. Strongest residual moat.
- Infrastructure integration — specific Docker compose layouts, Traefik patterns, Authentik configs encoded as gate rules. A competitor's infrastructure is different.
Strongest competitor strategy: Not copying your gate rules — offering the same architecture as a service with their own pre-seeded general knowledge and a consulting engagement to customize gate rules. The AGPL prevents closing the architecture but does not prevent offering it as a service with a customization layer.
The defensible business is services, not product. The defensible entity is "the organization that best understands how to adapt Passepartout to your domain" — not "the organization that owns Passepartout."
See also: Infrastructure lock-in, Verification monopoly, Evaluation harness, Patent strategy, Licensing