FGLabs

Blueprints

Structured release planning for versioned software.

Blueprints is for projects where release notes, versions, and planning notes start drifting apart.

The app keeps the version first, attaches work items to it, and produces a changelog from the project state instead of from memory.

Browse source and plans
.NET 8Avalonia UICommunityToolkit.MvvmWindows-first v1.0

Current state

Real architecture, incomplete product workflow.

The desktop shell, domain models, signed storage, and core tests exist. Project loading, editing, export, and the complete collaboration flow still need product work.

Implemented
  • Desktop shell
  • Signed storage
  • Domain records
  • Core tests
Still ahead
  • Project loading
  • Editing flow
  • Changelog export
  • Sync workflow

Release flow

Version first, changelog last.

Work belongs to a version. Release is an explicit signed action, and the changelog is generated from project state.

  1. 01Create the version
  2. 02Add categorized items
  3. 03Freeze and release
  4. 04Export the changelog

System principles

  • Versions come first.
  • Local-first by default.
  • Signed project data.
  • Each item belongs to one version.
  • Item keys are generated automatically.
  • Release is a signed action.
  • Released versions are immutable in v1.0.

Architecture

  • App holds the Avalonia shell.
  • Core holds the planning models.
  • Security handles signatures and trust.
  • Storage handles canonical JSON and signed files.
  • Collaboration holds the sync side.

Storage and trust

  • Canonical JSON is used for signing.
  • Each signed document writes a matching .sig file.
  • Trust state is tracked per document.
  • The full sync workflow is not finished yet.

Shared-folder model

Local workspaces with signed shared state.

  1. 01Each user works from a local workspace.
  2. 02Changes are pulled, verified, and merged locally.
  3. 03Push writes signed changes to shared project state.

Who it is for

Release discipline without a hosted SaaS dependency.

  • Solo developers shipping versioned products
  • Small teams that need release discipline without a hosted SaaS stack
  • Projects that care about auditability, trust, and cleaner changelog structure
Review the repository