Autosite is one of the clearest expressions of a recurring T-drive theme: if a task keeps repeating, it should eventually become a system. Building one website is craft. Building the tenth should start to look like infrastructure.
Where it is now
Autosite sits in the active project area as a build-pattern project rather than a single public product. Its role in the stack is to capture the parts of site creation that repeat: structure, copy scaffolding, deployment, routing, assets, and live verification.
The barriers
The barrier is quality control. Automating a bad website is easy. Automating a site that still feels specific, useful, and credible is much harder. The stack needs enough automation to move quickly and enough judgement to avoid generic output.
How I am approaching it
The approach is to treat each live site as training material for the next one. whytohireme, LabLocum, Fortress404, FocusGoods, and Worthington all teach something different about how a generated or assisted site should be structured, deployed, and verified.