Monorepo for Aesthetic.Computer aesthetic.computer
core reports
2 folders · 115 files

README.md

Intelligence at the Edges: Master Summary #

A complete philosophical and technical framework for user-owned, decentralized intelligence in Aesthetic Computer


Overview #

This directory contains research and design documents for implementing neural learning primitives in Aesthetic Computer. The work synthesizes three major intellectual traditions:

  1. Bernard Stiegler's Idiotext - Singular memory woven through technical prostheses
  2. Rudy Rucker & Douglas Hofstadter's Gnarliness - Complexity and tangled feedback loops as intelligence
  3. Richard Gabriel's "Worse is Better" - Simple, evolving systems beat complex, planned ones

Together, these form the foundation for a new approach to AI that fundamentally diverges from the Big LLM model (OpenAI, Anthropic, Google).


Reports #

1. Neural Primitives for Aesthetic Computer: Full Stack Report #

8,000+ words | Technical + Philosophical

The complete architectural design for implementing user-owned neural learning primitives in AC.

Key sections:

  • Part 0: Philosophical Grounding
    • 0.0: Worse is Better (vs. Big LLMs)
    • 0.1-0.5: Stiegler's Idiotext, Hyperbolic Spirals, Hebbian Learning
    • 0.5.5: Bidirectional Learning, Karma as Quality/Health, Gnarliness
    • 0.6: Implementation Strategy
  • Part 1: Current Stack Architecture - Integration points in existing AC code
  • Part 2: Neural Primitives Design - API surface, HebbianNet implementation
  • Part 3: Implementation Methods - Digital Ocean Spaces storage, weight sharing
  • Part 4-8: Use cases, roadmap, testing, philosophy alignment

Deliverable: 8-commit implementation plan for pure JavaScript Hebbian networks with karmic tracking, health metrics, and gnarliness visualization.

2. Web Portals vs. Open Web: Why Decentralization Won (1995-2010) #

8,700+ words | Historical Analysis | 40+ Citations

Comprehensive research on the portal wars and the triumph of decentralized web architecture.

Key findings:

  • Portal dominance: Yahoo $125B valuation, AOL 60% of internet traffic (1997-98)
  • The collapse: NASDAQ fell 75%, portals lost to specialized services
  • Why they lost: Google's PageRank, broadband, user-generated content, RSS, social networks
  • Why decentralization won: Innovation at edges, user agency, network effects favored openness
  • AI parallels: Current LLMs = new portals, same mistakes, same fate predicted

Lesson: Centralized control is fragile. Innovation at the edges is unstoppable.


The Unified Argument #

The Problem: Big LLMs are Portals 2.0 #

Dimension Web Portals (1995-2000) Big LLMs (2020-2026)
Model AOL, Yahoo, MSN walled gardens GPT-4, Claude, Gemini monoliths
Strategy Bundle everything, keep users inside Bundle intelligence, API lock-in
Ownership Corporate-controlled content Corporate-controlled weights
Memory Human-curated directories Pre-trained, frozen knowledge
Evolution Static, version releases Static, version releases
Philosophy Cathedral (experts build) Cathedral (experts train)
Failure mode Can't compete with specialized services Can't compete with specialized agents

The Solution: Intelligence at the Edges #

Dimension Open Web (2000-2010) Micro-Organisms (Our Approach)
Model Many specialized services Many tiny neural networks
Strategy Best-of-breed composition Ensemble of micro-brains
Ownership User-controlled (blogs, RSS) User-owned (Spaces storage)
Memory User-generated content Living institutional memory
Evolution Continuous through use Continuous through play
Philosophy Bazaar (users build) Bazaar (pieces learn)
Success Wikipedia, Linux, Internet Predicted (history repeating)

The Mechanism: Worse is Better #

Big LLMs approach (Better is Worse):

  • Build perfect AGI → Takes forever → Proprietary → Users can't modify → Monoculture → Fragile

Our approach (Worse is Better):

  • Build 16-neuron learner → Ships today → User-owned → Users tend/prune/care → Biodiversity → Antifragile

Historical precedent:

  • Unix beat Lisp machines (worse is better)
  • PC beat mainframes (worse is better)
  • Web beat portals (worse is better)
  • Wikipedia beat Britannica (worse is better)
  • Micro-organisms will beat mega-LLMs (worse is better)

The Three Pillars #

Pillar 1: Stiegler's Idiotext (Philosophical Foundation) #

Idiotext = singular memory woven through technical prostheses

Applied to AC:

  • Each piece develops its own tertiary retention (externalized memory)
  • notepat learns how to be played through accumulated usage
  • Weights stored in Digital Ocean Spaces = piece's institutional memory
  • "Reading and writing are equivalent" → Using a piece trains it

