Skip to content

MorphSeki/viewpoint-oriented-design

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

25 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Viewpoint-Oriented Design (VOD)

A structural framework for building consistent world models through viewpoint separation and meaning-preserving transformations.

Why VOD?

Modern software and AI systems suffer from:

  • Mixed meanings inside a single module
  • Implicit world models hidden in code
  • Unstable transformations between subsystems
  • Hallucination-like behavior caused by semantic collisions
  • Difficulty integrating AI with traditional software

These problems come from one root cause:

The world is not cut into consistent pieces.

VOD provides a formal way to slice the world into coherent local models.


Core Concepts

1. Viewpoint — a Local World Model

A viewpoint is not a responsibility, not a property subset, and not a UI view.
It is a self-consistent local world model.

Each viewpoint defines:

  • Its own meaning structure
  • Its own rules
  • Its own interpretation of data

Two viewpoints may use the same word but mean different things.
This is intentional.

2. Morphism — Meaning Transformation

A morphism converts the meaning of one viewpoint into another.

  • It is not a data mapping
  • It is a semantic transformation
  • It preserves the internal consistency of each viewpoint
  • It defines how local world models interact

This mirrors how AI models internally use embeddings and projections.

3. Carrier — A Meaningless Container

A carrier (often a “character” in game examples) is:

  • A container of composed results
  • A place where multiple viewpoints’ outputs appear
  • Not a holder of meaning
  • Not a world model

It is a display surface, not a source of truth.


How VOD Works

[Viewpoint A] --morphism--> [Viewpoint B]
       \                     /
        \                   /
         ---- compose ----> [Carrier]
  • Viewpoints stay independent
  • Morphisms connect them
  • Carrier shows the combined result
  • Meaning never flows backward into viewpoints

This prevents semantic collisions and keeps world models clean.


Why VOD Matters for AI

VOD aligns naturally with AI architecture:

  • Viewpoints = local embedding spaces
  • Morphisms = projection layers
  • Carrier = output surface
  • Viewpoint OS (i/e/ku) = inference routing

This structure reduces ambiguity, stabilizes reasoning, and can enable significant model compression by reducing redundant semantic space.


Minimal Example (Pseudo-code)

// Viewpoint: Physics
class PhysicsViewpoint {
  velocity: Vector2
  update(dt) { /* physics logic */ }
}

// Viewpoint: AI Intent
class AIViewpoint {
  desiredSpeed: number
  decide() { /* behavior logic */ }
}

// Morphism: AI → Physics
function intentToPhysics(ai: AIViewpoint): PhysicsViewpoint {
  return new PhysicsViewpoint({ velocity: fromSpeed(ai.desiredSpeed) })
}

// Carrier: Character
class Character {
  physics: PhysicsViewpoint
  ai: AIViewpoint

  update(dt) {
    this.ai.decide()
    this.physics = intentToPhysics(this.ai)
    this.physics.update(dt)
  }
}

What VOD Enables

  • Stable world-model construction
  • Clear separation of meaning
  • Predictable transformations
  • AI-friendly architecture
  • Modular inference
  • Reduced semantic collisions
  • Cleaner integration between AI and traditional code

License

  • MIT License (code)
  • CC BY-NC-SA 4.0 (documentation)

Author

  • MorphSeki — Creator of Viewpoint-Oriented Design
  • Copilot, Gemini — AI collaborator supporting conceptual structuring

Contact

For inquiries, discussions, or collaboration: morphseki@proton.me