6e992cc0c5
- Rename 'three-pronged' folder to 'knowledge-layers' — prong metaphor
was misleading (implied parallel tines), replaced with epistemic layers
(deductive base, empirical middle, probabilistic oracle — vertical stack)
- Collapse 11 overlapping files into 3 coherent documents:
- knowledge-layers/_index.org: core framework (two engines + one store,
World Model formula, 0-14 layer table, provenance store design,
conflict resolution, cold-start, stage mapping)
- knowledge-layers/practical-implications.org: design-world-aware-of-
physics, 10 powers, Schafmeister existence proof, epistemic transparency
- knowledge-layers/neurological-empirical.org: neural networks in
provenance framework (kept intact)
- Relocate wolfram/mathematica and Schafmeister docs to ideas/viability/
- Integrate into main architecture _index.org:
- Gate: expanded from two vectors (ACL2+LLM) to three (deductive,
provenance/empirical, LLM oracle)
- Autodidactic loop: split into Track 1 (deductive hardening, fast)
and Track 2 (empirical validation, slow, experimental-feedback-driven)
- See also: added Knowledge Layers cross-reference
- Add all-lisp geometry engine note (ideas/lisp-geometry-engine.org) as
concrete illustration of the empirical layer's effect on design work
- Rebuild site: 148 files, 0 errors
1.5 KiB
Phase 0
Phase 0 spans 10 to 10² users. The system is live but barely visible. See the Impact overview for context.
Verification: Nothing breaks. The conventional world does not notice. First enterprise compliance savings ($200K→$50K). First gate rule packages. Unit economics demonstrated.
Social protocol: First organized communities using the full bundle (identity + publishing + payments + contracts + governance). The experience of unified identity — one account replacing five platforms — creates a new expectation: software should be integrated, not siloed. First creator migration: an OnlyFans or Patreon refugee who cannot be deplatformed discovers censorship resistance is not abstract — it is the reason they still have an income.
Financial services: None at this scale. The first enterprise compliance savings are in general regulated industries (pharma, finance compliance), not in core banking or markets. The protocol is not yet a financial services product.
Economics: Verification revenue from gateway subscriptions and gate rules ($50-200K per enterprise). Social protocol revenue from community fees and creator subscriptions ($1-5M). Small. Insufficient to sustain development — the system is self-developing through the bootstrap loop, not dependent on this revenue.