Product blog

Product blog

Product updates, field guides, and field notes—each with links to docs and the hub where relevant. High-level milestones also appear on the changelog.

  1. A map of autonomous agent zones and mandatory human-review checkpoints divided by reversibility and blast radius

    Field guide · Jun 4, 2026

    Guardrails and human review: where we let the agent run and where we don't

    A practical map of where AI agents operate autonomously and where a human checkpoint is non-negotiable, and the reasoning behind each boundary.

    • Autonomous zones vs hard gates
    • Reversibility decides the line
    • The build as a tireless reviewer

    Engineering

    Read
  2. Push to preview URL, promote to production, and instant rollback as the solo deploy loop

    Field guide · Jun 3, 2026

    Shipping on Vercel solo: the deploy and preview workflow that keeps overhead near zero

    The deploy, preview, and rollback loop that removes the ops tax from running multiple apps as a solo operator.

    • Every push gets a preview URL
    • Promote to production in a click
    • Instant rollback to any prior deploy

    Engineering

    Read
  3. A three-stage workflow from prompt expansion through planning to coding, with the planning step highlighted

    Field guide · Jun 3, 2026

    Our three-mode workflow: prompt expansion → planning → coding (and why we never skip the middle)

    Why the planning pass between understanding a request and writing code is the step that determines whether AI-assisted development produces something maintainable.

    • Expand → plan → code
    • The planning pass is non-negotiable
    • Where rework actually comes from

    Engineering

    Read
  4. A page request producing an on-demand Open Graph image at the edge from the page title and description

    Field guide · Jun 2, 2026

    Generating social share images at the edge

    How an edge image route turns the typed post data into a per-page share card automatically, and why dynamic beats static here.

    • OG images generated on demand
    • Rendered at the edge per page
    • No static asset to maintain

    Engineering

    Read
  5. A single Next.js app serving many hub sections, with product spokes as linked external apps

    Field guide · Jun 2, 2026

    One Next.js app, many sections: routing a hub-and-spoke portfolio from a single codebase

    How a single App Router codebase serves an entire multi-product hub, and why that beats a constellation of separate apps when one person maintains it.

    • One App Router project
    • components/sections pattern
    • Shared layout, metadata, sitemap

    Engineering

    Read
  6. The persistence ladder: in-memory state, IndexedDB local saves, and account-backed durable saves

    Field guide · Jun 2, 2026

    Durable saves without a backend war: IndexedDB, account sync, and when you finally add login

    An engineering field note on persistence for browser tools: in-memory loss, local IndexedDB saves, the jump to account-backed durability, and matching the saving model to the product rather than the fashion.

    • IndexedDB local saves
    • Accounts add cross-device durability
    • Match saving to the product

    Novus Stream Solutions

    Read
  7. Content stored as typed TypeScript objects compiled into the site versus a separate CMS and database

    Field guide · Jun 1, 2026

    Code-as-content: why our blog is hundreds of TypeScript objects, not a CMS

    The case for treating content as code — version-controlled, type-checked, deployed with the app — instead of running a content management system.

    • No CMS, no database
    • Posts are typed TS objects
    • Content ships with the code

    Engineering

    Read
  8. A union type constraining doc links and a structured section schema rejecting malformed posts at compile time

    Field guide · Jun 1, 2026

    Type-safe content: how a DocSlug union and structured sections stop broken posts

    How a few lines of TypeScript types make broken links and malformed posts impossible to ship, not just unlikely.

    • A union type for doc links
    • Structured sections, not raw HTML
    • Broken content = build failure

    Engineering

    Read
  9. A model registry being checked against the Hugging Face API, with unverified entries flagged and replaced

    Field guide · Jun 1, 2026

    Shipping a model registry you can trust: auditing against Hugging Face

    An engineering note on auditing an AI model registry for honesty — verified IDs, real sizes and licenses, and classical baselines labelled as such.

    • Audited vs HF API + Transformers.js v3
    • Five unverified IDs replaced
    • Classical baselines labelled honestly

    Stack & engineering

    Read