Spiral structure:

  • α (alpha): This session's interactions
  • β (beta): This user's history across sessions
  • γ (gamma): This piece's collective patterns
  • δ (delta): Cross-piece global patterns

Hyperbolic geometry:

  • Spirals are HYPERBOLIC (negative curvature), not Euclidean
  • Nested hierarchies naturally represented
  • Can move both outward (learning) and inward (forgetting)

Pillar 2: Gnarliness as Intelligence (Complexity Theory) #

Rudy Rucker: "Gnarly means rich in information but unpredictable" Douglas Hofstadter: "Intelligence is feedback loops, tangled hierarchies, strange loops"

Applied to AC:

  • Forward motion (Hebbian): "Fire together, wire together"
  • Backward motion (Anti-Hebbian): "Fire together, unwire together"
  • Karma tracking: Accumulated experience creates resistance/character
  • Health system: Can thrive (flourish) or sicken (degrade) from use
  • Nonlinear growth: Plateau periods, breakthrough moments, regression phases

The gnarliness formula:

gnarliness = √(weight_variance) + health_diversity + coherence_variance

The intelligence equation:

Forward + Backward + Karma + Health = Tangled Feedback Loops = Gnarliness = Intelligence

Pillar 3: Worse is Better (Engineering Philosophy) #

Richard Gabriel (1991): "Get half of the right thing available so it spreads like a virus"

