v1.9.0
Puntovivo v1.9.0 — a calmer console with stronger receipts and recovery
Why this release matters
v1.9.0 is about making a capable POS easier to approach. The application had
grown into many modules; this release reorganizes that depth around the tasks a
cashier, manager, or administrator is trying to complete. Common actions are
more direct, advanced controls stay available without dominating the screen,
and recovery guidance leads to real actions instead of decorative status cards.
The same release also strengthens the evidence printed on a receipt and the
evidence used to trust a desktop build. It is a meaningful internal-beta
candidate, not a claim of Colombian fiscal certification or field-proven
hardware support.
What changed
A console organized around work
- Introduced task-first navigation and command search so operators can start
from an outcome instead of learning the module tree. - Added guided business setup and simplified the first checkout viewport.
- Made creation flows for products, categories, customers, suppliers, units,
locations, VAT rates, and sequentials progressively disclose advanced fields. - Added inline manager approval at checkout and protected unsaved drafts from
accidental navigation. - Replaced internal tenant and device jargon with language intended for store
operators.
Receipts that preserve what happened at sale time
- Connected active receipt templates to browser, Electron system printing, and
ESC/POS output. - Preserved the business identity, display labels, layout, logo source, locale,
and customer-facing presentation used when the sale was completed. - Added native Code 128 output and localized customer-facing labels and
timestamps. - Simplified template editing and fitted previews to the available viewport.
These changes improve ordinary and fiscal evidence, but they do not make a
document DIAN-authorized by themselves.
Recovery that points to real controls
- Added ownership, thresholds, response targets, and playbooks for sync,
fiscal, printing, payments, backups, and desktop updates. - Connected lost-device and damaged-storage guidance to the real revoke,
backup, and restore surfaces. - Repaired migration-journal drift and proved incremental database recovery.
- Renewed and actively revoked Store Hub sessions, authenticated realtime
streams, and kept sensitive desktop credentials in the main process.
Faster and more trustworthy delivery
- Reduced first-paint query contention in sales and deferred closed overlay
bundles. - Added warning-free quality gates, store-scale read budgets, desktop memory
budgets, and packaged runtime smoke checks. - Built and runtime-smoked the release candidate on Linux, macOS, and Windows.
- Signed and notarized the macOS application, signed the Windows installer and
packaged helpers, and published a staged desktop update feed.
Before you use it
- Puntovivo still does not sign or transmit production documents through a
DIAN-authorized Technology Provider. Provider credentials, certificates,
contingency behavior, conformance testing, and certification are still
required. - Software paths exist for receipt printing, cash-drawer commands, scanner
input, and manual payment-terminal recording. Representative physical devices
still need qualification in a store-like lab. - Cross-platform packaged builds and runtime journeys passed, but encrypted
packaged recovery across every desktop platform remains tracked in
issue #177. - Optional AI uses the provider account configured by the operator. Co-pilot,
OCR, and voice calls use Puntovivo's monthly spend guard; semantic embedding
calls are not yet included in that guard and remain tracked in
issue #179. Provider
limits are the authoritative cap until that work ships. - There is no managed cloud or staffed 24/7 support service. The current product
is local-first, open source, and still requires an observed private pilot
before any production-readiness claim.
Downloads
Open the v1.9.0 GitHub release
and choose the signed Windows x64 installer, notarized macOS Apple Silicon
archive, Linux x64 AppImage, or web bundle. Update-feed files are consumed by
the desktop updater and are not manual installers.
For engineers and auditors, the generated
v1.8.1...v1.9.0 comparison
keeps the complete commit-level history.