Implementation, registries, and GitHub
Where explanatory architecture ends and exact package identities, specifications, fixtures, libraries, implementation notes, and release evidence begin.
Use each source for the job it owns#
| Source | Use it for |
|---|---|
language.blue |
mental models, solution patterns, progressive explanations, and architectural boundaries |
| Playground | runnable proof, state inspection, processing traces, and presentations |
repo.blue |
canonical package content, type source, exact BlueIds, dependencies, and package discovery |
| specification repositories | normative algorithms, processing behavior, conformance requirements, and versioned semantics |
| implementation repositories | APIs, build instructions, adapters, examples, tests, releases, and performance notes |
| MyOS | a practical portal/operator experience built on the open technology |
Reference implementation component map#
Language runtime#
A mature runtime distinguishes Source Document, preprocessed content, expanded references, Resolved View, Canonical Identity Input, minimized overlay, and immutable runtime snapshots. Every provider-returned node must verify against the requested BlueId.
Contracts processor#
The processor discovers supported contract capabilities by exact type identity, fails closed on unsupported active capabilities, accepts one document and one eligible event, applies deterministic effects, manages checkpoints and embedded scopes, and returns the new Root, emitted events, and gas.
BEX compiler and runtime#
BEX programs are Blue data. Compilation validates structure and declared dependencies. Execution receives immutable declared inputs and returns values, changesets, and events. It has no ambient network, clock, random source, or unrestricted host function access.
Timeline provider and feeder#
Providers authenticate appenders, attribute actors and sources, assign strictly increasing microsecond timestamps inside each Timeline, preserve predecessor history, and close completeness frontiers. The feeder verifies evidence, closes a common window, orders entries deterministically, resolves direct or Mandate-backed eligibility, and invokes the processor once per accepted entry.
Mandate and operator services#
Mandate services maintain FULL_CHAIN lifecycle state and resolve exact authority at the action time. Operators manage sessions, storage, subscriptions, bootstrap, evidence, audit, availability, export, and failover. One deployment can combine components, but the trust model should preserve their conceptual boundaries.
Quality gates#
A release candidate should include:
- exact canonical source and published BlueIds;
- reproducible registry generation;
- Language, BlueId, circular-reference, resolution, and schema fixtures;
- Contracts, patch, scope, checkpoint, gas, and failure fixtures;
- BEX compile, execution, intrinsic, and gas fixtures;
- Timeline completeness, ordering, and replay fixtures;
- Mandate lifecycle, exact-at-time, scope, and revocation fixtures;
- domain-package lifecycle and provider-integration fixtures;
- cross-language agreement on resulting identities and states;
- resource limits and adversarial tests;
- a clear normative-status and compatibility matrix.
Current public entry points#
- Blue Language Java
- Blue Language JavaScript
- Blue organization repositories
- repo.blue package registry
Repository names, releases, and package maturity can change. Use as the website's publication-time checklist, then verify exact release tags in the repositories.