NordbriefNordbrief
Sign inStart free
Changelog

What has shipped, what comes next.

A dated record of what has been built, what changed, and what is being prepared next in the product and site.

v0.4
April 18, 2026
New

Multi-page marketing, localisation, and indexed route structure

  • The public site now ships as a real multi-route marketing surface instead of a single SPA entry. Every public route has its own URL, metadata, sitemap entry, and locale variant, which means search engines and AI crawlers can read the content directly rather than depending on client-side rendering.
  • This change also formalised the content structure across home, product, pricing, security, docs, glossary, contact, compared, about, careers, and changelog, so the public layer behaves like a proper product site rather than a prototype shell.
v0.3
April 17, 2026
ImprovedImproved

Workspace surfaces ported into Next.js App Router

  • Pipeline, Writer, Ledger, Organisation, and Settings now exist as dedicated application routes inside the App Router structure. The shell, command palette, toasts, kanban interactions, CSV export, draft persistence, and AI action seam all survive the migration from the single-file prototype.
  • The main goal of this step was not final backend wiring but preservation of the interface contract. The UI now sits in a structure that can be deployed once and extended via route handlers, server actions, and external APIs without redesigning the front-end.
v0.2
April 16, 2026
ImprovedImproved

PRH lookup, lead capture, and legal-operational groundwork

  • The server-side PRH proxy now supports organisation-name lookup and direct Y-tunnus lookup through a stable internal endpoint. Contact intake is validated and can already forward to email when credentials are present, while still degrading safely when they are not.
  • This laid down the pattern for the rest of the external integrations: keep the public and application surfaces usable immediately, but make every meaningful side-effect pass through a stable API seam that can later be backed by real credentials.
Next in line
  • 01

    Auth.js or equivalent managed authentication replacing demo-mode cookie auth.

    This is next because it unlocks real account ownership and production-safe access control across the workspace.

  • 02

    Stripe Checkout and customer portal wiring for paid plans and seat changes.

    This is next because paid plans, seat expansion, and procurement-safe billing all depend on it.

  • 03

    AI Gateway-backed Writer actions replacing canned prose with real completion flows.

    This is next because the Writer already has the UI seam; the remaining work is secure model routing and evaluation discipline.

  • 04

    Persistent database storage for organisations, grants, drafts, and report artefacts.

    This is next because local persistence is enough for prototype realism, but not for a real operating system shared by organisations.