Release Notes
Release notes
Running log of platform releases.
Major platform updates are listed newest first. Use View next 10 for older entries; without JavaScript, every entry remains readable on this page.
2026.09.15 - Developer Kit 1.20.3 live connector verification
Fixed The shipped TypeScript connector was compiled from the public ZIP and exercised with disposable live-app and read-only credentials against the million-record local tenant. Organization listing exposed and drove a fix for an API service that incorrectly supplied the planner-owned correlation parameter to organization procedures. The battle credential now includes the current marketplace, asset, and theme scopes. After correction, 23 SDK workflows, all 199 authenticated module-route registration checks, 24 module representative reads, 40 gateway-family cases, 95 gateway unit tests, 18 kit examples, and 19 post-run database integrity checks passed. All disposable credentials and the temporary SQL principal were revoked and removed. This is local integration evidence, not public-production or external-provider certification.
2026.09.15 - Builder staged database inventory and guarded executor
Added The Builder Backups page displays an operator-published, app-scoped database inventory with Ready, Blocked, and Manual review classifications and Stage 2 prerequisite counts. The PowerShell operator entry point now consumes the exact Builder-approved release fingerprint, makes and verifies all three source backups, applies migrations on disposable restored copies first, compares live results with the rehearsed schema fingerprints, and automatically attempts three-plane restoration after a live failure. Inventory still requires reviewed migration authoring before registration. The six golden database procedure catalogs were also reverified at exact 1,236-procedure parity after the asset procedure module settings were normalized. Read the staged upgrade guide.
2026.09.15 - React styling support guide
Documentation Added Support for React, covering Tailwind, ordinary CSS, CSS Modules, inline styles, component libraries, and CSS-in-JS. The guide includes small source examples, publishing checks, and the distinction between hosted registered components and a developer-owned React build. It does not introduce new package installation or arbitrary-code execution capabilities.
2026.09.15 - Golden Discussion post-delete error contract synchronized
Fixed The golden core database's secured Discussion post-delete procedure now matches the reviewed error mapping for invalid requests, absent records, and denied removal. Execute-only application-role grants were preserved. The change was rehearsed with rollback, applied after a verified backup, and checked against the current export. Existing customer database copies are not silently upgraded by a golden database change.
2026.09.15 - Production-build customer browser verification
Verified A rebuilt frontend served by local IIS passed signed-in desktop and mobile checks on the seven pages installed in the million-record test tenant. Contacts passed paging, configurable page sizes, search, validation, create, saved edit, favorite/unfavorite, and removal through visible controls. Session reload and sign-out also passed. This is scoped local verification, not a public-production or every-module launch certification. Mobile contact-row star clipping remains a visual follow-up; external compute availability remains independently gated.
2026.09.15 - Contacts full pagination and page-size controls
Fixed Contacts now traverses the complete authorized directory instead of stopping at 2,000 rows. The secured procedure reads one bounded page plus a look-ahead row, returns hasMore for Next-button behavior, and marks totals exact on the last populated page. The standard directory supports 25, 50, 100, or 200 rows per page and a configurable initial pageSize. A fresh million-record tenant passed first, middle, final, and beyond-final paging through the compiled IIS runtime; the final authorized Contacts page returned 197 rows and hasMore: false. The reviewed procedure was installed in the golden Core database after a verified backup so future tenants inherit it.
2026.09.15 - Local IIS compiled-runtime verification
Improved The production-built React tenant frontend can now be staged on loopback-only IIS port 8080 using URL Rewrite and Application Request Routing. Localhost redirects to the selected tenant's routed localhost hostname; secured API calls stay same-origin and forward to local backend services. Login and Contacts, Calendar, and explainable-scoring passed desktop/mobile browser smoke checks. Missing API and asset paths return 404 instead of the React page. This verifies local IIS delivery, not a public production cutover: production secrets, persistent backend hosting, HTTPS, and external infrastructure still require their own deployment checks. Public site bindings were not changed.
2026.09.15 - Developer runtime gateway startup repair
Fixed The Developer API now registers the page executor required by its runtime bootstrap service through the existing secured Developer API database adapter. A dependency-resolution regression test covers the shared page/data adapter and identity forwarding. Golden-export test sentinels were updated to the reviewed current schema. Gateway throttling tests now exercise the authenticated partition and Retry-After instead of expecting anonymous calls to consume that budget. No database schema migration is required for these fixes.
2026.09.15 - Local battle-test rate-limit override
Improved Local test startup now supports an explicit high rate limit for bounded runtime and API testing. Production defaults and authorization checks remain unchanged. High-limit runs do not verify normal throttling behavior; rate-limit and Retry-After checks remain a separate test. Local startup can also skip shared billing-catalog setup.
2026.09.15 - Battle-test integrity classification and isolated report tests
Fixed Integrity checks distinguish verified zero-duration DataRole history boundary pairs from actionable constraint failures, retaining raw diagnostics and failing closed on unrecognized cases. Report unit tests use their own synthetic benchmark fixture instead of depending on a local historical run. Missing real performance evidence still fails release readiness. The retained test database passed 19 integrity invariants without deleting any data; this is not a production load certification.
2026.09.14 - Marketing pitch form restored to Classic ASP
Fixed Build My Pitch now posts to its same-origin ASP service with a session-bound human check and separate enabled/possible capability lists. The service reads its private OpenAI credential, targets Luna through Responses, and returns a downloadable Word-readable document without a public generated-file URL. Browser tests cover submission and download recovery. Live generation requires Responses write permission on the configured key; email delivery also requires working SMTP configuration.
2026.09.14 - Marketing site IIS availability restored
Fixed Removed a redundant local ASP setting that conflicted with the server's locked IIS configuration and prevented the marketing application from starting. The existing HTML-to-ASP mappings remain in place. Public page loads and the ASP health check now return successful responses; pitch-generation configuration is a separate integration check.
2026.09.14 - Homepage clarity and mobile navigation
Improved Public product pages now provide a mobile menu without requiring JavaScript. Homepage links lead to page design, customer signup, and the current developer kit. Database guidance distinguishes each SaaS from its customer organizations, service compute is identified as a deployment dependency, and MCP examples distinguish architectural concepts from published tool names.
2026.09.14 - Support navigation and documentation clarity
Improved Added a current developer-kit and version guide, role-based starting points, stable section links, and clearer public-kit versus account-kit instructions. Corrected SaaS database versus organization isolation wording, white-label reuse guidance, and public HTTPS versus origin configuration. The custom-service guide now identifies the pending compute dependency. Current kit checks read the release manifest; historical release notes retain their original versions.
2026.09.14 - Webhook example reliability fixes
Fixed Developer Kit 1.20.3 rejects corrupt or conflicting duplicate files, publishes complete event payloads atomically, serializes workers, isolates failed events after bounded retries, and enforces polling deadlines during requests and waits. Regression tests cover each failure. The Webhook Lab uses a versioned static release; Cloudflare handles public HTTPS, with an HTTP origin connection documented separately from the production origin-TLS target.
2026.09.14 - Webhook Lab and background-job examples
New webhooks.buildwithhq.com now has a deployable public reference site with dependency-free Node.js examples for exact-body HMAC verification, five-minute replay rejection, durable event-ID deduplication, fast acknowledgement, and bounded AI rebuild polling with required 429 Retry-After handling. The site does not collect customer deliveries; developers run the receiver in their own trusted backend. Developer Kit 1.20.2 includes the same sources and offline tests.
2026.09.14 - Developer webhook contract maintenance
Fixed Generated TypeScript now carries the documented account | app webhook subscription scope. Webhook update, secret rotation, delivery query, and dead-letter retry operations publish their real validation and not-found responses, while every Developer API 429 response declares the runtime Retry-After seconds header. The lifecycle example now uses the UUID event identifier emitted by the actual contract.
2026.09.14 - API pagination, filtering, limits, and versioning guide
New Developers now have one contract-backed operating guide for numbered module pages, organization cursor traversal, server-side filters, required 429 Retry-After handling, bounded transient retries, and OpenAPI fingerprint pinning. Developer Kit 1.20.1 includes a dependency-free JavaScript request helper and offline tests for rate-limit waits and both pagination families.
2026.09.14 - Developer Kit example portability
Fixed The Developer Kit assembler now rewrites the example catalog's OpenAPI reference to the portable kit path and removes repository-only .NET adapter and method names from the distributed copy. Public operation IDs, SDK methods, MCP tool names, scopes, requests, and the verified OpenAPI fingerprint remain available. The kit README now points developers to the portable catalog and copyable webhook signature verifier under examples/.
2026.09.14 - App-wide organization and user lifecycle webhooks
New Webhook subscriptions now distinguish backward-compatible account scope from app scope. A trusted SaaS backend can subscribe once for all customer organizations and receive nine sensitive, versioned events: organization create/update/deactivate, user create/update/deactivate, membership create/role change, and invitation acceptance. Lifecycle mutations stage events transactionally, role changes within one transaction collapse to final state, and the existing HMAC-signed retry/dead-letter worker performs delivery. Subscription ownership remains bound to the calling credential's AppAccount even when an app-scoped event names another customer organization; receivers gain visibility, not database or API authority.
2026.09.14 - Developer Kit 1.19.0 organization lifecycle
New Trusted SaaS backends can now list and search customer organizations, load their typed administration snapshot, update name/billing email, suspend or reactivate accounts, maintain DataRoles and Locations, create/resend/revoke hosted invitations, and transfer ownership through app-scoped Developer API routes. Mutations reuse reviewed CustomerCopy procedures, enforce revision fences and app/database binding, and write audit evidence. OpenAPI declares safe 404 and fenced 409 responses; all annotated email fields now publish format: email. Invitation tokens are hash-only in storage and returned once to the trusted backend for delivery; password acceptance remains on the hosted tenant authentication route.
2026.09.14 - Developer Kit 1.18.2 signup contract alignment
Fixed Customer-organization signup now declares its real retry semantics in OpenAPI: first creation and a matching idempotent replay both return HTTP 201, with created distinguishing the outcome, while an owner-subject conflict returns HTTP 409 using the shared error envelope. Signup and tenant-user email inputs publish format: email, account status is constrained to Active or Inactive, and the connector rejects non-live credentials and duplicate normalized DataRole or Location keys before making a request.
2026.09.14 - Full support capability review
Improved All 173 support articles plus the home, section indexes, sitemap, and 404 surface were regenerated and checked in navigation order against the current capability contracts. Current documentation now consistently uses 273 Developer API operations across 211 paths, 199 promoted module operations, 23 cataloged first-class capabilities, and 43 MCP tools; historical release figures remain historical. Every article links to the generated API Map and first-class module inventory. Seller payout guidance now distinguishes BuildWithHQ ledger eligibility and transfer submission from Stripe Connect processing and bank-delivery timing, which Stripe controls.
2026.09.14 - SaaS CSS, design assets, and Developer API themes
New App Assets now provides app-scoped Custom CSS and design-file hosting. Trusted developer backends can also read and version-safely update the dashboard's app-wide theme, validated --runtime-* variables, and bounded design tokens through GET/PUT /v1/apps/{saasAppId}/theme and the connector SDK. Uploads now default to private, public delivery requires explicit selection, asset categories use a fixed enum, and authenticated binary-download errors remain JSON envelopes. Combined with page drafts/publishing and compiled CSS/assets, React, Tailwind, and pure React hosts have the complete supported styling workflow without exposing live credentials or running arbitrary customer build code in the API.
2026.09.14 - TailAdmin-style template design guide
New The Builder Guide now provides one end-to-end workflow for adapting a licensed professional React design into BuildWithHQ: establish token-safe CSS, refine shared primitives, customize module React at the correct ownership layer, edit every page through Puck, cover responsive and failure states, verify real lifecycle actions, then harvest and publish an immutable exact-version template. The guide keeps TailAdmin as visual reference while BuildWithHQ retains routing, identity, bindings, permissions and stored-procedure authority.
2026.09.14 - Developer Kit 1.18.1 customer signup bootstrap
New A SaaS builder's trusted marketing-site backend can now create a top-level customer organization, its first owner, protected owner authority, up to five initial DataRoles, and up to five initial Locations through one idempotent createTenantAccount call. The route reuses the reviewed Builder organization transaction, returns caller-key-to-ID maps, and writes the same routed AppAccount immediately shown in the Builder Organizations directory and the in-SaaS account administration area. The browser never receives the long-lived app credential: signup and login remain with the builder's verified identity provider/BFF, which exchanges the authenticated external subject for a short-lived delegated-user token. The golden CustomerCopy procedure was updated only after a verified COPY_ONLY/CHECKSUM backup and rollback-only creation/replay/limit proof, with zero fixture residue and no direct developer-role data, DDL, or Builder-procedure grant.
2026.09.13 - Local validation and release-contract maintenance
Fixed Local React, Puck, Developer Console, Developer Kit, OpenAPI, database-contract, and secured-service tests now follow the current generated contracts. Developer Console requests restore their short-lived access token through the secure refresh session before a protected call, text-file fingerprints are stable across LF/CRLF checkouts, the Qwen profile uses its approved 4096 native dimension, and SQL principal materialization includes the database-upgrade worker. Current package-lock audits for the Builder and tenant apps, Universal Inbox, page runtime, E2E harness, React kit, and local Puck report zero known vulnerabilities. The refreshed 1.18.0 Developer Kit remains local-only for @buildwithhq/page-runtime, and its assembler removes repository-only Local Puck aliases and internal monorepo paths from the customer ZIP while retaining them for direct source-tree tests. Physical GPU, Firecracker, live database, and production performance evidence remain environment-gated and are not claimed by this maintenance pass.
2026.09.12 - Developer Kit 1.18.0 local page runtime package
Fixed React and the local Puck editor now share one compiled, local-only @buildwithhq/page-runtime package from the kit's packages/ directory. Locked file: dependencies replace the Vite/TypeScript aliases and the duplicated 577-line presentation parser. The hosted tenant app also resolves the compiled package through preserved local-package symlinks; its old source alias and direct TypeScript source inclusion are gone. The package allowlists compiled JavaScript and declarations only, emits no source maps, remains protected by "private": true, and passes packed-artifact checks in clean React 18 and React 19 projects. The route explorer now also accepts the delegated-user-only authentication mode used by the runtime page and binding operations. The optional react/native/ source drop still requires the host's larger @buildwithhq/universal-inbox product dependency; that is its only unresolved native module and is not folded into this parser package. Normal npm ci still downloads declared third-party dependencies; no BuildWithHQ source is published to npm.
2026.09.12 - Developer Kit 1.17.4 uniform public conflict envelopes
Fixed The Developer API gateway now converts errors returned by imported tenant controllers into the canonical public ApiErrorResponse. Contacts and Checklist item update conflicts therefore include required contractVersion, code, error, and correlationId fields like every other public error. TenantRuntimeErrorResponse and its six media-type references have been removed from public OpenAPI, while native tenant-runtime routes retain their internal envelope.
2026.09.12 - Developer Kit 1.17.3 shared API errors and database posture
Improved All 528 rate-limit and internal-error responses now reference the single shared ApiErrorResponse component, eliminating 522 anonymous duplicate schemas for generated clients. Marketplace service guidance now states the database boundary in one place: API callers receive no SQL credentials; verified SaaS, tenant, and user identity is server-injected; and bwhq_developer_api has allow-listed procedure execution only, with no table rights or DDL authority.
2026.09.12 - Developer Kit 1.17.2 installed-service upgrade discovery
Fixed Installed-service discovery now excludes inactive installations and endpoints from duplicate-key detection, so an inactive prior package version cannot hide its active replacement from GET /services or the per-app OpenAPI projection. The secured procedure uses the repository DROP/CREATE convention, computes appliance executability and endpoint availability once, and uses collision-free errors 58708/58709. A rollback-only golden-database proof installs v1, deactivates it, installs v2, and verifies that discovery exposes only available/invocable v2. The updated golden procedure was applied after a fresh COPY_ONLY/CHECKSUM backup passed RESTORE VERIFYONLY.
2026.09.12 - Developer Kit 1.17.1 marketplace contract evidence
Improved The per-app OpenAPI route now formally declares its SHA-256, ETag, and private no-store response headers, while installed service health and license states publish fixed enums for generated clients. Marketplace service guidance is linked from the system guide, API Map, headless workflow, and SDK guide. The ZIP also carries hash-bound review evidence for the exact secured discovery procedure, making its tenant-principal gate, requested-app installation filter, inactive-row exclusion, and exact endpoint-permission canInvoke decision independently inspectable without distributing server or backup topology.
2026.09.12 - Developer Kit 1.17.0 marketplace service contracts
New Trusted app backends can now list exact-version installed marketplace endpoint schemas through GET /services and download a per-app OpenAPI projection through GET /openapi.json. The projection combines the current static Developer API contract with available installed endpoints and publishes a deterministic contract fingerprint. MCP adds buildwithhq.services.list for dynamic schema discovery while retaining the generic invoke fallback. The new appliances.read scope grants metadata visibility only; execution still requires appliances.invoke, endpoint permission, exact artifact/license/health validation, secured source records, and MCP approval. The golden CustomerCopy received the reviewed secured discovery procedure after a verified COPY_ONLY/CHECKSUM backup.
2026.09.12 - Developer Kit 1.16.3 request contract normalization
Improved The OpenAPI document transformer now removes nullability from every required component property, gives required strings a minimum length of one, and publishes the finite request values enforced by current services and stored procedures. Literal enums now cover tenant identity, checklist item/evidence, conversation, Active Workplace, Work Order, reservation, Universal Inbox, AI search, inbound conversation, and payment policy requests. Optional enum fields reject explicit null consistently with the generated TypeScript client. Generic record and dynamic-module statuses remain intentionally extensible. The public contract remains 265 operations across 205 paths.
2026.09.12 - Developer Kit 1.16.2 tenant identity enums
Improved OpenAPI now publishes the exact all | selected location-scope values for tenant-user create and update requests and the exact Active | Inactive update status values enforced by the current tenant procedure. Create location scope is required and non-null; PATCH fields remain optional and nullable. Generated clients no longer accept arbitrary strings, and the tenant provisioning guide is linked from both kit indexes and both headless workflow entry points. The public contract remains 265 operations across 205 paths.
2026.09.12 - Builder-managed customer organizations
New SaaS builders can now create, view, edit, deactivate, and reactivate every customer organization inside an app they own, then add or update its tenant users, DataRoles, and Locations from the professional Organizations workspace. Initial organization, owner, owner authority, optional DataRoles, and optional Locations commit atomically. Subsequent changes use stale-write fences and safe deactivation where retained history or assignments prevent deletion. Every operation routes through the selected builder-owned SaaS database under reviewed stored procedures; record IDs never act as authority and the browser receives no database topology.
2026.09.12 - Developer Kit 1.16.1 tenant provisioning map
New A new kit-root tenant-provisioning and authentication guide maps signed-in Builder organization administration separately from public bwk_live_ tenant-account and tenant-user provisioning and short-lived bwu_live_ user delegation. It documents atomic owner, DataRole, and Location setup, revision-fenced Builder edits, public SDK methods and least-privilege scopes without weakening the credential boundary. The public contract intentionally remains 265 operations across 205 paths.
2026.09.12 - Developer Kit 1.16.0 runtime page embedding
New External applications can now load either a portable published page body or the complete SaaS shell through a delegated-user-only runtime client, then resolve registered block bindings in a secured batch. The three new routes reuse native entitlement fallback, component contracts, DataRole and Location scope, record authorization, tenant routing, stored procedures, and page audit. Body reads omit design tokens by default so the host theme wins. The binding request publishes its required, unique 1..24-key collection bounds for every generated client, and all runtime error statuses reuse the shared API error contract. The generated contract now contains 265 operations across 205 paths, and all 37 double schemas are numeric rather than numeric-string unions.
2026.09.12 - Developer Kit 1.15.3 body schema normalization
Improved Integer normalization now runs through the global OpenAPI schema transformer instead of only at the operation-parameter layer. All 1,957 integer schema nodes across parameters, request bodies, response bodies, and reusable components exclude numeric strings and leaked regex patterns; the 137 genuinely nullable integer nodes retain null | integer rather than being incorrectly narrowed. Generated clients now receive numeric contractVersion, paging, count, sort order, priority, and integer custom-field contracts throughout the API.
2026.09.12 - Developer Kit 1.15.2 integer contract normalization
Improved The OpenAPI generator now normalizes all 77 integer parameters at the contract boundary instead of special-casing two Record Graph fields; none retain the ASP.NET integer/string union or numeric regex artifact. Record Graph additionally publishes its actual service rejection bounds for record search, related knowledge, and contextual candidates. The package gate directly compares both distributed presentation.ts copies with the LF-normalized canonical page-runtime source and with each other, so newline normalization cannot hide implementation drift. Current kit and API43 copy also use the generated 262-operation and 199-module-operation totals.
2026.09.12 - Developer Kit 1.15.1 contract alignment
Improved Record Graph OpenAPI now publishes integer-only maxDepth 1-5 and maxNodes 2-200 constraints and requires non-empty toRecordId and relationKey association fields. The API Map distinguishes vendor-only regeneration inputs from the two hash-verifiable shipped contracts and states that Record Graph is REST/SDK-only in the intentionally curated 42-tool MCP release. Native React extension dependencies and self-contained Puck-vendored sources are labeled explicitly, the stale 243-operation sentence is corrected to 262, and every UTF-8 ZIP entry uses LF line endings. The release builder now refreshes the operation and recipe inputs before generating the hash-bound API Map, preventing a successful write from immediately making its own map stale.
2026.09.12 - Developer Kit 1.15.0
New The shared BuildWithHQ/API43 Developer and Headless API ZIP now includes docs/API-MAP.md: all 23 first-class capability surfaces, all 18 Build This product routes, complete add/view/edit/remove/favorite/relationship/file/activity matrices, module-specific actions, and the secured bounded recursive Record Graph workflow. The deterministic archive carries all 262 published operations across 202 paths, regenerates and verifies the API Map before packaging, and retains exact authentication, SDK coverage, OpenAPI, recipe, React, MCP, and headless-server contracts.
2026.09.12 - Complete API route and usability inventory
Improved The new API Map provides a reproducible, source-backed route and day-to-day usability inventory for all 23 first-class capabilities and all 18 Build This products. It distinguishes the 194 authenticated tenant-runtime routes used by rendered SaaS pages from the 193 published Developer API module routes, classifies list/view, add, edit/modify, remove, favorite, association, files/evidence, activity, and module-specific actions, and maps every canonical Build This recipe step plus every additional operation explicitly named by the runnable solution manifests. A dedicated guide shows how any eligible canonical record can use registered relationship types to build a bounded recursive graph, safely supporting multi-level and cyclic associations without inheriting authorization through an edge. Product-managed record families have explicit lifecycle matrices, while derived views point back to their native secured owner instead of duplicating destructive actions.
2026.09.12 - Support Tickets production solution
New Support Tickets is now an operable mailbox-to-resolution SaaS over native Conversations and Universal Inbox. One managed Support Playbooks family uses 14 database-backed dynamic/custom fields across five responsive workspaces, while Conversations retain thread history and Inbox owns ticket identity, attention, assignment, priority, service level, resolution state, and ActivityVersion. Current secured contracts provide mailbox-owner configuration, atomic stable ticket allocation, customer replies on the canonical thread, explicit resolution, automatic reopen on later inbound mail, and HTTP conflict for stale replies. The routed journey also proved complete playbook lifecycle, gray/gold 25-pixel favorites, relationships, files, activity, cleanup, and owner/permission boundaries; golden/disposable SQL policy and desktop/mobile Chromium rendering passed. Template Library packaging remains separate.
2026.09.12 - Checkoff & Approval production solution
New Checkoff & Approval is now an operable evidence-backed checklist and human-signoff SaaS. One managed Verification Programs family uses 12 database-backed dynamic/custom fields across five responsive workspaces, while native Checklists & Signoffs, Files, Workflow, Universal Inbox, Favorites, relationships, and activity retain ownership. The current secured contracts provide template list/read/create/revision-fenced update/deactivation, exact run snapshots, up to 1,000 bounded items, verified document/photo proof, idempotent submit, stale-context protection, reject/revise/resubmit, and approval. The public Developer API recipe now exposes the complete template lifecycle. The routed journey proved proof replacement after rejection, gray/gold 25-pixel favorites, relations, files, activity, and cleanup; golden/disposable SQL policy, developer execute grants, OpenAPI/SDK checks, and desktop/mobile Chromium rendering passed. Template Library packaging remains separate.
2026.09.12 - Reservations production solution
New Reservations is now an operable capacity-protected booking SaaS over the current first-class module. Reservation Policies use 10 database-backed dynamic/custom fields; native products, Reservations, Contacts, Calendar, Files, Favorites, relationships, activity, tenant payment controls, and durable follow-ups retain their secured typed APIs and reviewed stored procedures. Five responsive workspaces cover booking, operations, product/capacity setup, customers, and payment/follow-up. The routed journey proved product lifecycle, authenticated booking, idempotent replay, server-locked capacity, party limits, active-user assignment, free-booking payment state, paid-booking payment-method enforcement, stale-write denials, follow-ups, gray/gold 25-pixel favorites, relations, files, check-in/completion, audited cancellation, and cleanup. Golden/disposable procedure policy and desktop/mobile Chromium rendering passed. Anonymous checkout and Template Library packaging remain intentionally separate.
2026.09.12 - FieldService production solution
New FieldService is now an operable request-to-approved-closeout SaaS refreshed from the repository's existing reference implementation. Template-owned Change Requests use 12 database-backed dynamic/custom fields; native Contacts own customers and team profiles, Work Orders own jobs and legal transitions, Calendar owns scheduling, Files and Checklists & Signoffs own evidence and approval, and Conversations plus Universal Inbox own communication and attention. Six responsive workspaces cover dispatcher, customer, technician, schedule, evidence, manager approval, and follow-up work. The routed journey proved lifecycle, gray/gold 25-pixel favorites, relations, assignment, schedule, file attachment, checklist photo proof, approval, follow-up, stale-write denials, and cleanup. Golden/disposable procedure parity, the deterministic reference bundle, and desktop/mobile Chromium rendering passed. Tenant billing remains explicitly deferred; Template Library packaging remains separate.
2026.09.12 - ActiveWorkplace production solution
New ActiveWorkplace is now an operable recursive-record coordination SaaS. Two managed record families use 16 database-backed dynamic/custom fields for pinnable work items and reusable graph playbooks across four responsive workspaces. The native first-class module owns idempotent pinning, bounded cyclic graphs, participants, responsibilities, deterministic Pulse, retained activity and snapshots, and read-only playback; Universal Inbox remains the shared attention layer. Current secured typed APIs and reviewed stored procedures provide complete record lifecycle, gray/gold 25-pixel favorites, registered relationships, stale-write protection, and current tenant, DataRole, location, and AI-read authorization. The routed journey proved pin, update, favorite, relation, participant, activity, graph-refresh, playback, resolve, and cleanup behavior. Golden/disposable procedure parity and desktop/mobile Chromium rendering passed. Template Library packaging remains intentionally separate.
2026.09.12 - AssetOps production solution
New AssetOps is now an operable asset, inspection, and maintenance SaaS. Five managed record families use 47 database-backed dynamic/custom fields for sites, assets, inspection findings, parts usage, and service history across five responsive workspaces. Native Contacts, Work Orders, Checklists & Signoffs, Files, Calendar, Favorites, record relationships, and activity preserve their current secured typed APIs and reviewed stored procedures. The routed journey proved customer and asset lifecycle, 25-pixel gray/gold favorites, recursive relationships, signature-verified photo proof, inspection approval, technician assignment, legal Requested-to-Completed work-order transitions, and cleanup. Location, assignee, invalid-transition, and stale-write denials passed, as did golden/disposable procedure parity and desktop/mobile Chromium rendering. Template Library packaging remains intentionally separate.
2026.09.12 - CaseFlow production solution
New CaseFlow is now an operable controlled case-management SaaS. Seven managed record families use 53 database-backed dynamic/custom fields for cases, parties, immutable stage evidence, tasks, evidence, decisions, and approvals across five responsive workspaces. Current secured typed APIs and reviewed stored procedures provide complete lifecycle, gray/gold 25-pixel favorites, registered relationships, secured files, activity, and personal Favorites. A server-owned transition procedure fixes new cases at Intake, serializes adjacent stages, rejects direct, stale, invalid, and out-of-order changes, and requires an approved Checklists & Signoffs run before Decision or Closed. The checklist revision and Universal Inbox ActivityVersion fences survive submission and approval. Five role policies, two locations, golden/disposable procedure parity, the routed intake-to-decision journey, and desktop/mobile Chromium rendering passed. Template Library packaging remains intentionally separate.
2026.09.12 - Headless SaaS DB production solution
New Headless SaaS DB is now an operable API-first managed backend with five record families, 35 database-backed dynamic/custom fields, and five professional responsive workspaces. Its exported server-side TypeScript client covers schema/search, complete record lifecycle, gray/gold 25-pixel favorites, registered relationship add/remove, inbound endpoints, webhooks, delivery retries, and correlation logs. A working React administration client keeps live app credentials and physical database routing inside a same-origin BFF. The routed public API journey proved create, read, update, cleanup/remove, favorite/unfavorite, relationship add/remove, read-only denial, webhook creation and signing-secret rotation, safe correlations, and secret/SQL authority exclusion. Golden and disposable stored-procedure policy, SDK routes, generated API recipes, and desktop/mobile Chromium rendering passed. Template Library packaging remains intentionally separate.
2026.09.12 - OpsAtlas production solution
New OpsAtlas is now an operable owned and revisioned operating-memory SaaS. Five managed record families use 35 database-backed dynamic/custom fields for operating domains, approved source registers, review programs, gap triage, and governed workflow links across five responsive workspaces. The native Knowledge Core supplies draft, view, edit, immutable revision, publish, archive/restore, collection, ownership, review, question, feedback, favorite, relation, file, and activity workflows through current secured typed APIs and reviewed procedures. Published AI-eligible sources enter the canonical multimodal pipeline; role-aware cited answers apply tenant, DataRole, location, field, record, and CanAiReadRecords policy before context, preserve visual evidence, and create a Knowledge Question instead of fabricating unsupported guidance. The routed author-to-publish/favorite/relation/ingest/answer journey, database policy, and desktop/mobile Chromium proof passed. Template Library packaging remains intentionally separate.
2026.09.12 - CompanyIQ production solution
New CompanyIQ is now an operable permission-aware company-knowledge and opportunity-intelligence SaaS. Five managed record families use 40 database-backed dynamic/custom fields for knowledge sources, business context, evidence-backed insights, cited evidence, and governed suggested actions across five responsive workspaces. Current secured typed APIs and reviewed stored procedures provide complete lifecycle, gray/gold 25-pixel favorites, registered relationships, files, activity, bounded ingestion, and cited semantic search. Retrieval filters the represented user's tenant, DataRole, location, record, field, and CanAiReadRecords scope before model context and preserves text and visual evidence through the canonical 256, 1024, and 1998-dimensional multimodal lanes using the current Qwen3-VL 8B profile. Golden/disposable database policy, the routed lifecycle/favorite/relation/AI product journey, and desktop/mobile Chromium proof passed. Template Library packaging remains intentionally separate.
2026.09.12 - CustomerPortal production solution
New CustomerPortal is now an operable branded external-collaboration SaaS with six managed record families and 54 database-backed dynamic/custom fields for requests, milestones, approvals, shared updates, private internal operations, and visibility reviews across five responsive workspaces. Explicit customer and internal-staff User Types have separate reviewed menus and assignment policies; DataRoles and shared/internal Locations enforce the disclosure boundary. Current secured typed APIs and stored procedures provide create, view, edit, safe remove, gray/gold 25-pixel favorites, registered record relationships, files, messages, activity, and personal Favorites. External users can work customer-safe records while internal pages, records, fields, search hits, graph nodes, and cross-boundary edges remain concealed. The routed internal/external API and SQL isolation journey plus desktop/mobile Chromium proof passed. Template Library packaging remains intentionally separate.
2026.09.12 - RelateEverything production solution
New RelateEverything is now an operable relationship-first CRM over canonical Records and RecordRelations. Native Contacts retain complete create, view, edit, 25-pixel favorite, and safe removal lifecycle; six managed dynamic/custom-field record families cover companies, workstreams, opportunities, relationship context, duplicate review, and connected automations across five responsive workspaces. Current secured typed APIs and stored procedures provide lifecycle, favorite/unfavorite, registered relation add/remove, evidence files, activity, AI Insights, and personal Favorites. The relationship graph applies current tenant/SaaS identity, active DataRole, location, and direct-conversation participation rules before adding nodes, then returns edges only when both endpoints are authorized. Connected automations remain approval-required for material mutations. Golden/disposable procedure and graph policy checks, the routed native-Contact and six-entity journey, and desktop/mobile Chromium proof all passed. Template Library packaging remains intentionally separate.
2026.09.12 - TeamBox production solution
New TeamBox is now an operable shared communications command center. Native Conversations retain thread, message, reply, favorite, and removal lifecycle; Universal Inbox remains a bounded attention and ownership projection with the ActivityVersion stale-context fence. Six managed dynamic/custom-field record families cover channel intake policies, queues, routing rules, classification review, SLA policies, and handoff playbooks across five responsive workspaces. Current secured typed APIs and stored procedures provide complete lifecycle, favorite/unfavorite, record relations, evidence files, activity, and personal Favorites. Classification reviews retain the native Conversation pointer, authorized evidence, confidence, model/harness version, and reviewed disposition, while customer-facing replies and material actions stay policy- or human-approval gated. The initial Inbox view is bounded to 25 records so every visible source can resolve its accurate favorite state without exhausting the tenant request budget. Golden/disposable procedure verification, the routed native-conversation and six-entity journey, stale-write rejection, and desktop/mobile Chromium proof all passed. Template Library packaging remains intentionally separate.
2026.09.12 - Northstar production solution
New Northstar is now an operable evidence-backed executive-intelligence SaaS with six managed record families for versioned metric definitions, source-watermarked observations, forecasts, material signals, scenarios, and frozen briefings. Five professional responsive workspaces provide the executive scorecard, material-change queue, metric/forecast drill-down, scenario comparison, and executive briefing/decision log. Current secured typed APIs and stored procedures provide complete lifecycle, favorite/unfavorite, record relations, evidence files, activity, and personal Favorites. Secured AI Insights remain read-only synthesis; briefings retain exact evidence and assumptions, model/harness lineage, reviewer and disposition, and a frozen timestamp, while financial commitments and operating writes remain approval-gated. Golden/disposable parity, fail-closed AI roles, the routed six-entity journey, and desktop/mobile Chromium proof all passed. Template Library packaging remains intentionally separate.
2026.09.12 - LaunchPilot production solution
New LaunchPilot is now an operable governed marketing-operations SaaS with six managed record families for campaigns, consent-aware audience snapshots, approved asset versions, channel runs, experiments, and performance snapshots. Five professional responsive workspaces provide campaign command and calendar, campaign detail, audience/consent review, asset and launch approval, and experiment/performance analysis. Current secured typed APIs and stored procedures provide complete lifecycle, favorite/unfavorite, record relations, evidence files, activity, and the personal Favorites workspace. Universal Inbox and the reviewed Workflow approval contract retain launch decisions; channel records freeze audience, asset, spend, idempotency, and evidence while remaining non-activatable until configured approval. Golden/disposable procedure parity, fail-closed AI roles, the routed six-entity journey, and desktop/mobile Chromium create-favorite-remove proof all passed. Template Library packaging remains intentionally separate.
2026.09.12 - Resolve production solution
New Resolve is now an operable permission-aware support SaaS. Native Conversations retain customer communication, Universal Inbox remains the attention layer, and Knowledge Core supplies versioned Official policy evidence. Four managed record families cover customer context, issues, cited resolution suggestions, and escalations across five professional responsive pages. Current secured typed APIs and stored procedures provide lifecycle, favorite/unfavorite, record relations, evidence files, activity, and the personal Favorites workspace. Customer-facing and material operations remain policy- or human-approval gated with the Inbox ActivityVersion stale-context fence. Golden/disposable procedure parity, fail-closed AI roles, the routed API journey, and desktop/mobile Chromium create-favorite-remove proof all passed. Template Library packaging remains intentionally separate.
2026.09.12 - SignalIQ production solution
New SignalIQ is now an operable revenue-intelligence SaaS solution with six managed record families for accounts, contacts, opportunities, signals, versioned score snapshots, and recommendations. Five professional responsive pages provide a revenue command center, Account 360, buying-signal feed, governed next-best-action queue, and explainable scoring. Every managed entity uses current secured typed APIs and stored procedures for create, view, edit, remove, favorite/unfavorite, relationships, files, and activity. Secured AI Insights are read-only findings; recommendations retain evidence, confidence, score/model versions, ownership and expiry, while material actions remain behind policy or human approval. Golden/disposable procedure parity, fail-closed AI roles, the routed six-entity API journey, and desktop/mobile Chromium create-favorite-remove proof all passed. Template Library packaging remains intentionally separate.
2026.09.12 - CrewOS production solution
New CrewOS is the first product-specific Build This concept completed as an operable SaaS solution. It includes a professional governed AI team command center, owner-scoped add/edit/security/deactivate controls over the current GoClaw team contracts, three managed record families, six published pages, shared gray/gold 25-pixel favorites, secured file attachments, record relationships and activity, Universal Inbox approvals, and the existing ActivityVersion stale-context fence. Its materializer now adds installed pages to the verified installer User Type menu through the reviewed menu procedure. The complete API journey and desktop/mobile Chromium experience passed against a route-resolved disposable tenant. CrewOS remains a production solution rather than a Template Library listing until the later exact-version packaging task.
2026.09.12 - Build This production-solution program
New The eighteen Build This concepts now have a dedicated production build queue, separate from the Template Library. A shared Professional Foundation has been materialized into a guarded, route-resolved disposable tenant and exercised through its real React UI and APIs for create, view, update, remove, favorite/unfavorite, record relationships, and activity. Desktop and mobile rendering use the current TailAdmin-derived visual system. Each product will be built and proven as an operable SaaS solution before an exact-version reusable template is published; the remaining product solutions are not yet represented as complete.
2026.09.12 - Universal Favorites and database-contract hardening
Improved Record surfaces can now load the signed-in user's secured favorite state and show the shared 25-by-25-pixel star: gray when unsaved and gold when favorited. The Favorites workspace remains the personal cross-module destination. The missing state procedure was restored to the CustomerCopy golden database, all six golden exports now rebuild cleanly with exact live/export parity across 1,210 stored procedures, and the active npm dependency scopes were upgraded to resolve the reviewed Vitest, Tiptap, and fast-uri advisories.
2026.09.09 - Tenant presentation administration and live developer kits
New Builders can explicitly allow shared User Types and menu/page subsets for tenant administration. Account owners can narrow and reorder those menus without gaining data authority, and download a deterministic developer ZIP containing only their active module routes, current pages, bindings, compatibility versions, working typed clients, React starters, and offline validation—with no credential, fixture, or placeholder contract.
2026.09.09 - Hosted tenant user invitations
New Tenant account owners can send expiring, single-use hosted invitations with snapshotted User Type, DataRole, and location assignments. Recipients establish their own password; external/headless users remain passwordless unless explicitly invited. Tokens are hash-only in storage, fragment-only in email links, POST-only during resolution, revocable, rotation-safe, and replay-protected.
2026.09.08 - Exact API authentication catalogs
New Developer Kit 1.14.2 derives public, draft-app, live-app, and live-or-delegated labels directly from each OpenAPI operation. Product recipes carry the same accepted clients, regenerate during release builds, and fail the gate if their operation hash or authentication contracts drift. The extension guide also documents the current opaque invocation identity boundary without claiming a token-introspection API.
2026.09.08 - Developer Kit contract clarity
New Developer Kit 1.14.1 publishes required arguments for all 42 MCP tools, full concurrency-fenced schemas and per-app approval metadata for sensitive writes, and separate OpenAPI schemes for draft-app, live-app, and delegated-user credentials. A twelve-chapter system guide explains the platform, all first-class modules, React and page JSON, exact-version forking, headless use, MCP, and private VM/PostgreSQL extension services.
2026.09.08 - Approval-gated MCP module writes
New Developer Kit 1.14.0 adds real checklist-item toggle and Work Order status-change tools. Both use the same secured service and stored procedure as their REST operation, require the exact module write scope and optimistic-concurrency token, and remain undiscoverable until a permitted builder approves the capability for that SaaS app.
2026.09.07 - Local Puck binding editor
New Developer Kit 1.13.0 includes a self-contained local Puck 0.23.0 editor over the production BuildWithHQ adapter. Developers can open canonical page JSON, set registered binding keys and bounded data paths, download the result, and save and validate a real unpublished draft through a trusted-server command without exposing credentials to Vite.
2026.09.07 - HTML-to-Puck developer converter
New Developer Kit 1.12.0 converts static HTML or a dist/index.html entry into deterministic, schema-valid Professional Foundation page JSON. It ships an annotated control-panel example, strict lossy-conversion reporting, catalog-enforced component properties, and intentionally excludes scripts, arbitrary CSS, credentials, identity and inferred bindings.
2026.09.06 - Headless end-user delegation
New App-bound Developer API clients can create tenant accounts and passwordless external users, assign DataRoles and Locations, issue 2-15 minute delegated-user tokens, revoke them, and deactivate users. Module calls execute as that exact user and retain the originating API client for audit.
2026.09.06 - Complete API43 / headless surface
New The generated v1 contract publishes 237 operations across 192 paths, including all 181 promoted first-class module operations, nine tenant identity operations, and the MCP Streamable HTTP transport.
2026.09.07 - Developer Kit 1.10.0
New Eighteen Build This concepts now ship as contract-generated API recipes with exact routes, least-privilege scopes, SDK methods, request schemas, response statuses, delegated-user boundaries, and isolation/idempotency release assertions. The kit retains the secured module MCP reads, browser credential guard, and tested DeepSeek Harness setup from 1.9.2.
2026.09.07 - Draft and live Developer API keys
New Draft-only bwk_draft_ credentials can edit and validate unpublished page JSON without gaining tenant-data or publication authority. Publishing now requires an explicit bwk_live_ credential, pages.publish, the exact draft-history ID, and the expected live version. Developer Kit 1.11.0 contains all 243 operations and the separate draft/live TypeScript clients.
2026.09.07 - Tenant account-owner administration
New Tenant account owners can manage users, DataRoles and locations, review last-login information, and generate a secret-free developer ZIP containing only their account identity and active module capabilities. The console and ZIP remain tenant-session authorized; account IDs never act as credentials.
2026.09.05 - Professional presentation system
New Metrics, entity and progress lists, charts, grids, timelines, tasks, row actions, icons, and responsive layouts can be combined into original admin experiences.
2026.09.05 - First-class module gallery
New Every cataloged first-class feature has validated sample and live pages, with save-to-Builder and page-JSON downloads.
2026.09.05 - Copyable React module guides
Improved First-class feature articles now include complete styled and unstyled React starting points, data contracts, loading, empty, error, and action behavior.
2026.09.05 - Responsive presentation hardening
Improved Wide grids, charts, badges, and trailing values remain contained and usable on desktop, tablet, and small mobile screens.
2026.09.04 - SaaS themes
New Version-fenced themes carry mode, CSS variables, and design tokens from the database to painted React pixels.
2026.09.04 - Interactive presentation actions
New Checklist toggles and declared grid actions preserve entitlement, revisions, conflict refresh, failure rollback, and in-flight state.
2026.09.04 - Embedded Universal Inbox
New Builders can place a full Inbox experience on a normal page and launch it from a menu while retaining the top-bar attention view.
2026.09.03 - Runtime-observed catalog
Improved Static inventory joins runtime observations so route-to-procedure pairs are evidence and the delta identifies untested operations.
2026.09.03 - Developer route explorer
New Developers can search the published API catalog by route, operation, module, verb, scope, and authentication requirement.
2026.09.03 - Database-backed theme contracts
New Procedure-only, version-fenced contracts read and write SaaS themes and surface them through tenant bootstrap without granting direct table access.
2026.09.02 - Tenant session lifecycle
Improved Sessions restore across browser reloads and expired sessions return users to a clear sign-in state.
2026.09.02 - Negative-path API hardening
Improved Missing and foreign identifiers remain indistinguishable while ordinary misses return 404 instead of outage-like 503 responses.
2026.09.02 - Security rejection audit
New Rejected tenant identities and other reviewed security events are recorded with correlation evidence so blocked attacks are observable.
2026.09.01 - Checklists & Signoffs
New Checklists attach to records, tickets, projects, and work orders, support up to 1,000 items, and accept documents or photos as proof.
2026.09.01 - Universal data presentation blocks
New Reviewed API results can render as metric sets, entity lists, progress lists, series charts, data grids, and timelines without loading an unbounded record graph into the page.
2026.08.30 - Multi-tenant battle testing
Improved Realistic tenant, API, permission, workflow, Inbox, AI, and routing journeys feed a repeatable readiness harness.
2026.08.29 - Universal Inbox ticketing
New Inbound email addresses can be ticketing channels with permanent keys, assignment, SLA, resolution, approval, and ActivityVersion protections.
Capability review: 2026-09-14. For exact current technical availability, use the generated API Map and first-class module inventory.