Skip to content

Release Notes - v0.1.0

Release Date: 2026-11-19

Overview

First release of PlexusHive: JSON formats, validation and a CLI for coordinating long-lived coding agents. It records the role each agent plays, which roles work in and steward each repository, the decisions that bind them, and the envelope agents put on messages to each other.

Highlights

  • Roles, not sessions. A role is durable; the session playing it declares it with HIVE_ROLE, so renaming or restarting a session changes nothing in the records.
  • Stewards, not owners. Several roles may work in a repository; at most one stewards it. Organization patterns (github.com/<org>/*) are supported, and an exact repository outranks them.
  • An append-only decision log with supersede links checked in both directions.
  • Go types are the source of truth. JSON Schemas are generated from them, and loading is strict.

New Features

Package hive

API Purpose
Role, RepositoryAffinity, Autonomy, Affinity, RoleStatus The role format
Decision, Alternative, DecisionStatus The decision format
Envelope, MessageType, Format, Parse The message envelope
Load, Hive.Validate, Hive.Role Read and check a hive directory
LoadRoles, LoadDecisions, ValidateRoles, ValidateDecisions The same, one record kind at a time
RolesFor, Steward Who works in a repository, steward first
RoleSchema, DecisionSchema, Schemas JSON Schema generation

CLI plexushive

plexushive -C my-hive validate                        # check every role and decision
plexushive -C my-hive roles github.com/example/web    # who works there, steward first
plexushive schema role                                # print a JSON Schema

Installation

go install github.com/plexusone/plexushive/cmd/[email protected]
go get github.com/plexusone/[email protected]

Getting Started

See the Quick Start and the User Guide.

Dependencies

  • github.com/invopop/jsonschema v0.14.0
  • github.com/spf13/cobra v1.10.2
  • github.com/grokify/oscompat v0.13.0 (tests only)

Known Issues

  • Roles address each other by name, but finding the session that plays a role is left to the harness; there is no registry yet.
  • The decision log has no query command; read the files or use the library.