Thanks! You caught us—the blog post is definitely more about the 'Why' (the creative philosophy) than the 'How' (the technical implementation).
Here’s the technical side: I've built a private RAG (Retrieval-Augmented Generation) system. We've indexed our 'Lucent Universe' world-bible—which includes everything from character timelines to the specific physical laws of Lucarn shapeshifting (conservation of mass, thermal limits, etc.)—into a vector database.
I essentially treat the world-bible as 'Source Truth' and the draft manuscript as 'Code' to be linted. We run an audit script that cross-references new chapters against the index to flag logical breaks—like a character knowing something they haven't learned yet, or a physical impossibility in a shift.
It solves the massive cognitive load of maintaining 300k words of consistency without the machine ever touching the actual prose generation. If there’s interest, I’d be happy to do a deeper write-up on the stack itself!
unknown|23 days ago
[deleted]
kpinkerman|23 days ago
Here’s the technical side: I've built a private RAG (Retrieval-Augmented Generation) system. We've indexed our 'Lucent Universe' world-bible—which includes everything from character timelines to the specific physical laws of Lucarn shapeshifting (conservation of mass, thermal limits, etc.)—into a vector database.
I essentially treat the world-bible as 'Source Truth' and the draft manuscript as 'Code' to be linted. We run an audit script that cross-references new chapters against the index to flag logical breaks—like a character knowing something they haven't learned yet, or a physical impossibility in a shift.
It solves the massive cognitive load of maintaining 300k words of consistency without the machine ever touching the actual prose generation. If there’s interest, I’d be happy to do a deeper write-up on the stack itself!