UTC :: --:--:-- RUST :: stable :: 1.96.0 CLIENT :: browser :: detecting PYPI :: status :: operational CLIENT :: AWS/REGION :: us-east-2 LINUX :: stable_kernel :: 7.0.10 CLOUDFLARE :: pages :: degraded_performance NODE :: lts :: 24.16.0 CLIENT :: os :: detecting CRATES.IO :: crates :: 275k+ GITHUB :: actions :: operational CLIENT :: ip :: masked PYTHON :: stable :: 3.14.x UTC :: --:--:-- RUST :: stable :: 1.96.0 CLIENT :: browser :: detecting PYPI :: status :: operational CLIENT :: AWS/REGION :: us-east-2 LINUX :: stable_kernel :: 7.0.10 CLOUDFLARE :: pages :: degraded_performance NODE :: lts :: 24.16.0 CLIENT :: os :: detecting CRATES.IO :: crates :: 275k+ GITHUB :: actions :: operational CLIENT :: ip :: masked PYTHON :: stable :: 3.14.x
~/products.d :: public launch surface

Product systems, not brochureware

LatticeFoundry launches with two public product lanes: RoleThread Lite for local-first narrative AI dataset engineering and LitLaunch for Streamlit runtime governance. Additional ecosystem tooling stays withheld until it earns its own launch surface.

PUBLIC_PRODUCTS::02
RC::V1_SURFACE

RoleThread Lite

RoleThread Lite is a creator-controlled workspace for shaping narrative AI training data: create, validate, repair, organize, merge, and export clean datasets while keeping JSONL files, sidecars, registry data, backups, and workflow decisions local.

./open_product
RC::RUNTIME_LAYER

LitLaunch

LitLaunch is the operational launch layer for serious Streamlit applications: explicit backend ownership, health checks, browser/app-window strategy, graceful shutdown, diagnostics, and runtime posture visibility without replacing Streamlit.

./open_product

Visibility Policy

  • Public launch products: RoleThread Lite and LitLaunch.
  • Future ecosystem tooling remains intentionally undisclosed until it is ready for its own surface.
  • Product pages should explain real software without inventing scale or fake traction.

Download Strategy

  • LatticeFoundry should eventually become the primary user-facing download location.
  • GitHub Releases remain developer-facing until a dedicated download surface is implemented.
  • Download automation comes online only after release ownership and support paths are stable.