promptfluid

6 ms·

31.
by promptfluid 10mo ago
I am implementing a diagnostic mode that will toggle the tools and story on and off. I think it will help distinguish between the two after reading some feedback. Thanks for your input. I will resolve this gap.
32.
by promptfluid 10mo ago
Good questions. Records aren’t public by default — they’re decoupled from accounts, not from access control. The benefit is durability and reuse: records can persist, move, or be re-associated without being owned by a single app or login. I
33.
by promptfluid 10mo ago
Fair surface read — if you only see the drop zone, it does look like “pastebin for files.” The deeper bit is the default: records persist without accounts, and identity/auth is a separate layer that only shows up when ownership is need
34.
by promptfluid 10mo ago
Fair criticism. 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.
35.
by promptfluid 10mo ago
If you just want to explore the system without worrying about records or architecture, start here: https://XCTBL.com That entry is experiential-first. RCRDBL is the records layer; XCTBL is the place to understand the model by wa
36.
by promptfluid 10mo ago
Close, with one correction: the memory isn’t AI-owned—it’s system-owned and user-agnostic by default. The story layer exists because most tools hide weak models behind dashboards that feel coherent. This flips that: the system model is expl
37.
by promptfluid 10mo ago
That’s a reasonable read, and I won’t dodge it. 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 langu
38.
by promptfluid 10mo ago
Totally fair. If it didn’t click, that’s on me, not you. 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 persiste
39.
An experiment in separating identity, memory, and tools(rcrdbl.com)
33 points by promptfluid 10mo ago|25 comments
40.
by promptfluid 10mo ago
We’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 t
41.
by promptfluid 10mo ago
Just updated the beginning routes for greater lore and clarification
42.
Show HN: Xctbl – a system built around records, tools, and context (no signup)(rcrdbl.com)
1 points by promptfluid 10mo ago|1 comments
43.
by promptfluid 10mo ago
That’s fair feedback, and I agree. The current flow is intentionally minimal, but it does front-load the account wall more than it should. A better approach is letting people explore at least one system or environment before asking for an e
44.
by promptfluid 10mo ago
I built Space after noticing that most projects I worked on felt rushed into clarity, features, pricing, positioning - before the system itself had time to settle. This is an attempt to reverse that. I’m deliberately keeping things small, v
45.
Show HN: A living system of software that grows over time(xctbl.com)
2 points by promptfluid 10mo ago|3 comments
46.
by promptfluid 11mo ago
Yeah, it’s the panic tells that give it away — reflexive, not rational. When markets start reacting like prey instead of predators, it’s because they know the whole structure’s wired too tight. Tiny sparks shouldn’t cause stampedes unless e
47.
by promptfluid 11mo ago
This is wild — optimizing I/O and memory flow instead of brute-forcing with clusters is exactly the kind of rethink AI infrastructure needs. You basically inverted the whole scaling narrative. Curious if the zero disk reads trick could
48.
by promptfluid 11mo ago
Hallucination usually isn’t random — it’s a confidence problem. The model commits to a guess when context certainty drops below a threshold. I’ve had success fixing that by letting multiple small models “cross-check” each other instead of o
49.
by promptfluid 11mo ago
I’ve seen better results when the model isn’t just generating code, but maintaining context across revisions — like an internal “memory” that remembers past fixes and mistakes. Once you treat the agent like a long-term learner instead of a
50.
by promptfluid 11mo ago
Been through this cycle a few times. What helped wasn’t stepping away from AI — it was building something that runs itself. Once you stop babysitting models and start automating the orchestration, the stress drops fast. My current project b