Blueprints

A local-first release planner for developers and small teams. Plan versions, produce changelogs, and trust the files.

Important

Blueprints is pre-release software. The local planning workflow is functional, but packaging, recovery tooling, and multi-user collaboration still need hardening before production use.

Why Blueprints?

Release notes often live in scattered issues, commit messages, and private documents. Blueprints keeps release intent in a portable workspace that remains readable without a server:

• plan versions and categorized release items;
• plan inside movable version frames with Planned, In Progress, Review, and Complete lifecycle columns;
• switch between an interactive planning board, dependency graph, and release-note projection;
• create, select, label, and edit signed typed relationships directly from the canvas;
• generate stable human-readable item keys;
• freeze and release versions with immutable released content;
• export Markdown changelogs, optionally enriched by local Git history;
• discover changelog, roadmap, GitHub issue, and Project signals as editable approval-first proposals;
• browse or clone local repositories and explicitly pull, commit, and push without running repository hooks;
• validate signed project files and enter read-only mode when trust breaks;
• exchange signed changes through a shared folder with explicit push, pull, and conflict resolution;
• inspect membership, audit history, sync state, and integration boundaries in one desktop app;
• inspect passive VaultSync backup and restore-readiness evidence without coupling signed project truth to backup metadata.

Current status

Area	Status
Local project, version, and item workflow	Working
Persistent signed canvas layout	Working
Interactive Plan and Dependencies views	Working
Signed persistence and trust validation	Working
Markdown changelog export	Working
Shared-folder push/pull	Working with distinct signed identities and staged validation
Conflict and audit diagnostics	Document-aware, recoverable, and actionable
Local Git workflow	Browse, clone, inspect, fast-forward pull, commit all, and push
Changelog, roadmap, and GitHub issue discovery	Working, explicit approval required
GitHub and GitLab source discovery	Working, read-only and bounded
VaultSync integration	Passive metadata and backup-health awareness
Installers and supported releases	Not ready

The canonical delivery plan is ROADMAP.md. Older planning files remain as design history and are not the active backlog.

Quick start

Prerequisites:

• the .NET 10 SDK (10.0.300 or a newer patch);
• Git, if you want local source-change diagnostics.

git clone https://github.com/ATAC-Helicopter/Blueprints.git
cd Blueprints
./scripts/verify.sh
./scripts/run-app.sh

Equivalent commands on any platform:

dotnet restore Blueprints.sln
dotnet build Blueprints.sln --configuration Release --no-restore
dotnet test Blueprints.Tests/Blueprints.Tests.csproj --configuration Release --no-build
dotnet run --project Blueprints.App/Blueprints.App.csproj

See the development guide for platform notes and troubleshooting.

Architecture at a glance

Project	Responsibility
Blueprints.Core	Domain models, enums, item-key rules
Blueprints.Security	Identity, key protection, Ed25519 signatures
Blueprints.Storage	Canonical JSON and signed workspace persistence
Blueprints.Collaboration	Sync analysis, manifests, audit chain, shared-folder safety
Blueprints.App	Avalonia UI, workflows, changelog and Git integration
Blueprints.Tests	Unit and integration coverage

Blueprints uses a local workspace as the editable source of truth and a separate shared directory as an exchange layer. See architecture, workspace format, and security model.

Documentation

• Documentation index
• User guide
• Accessibility
• Canvas engine
• Source Lens
• VaultSync integration
• Troubleshooting
• Architecture
• Workspace format
• Security model
• Threat model
• Support policy
• SonarQube Cloud
• Development guide
• Release process
• Release history
• Roadmap
• Contributing
• Security policy

Contributing

Issues and pull requests are welcome. Start with CONTRIBUTING.md, use develop as the pull-request base, and keep security reports out of public issues.

License

Blueprints is available under the MIT License.