LibraryFounder ecosystem

Architecture note · October 2, 2026

A small public stack, with larger choices deferred.

These are current implementation facts and scoped tradeoffs, not universal technology recommendations.

Founder portfolio and operating philosophy. These systems are separate from the Tesseract customer platform.

Public site

01

Next.js 14 App Router

Static export creates deployable files without requiring application server rendering.

02

React 18

Pinned for compatibility with the site’s current 3D dependency generation.

03

TypeScript

Strict types make page and content contracts easier to review.

04

Tailwind CSS

Shared tokens and semantic component classes keep the redesign consistent.

05

Vitest

Focused render and behavior tests protect the public content contract.

This repository is a fully static export. It contains no API routes, middleware or server-rendered customer application.

Local workflow prototype

What exists

Local inquiry records, a document library, manual cited review and simulated actions support evaluation without external effects.

What is deliberately open

No public commitment has been made to an AI provider, hosted application architecture, scheduler vendor or sending integration.

Tradeoffs

  • Static export favors resilience and simple hosting, but cannot provide authenticated customer workflows by itself.
  • Local-first prototyping makes claims easier to inspect, but does not establish production readiness.
  • A small stack reduces coordination overhead, but future integrations must be selected around the customer’s existing tools.

Founder architecture model

The ecosystem’s canonical five layers are Soul → Council → Intelligence → Governance → Harness. That conceptual model is separate from this site’s Next.js stack.