alt Hacker NewsWe’ve been building a small system called XCTBL.
It’s an identity layer for tools that require persistent state — but it deliberately separates identity/authentication from recording and retention.
The fastest way to understand it is the new start route here:
RCRDBL is the records layer. It accepts signals (files, text, artifacts), retains them permanently, and does not authenticate users.
XCTBL is the external system that creates identities (“Stars”) and manages access to tools that need persistence.
The separation is intentional:
• One system remembers. • One system authenticates. • Tools sit on top.
There’s optional narrative framing, but it’s not required to use anything. Tools work without engaging with the story layer.
This is early, opinionated, and intentionally constrained. Curious how others think about permanent records, identity boundaries, and whether this kind of separation makes sense.
Replies
I don't understand anything on your website or this comment. Maybe I'm not the target audience?
Records and documents are usually private and owned for various good reasons. I don’t understand the core concept of decoupling them. What is the benefit? How does one make associations or use tools? Is everything public? How can you prevent spam?
So if I understand it correctly, its basically a system where AI gets a persistent internal memory? and authentication works on another layer and everything is wrapped in a sci-fi story-system? Is it because other tools always give dashboards that dont actually make a lot of sense, just "feel logical" but dont really give a lot of usefull context?
To me this is all insufferably pompous. Drop the big talking and marketing and I would pay more attention. The quality of the idea and implementation should speak a lot more for itself.