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
20 lines
1.8 KiB
Org Mode
20 lines
1.8 KiB
Org Mode
:PROPERTIES:
|
|
:ID: aa6d062e-a520-5d14-8773-00687ed9c689
|
|
:END:
|
|
#+title: Competitive Moats
|
|
#+filetags: :passepartout:economics:moats:competition:
|
|
|
|
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):**
|
|
1. **Domain-specific gate rules** — thin. A few hundred lines of Lisp data. Write once, trivial to copy. Not a real moat.
|
|
2. **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.
|
|
3. **Evaluation harness (regression suite)** — thousands of test cases accumulated from every bug fix. Cannot be ingested from public data. Strongest residual moat.
|
|
4. **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: [[file:infrastructure-lock-in.org][Infrastructure lock-in]], [[file:verification-monopoly.org][Verification monopoly]], [[file:evaluation-harness.org][Evaluation harness]], [[file:patent-strategy.org][Patent strategy]], [[file:licensing.org][Licensing]]
|