EXPERIMENTS
Nucleus, before it was a framework
Before Nucleus had a public manifest and 697 documented classes, it was an undocumented pile of CSS shared between two live products.
An internal shortcut, not a plan
Nucleus didn't start as a framework. It started as the CSS both LeadScrapper Pro and Itiner needed and neither had time to write twice. Copy the button styles from one project into the other, then copy them back with a fix, repeated until the drift became its own problem.
The decision to formalize it into a real system (tokens, a manifest, a validator) came only after the informal version had already proven the shortcut was worth keeping. That's the pattern most experiments here follow: build the small version first, only build the documented version once the small one earns it.
RELATED
