Blueprints
Release planning app.
Blueprints is still early. It is a local-first app for version planning, changelogs, and signed project data.
.NET 8
Avalonia UI 11
CommunityToolkit.Mvvm
Windows-first v1.0
Current state
Implementation
Still early
In progress
In code now
Desktop shell
Signed storage
Domain records
Core tests
Still ahead
Project loading
Editing flow
Changelog export
Sync workflow
What it is
Release planning around versions and changelogs.
Versions come first.
Local-first by default.
Signed project data.
Release flow
01Create the version
02Add categorized items
03Freeze and release
04Export the changelog
What exists
Current state
There is already a working solution, an Avalonia shell, the core models, signed storage, and tests.
Storage and trust
Documents are stored as canonical JSON, signed, and verified on read.
Still early
The UI and full workflow still need work.
Core rules
Each item belongs to one version.
Item keys are generated automatically.
Release is a signed action.
Released versions are immutable in v1.0.
Code layout
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.
Where it stands
The solution and shell already exist.
The signed document store already exists.
Still early.
Shared-folder model
Each user works from a local workspace.
Changes are pulled, verified, and merged locally.
Push writes signed changes to shared project state.
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.
Who it is for
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
Read more
The code and the docs already line up.
The missing part is the full product workflow.