Lattice

A Seed is the smallest unit — a single page or article on a single domain. Seeds have topical affinity but no obligation to each other.

A Cluster is a group of seeds that share enough topological overlap to link usefully. Clusters live on one domain but have their own internal hub / spoke structure. The Content Empire blueprint in Brainboot produces one cluster per run — that's where Brainboot and Lattice overlap operationally.

A Constellation is a set of clusters spanning multiple domains that share an underlying thesis. The same topic treated from multiple angles, each on its own site, with cross-site backlinking that reinforces topical authority at the constellation level without concentrating link juice on a single domain.

A Lattice is the full network — every constellation together, treated as one organism for the purpose of pruning, promoting, and reallocating attention. The Lattice Dashboard is how I steward the organism: an admin surface that lets me audit, monitor, and auto-patch the network from one control plane instead of one domain at a time.

Classical SEO strategy is "build a site, pick keywords, write articles, get links." That approach scales linearly — each site is an independent project that needs its own authority, its own content, its own linking, its own monetization, its own monitoring.

Lattice treats the entire network as one system. Content that works in one cluster gets adapted for sibling clusters in the same constellation. Monetization strategies that perform at one tier migrate upward or downward depending on the stage of the cluster's growth. The Lattice Dashboard shows which joints of the network are under the most load and which ones are starving — exactly the same inspection you'd run on a literal garden lattice.

12+ live SEO cluster sites running in production on Cloudflare. Each one is independently deployed and independently monetized, but all are tracked in a unified Supabase database and routed through shared workers for affiliate links, monitoring, and content distribution.

An affiliate-config.json system lets me adjust monetization across clusters without touching code. A monitoring dashboard (private — the Lattice admin) shows traffic, revenue, and content velocity at every tier of the hierarchy.

The dashboard itself is the part of Lattice the public will never see. It lives under dashboard.deepsynthesis.org (a subdomain reserved specifically for it) and is gated behind authentication. The public-facing cluster sites themselves are where the content lives — the dashboard is where the gardener tends the network.

A lattice in horticulture is a framework you give to a climbing plant so the plant can decide its own shape while still holding together structurally. That's exactly what the network architecture does: it provides the topological framework (the tiers, the routing, the monitoring) and lets the content decide where it wants to grow.

An Architect would call this "content strategy with analytics." A Gardener calls it "tending the lattice." The difference isn't cosmetic — it's the difference between forcing content to fit a plan and watching which content wants to grow and feeding it.