Addison

Addison provides the foundational abstractions for reactive models in the Chicago System, enabling protocol-agnostic data interaction within the RMVC+R architecture.

Background

Addison's primary purpose is to provide a unified, protocol-agnostic interface for interacting with reactive data. In the Chicago System's RMVC+R (Reactive Model-View-Controller + Resources) architecture, Addison serves as the "Model" layer. It abstracts away the complexities of the underlying resource protocols (handled by Belmont) and provides application logic with a consistent way to observe and mutate state.

By wrapping resources in Atomic (single-resource) or Composite (aggregate-resource) models, Addison allows developers to focus on domain logic rather than the mechanics of resource resolution, synchronization, and state management. Its built-in command queuing and centralized lifecycle management ensure that data remains consistent and predictable, even when dealing with high-latency or complex multi-resource dependencies.

Installation

Use your favorite package manager:

npm install @dashkite/addison

Usage

Atomic Models

Atomic models represent a single resource.

import Model from "@dashkite/addison/models/atomic"

class Greeting extends Model
  @make: -> super template: "local:/components/greeting"
  fallback: "hello!"

# usage
greeting = await Greeting.resolve()
greeting.put ( data ) -> "hola!"

Composite Models

Composite models aggregate multiple resources into a single state.

import Model from "@dashkite/addison/models/composite"

class PersonalizedGreeting extends Model
  @make: ->
    super
      greeting: template: "local:/components/greeting/{name}"
      profile: template: "local:/profile"

# usage
greeting = await PersonalizedGreeting.resolve greeting: name: "Dan"

Other Resources

• Reference
• Design

Status

Not suitable for production use. Please report any issues on the GitHub repository.