Version and Scope¶

This guide follows the development checkout: release notes and artifact validation/publication checklist. Installation from a wheel is tested separately from this repository's editable, locked environment. brecon --version reports installed metadata without initializing Qt; the desktop application and MCP server use the same version.

Brecon was formerly named PyniteGUI. The brecon command and Python entry module are canonical; pynitegui remains a compatible command/import namespace. Existing .pynite.json, mesh/plate recipes, preferences and recovery storage keep their identifiers. Existing MCP clients may continue using the pynitegui://automation/reference resource. Repository/documentation URLs and historical release artifacts retain the previous name. The first Brecon release candidate is 1.0.0rc4; see publication and validation status. Install Brecon in a fresh environment. If reusing an environment, uninstall the old pynitegui distribution first: both provide the compatibility import namespace and launch command. With uv tools, remove the old tool before installing Brecon so its pynitegui compatibility command can be created. Keep project files; uninstalling the tool does not delete them.

The stable 1.0 scope is elastic 2D/3D frames and bilateral axial-only trusses, with frame-only P-Delta within the documented restrictions. Surface/plate tools retain their experimental status; nonlinear plastic, modal and reinforced-concrete workflows are outside the stable scope. See Engineering Scope for limits.

The searchable Zensical manual is built from this GUIDE and the project records. See Documentation Site below for local preview and publication instructions.

A Python desktop editor for 2D/3D frames and axial-only trusses with PyNite.

For an audited comparison of PyNite engine capabilities with features actually exposed here, see PyNite Capability Coverage.

Source: GUIDE.md. This manual follows the current repository; the published rc1 wheel has a smaller feature set.