That entry is experiential-first. RCRDBL is the records layer; XCTBL is the place to understand the model by walking through it.
The deeper bit is the default: records persist without accounts, and identity/auth is a separate layer that only shows up when ownership is needed. The UI is just the thinnest slice of the model.
> EXCITABLE. EXACTABLE. EXECUTABLE. A shared universe of destinations and memory.
> Space is a SaaS platform presented by PromptFluid. It contains a collection of tools and toys that are released on a regular cadence.
> PromptFluid Official Briefing: You are reading from the ground. Space is above. We transmit because the colony cannot afford silence.
> You can ignore the story and still use everything. But if you want the deeper current: this relay exists because the colony is fragile, and Space is the only place the tools can grow without choking the ground.
> Creating an account creates a Star. Your Star is your identity within Space and unlocks Spacewalking capabilities and certain tools that require persistent state
“Fair point — that’s totally valid…” come on, are we supposed to just pretend this is an acceptable submission? I’m all in for vibe coding but at least be upfront about it and don’t waste other people’s time and energy.
What’s this supposed to be?
promptfluid•1mo ago
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:
https://rcrdbl.com
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.
andai•1mo ago
viraptor•1mo ago
promptfluid•1mo ago
The difference (for me) is scope: I’m not trying to replace an OS or invent a new universe. It’s intentionally narrow—persistent records first, identity second, tools layered on top.
The language is opinionated, but the constraint is real: records shouldn’t depend on accounts by default.
photon_garden•1mo ago
x______________•1mo ago
I'm going to miss the days where these signs were obvious.
promptfluid•1mo ago
The short version: RCRDBL is just a place to drop things that should persist (text, files, artifacts) without accounts. XCTBL is a separate system for identity/auth when persistence needs ownership.
If you’re not interested in permanent records or identity boundaries, it probably won’t resonate—and that’s okay.
pineaux•1mo ago
promptfluid•1mo ago
The story layer exists because most tools hide weak models behind dashboards that feel coherent. This flips that: the system model is explicit, and the UI adapts to how people actually reason.
You can ignore the story entirely and still use the tools.
Check back on the first of the month. Space will double in size.
dwb•1mo ago
promptfluid•1mo ago
I’m trying to be explicit about the constraints rather than persuasive about the outcome. If the ideas or implementation don’t stand on their own yet, that’s useful signal — I’d rather expose that than hide it behind polish.
Appreciate you calling it out.
reilly3000•1mo ago
promptfluid•1mo ago
The benefit is durability and reuse: records can persist, move, or be re-associated without being owned by a single app or login. Identity is layered on top rather than baked in.
Tools operate on records they have explicit access to (by Star / capability), not global visibility. Spam is constrained by identity cost and rate limits, same as any system — decoupling doesn’t imply openness.
If this ends up being a bad abstraction, I want that to fail visibly rather than hide behind a conventional model.