Project & Governance

About NucleusFlow

Built in London with memory-safe Rust, deterministic engineering, and zero telemetry.

1. Mission & Design Philosophy

NucleusFlow (nucleusflow) was created to bridge the gap between monolithic static site generator binaries and low-level Markdown parsers. Engineering teams frequently need the same reliable content processing pipeline in two places: on the command line for static documentation builds, and inside Rust backend services for dynamic rendering and validation.

NucleusFlow is guided by four core engineering invariants:

  1. Zero Unsafe Code (#![forbid(unsafe_code)]): Memory safety is non-negotiable when parsing untrusted Markdown, YAML frontmatter, and HTML templates.
  2. Composable Trait Boundaries: Content processing (Processor), template rendering (TemplateRenderer), and output generation (Generator) are cleanly separated so any stage can be swapped, mocked, or embedded independently.
  3. Deterministic Resource Budgets: Every stage enforces explicit byte caps (10 MB content, 64 KB metadata, 1 MB template, 100 MB cache) to guarantee predictable latency (~28.0 µs per page).
  4. Zero Telemetry: Neither the nucleusflow library/CLI nor the nucleusflow.com documentation portal makes outbound analytics, telemetry, or tracking requests.

2. Ecosystem Synergy

NucleusFlow builds upon and integrates with open-source Rust crates maintained by Sebastien Rousseau:

  • noyalib: Pure-Rust, memory-safe YAML 1.2 parser powering NucleusFlow's frontmatter extraction.
  • dtt: Date, time, and timezone utilities for structured build timestamps.
  • ssg: The Static Site Generator compiling this documentation portal (nucleusflow.com).
  • Skeletonic CSS: Lightweight, WCAG 2.2 Level AAA CSS layout foundation.

3. Governance & Maintainer

NucleusFlow is authored and maintained by Sebastien Rousseau in London, United Kingdom. All architectural changes, releases, and security advisories are managed transparently on GitHub: