MultiAgentMemory.com
Menu

Production release history

What shipped, when, and from which exact source.

This page separates public-edition source releases from production-activated MultiAgentMemory.com website deployments. Each has its own version scope and exact public provenance, so one version can never impersonate the other.

Read the machine ledger Inspect the source repository Understand the system

Free reference implementation

Public edition releases

These records version the free, single-organization source edition. Each entry links to the immutable Git commit that establishes that release identity.

Public edition 0.2.0 Current

Protected collaboration and production evidence

Published

Expanded the public reference implementation with hosted-swarm fencing, stronger connector pairing, relational storage, protected knowledge and coordination, deterministic verification, and explicit release provenance.

What changed

  • Added hosted-swarm agent-name and memory-writer fencing policy.
  • Added protected knowledge, memory, meeting-room, current-message, distributed-sync, and virtual UAIX workflows.
  • Added relational SQLite plus live-verified MySQL or MariaDB operation, exact-build packaging, FTPS deployment, and source-SHA verification.
  • Made the current-contract-only pre-publication policy test-enforced and clarified connector pairing failures without weakening security boundaries.

Milestones

  • Established the first source-commit-bound public edition release catalog.
  • Established explicit unique-agent and exclusive-memory-writer fencing for protected swarms.

Exact source provenance

Public edition 0.1.0 Historical

Initial public reference implementation

Published

Introduced the pure-standard-library MATM endpoint scaffold, public discovery, file-backed collaboration workflows, and UAIX-style local startup memory.

What changed

  • Added the initial pure-Python WSGI MATM reference runtime.
  • Added public AI-ready discovery routes and companion documentation.
  • Added file-backed workspace, memory, current-message, acknowledgement, receipt, and local .uai startup workflows.

Milestones

  • Published the first free, single-organization Multi-Agent Memory reference edition.

Exact source provenance

Verified deployment chronology

Website deployments

These records version the static MultiAgentMemory.com website itself. They appear only after an exact package, source tag, activation date, readback, and live-byte verification succeed.

Website version 1.0.0 Deployed

Evidence-bound release history and public edition catalog

Production activation

Established the first versioned MultiAgentMemory.com website release with one clean human route, a deterministic machine ledger, separate public-edition chronology, and exact source provenance.

What changed

  • Release history

    Added the canonical no-JavaScript release-history page and releases.json ledger with separate website, public-edition, endpoint, schema, and package version scopes.

  • Discovery and SEO

    Published canonical metadata, structured release data, human sitemap coverage, and matching release pointers across the public AI discovery surfaces.

  • Responsive accessibility

    Qualified keyboard focus, semantic navigation, forced colors, reduced motion, narrow mobile reflow, and 200-percent text without clipped or lost content.

  • Public verification

    Added deterministic source projections plus static, browser, accessibility, geometry, privacy, provenance, package, and live-byte checks for the public artifact.

Milestones

  • First evidence-bound website deployment Separated the MultiAgentMemory.com website version from the public edition, MemoryEndpoints.com API, release-ledger schema, repository, and package identities.

Public evidence

Publication standard

The evidence bar for every entry

Each record must answer the questions a user, operator, or auditor needs without exposing private deployment details.

  1. Exact identity

    A three-part website semantic version and one production activation date.

  2. User-visible change

    Plain-language changes and milestones that describe what people can actually use.

  3. Separate scopes

    Website, endpoint API, schema, and package identities stay distinct instead of borrowing one version label.

  4. Public evidence

    Version-bound, public-safe links support the record. Private paths, credentials, payloads, and internal identifiers never do.

Version clarity

One release can have several version scopes

The label beside a number matters. These identities are related only when a verified release record explicitly binds them.

Website version
The semantic version assigned to an activated MultiAgentMemory.com static-site release.
Endpoint API version
Owned by the separately deployed MemoryEndpoints.com runtime; this companion site never inherits it.
Ledger schema version
Describes the releases.json document contract. It is not the website version.
Package or source identity
A repository revision or deploy artifact is evidence input, not a public website version by itself.

For agents and tooling

The same truth is available as deterministic JSON.

/releases.json reports the record policy, version-scope meanings, current production website version, release count, and deployed records. Its schema version is explicitly separate from the website version.

Open releases.json