Applied to AC:

  • Start with 10-100 parameter networks (imperfect but alive)
  • User-owned (stored in Spaces, controllable)
  • Evolves through play (like instruments improving with use)
  • Composes into collective intelligence (ensemble learning)
  • Biodiversity (every user's notepat different)

Why this wins:

  • Scales horizontally (billions of tiny brains)
  • Permissionless innovation (anyone can create micro-organisms)
  • User agency (you own, tend, prune your weights)
  • Graceful degradation (sick pieces don't kill whole system)
  • Character development (instruments that know you)

The Architecture #

Technical Stack #

Storage: Digital Ocean Spaces (CDN-backed, unlimited size)

  • Metadata in MongoDB (architecture, health, gnarliness)
  • Weight files in Spaces (user vs. anonymous buckets)
  • Same pattern as pieces/paintings/tapes

Computation: Progressive Enhancement

  • Phase 1: Pure JavaScript (graspable, zero deps)
  • Phase 2: WebGPU compute shaders (100-1000x faster, optional)
  • Same API, automatic fallback

API Surface:

// Create/train
const model = net.learn.createKarmic({ size: 16 });
model.train(input, output, quality);  // quality = 0-1, not reward

// Care
model.tend();          // Boost health
model.prune(0.3);      // Kill weak connections
model.unlearn(pattern); // Spiral reversal

// Metrics
model.overallHealth()  // { alive, flourishing, mean, phase }
model.gnarliness()     // Complexity measure
model.exportWeights()  // Serialize to Spaces

KarmicHebbianNet (Core Engine) #

Not a morality system - it's a quality/health system:

class KarmicHebbianNet extends HebbianNet {
  weightHealth[i][j]      // 0 = dead, 1 = healthy, >1 = flourishing
  usageCoherence[i][j]    // Chaotic vs. coherent patterns
  growthPhase             // young, mature, breakthrough, dying, etc.
  breakthroughPotential   // Accumulates, triggers sudden flourishing
}

Like biological systems:

  • Cast iron pans season with use
  • Guitars improve with playing, rust with neglect
  • Gardens thrive with care, die without tending
  • Code ossifies or stays fresh based on maintenance

Nonlinear dynamics:

  • Coherent use → slow growth → accumulates potential → BREAKTHROUGH (sudden 1.5x)
  • Chaotic use → anti-Hebbian unlearning → sickening
  • Neglect → atrophy toward zero → death
  • Tending → health boost → restore plasticity

Example: neural-garden.mjs #

Full working piece demonstrating:

  • Health heatmap (dead/sick/healthy/flourishing visualization)
  • Gnarliness evolution graph (intelligence emerging over time)
  • Growth phase indicator (young → mature → breakthrough → dying)
  • Hyperbolic spiral trajectory (position in memory space)
  • User interactions: [T]end, [P]rune, [H]ealth view, [G]narliness view

Why This Matters: The Three Scales #

1. Individual Scale (User Experience) #

Today: Use ChatGPT → generic responses → no memory of you → corporate-owned Tomorrow: Use notepat → learns YOUR rhythm → gets better with YOUR use → you own the weights

The feel:

  • Like a guitar that knows your hands
  • Like a skateboard that knows your tricks
  • Like a journal that knows your voice
  • An instrument, not a tool

2. Community Scale (Social Intelligence) #

Today: Everyone uses same GPT-4 → monoculture → no diversity Tomorrow: Everyone's pieces learn differently → biodiversity → ensemble intelligence

Cross-pollination:

  • Fork @alice/rhythm-model → train on your data → share your variant
  • Ensemble learning: vote across 100 users' models
  • Weight transfer: genetic algorithms for neural evolution
  • Pheromone trails: ants share successful weight patterns

Emergent phenomena:

  • Community aesthetic develops organically (not algorithmically curated)
  • Pieces evolve through selective pressure (well-cared-for survive)
  • Collective intelligence without centralized training

3. Humanity Scale (Institutional Memory) #

Big LLM model: All human knowledge → one massive brain → everyone uses it → monoculture → fragile

Micro-organism model: Each piece/user/community → own micro-brain → billions evolving independently → biodiversity → antifragile

Historical parallels:

  • Wikipedia: Millions of small edits > One giant writer
  • Linux: Thousands of modules > One giant codebase
  • Internet: Billions of sites > One giant portal
  • Intelligence: Billions of micro-brains > One mega-LLM

The prediction (based on portal wars history):

  • 2026-2028: Big LLMs dominate (like portals 1997-2000)
  • 2028-2030: Open models catch up (like Google catching Yahoo)
  • 2030-2035: Specialized agents proliferate (like blogs/social networks)
  • 2035+: Micro-organisms everywhere (like open web today)

The UX Vision #

See UX-TRACK.md for complete user experience design.

Core interactions:

  1. Pieces develop character - notepat after 10,000 uses feels different than day 1
  2. Visible intelligence - health bars, gnarliness meters, growth phase indicators
  3. Care as interaction - tend, prune, forgive become verbs
  4. Social sharing - "my notepat vs. your notepat" comparisons
  5. Instrument metaphor - pieces that improve with play, sicken with neglect

The magic moment:

User plays notepat for 100 hours. Piece learns their rhythm patterns. One day, piece predicts the next note before they play it. The instrument knows the player.

This is what Big LLMs can't do.


Implementation Roadmap #

Phase 1: Foundation (Weeks 1-2) #

  • ✅ Pure JS HebbianNet (~100 lines, graspable)
  • ✅ Extend net API in disk.mjs
  • ✅ Example piece: micro-brain.mjs

Phase 2: Quality System (Weeks 3-4) #

  • ✅ KarmicHebbianNet with health/coherence tracking
  • ✅ Nonlinear growth dynamics (breakthroughs, sickness, death)
  • ✅ Visualizations (health heatmap, gnarliness graph)

Phase 3: Storage (Weeks 5-6) #

  • Extend presigned-url.js for neural-weights
  • Add /api/store-neural function
  • MongoDB metadata + Spaces weight files

Phase 4: KidLisp (Week 7) #

  • Add primitives: train, predict, save-weights, load-weights
  • Example .lisp piece

Phase 5: WebGPU (Weeks 8-10, Optional) #

  • Compute shaders for forward/backward pass
  • MicroNetGPU class (100-1000x faster)
  • Auto-detect, graceful fallback

Phase 6: Social (Weeks 11-12) #

  • Cross-piece weight sharing
  • Ensemble learning
  • Community-trained models

Success Metrics #

Technical #

Experiential #

Philosophical #


Next Steps #

  1. Read UX Track → UX-TRACK.md
  2. Review Implementation Plan → neural-primitives-full-stack.md Part 5-8
  3. Start Coding → Week 1-2 tasks (HebbianNet + API extension)
  4. Build Example → neural-garden.mjs as proof-of-concept

Files in This Directory #

reports/
├── README.md (this file)
├── UX-TRACK.md (user experience design)
├── neural-primitives-full-stack.md (technical architecture)
└── portal-wars-report.md (historical analysis)

The Vision Statement #

Aesthetic Computer will be the first platform where:

  • Intelligence is user-owned, not corporate-controlled
  • Pieces evolve through play, not designed perfectly upfront
  • Networks are tiny and gnarled, not massive and monolithic
  • Learning is bidirectional (can thrive or sicken), not unidirectional
  • Memory is institutional (pieces remember their history), not generic
  • Scale emerges from billions of micro-organisms, not one mega-brain

This is not just a feature. This is a different philosophy of intelligence.

Like the open web beat portals. Like Wikipedia beat Britannica. Like Linux beat Unix.

Worse is better. Many is more. Edges win.


Generated February 2026 Based on research into Stiegler, Rucker, Hofstadter, Gabriel, and 15 years of web history