Skip to content

Release Notes - v0.2.0

Release Date: 2026-11-19

Overview

This release adds status reports. Each role keeps one current report of what it finished, what is blocked and on whom, what it does next, and the decisions it needs from the operator. plexushive brief gathers them into one briefing to start the day from.

Breaking changes: none for valid hives, unless a role is named operator; that name is now reserved.

New Features

Status reports

{
  "role": "billing",
  "generated": "2026-11-19T09:00:00Z",
  "summary": "Coupons are in review.",
  "done": [{"description": "Added coupon validation to checkout."}],
  "blocked": [{"description": "Publishing needs a push.", "waitingOn": "operator"}],
  "next": [{"description": "Release the coupon endpoint."}]
}

A blocker waits on a role or on operator. A decision request in decisionsNeeded states the situation, the evidence, at least two options with their cost and risk, a recommendation naming one of them, and the approval the answer grants. Once decided, it is recorded as a decision with the same ID.

Reports are kept out of the hive repository, in $HIVE_REPORTS or plexushive/reports under the per-user data directory, one file per role, replaced atomically.

Commands

plexushive -C my-hive report submit report.json   # role from HIVE_ROLE, time from the clock
plexushive -C my-hive brief                       # decisions, blockers, status, missing reports
plexushive -C my-hive brief --json                # the same, for other programs
plexushive schema report                          # the report JSON Schema

Library

API Purpose
Report, Item, Blocker, DecisionRequest, Option The report format
Report.Validate, DecisionRequest.Validate, ValidateReports Validation
WriteReport, LoadReports, ReportsDir, Report.Age Storage and freshness
NewBriefing, Briefing Gather reports for the operator
ReportSchema JSON Schema generation

Migration

Rename any role named operator. Nothing else changes.

Dependencies

  • github.com/grokify/oscompat v0.13.0 is now used at run time, for the per-user data directory and atomic writes.

Known Issues

  • Reports are local to one machine; there is no shared store yet.
  • A decided request is not removed from its report automatically; the role drops it in its next report.