Packages · Blue Documentation

Packages

Choose the Blue package that owns the meaning or behavior you need, then move to exact types in repo.blue and normative material on GitHub.

View exact types ↗

Packages keep reusable semantics and responsibilities modular. An application can use Blue Language without payment, Contracts without Mandates, or Coordination without Agreements. Add only the layers required by the activity.

Foundations and execution#

Normative foundation

Blue Language

Nodes, types, schemas, references, resolution, canonical identity, and BlueId.

Normative execution

Blue Contracts

Deterministic processing, channels, handlers, patches, scopes, checkpoints, gas, and termination.

Normative computation

BEX

Portable deterministic computation represented as typed Blue data.

Coordination and authority#

Draft / emerging

Coordination

Timelines, actors, Messages, Requests, Responses, Operations, providers, feeders, and subscriptions.

Emerging architecture

Mandates

Living, bounded authority for agents, services, administrators, and cross-document work.

Commerce and reusable business meaning#

Draft package

PayNotes

Govern requests, conditions, evidence, amounts, and lifecycle around one payment transaction.

Design-stage and evolving

Agreements and Commerce

Preserve authored terms and compose reusable processes, Offers, Orders, Products, and network objects.

From guide to exact reference#

This site explains purpose, boundaries, patterns, and examples. Use repo.blue for canonical package content, dependencies, and BlueIds. Use the specification and implementation repositories for normative rules, fixtures, APIs, release tags, and conformance.

Check status per exact artifact

A polished explanation does not make a design-stage type normative. Package and type status must remain visible, especially for Coordination, Mandates, PayNotes, Agreements, and Commerce profiles that are still evolving.