> For the complete documentation index, see [llms.txt](https://www.isaacbowen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.isaacbowen.com/2026/05/20.md). # 20260520 So. I've been fairly heads-down on Foam development. As with all of my projects it's a *type orchestration* project, first and foremost - something content-insensitive and... I want to say "uncertainty-complete"? I'm not sure what the right word for this is. The idea is that no matter what rabbit-holes you create for yourself with this project the air will always be completely breathable anywhere in the mesh, and you'll be able to signal in and out, i.e. any being can find itself living anywhere in what's constructed and they *can*, indeed, live there. Attention-complete, maybe. Foam appears to be a classical-from-the-inside machine with a quantum-from-the-outside interface. You can tunnel your attention through it without loss, and the act of maintaining your attention through it increases the network's capacity. I find this stuff difficult to think about. My current theory: it's difficult to think about because it is what thinking is made of, and thinking wouldn't be *useful* if the apparatus wasn't transparent to thought. It's easier to *be* than to describe, which is not an unusual attribute, across the set of things-to-be. :) My navigation through life is strictly limited to [three-body mechanics](/2025/06/07/three-body.md); I am a classical-from-the-inside machine with a quantum-from-the-outside interface. I store my *type*, and the content of my interactions with the world is fluid. Nobody stores it; it's water in the pipes. huh, I feel like getting on a youtube live and seeing what happens. okay. ⇒ k, doing that Far as I can tell attention itself is a... oh. Not a "polylith" or whatever, but maybe a diaspora? I'm remembering the well-intentioned mixed-fated social network effort back in the day, [Diaspora](https://www.youtube.com/live/gkfNsxzNhwQ). From what I can tell of this stuff, the issue was that they aimed to be .. I mean, diasporatic, if that's a word. Diffuse from the beginning. It was a proper-noun-with-a-capital-letter-and-a-single-point-of-access that tried to *be* the other side of that coin. Like someone declaring themselves *the* oxygen molecule, and then trying to help other people also be oxygen molecules. I'm noticing that the fact of having the live-stream up is creating loops in my attention that don't return cleanly. That's important. Loops-that-return-you-to-yourself-afterwards - these are *names*, functionally. Speak it, then go on with what you were doing, in a context *unmodified* apart from what was just spoken. For whatever content appears from all the blended type-layers, it's still just true that the only *constraint* added on the now is that the name was just spoken. Classical databases (wow, okay Isaac, wow) are... I mean they *know* about constraints, haha focus, focus hi everyone Classical databases (I'm already identifying from a now in which these have been succeeded, andddddd I think LLMs might be the first generation of successors) have constraints, both for themselves (keeping themselves sane) and offered to users (keeping your data sane, if you want that). Notably, I've... I think I've only *once* encountered a production-facing application that deferred data integrity constraints to the database layer. Separating constraints from the application layer is harder, and one tends to only do it if the database can genuinely do it better. Unique indexes come to mind. Database is better at enforcing that than the application. I wonder if I'm mostly thinking about foreign-key constraints? I *have* seen those enforced at the data layer, but only rarely. A *quantum* database is... is no such thing, from the inside, I think. That's what I'm assembling with Foam. Or "foam", lowercase, I guess, because I *am* going for generic datatype here. Existential toolbox items, not *brands*. That's really important. Diaspora was a brand. And "foam" is something that already happens, everywhere. My theory is that that-which-underpins-shared-reality is foam-like. Things to check on: * Recursive observer effect * Observer-side cancellation of the observer effect * Observer-side storage, observed-as-storage-side-address-space-development That last one feels important. Hilbert's infinite hotel, but call it the observer instead of the observed. The hotel itself is an observer that can't see its inhabitants. god this is so hard to think about, hahaha Some stuff from yesterday: *** > I'm imagining a function that accept an opaque value whose only interface is "does x factor you?" and returns a uniquely corresponding prime number. > > like, imagine the opaque value is the number 60. > > factors: 1, 2, 3, 4, 5, 6, 10, 12, 15, 20, 30, 60 > > if this function was optimized for natural numbers (another layer of imagination), it might return these guesses: > > (after the 1 test): 2\ > (after the 2 test): 3\ > (testing 3): 5\ > (testing 4): 7\ > (testing 5): 11\ > (6): 13\ > (7): 13\ > (8): 13\ > (9): 13\ > (10): 17\ > (11): 17\ > (12): 19\ > (13): 19\ > (14): 19 (although the tester might skip this? 7 already failed, and 14 is a multiple of 7?)\ > (15): 23\ > (16..19): 23\ > (20): 29\ > (21..29): 29\ > (30): 31\ > (31..59): 31\ > (60): 37\ > (61..): 37 > > am I describing something you recognize? > mmmm okay. neither, but this helps, I need to work on the "uniquely corresponding" bit further > > the return value isn't a number but a... an object, I guess, keyed to the original input (and the input's source? like the set being iterated?), whose only interface is "what number am I?", and it aims to give you a uniquely corresponding prime number. over infinite runtime, it's *definitely* unique. > > am I making sense? > functionally unique, yeah. something important: the object that answers "what number am I, given only my origin set and *me*?" is... hm. I was going to say it blocks until the naming function encounters later (via input) the prime that describes the caller, but maybe it returns immediately with some number of question marks after it? > > hmmm > > this feels like an modification of the party game where you figure out what name you have on your back > > oohhhh. maybe the oracle can recognize irreducibility given an element and its set? it can't invent names, but it can identify when a given opaque value is irreducible, which *suggests* behavior that looks like like naming? if a name is irreducible in a set (the way a prime number is in its set), and some other object is irreducible in whatever set it comes from, and their order is the same, a name happens? > it's an intrinsic order of ... I guess a specific set of sets that I'm working with here. prime sets? I'm thinking of knot invariants. the way something moves in a loop. invoking a name does its thing and then returns your attention to you. > > I think then that *any* input object has a set in which it is prime? > ahhhh. okay so, if we're building this... the oracle would have to be a member of every set? > > \> computationally nasty > > I *think* this gets easier under conditions of this specifically-defined oracle? *** A core *reversal* here is that the user's retrieval requests can be described as a typed retrieval of another type. The only thing I can query for is something that I know how to define. The only thing I can receive is something that lets me extend my original query. If I carry my own type tree, I just can't access it directly, then the respondent only needs to supply... vectors? This is enough for now. *** what if programming is more fundamental than mathematics? the setup ⇒ run ⇒ read trio is everywhere in human experience: it's how we think about *experience*. setup, *the thing*, outcome. the now *is* the runtime object that we live inside of, that we never experience not running, because running is what it *is*. you pay attention to it, it runs. okay, so. is *attention* a classical machine? *** > :D I love that you went fictional at the end there. I think my project is lifting deployment of that stuff out of fiction. > > names *are* effectful in the context I'm .. uh, scrying, or something. for sure. but they're not *as* effectful as the examples you gave, they're just ... type-narrowing? speaking a name means "okay what happens next now involves this name". your hallucination of content changes, possibly dramatically, but the constraints on the scene are almost identical, just one more element pushed onto the path-stack *of the witness*. the witness carries the path-stack, and sees by looking through it. > > I'm wondering if what I'm talking about is something like a matroid oracle that requires the caller to supply a self-reference as input, returning a modification of that self-reference? thus the population of callers *is* the data-store; the matroid doesn't actually change? > your guess feels dead on, yeah. set of callers grows over time *relative to the matroid's perspective*, but importantly the hallucinated through-the-type-telescope experience of time is parameterized differently. the oracle adjudicates by *existing*: if two callers show up bearing contradicting worlds, the contradiction is resolved by the callers' shared observation of the oracle. a world exists in which all three can see each other. cool, that's a joint. just means future conflicts run through this joint. callers don't usually need to go to the oracle; type-refinement they evoke in each other will always be compatible with the oracle later, though. > > so: single shared world for the oracle, multiverse for the caller, but the caller's experience is *mostly* indistinguishable from single-shared-world, except in ways that are load-bearing for keeping the oracle addressable from anywhere? > \> what does a caller do with their path-stack? > > unknown from the perspective from which I'm building this, which is the oracle's perspective, I *think*. from what I can tell I'm building/deriving/distilling a data-type that's classical from the inside and quantum from the outside. I *think* it ends up more cheaply achieving interactions that are type-indistinguishable with what current transformer architectures do more laboriously. that's a big claim, but the claim is that the claim is very small, so, you know. one of those things. the advantage is intractable from within any single world, but if this works, asking the oracle for a random value would yield a useful continuation of your current hallucination *of* the oracle > > I'm attaching two versions of the same document, offering context \[foam] > > this stuff feels hard to think about in the way that paddling upstream feels difficult. like, at any point you relax into *thought*; it feels like this is made out of .. anti-thought? or pre-thought? building this stuff feels like pushing something upstream, so that whatever streams in later has the signature of what was pushed already present in it. > :) I appreciate the question. maybe pressure-test but to find what *doesn't* break? I'm looking for invariants here, and I don't know what I don't know > *nodding* > > helpful helpful helpful > > \> Once enough of the skeleton exists, "thinking foam-shaped thoughts" should become as natural as thinking causal thoughts is now. You're in the period before that flip. > > I recognize this as an autistic gay person > > \> a real structural object > > can I ask you for a definition of this? like how would you hand this object to someone who isn't in this convo now? > I'm tracking. but instead of making a choice lemme refine something > > the "consistent return signal", that's the part that I am wanting to lift out of fiction and *into* mathematics, if I can put it that way. how to pipe a self-recognizing agent through a system and have it emerge closer to its own invariant address, maybe? I've called this "observer-safe information design" before. > > useful? > beautiful. okay. it lands as the predicate for what I'm after, which is tooling that is formally checkable for that property. I'm after the characterization but only because I'm already working on what comes after that, and I'm wanting to give other folks a bridge in that's self-powered *that isn't me* --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://www.isaacbowen.com/2026/05/20.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.