Concepts

This section explores the architecture, philosophy, and design patterns that make Viper a powerful metadata-driven runtime.

Viper Runtime (Core)

The Viper Runtime provides Type/Value system, serialization, database, and RPC.

• Viper Philosophy
  • What is Viper?
  • Principle 0: Think Before You Code
  • Metadata Everywhere
  • Commit Immutability
  • Reference Semantics
  • Proactive Philosophy
  • The Viper Paradox
  • See Also
• Viper Architecture
  • The 7-Layer Model
  • Layer Diagram
  • Domain Catalog
  • Core Data Flows
  • Domain Dependencies
  • Runtime Invariants
  • See Also
• Type System
  • TypeCode: Fast Polymorphic Dispatch
  • Type Hierarchy
  • RuntimeId: Cross-Language Compatibility
  • Type-Value Duality
  • Type Interface
  • TypeChecker: Validation
  • Definitions: Type Registry
  • See Also
• Value System
  • Reference Semantics
  • Value Interface
  • Primitives
  • Containers
  • Compound Types
  • Special Values
  • Seamless Python Integration
  • See Also
• Design Patterns
  • Overview
  • Token Constructor Pattern
  • Content-Addressable Storage
  • TypeCode Dispatch
  • Strategy Pattern
  • Interface Segregation (Read/Write)
  • RAII (Resource Acquisition Is Initialization)
  • Facade Pattern
  • Command Pattern
  • Type-Value Duality
  • Fluent Interface
  • Platform Abstraction
  • See Also
• Viper Runtime Glossary
  • Core Concepts
  • Type System
  • Value System
  • Key System
  • Path System
  • Blob System
  • Definitions System
  • Attachment Interfaces
  • Database System
  • Serialization
  • Hashing
  • Network
  • Error Handling
  • Python Binding
  • Patterns
  • See Also

Commit Engine

The Commit Engine provides DAG versioning with immutable history, built on top of the Viper Runtime.

• Commit Engine Overview
  • Positioning
  • Architecture
  • Key Classes
  • Commit Types
  • Content-Addressable Commits
  • Philosophy: Best-Effort
  • Interactions with Viper Runtime
  • Typical Flow
  • See Also
• The Dual-Layer Contract
  • The Contract
  • What Commit Provides
  • What Commit Does NOT Provide
  • Summary
  • See Also
• Commit Patterns
  • CommitStore (Redux-Inspired)
  • State Isolation
  • XArray: CRDT Pattern
  • Undo/Redo Pattern
  • Synchronization Pattern
  • Value Reconstruction Optimization
  • Concurrent Operations Matrix
  • See Also
• Commit Engine Glossary
  • Core Concepts
  • Multiplayer Terminology
  • Commit Types
  • ValueOpcode Types
  • Classes
  • Interfaces
  • See Also
• Industry Context
  • The Universal Pattern
  • Why Every System Uses Deterministic No-Op
  • Why No System Notifies Users
  • The Dual-Layer Contract is Universal
  • What Makes Viper Different
  • See Also

Transversal Topics

Topics spanning both Viper Runtime and Commit Engine.

• Code Generation
  • DSM: Digital Substrate Model
  • Enumeration Example
  • Attachment Function Pool Example
  • Function Pool Example
  • Kibo: Code Generator
  • The Dual Reality
  • Amplification Ratio
  • Workflow
  • Key Distinction
  • See Also
• Services and RPC
  • Overview
  • Service Architecture
  • Function System
  • Service
  • RPC Protocol
  • Transparent Remote Access
  • Bidirectional Protocol
  • Attachment Function Integration
  • Database Remote Access
  • Commit Database Remote
  • Definitions Synchronization
  • See Also