1 comments

  • promptfluid1 day ago
    We’ve been building a small system called XCTBL.<p>It’s an identity layer for tools that require persistent state — but it deliberately separates identity&#x2F;authentication from recording and retention.<p>The fastest way to understand it is the new start route here:<p><a href="https:&#x2F;&#x2F;rcrdbl.com" rel="nofollow">https:&#x2F;&#x2F;rcrdbl.com</a><p>RCRDBL is the records layer. It accepts signals (files, text, artifacts), retains them permanently, and does not authenticate users.<p>XCTBL is the external system that creates identities (“Stars”) and manages access to tools that need persistence.<p>The separation is intentional:<p>• One system remembers. • One system authenticates. • Tools sit on top.<p>There’s optional narrative framing, but it’s not required to use anything. Tools work without engaging with the story layer.<p>This is early, opinionated, and intentionally constrained. Curious how others think about permanent records, identity boundaries, and whether this kind of separation makes sense.
    • andai1 hour ago
      I don&#x27;t understand anything on your website or this comment. Maybe I&#x27;m not the target audience?
      • viraptor18 minutes ago
        The vibe I get is Urbit meets browsable S3 with Kerberos on the side as the XCTBL project. It&#x27;s half serious half art and uses confusing vocabulary on purpose. (I mean both Urbit and this)