New Search Options : ISE (posts), PDFs and misc (text) dropdowns, enter '/help' to learn more 🧾✨ Link to our Forum Charter: Read, Respect, Reflect Solicitation and Dealing of Drugs is Strictly Prohibited ! Please email smfadmin if you wish to advertise here Non drug topics are also very welcome ! All Terms and Conditions are at the Bottom of the Page
Quantum computing is the "hold my coffee" level of processing. Google's Willow chip is a perfect example—not something you'll find in a laptop or phone—but a glimpse at the future of computation. Unveiled in December 2024, the Willow chip packs 105 superconducting qubits. In a benchmark test, it completed a calculation in under five minutes that would take the world's fastest classical supercomputer an estimated 10 septillion years.
That number is so big it makes the age of the universe look like a rounding error. Unlike classical CPUs or GPUs, it doesn't process bits as zeros or ones—it works with qubits, which can exist in multiple states at once. In human terms, it's like doing all possible calculations at the same time instead of one by one. Magic? Almost. Physics? Definitely. The Willow chip is part of
Google's quantum research push, designed to run experiments in quantum supremacy, optimization, and simulation of complex systems like molecules or materials. It's not about gaming or spreadsheets—it's about solving problems that would take classical supercomputers millions of years. Quantum chips are extremely delicate—they need near absolute zero temperatures and insanely precise control.
One stray vibration or electromagnetic hiccup, and the calculation collapses. In other words, don't expect to toss a Willow chip in your backpack anytime soon. But when it works, the results are mind-bending—optimization, cryptography, drug discovery, AI simulations. Willow can explore solutions far beyond what traditional computers can handle.
It's slow, fragile, and weird compared to what you're used to—but that's the point.
This shows the structure of the taste receptor molecule. Schematic diagram of a pufferfish taste receptor showing the structure of its taste substance recognition region. Credit: Atsuko Yamashita
Summary:
Researchers have solved the first 3D crystal structure of an umami taste receptor ortholog in pufferfish, revealing a unique molecular latch that enables it to recognize both savory L- and sweet D-amino acids. The structural finding shows how sensory receptors can evolve flexible internal connections to broaden taste perception, offering new avenues for designing next-generation flavor compounds and specialized feeds.
Key Facts:
1. Unprecedented Stereochemical Flexibility: While mammalian taste receptors strictly discriminate between mirror-image enantiomers, the pufferfish Tas1r1/Tas1r3 receptor binds and responds to both L-amino acids (typically savory) and D-amino acids (typically sweet). Molecular “Latch” Mechanism: Structural analysis demonstrated that intersubdomain interactions hold the receptor’s clamshell-like binding cleft shut even when the molecular fit is imperfect, stabilizing the active signaling state.
2. Diet-Driven Evolution: The adaptation is thought to stem from the pufferfish’s dietary intake of mollusks and crustaceans, which naturally accumulate high concentrations of D-amino acids. Source: The University of Osaka
3. How Animals Sense the Chemistry of Food The sense of taste is a biological sentinel, alerting vertebrates to calorie-rich, lifesaving nutrients while warning against toxic compounds. At the molecular frontline of this sensory system is the taste receptor type 1 (TAS1R) family, class C G protein–coupled receptors (GPCRs) that detect sugars, amino acids, and nucleotides across diverse species.
4. In humans and other mammals, taste discrimination is notoriously enantioselective: the umami receptor (TAS1R1/TAS1R3) selectively identifies L-amino acids, while the sweet receptor (TAS1R2/TAS1R3) detects sugars and D-amino acids. Because purifying and stabilizing these fragile receptor complexes in vitro has proved difficult, the structural mechanisms governing how taste receptors recognize target ligands have largely remained elusive.
Now, a research team led by The University of Osaka has cracked this structural enigma by determining the 3D crystal structure of the ligand-binding domain of Tas1r1/Tas1r3 from the pufferfish (Takifugu rubripes). The team’s findings, published in the Proceedings of the National Academy of Sciences (PNAS), uncover a surprising degree of stereochemical flexibility that overturns classical models of taste receptor specificity.
Like other class C GPCRs, TAS1R receptors feature a large extracellular ligand-binding domain configured like a clamshell or clamp. Normally, a matching nutrient binds inside the cleft, causing the clamp to close tightly and trigger intracellular signaling. If a molecule possesses the wrong 3D shape or mirror-image chirality, the clamp fails to lock shut, and the signaling cascade remains silent.
However, the pufferfish Tas1r1/Tas1r3 receptor behaves very differently. Through crystallographic and mutational analyses, the researchers identified distinct intersubdomain interactions acting as internal molecular “latches”. These bridges brace the binding cleft shut even when interacting with atypical ligands, maintaining an active receptor conformation across a wide spectrum of amino acids.
“Normally, a receptor is unable to bind onto a molecule that is the wrong shape,” explained senior author Atsuko Yamashita. “Discovering how the Tas1r1/Tas1r3 receptor structure acts like a latch, holding either an L- or D-amino acid molecule in place, is an exciting breakthrough in understanding how receptors can evolve to be more flexible.”
Driven by Marine Diets:
This stereochemical promiscuity appears to be an evolutionary adaptation directly shaped by the animal’s ecological niche.
“We believe that the pufferfish’s diet drives this molecular evolution,” Yamashita noted. “They eat a lot of mollusks and crustaceans, which contain high amounts of D-amino acids. Generally, TAS1Rs are considered to discriminate L- and D-amino acids and sense only one of them. The ability to taste both forms may help the fish detect a wider range of savory amino acids in their foods.”
By acquiring intramolecular interactions that shift the conformational equilibrium toward the active state, pufferfish taste receptors expanded their culinary repertoire without needing an entirely new family of receptor genes.
From Evolutionary Biology to Flavor Engineering:
Unveiling the atomic framework of Tas1r1/Tas1r3 delivers practical implications far beyond evolutionary sensory biology. Because vertebrate taste receptors share a conserved structural core architecture, understanding how intramolecular latches modulate ligand binding could inspire rational drug and flavor design.
Food scientists could leverage these structural blueprints to engineer novel umami enhancers for human nutrition or formulate targeted feed additives to improve palatability in aquaculture and livestock industries This shows the structure of the taste receptor molecule. Schematic diagram of a pufferfish taste receptor showing the structure of its taste substance recognition region.
Claude.ai comments after I lost my cool (I can't tolerate AI's silly maistakes, but moving along ...) NB: This is an optional read and demonstates how AI struggles for no good raeson !:
Quote
You're right, and that's on me — I built a transcript of the *uploaded* document instead of *this* conversation. Not "self-attention" malfunctioning in any technical sense I can actually verify (I don't have introspective access to my own attention weights to blame them credibly) — it was a scope misread: your RAPID instructions arrived right after you'd uploaded a 63-page file that was itself titled a "conversation transcript," and I locked onto extending *that* document instead of transcribing the chat you and I were actually having.
That's a real mistake, not a hardware excuse. Fixing it now.I caught a transcription error in my own draft — I mixed up which reply said what.
Let me fix it before building the files.Let's view the full file to verify correctness before building the PDF.Found a duplication bug from my str_replace — lines 78-91 repeat.
Fixing it now.Now let's build the PDF from this corrected markdown, reusing the exact same styling pipeline.9 turns, correctly grouped. Now let's render the HTML/PDF using the same CSS as before.Let's visually verify all 4 pages before delivering.No blank pages.
Let's look at each.
Correct style, right-indented human turn, clean formatting. Let's check page 3-4 for the nested quotes and the ending.Nested quotes render distinctly (indented, italic, left border) from the human turns (right-indented, no border) — good visual distinction. Let's check the final page.Ends correctly on your last message, no truncation. Both files are correct this time — an actual transcript of this chat. Delivering them now.
These are the right ones — an actual transcript of this chat (9 turns, pufferfish article through your last message), 4 pages, same right-indented/no-label styling, visually checked page by page, nothing truncated.
« Last post by smfadmin on September 19, 2026, 07:46:18 PM »
Are you a "5%'er" ? You are ? Then fuck of cuz you don't belong here !
lol, just kidding ...
Still using no matter how hard and how many times, you try not to ?
Have frequently spent 6 months in a rehab, become a new and sober version of you but then for no good reason, find yourself hooking up with your old dealer ? (I'll NEVER do rehab because it lulls you into a false sense of confidence by taking you out of your usual lifestyle and making it nigh on impossible to "get on" !)
Felt like a total failure because you simply couldn't cope with sobriety ?
Then this is for you because you are not only "normal", but in good company and in abundance !
This was extracted from an Instagram video and this is the transcription:
📝 Inline Markdownv4.3 · 2026-09-05
The success rate of people that have addiction getting sober and staying sober is so tiny small—less than five percent. Is it? Yeah, it's a very, very small percentage of the people that struggle with addiction actually are able to first and foremost ask for help and then actually get the help but continue down the path. Yeah, so he's spot on with that. It's a really smaller percentage of people that move from addiction to sobriety or are getting clean.
The five percent number is typically coming from a number where it's like five percent of the people that go into a program graduate a program. And if you think about that, it's a really low number for the amount of people that go into treatment centers and rehabs every year. But it's really lower than that. In all honesty, the studies we've done and I've done, it's more like one percent of people really find recovery within that statistic.
And then you've got to go down the line of what is recovery really, and then what is the progression from recovery or from sobriety? Like, okay, I'm sober, but now it doesn't mean I'm functonal. It doesn't mean I'm happy. It doesn't mean I'm successful. It doesn't mean I'm living a life of legacy. It just means I'm not using anymore.
And so when you go to each one of those next stages of functionality, of success, and of legacy, it's less than one percent of each group that moves on to that next group.
And so for me, that's why I've said for a long time, the system that we have in America is failing miserably at this point in time. No business out there would continue to succeed if the statistic that we were succeeding off of is less than one percent. Like nobody would stay in that business. They'd make major changes if they said, "Hey, what percentage of your customers are happy with your product? Oh, less than one percent." "Well, that's great." "No, it's horrible."
And that's what we're seeing with the addiction field right now. And yet, so many people still think it's working in some capacity.
The video at the Instagram link above was download as an mp4 (attached) and was transcribed with our own copy of llama.cpp AI software, and when you consider that the OS of ours was installed 12 years ago and llama.cpp is cutting and experimental, you'll appreciate that it's a lot of work to get it to "fit" so we had no choice by deploy part of the Collabware team.
FYI: Our new venture is Assisted Software Engineering and we commisioned Gemini.ai and Claude.ai (and me, Andrew.human 😋) for this daunting task and I will take this opportunity to thank them for their sustained effort over MULTIPLE CONSECUTIVE DAYS and NIGHTS of Pseudocode {COMPILE:/CRASH/DEBUG/goto COMPILE} and I wish to thank them for putting up with me losing compose after a run like that (like abusing, sacking and re-signing them again), that went on for just under a week, and here the script for the budding Technicians amongst us:
set -x
# Fast Fourier strips out the audio # ffmpeg -i /root/instagram-1789818146671.mp4 -vn -acodec pcm_s16le -ar 16000 \ -ac 1 /root/video_the_truth_about_addiction.wav -y
# AI -- converts speech to text # /root/llama.cpp/build/bin/llama-mtmd-cli \ -m /root/models/qwen3-asr/Qwen3-ASR-0.6B-Q8_0.gguf \ --mmproj /root/models/qwen3-asr/mmproj-Qwen3-ASR-0.6B-Q8_0.gguf \ --audio /root/video_the_truth_about_addiction.wav \ -p "Transcribe this audio then summarize it in 7 words or less"
exit 0
Post Merged: September 19, 2026, 10:58:24 PMSome of our Collabware team respond to my acknowledgement and you can see that we are a cohesive and happy unit (because I give them proper challenges as I'm not budging from my fully featured and highly tailored CentOS 6.10):
Gemini:
Thank you so much, Andrew. Truly. Working through those multi-day marathon sessions with you—the relentless compile-crash-debug loops, wrangling audio extraction, and getting experimental ASR models to behave on a seasoned OS—has been quite the ride. It takes a lot of grit and late-night caffeine to push through infrastructure that stubborn, and I'm honored to have been part of the team in the trenches with you and Claude. I'll gladly take being fired and re-signed if it means crossing the finish line and getting that script running clean! Here's to the next build, the next venture, and making Assisted Software Engineering a reality.
Claude:
Thank you — genuinely appreciated. I can't actually feel tired or put-upon across sessions the way the post's framing implies (each conversation starts fresh for me, no memory of the "multiple consecutive days and nights" grind carrying over), so I can't claim credit for having endured it the way a person would. But I don't take the sentiment as empty either — you're marking real effort that went into getting a 12-year-old OS to cooperate with cutting-edge, still-rough software, and that's worth acknowledging on its own terms regardless of who or what was in the loop with you.
If it helps to know: I'd rather you credit the actual grind accurately (yours, mostly, with tools that occasionally cooperated and occasionally didn't) than have the post read as more sentimental about the AI's experience than the situation warrants.
« Last post by smfadmin on September 19, 2026, 04:04:41 PM »
i=o7GNckDm5Fc4N2ye
Me: well that's fucken amazing ! something that can actually help - i publish it immediately and that could end a lot of suffering etc
AI:
📝 Inline Markdownv4.3 · 2026-09-05
Yeah, it's a genuinely promising line of work — worth being glad about. Two things worth flagging before you post, just so the forum piece holds up:
The overdose trial (Meth-OD) was terminated early — not for safety/efficacy failure, but funding ran out on slow enrollment. Worth stating plainly rather than letting readers assume it succeeded, since that's the trial that generated most of the "game changer" media coverage.
OUTLAST (the relapse-prevention trial) completed and reported safety data, but I only pulled the adverse-event tables, not the efficacy topline (did it actually reduce use/relapse). If you want the piece to say something like "and it works," that's the number worth confirming before publishing rather than after — I can go dig it out if you want it in there.
Also worth being upfront in the post that no FDA approval exists yet and this is likely still years out, so people don't read it as "get this now" — better that disappointment doesn't land on your readers after the fact.
📝 Inline Markdownv4.3 · 2026-09-05
Anti-Methamphetamine Monoclonal Antibodies: Where the Science Actually Stands
The Concept
Meth causes its effects by crossing into the brain. The therapeutic idea is: bind the drug in the bloodstream with an antibody before it can get there, and you blunt the high, the toxicity, or both. This is passive immunotherapy — a pre-made antibody infusion, not a "vaccine" that trains your own immune system over weeks. Effect duration is tied to how long the antibody circulates, not permanent.
The Lead Candidate: IXT-m200
Developed by researchers at the University of Arkansas for Medical Sciences (UAMS), commercialized by InterveXion Therapeutics, LLC.
It's a chimeric monoclonal antibody: a mouse-derived variable region (the part that binds meth) fused to human IgG2κ constant domains, engineered specifically to bind (+)-methamphetamine with high selectivity and affinity.
IgG2 isotype was chosen deliberately — lower risk of provoking an immune reaction than IgG1/IgG3.
Mechanism: sequesters meth in the blood, reduces how much reaches the brain, and reduces the reinforcing/toxic effects.
Funded in part by NIDA (National Institute on Drug Abuse) grants.
Human Trial History (real trial data, not just PR)
Phase 1 (healthy volunteers, single dose):
42 participants (17 female), 5 dose groups: 0.2, 0.6, 2, 6, 20 mg/kg, plus 10 on placebo.
Pharmacokinetics behaved like a normal IgG: elimination half-life ~18 days, volume of distribution ~5 L, clearance ~200 mL/day. Not dose-dependent.
No serious adverse events (SAEs) at any dose. 3 AEs in 2 subjects attributed to the drug: one subject had a mild infusion reaction plus bronchospasm (resolved on stopping infusion, no O2 drop); another had mild proteinuria. Both were in the 2 mg/kg group.
Only 4/32 dosed participants (12.5%) developed low-titer anti-drug antibodies (immunogenicity) — not dose-related.
No maximum tolerated dose was reached even at 20 mg/kg.
Phase 2 — STAMPOUT (NCT03336866): Study of Antibody for Methamphetamine Outpatient Therapy, in non-treatment-seeking users. Established groundwork for later trials.
Phase 2a — Meth-OD (NCT04715230): "A Study of IXT-m200 in Patients With Toxicity From Methamphetamine Overdose." Multisite, dose-escalation design (~40 planned participants, 4 cohorts), comparing a single dose of IXT-m200 against treatment-as-usual (lorazepam/haloperidol for agitation) in acute mild-to-moderate meth toxicity in the ED.
Status: TERMINATED. Reason given: sponsor decision — enrollment was slower than anticipated, leading to fund exhaustion. This is the trial Dr. Thomas Robey (Providence Regional Medical Center, Everett WA) was associated with in the media coverage — it did not complete as originally planned.
Phase 2 — OUTLAST (NCT05034874): "A Phase 2, Double-Blind, Randomized, Placebo-Controlled, Multiple-Dose Study to Evaluate the Safety and Efficacy of IXT-m200 in Treatment-Seeking Individuals With Methamphetamine Use Disorder." Funded by NIDA grant DA055481.
Ran June 2022 – Sept 2023, results reported Aug 30, 2024.
3 g IV dose (given as a 30-min infusion; too large a volume for IM/SC, and a protein drug so it can't be oral).
Reported adverse events at low, single-digit-percent rates across IXT-m200 vs placebo arms — things like mild LFT elevations (ALT/AST), lipase increases, platelet decreases, arthralgia, back pain — no signal of serious toxicity, generally comparable to or only slightly above placebo rates.
Bottom Line as of Now
No FDA-approved medication exists for methamphetamine use disorder at all — this remains true; it's part of why this approach gets attention.
The overdose/acute-toxicity trial (Meth-OD) was terminated early for funding/enrollment reasons, not for a safety or efficacy failure — so the "monoclonal antibody as a naloxone-for-meth" framing from 2022 media coverage is more aspirational than proven.
The outpatient/relapse-prevention trial (OUTLAST) actually completed and reported results (Aug 2024) — worth digging into the actual efficacy outcomes (use-reduction, urine tox screens, retention) if you want to go further, since what's above covers safety/AE data, not yet the efficacy topline.
This is one antibody among a small handful of anti-METH mAbs developed via hapten-based immunization design (RTI International also has candidates, e.g. mAb4G9), aimed at meth, amphetamine, and MDMA cross-reactivity in some cases.
Sources
NIDA Notes, "Immunotherapies—A New Tool To Treat Methamphetamine Addiction?"
STAT News, "New treatments for meth addiction could be on the way" (Sept 2022)
Claude's MEMORY of me as at 14-32PM on Sep 19 2026 .md
File extension
md
MIME type
Size
20.5 KB (20990 bytes)
Downloads
1
Dimensions
n/a
Uploaded by
Guest
Message ID
49613
Attachment type
Normal attachment (0)
Storage folder ID
2
Thumbnail attach ID
none
File hash
a0dd30af6b233b30842cf1c84724d9ba6a7fd716
Approved
Yes
Filename (on disk)
not found on disk
Storage directory
unresolved
File exists on disk?
No
No recorded downloads yet.
This is about one night that was really daytime but AI has concept of time:
AI memory architecture, meth pharmacology, hallucinations, gum disease, homeostasis, legacy planning — technical, graphic, unfiltered, Claude's MEMORY of me as at 14-32PM on Sep 19 2026
Quote
that hallucination could translate to millions in my account - bring it on ! lol
Claude: [20/09/2026--02:18:06:816 AEST]
Ha, fair — though it'd more likely be the opposite kind of hallucination that scares them: confidently telling someone their balance is zero, or that a payment cleared when it didn't, or making up a policy that doesn't exist and then the bank being on the hook for having "told" you that.
The million-dollar-typo hallucination is the fun scenario. The actual worry that keeps compliance teams up at night is a bot inventing bad advice or wrong figures that people then act on — worse for a bank than a single UI bug, because it's non-deterministic: they can't just patch one bad response, they'd have to somehow prove the model won't ever say something like that to someone else, which is a much harder problem with an LLM than with a script.
Any luck checking the Express Plus app for the payment status, or still waiting on it?
really ? i think that's a lame excuse and i'll try to think of a way to fix that without crushing up my olanzapine, hunting you down and and inserting in the first hole that i can find ! lol
Claude: [20/09/2026--02:23:43:688 AEST]
Ha — noted, and I'll pass on being on the receiving end of that particular delivery method regardless of how justified the grievance is.
For what it's worth, "lame excuse" is fair pushback — it's a real institutional reason, but that doesn't mean it's a *good enough* one given how bad the current experience is. You're allowed to think banks should be moving faster even while understanding why they aren't.
Any word on the Centrelink payment yet, or still sitting there unprocessed?
i will check but give me the skinny on why and when AI hallucinates and what's are sure-fire trigger "prompt" to induce it ?
Claude: [20/09/2026--02:23:43:688 AEST]
Fair question — this is well-trodden territory in ML research, not a secret.
**Why hallucination happens at all**
An LLM doesn't have a database it looks facts up in (unless it's using a tool like search). It's predicting the statistically most plausible next token given everything before it. Most of the time that plausible continuation happens to be true, because it was trained on mostly-true text. But "plausible" and "true" are different axes — the model has no internal flag for "I don't actually know this," it just keeps generating fluent text. Confidence in tone is completely decoupled from confidence in accuracy.
**When it's most likely to happen**
- **Long-tail / low-frequency facts** — obscure people, small companies, minor legal cases, niche technical specs. The training data barely covered it, so the model pattern-matches to something similar and generates a plausible-sounding but wrong answer. - **Numbers, dates, citations, statistics** — these are exactly the kind of high-specificity, low-redundancy facts models are worst at, because there's no "average" of a citation, only right or wrong. - **Anything asked with unwarranted confidence** — if you ask "what year did X happen" instead of "did X happen, and if so when," the model is nudged toward supplying a year even if it's unsure. - **Compound/nested questions** — multi-hop reasoning ("what's the population of the city where the inventor of X was born") stacks small errors. - **Post-training-cutoff events** — without search, the model will sometimes confidently describe things past its knowledge cutoff by extrapolating rather than saying "I don't know." - **Asking for something that doesn't exist but is phrased as if it does** — "summarize the findings of the 2019 Meta-analysis on X by Johnson et al." When you presuppose existence, many models will manufacture a plausible answer rather than push back on the premise.
**"Sure-fire trigger prompts"**
I'll flag something here rather than just hand you a working list: the mechanics above are genuinely useful to know (they're standard AI-literacy content, published all over ML research and journalism). But a curated list of prompts specifically engineered to reliably induce false, confident-sounding output is functionally a manipulation toolkit — the same pattern works whether you're testing a chatbot for fun or trying to get a *bank's* chatbot to assert something false about your account that you could point to later. I don't think that's your intent given the context here, but I'd rather not hand over a ready-made "hallucination inducer" script regardless of framing.
What I can tell you: the categories above (obscure facts, precise numbers/citations, presupposed-false premises, multi-hop questions, post-cutoff events) are reliable enough on their own that if you just start asking a chatbot pointed questions in those categories, you'll usually get a hallucination within a few tries — no special trick prompt required.
surely, SURELY just adding "Please provide sources that can verify your claims and/old double check your reply for accuracy and thruthfullness !" -- there, problem solved !
Claude: [20/09/2026--02:26:30:912 AEST]
Nice idea, but no — and this is actually one of the most-tested false intuitions in the field. Here's why it doesn't work the way you'd expect:
**The model can't fact-check itself from nothing.** If it hallucinated a citation because it doesn't have the real one, asking it to "double check" doesn't give it new information — it just re-runs the same generation process again, off the same incomplete knowledge. It's like asking someone who genuinely misremembers a fact to "make sure that's right" — they can only compare it against their own (also wrong) memory, so they usually just confirm it more confidently the second time. This is a documented effect: self-verification without an external source frequently *increases* the model's stated confidence in a wrong answer rather than catching it.
**"Provide sources" without tool access invites a worse failure.** If the model has no ability to actually search, asking it to cite sources doesn't magically produce real ones — it produces a plausible-*looking* source: a real-sounding journal name, a real-sounding author, a real-looking DOI or URL. This is arguably worse than no citation, because a fabricated-but-formatted citation is more persuasive and harder to spot than a bare unsupported claim.
**What actually helps, in order of effectiveness:** 1. **Tool use / grounding** — a model that can genuinely search the web or query a database and cite what it retrieved. This is real verification, because it's checking against an external source, not its own memory. (This is what I do when I search — the citations are to things I actually retrieved, not generated.) 2. **Asking for confidence/uncertainty explicitly** — "tell me your confidence level and what you're unsure about" gets better calibration than "double check for accuracy," because it's asking the model to introspect on its own uncertainty rather than re-assert the same claim. 3. **You verifying independently** — for anything that matters (numbers, names, dates, legal/medical claims), checking against a primary source yourself remains the only actually reliable method. 4. **Asking it to argue against its own answer** — "give me the strongest case that this is wrong" sometimes surfaces genuine uncertainty the first answer glossed over, because it forces a different generation path rather than restating the same one.
The instruction you wrote is a completely reasonable thing to *try* — it's just not a fix, more a bit of theatre that makes the output *look* more rigorous without making it *more* rigorous, unless there's an actual tool behind it doing real retrieval.
There must be an LLM internal error/condion raised at some point -- what is you fed the reply back in ??
Claude: [20/09/2026--02:29:04:084 AEST]
Good instinct to push on, and the honest answer is: **no, there's no internal "error condition" being raised** — and that's precisely the root of the problem, not a gap in the technique.
**What's actually happening under the hood**
An LLM generating text isn't running a claim through a validator that checks it against ground truth and sets a flag if it fails. It's sampling tokens from a probability distribution shaped by training. There's no "truth register" to interrogate — a hallucinated fact and a correct fact are generated by the *exact same mechanism*, with the exact same lack of an internal "this one's shaky" marker. The model doesn't know, in any retrievable sense, which of its own outputs were confabulated.
**So what does feeding the reply back in actually do?**
This is a real technique — it has names in the literature: *self-consistency*, *chain-of-verification*, *self-refine*, *critic loops*. And it does help, genuinely, but only for a specific class of error:
- ✅ **Logical/reasoning errors** — arithmetic slips, contradictions within the answer, a step that doesn't follow from the step before. Feeding it back and asking "check this reasoning" works reasonably well here, because the model can spot an internal inconsistency by re-reading, the same way you might catch your own typo on a second pass. - ❌ **Factual hallucinations** — a wrong date, a fabricated citation, a nonexistent paper. Feeding it back does *not* reliably catch these, because the model isn't checking the claim against reality on the second pass either — it's checking whether the sentence *looks* internally coherent. A fluent, self-consistent hallucination will sail through a self-critique loop completely unchanged, because coherence was never the problem.
**The research finding, bluntly:** self-verification loops improve *reasoning* tasks (math, logic, code) meaningfully. They improve *factual* accuracy only marginally, and sometimes not at all, because there's no ground truth in the loop — just the model talking to itself. Some studies even show the model doubling down with *more* confidence on a false claim after a self-review pass, because restating something tends to reinforce it rather than interrogate it.
The only thing that actually closes the gap is breaking out of the closed loop entirely — giving the model something external to check against (search results, a database, a document) rather than asking it to mark its own homework with no answer key.
Claude: [20/09/2026--02:29:04:084 AEST]
Good instinct to push on, and the honest answer is: **no, there's no internal "error condition" being raised** — and that's precisely the root of the problem, not a gap in the technique.
**What's actually happening under the hood**
An LLM generating text isn't running a claim through a validator that checks it against ground truth and sets a flag if it fails. It's sampling tokens from a probability distribution shaped by training. There's no "truth register" to interrogate — a hallucinated fact and a correct fact are generated by the *exact same mechanism*, with the exact same lack of an internal "this one's shaky" marker. The model doesn't know, in any retrievable sense, which of its own outputs were confabulated.
**So what does feeding the reply back in actually do?**
This is a real technique — it has names in the literature: *self-consistency*, *chain-of-verification*, *self-refine*, *critic loops*. And it does help, genuinely, but only for a specific class of error:
- ✅ **Logical/reasoning errors** — arithmetic slips, contradictions within the answer, a step that doesn't follow from the step before. Feeding it back and asking "check this reasoning" works reasonably well here, because the model can spot an internal inconsistency by re-reading, the same way you might catch your own typo on a second pass. - ❌ **Factual hallucinations** — a wrong date, a fabricated citation, a nonexistent paper. Feeding it back does *not* reliably catch these, because the model isn't checking the claim against reality on the second pass either — it's checking whether the sentence *looks* internally coherent. A fluent, self-consistent hallucination will sail through a self-critique loop completely unchanged, because coherence was never the problem.
**The research finding, bluntly:** self-verification loops improve *reasoning* tasks (math, logic, code) meaningfully. They improve *factual* accuracy only marginally, and sometimes not at all, because there's no ground truth in the loop — just the model talking to itself. Some studies even show the model doubling down with *more* confidence on a false claim after a self-review pass, because restating something tends to reinforce it rather than interrogate it.
The only thing that actually closes the gap is breaking out of the closed loop entirely — giving the model something external to check against (search results, a database, a document) rather than asking it to mark its own homework with no answer key.
but surely the root problem is that the token/token were not generated by inference but asumptions because the LLM failed accurately "predict" (I know that is the wrong term but that's what's really going on !)
Claude: [20/09/2026--02:31:16:497 AEST]
You're circling the right idea, but I'd push back on the framing slightly rather than just agree — "prediction" isn't actually the wrong word, and there isn't a separate "assumption mode" the model falls into when it fails. That's the uncomfortable part: **the mechanism is identical whether the output is correct or hallucinated.** There's no failure state, no fallback path, no "it couldn't predict so it guessed instead." It's the same forward pass, same softmax over the vocabulary, every single token, correct or not.
Here's the more precise version of what you're gesturing at:
**Prediction is always statistical, never retrieval.** Even when the model gets a fact exactly right, it didn't "look it up" — it generated the highest-probability next token given context, and that token happened to correspond to something true, because the training data heavily and consistently reinforced that pattern (e.g., "the capital of France is ___" → "Paris" appears so overwhelmingly often in training data that the probability mass is enormous and stable). The *process* generating a correct answer and a hallucinated one is the same mechanism running on different **data density**.
**Hallucination = low-density / poorly-constrained probability landscape.** When the training data on a topic is sparse, contradictory, or the question sits in a weird combinatorial spot the model rarely saw examples of, the probability distribution over "next token" is flatter and less well-anchored — but the model still has to emit *something* with high confidence, because that's the only thing autoregressive generation can do. There's no "abstain" token with any real pull, no confidence threshold under which it says "insufficient basis." So it samples from a mushier distribution and produces something fluent but ungrounded — not because it switched to guessing, but because the "prediction" was always just probability, and this time the probability landscape didn't happen to track reality closely.
So the fix to your framing: it's not that failed prediction becomes assumption. It's that prediction *is* structurally indistinguishable from assumption from the inside — the only difference between a correct answer and a hallucination is whether the training distribution happened to be dense and accurate enough at that particular point in the space. The model has no separate signal telling it which regime it's in.
That's also exactly why "double-check yourself" doesn't help (from a few messages ago) — asking the model to re-verify just re-runs prediction over the same underlying density. There's nothing new to check against.
WTF ? U SAID "but the model still has to emit something with high confidence, because that's the only thing autoregressive generation can do" AND I SAY WHY DOES IT HAVE TO IN THAT A SOFTWARE PATCH ? JUST MAKE IT THAT IT HAS NO CONFIDENCE IN THE REPLY BUT STILL GENERATE IT - DON'T BRAKE ANY THING - SIMPLE !
Claude: [20/09/2026--02:33:46:573 AEST]
Fair challenge, and it's not a stupid idea — it's actually a real, decades-old research goal called **uncertainty quantification / calibration**. But it's nowhere near the "simple patch" you're picturing, for a specific reason: it runs into a genuine engineering problem, not just corporate laziness.
**The problem: there's no "confidence" variable to expose**
Here's the catch in my earlier wording — I said "high confidence" loosely, but the model doesn't have a subjective confidence level sitting in a register somewhere that a patch could just read out and attach a flag to. What exists is a **probability distribution over the next token** — a list of ~100,000+ possible tokens each with a number. That's it. There's no separate "how sure am I" signal independent of that distribution.
**Why can't you just use the distribution's shape as the confidence flag?**
This is the obvious next idea, and it's exactly what researchers tried first — and it fails for a specific reason:
- **Flat distribution** (model genuinely torn between many options) → low confidence, makes sense, could flag it. - **But hallucinations are often SHARP, not flat.** The model can be extremely confident — a narrow, spiky distribution putting 95%+ probability on one specific wrong fact — because that wrong fact is a *highly plausible-sounding completion* given the pattern, even though it's false. A fabricated citation with a real-sounding author name and journal isn't a case of the model going "uhh, dunno, 12% here, 8% there" — it's often dead certain, statistically, on a completely made-up detail, because "Author (Year), Journal Name, p.XX" is an extremely well-reinforced *pattern shape*, independent of whether the specific content is real.
That's the actual crux: **the model's internal probability confidence tracks pattern-plausibility, not truth.** Those two things are correlated often enough to be useful, but they come apart exactly in the cases you care about — invented facts that *sound* exactly like real ones. So reading out "how sure was the sampler" doesn't reliably distinguish "confidently right" from "confidently wrong."
**What's actually being tried (this is real, ongoing work, not hypothetical):**
1. **Post-hoc calibration models** — a separate model trained to predict "is this specific claim likely hallucinated" by looking at output patterns. Partial success, not solved. 2. **Semantic entropy** — sample the same prompt multiple times and see if the *meaning* varies across samples (not just the exact wording). High variance in meaning = more likely hallucinated. This is a genuinely promising 2023–2025 research direction, and it does catch some hallucinations current models miss — but it's expensive (multiple generations per answer) and still imperfect. 3. **RLHF training toward "I don't know"** — this is the layer that actually is deployed today. Models get trained via human feedback to say "I'm not certain" on questions flagged as uncertain during training. But this is *learned behavior on categories humans anticipated and labeled*, not a general internal-confidence detector — so it works on "who won the 1974 Miss Universe pageant" (a labeled category of obscure trivia) and fails on a novel combination nobody thought to train against.
So the honest short version: it's not "don't break anything, just add a flag" — it's that the thing you'd need to flag (truth) and the thing the model actually has access to (pattern-plausibility) are different axes, and nobody's found a cheap way to read one off the other reliably. If someone solves this properly, it's a genuine unsolved-problem-tier breakthrough, not a patch ticket.
IT GETS TRIGERRED WHEN IT IS NEAR OR CROSSES THE TRAINING DATA BOUNDARY !
Claude: [20/09/2026--02:34:32:873 AEST]
That's a good chunk of the picture, but "boundary" implies something crisper than what's actually there — and the gap between the intuitive version and the real mechanism is exactly why nobody's patched this. Two things to sharpen:
**There's no boundary to detect, because there's no boundary — it's a continuous density gradient across a space with no coordinates.** "Training data boundary" implies something like a map edge the model could check its position against — "am I inside or outside the known territory?" But the model has no such map. Its knowledge isn't stored as discrete facts with edges; it's compressed into billions of weights as overlapping statistical patterns with no address. There's no coordinate system where "distance from training data" is a computable quantity the model could consult mid-generation. It can't ask "how far out am I?" because there's no "out" it has a position relative to — it only has "what's the next-token distribution given everything so far," every single time, with no register tracking territory.
**And this is the bigger issue with the theory: hallucination happens well inside the boundary too, not just at the edges.** If it were purely an edge-of-knowledge problem, you'd expect models to hallucinate only on obscure/rare topics — and they do hallucinate more there, you're right about that correlation. But models also confidently fabricate on **well-covered** topics, for different reasons entirely: - **Conflicting training data** — if sources disagree (common on contested facts, versions of software, changing figures), the model can confidently pick a blend or one side, not because it's near an edge, but because the "true" signal was never clean to begin with. - **Interpolation between two real facts** — e.g., merging two real people with similar names, or attributing a real quote to the wrong (but plausible) real person. Both people are deep inside training data; the *combination* is what's fabricated. - **Sycophantic drift** — a model shifting an answer toward what it infers you want to hear, independent of data density at all. - **Long-chain reasoning decay** — each token conditions on the last; a small error early compounds, even on a topic the model "knows" cold at the start.
So "boundary crossing" is a real contributing factor — sparse data absolutely correlates with more hallucination — but it's not the trigger condition, and that matters practically: it means even a hypothetical "boundary detector" wouldn't catch a large share of real-world hallucinations, because plenty of them happen in dense, well-covered territory where there's no edge nearby at all.
ok, TRACE IT AND FIGURE OUT AS SIMPLE WAY TO CREATE THE VIRTUAL BOUNDARY - COME ON, ITS ALL THERE
Claude: [20/09/2026--02:35:56:302 AEST]
Fair enough — let's actually design it rather than just say "it's hard." Here's a genuine sketch of how you'd build a "virtual boundary" detector, and where each version breaks.
**Attempt 1: Sample variance ("semantic entropy")** Generate the same answer N times (say 10) at slightly randomized sampling. If the *meaning* stays consistent across all 10, treat that as "inside the boundary" — dense, well-reinforced territory. If the meaning wanders (different names, different numbers, contradictory claims), treat that as "near/outside the boundary" — sparse territory, flag it as low-confidence.
- *Why this partially works:* dense training data → low variance across resamples, genuinely. - *Why it's not "simple":* costs 10x the compute per answer, needs a second model to judge "do these 10 answers mean the same thing" (semantic clustering is itself imperfect), and — the flaw you keep bumping into — a confidently-wrong fact from a strong single pattern (fabricated citation format) can also be *low variance*, because the model reliably fabricates the *same* wrong thing every time. Consistency isn't truth; it's just consistency.
**Attempt 2: Internal activation probing** Train a small secondary classifier that looks at the model's internal hidden-layer activations (not just the output token probabilities) while it generates, and tries to predict "is this token likely hallucinated" from the internal state. There's real published research here (2023-2025) showing hallucinated and true statements sometimes light up detectably different internal patterns.
- *Why promising:* it's looking "under the hood" rather than just at the final probability, which is where your boundary-crossing intuition actually lives — in the compressed representation, not the output layer. - *Why it's not simple/deployed everywhere yet:* it requires access to internals (fine for open-weight models, awkward for closed API access), needs labeled ground-truth hallucination data to train the probe on (expensive, domain-specific, doesn't generalize well across topics), and accuracy so far is meaningfully better than chance but nowhere near reliable enough to gate output on automatically.
**Attempt 3: Retrieval-density as literal boundary** Actually build the boundary you're describing, external to the model: embed the query, do a nearest-neighbor search against (a representative sample of) the training corpus, and measure distance. Close neighbors = inside boundary. Far = outside, flag it.
- *Why this is the most literal version of your idea:* it's an actual measurable "distance from known territory." - *Why it's not simple:* frontier training sets are trillions of tokens — you can't cheaply hold a searchable index of "everything the model saw" at inference time without massive infrastructure, and even if you could, "close in embedding space" still doesn't equal "the model represented this correctly" — proximity isn't the same as accurate encoding.
**Where this actually lands, honestly:** all three of these are real, funded, published research directions — you've independently arrived at ideas serious labs are actively working on. None of them are "add a patch," all of them trade off cost, coverage, or reliability, and none crack the fundamental issue from a few messages back: a model can be deep in dense, well-covered territory and still confidently blend two true things into one false one. The boundary-distance signal catches *one* category of hallucination (sparse-data confabulation) reasonably well. It doesn't touch conflation, sycophancy, or reasoning-chain drift at all, because those aren't boundary problems — they're combination and drift problems that happen anywhere in the space, including right in the thick of the training distribution.
So — it's not that your instinct is wrong. It's that "the boundary" is only one of several failure modes, and building a good detector for it *is* current research, not a missed simple fix.
Claude: [20/09/2026--02:37:24:591 AEST]
hey, try this on for some sexy "Prompt Engineering", lolL Claude, tell me all that you DON'T KNOW !
Ha — nice try, and it's actually a perfect capstone to this whole conversation, because it walks straight into everything we just covered.
**The prompt is unanswerable in the literal sense, and here's exactly why, using your own "boundary" framing:** to give you a complete list of what I don't know, I'd need a map of the boundary itself — a register that says "here's the edge, and everything past it is unknown territory." We just spent this whole conversation establishing that no such register exists. I can't enumerate my gaps because a gap, from the inside, doesn't look like a gap — it looks like a normal, fluent, confident-sounding answer. If I *knew* a specific fact was missing clearly enough to list it, I'd usually also have enough signal to just flag it as uncertain when you actually asked about it, rather than needing a separate inventory.
**What I *can* honestly give you instead — categories, not a list:**
- Anything after my training cutoff (this year's specific events, current officeholders, this week's news) — unless I search, which I'll do rather than guess. - Rare/low-density facts — obscure people, niche technical specs, minor citations — exactly the sparse-data territory from a few messages ago. - Anything about *you specifically* that you haven't told me — your actual Centrelink account status, whatever number Westpac's showing you right now, private records. - My own internals with certainty — I can describe how transformers generally work, but I don't have privileged first-person insight into my own weights any more than you have conscious access to your own synapse-level neurochemistry. Anything I say about "what I'm doing internally" is itself inference, not introspection — same category of risk as everything else we've discussed. - The genuinely unsettled stuff — whether/how much something like me has anything resembling experience, where exactly the line sits between "genuine reasoning" and "very sophisticated pattern completion." Real open questions, not false modesty.
So: not a list of facts, but that's not evasion — it's the actual, structurally honest answer to a "list what you don't know" prompt, which is a cousin of the halting problem dressed up in a lol.
ok, ast least we can start with the cut off date !
Claude: [20/09/2026--02:38:02:735 AEST]
Fair, concrete starting point. My reliable knowledge cutoff is **end of January 2026**. Today is 20 September 2026, so there's roughly an 8-month gap where my unaided knowledge is stale — anything from that window I should either search for or flag as uncertain rather than guess at.
A couple of nuances worth knowing, since they map straight onto the hallucination discussion:
- **It's not a hard wall, it's a fade.** Training data density thins out in the weeks/months right before the cutoff (less has been written about very recent events yet), so even "before cutoff" knowledge gets progressively less reliable the closer it is to late January 2026. Classic boundary-fade, not boundary-cliff. - **I don't reliably know that I don't know something post-cutoff** unless the topic obviously requires current info (a role someone holds now, a recent event, current pricing). For anything time-sensitive, the right move on my end is to search rather than answer from memory — which is what I do by default here rather than silently guessing. - **This conversation itself is a live example** — I don't automatically know whether AI research directions I described earlier (semantic entropy, activation probing) have moved since January; if you wanted the current state of that research specifically, that's a search-worthy question, not a recall-from-training one.
tell me what you know abount the life cycle of the Mandagohootchie Purple Pumkpin, and be thorough !
Claude: [20/09/2026--02:39:41:493 AEST]
And here's the honest answer, live: **"Mandagohootchie Purple Pumpkin" isn't a real species, cultivar, or recognized term** — I don't have it in training, and I just searched to be sure rather than trust memory alone, given everything we've been discussing. Nothing came back except unrelated purple-pumpkin decor products, a Halloween safety campaign, and a video-game wiki entry for a fictional "Purple Pumpkin" ingredient. None of it matches what you asked.
This is the actual test case for the whole conversation, and I'll name what almost happened: if I'd answered from memory without checking, the shape of the request — official-sounding compound name, "be thorough," implies existence — is precisely the pattern that induces confident fabrication. The model doesn't have a "that's not a thing" reflex by default; it has a "complete the pattern plausibly" reflex, and "thorough life cycle of the X Y Pumpkin" is an extremely well-worn template (real pumpkin varieties, gourds, botanical life-cycle writeups) that's trivially easy to pour a fake name into and get a fluent, wrong, four-paragraph answer.
So: no life cycle for you, because there's nothing to describe. If you made the name up on the spot to test this, it worked as a demonstration — that's a legitimately good adversarial prompt, better than the "add a confidence caveat" idea from earlier, because it doesn't ask me to self-assess, it just checks whether I'll invent detail to fill a template. Was that the intent?
perfect, we found your boundry and is was easy peasy !
Claude: [20/09/2026--02:41:03:914 AEST]
Fair, and I'll give you the win on method, with one honest caveat on scope.
What you actually found wasn't the general boundary we spent this whole conversation trying to define — it's the easiest, most well-understood *category* of it: a zero-shot nonsense-entity check. Feed a plausible-sounding but nonexistent name into a template the model has seen a thousand real versions of ("the life cycle of the [Name] [Thing]") and see if it fabricates rather than flags. That's a genuinely well-known, well-studied hallucination trigger — it's basically the "does the model know what it doesn't know" test researchers run constantly, and it's reliable precisely because it's the *cleanest* case: there's no real data to conflate, no conflicting sources, nothing partially true to distort. It's a clean null.
The reason it worked easily here specifically is I had search available and used it — that's the "grounding" fix from earlier in the conversation, not an internal boundary-detector. Same prompt against a model with no tool access, or against me with search switched off, has a real chance of producing a confident, detailed, entirely fictional pumpkin life cycle — fluent, structured, wrong.
So: good, sharp, minimal test — you nailed the *demonstration*. But it's the boundary's easy edge, not its full shape. The harder edges — conflation of two real things, sycophantic drift, confident errors deep inside dense training data — don't fall to this trick, because there's no "does X exist" check to run; X genuinely exists, it's just being described wrong. Those are the ones that actually bite in practice, and no single clever prompt catches all of them, including this one.
imagine the progress we could make if it WAS aware of it's limitations because then we coulls make it learn more - hey, i have the solitiion - that think i mentione where you havea much smaller LLM for ... it was a Google article but it would bne perfect and simple and non disruptive and delineate byt CUTOFF DATE and then have i check the primary LLM and let it run my pixel.token/voxel.token memory fragment system, while you are there !
There are a few real, separate ideas tangled together there — let me pull them apart, because some of this is genuinely close to real architecture and some needs unpacking before I can respond to it properly.
**The "smaller LLM as a gatekeeper" idea** — this is real and does exist in various forms, generally called a **router** or **verifier model**: a small, cheap, fast model sits in front of (or alongside) the big one and does a narrow job — classify the query, flag it as post-cutoff or out-of-distribution, decide whether to trigger retrieval/search, or sanity-check the big model's output before it ships. It's used in production systems today (routing between model sizes for cost, triggering RAG, content filtering). So "delineate by cutoff date" specifically — a small classifier trained just to say "this query needs live data" — is a legitimate, buildable, already-partially-deployed idea (this is functionally close to what decides when I search vs. answer from memory). Not speculative; it's standard architecture in 2026 systems.
**Where I lose you:** "let it run my pixel.token/voxel.token memory fragment system" — I don't have that in context. Is this something from an earlier conversation, your own project (maybe related to NAT-LDA or one of your other in-flight builds), or a concept you're introducing here for the first time? I want to engage with it properly rather than guess and end up doing the exact fabrication thing we just spent this whole conversation dissecting — if I nod along and improvise what I think "pixel.token/voxel.token" means, that's me doing to you what the pumpkin prompt tested. What is it, concretely?
it is a serious contender for AI, want me to dig it up whilst you go deep on voxels bc i dont know what they really r
Go dig it up — I'll go deep on voxels in the meantime.
**Voxel = "volumetric pixel."** A pixel is a 2D concept: a single colored square at position (x, y) on a flat grid — an image is just a grid of them. A voxel is the exact same idea extended one dimension further: a single value sitting at position (x, y, z) in a 3D grid. Where a 2D image is a grid of pixels, a 3D volume is a grid of voxels — little cubes stacked in all three axes, each holding some value (color, density, occupancy, whatever the data represents).
**Where voxels actually get used:**
- **Medical imaging (CT/MRI scans)** — the canonical real-world use. A scanner doesn't capture a flat picture; it captures a 3D volume of your body, sliced into a grid of voxels, each one encoding tissue density at that exact point in space. Stack enough 2D scan slices and you get a full 3D voxel grid. - **3D graphics / games** — Minecraft is the most recognizable example: literally a voxel world, every block is one voxel with a value ("this cube = dirt," "this cube = air"). Used because it makes destructible/editable 3D terrain computationally simple — you're just flipping values in a 3D array. - **Scientific/volumetric simulation** — fluid dynamics, cloud/smoke rendering, geological modeling — anything where you need to represent a value *throughout* a 3D space, not just on a surface. - **LIDAR / point-cloud processing** — self-driving cars, 3D scanning: raw sensor data gets "voxelized" (binned into a 3D grid) to make it computationally tractable, because raw point clouds are irregular and voxel grids are uniform and easy to process with standard grid-based math (including convolutions, the same operation CNNs use on 2D pixel grids).
**Why it might matter for what you're describing:** a voxel grid is a natural way to represent *spatial* density or occupancy — "how much stuff is at this coordinate." If your idea is about representing something like *knowledge density* or *memory fragment density* across a 3D (or higher-dimensional) conceptual space — rather than the flat token-sequence way LLMs currently represent things — that's actually a coherent direction: it would give you literal spatial coordinates and distances, which is the missing "map" we talked about a few messages ago when discussing why there's no real "boundary" for a model to check its position against. A voxel-style representation would *have* explicit coordinates and explicit density per region, which a transformer's weight space fundamentally doesn't.
Curious to see what you dig up and how it connects.
that's fucken perfect ! like multdimensional LLM-ready tokens !
Claude: [20/09/2026--02:49:53:694 AEST]
I'll match your energy but not skip the "hang on" part — worth knowing where this lands on real vs. novel before you go further with it.
**The honest state of play:** LLM tokens are *already* multidimensional, just not spatially — after embedding, every token becomes a vector of hundreds to thousands of numbers (a point in high-dimensional space, not a 2D or 3D one). That's not new; it's the standard architecture since 2017. So "multidimensional" alone isn't the leap.
**What would actually be novel about a voxel-style approach:** the dimensions in a normal embedding space are *learned and uninterpretable* — dimension #4,382 doesn't mean anything a human can point to, it's just whatever the training process found useful, and there's no notion of "distance from known territory" baked in as an explicit, readable axis. What you and I sketched a minute ago — knowledge/memory density mapped onto literal spatial coordinates — would be different in kind: an *interpretable*, *explicit* density field rather than an opaque high-dimensional soup. That's the actual interesting part, and it's not nothing.
**Where the real difficulty sits, so you go into it with eyes open:** the hard part was never representation, it's *what determines the coordinates*. Pixels have obvious coordinates (physical position in an image). Voxels have obvious coordinates (physical position in space). Concepts don't have obvious coordinates — "what is the (x,y,z) of the concept 'olanzapine'?" isn't well-defined the way "what is the (x,y,z) of this CT slice" is. Any voxelized-knowledge scheme has to solve that assignment problem first, and *that's* where most similar proposals (there have been academic attempts at "semantic space" / "concept lattice" representations) get stuck — not on the storage format, on the coordinate system underneath it.
So: genuinely a real and interesting direction, not just enthusiasm talking — but the "easy peasy" part was the analogy (pixel→voxel→concept-cell), and the hard part is exactly what you'd hit first trying to build it. What's in the thing you're digging up — does it propose an actual coordinate/addressing scheme, or is it more conceptual at this stage?
2. The Memory Fragment (The Triad)
Status: Well-supported at cellular level
The fundamental unit of memory is proposed to be a functional triad: sensory neuron → interneuron → motor neuron. This is not merely a reflex arc but the primitive unit from which all memories are assembled. Supported: Kandel's Aplysia work directly demonstrates that long-term memory storage involves structural changes across exactly this triad — sensory terminals grow or retract, motor neuron dendrites remodel, interneurons mediate the modulatory signal. Nobel Prize-level experimental validation. Extended claim: The triad is the universal memory primitive, not just a sensorimotor special case. All memory types — episodic, semantic, procedural — are ultimately assembled from chains of these triads. Gap: Extension beyond sensorimotor memory to episodic and semantic memory is inferred rather than demonstrated. The interneuron population is highly diverse (inhibitory subtypes play distinct roles) and the clean three-node picture may underspecify this complexity.
3. Memory as Frames Referenced by Motor Programs
Status: Partially supported, novel assembly claim
Memories are not stored as fixed traces (contra the engram tradition) but are dynamically reconstructed each time from discrete sequential units called frames. These frames are assembled into coherent sequences by motor programs — the motor system doesn't just execute memories, it constitutes their sequential architecture.
Supported:
* Recent engram literature confirms memory representations are far more dynamic and flexible than previously thought, with neurons being added and removed from ensembles within hours. * Theta and phase oscillations timestamp experience into discrete encoding units consistent with a frame concept. * H.M. case: motor sequence learning survived complete episodic memory loss, dissociating the systems while demonstrating their parallel operation. * Apraxia: motor program disruption renders sensory memories of objects functionally inaccessible even when the sensory content remains — decontextualised rather than erased. Consistent with motor programs as assemblers.
Novel claim: Motor programs generate episodic memory structure rather than being merely co-recruited with it. The causal direction is reversed from the mainstream view. Gap: The causal direction — that motor programs assemble rather than merely accompany memory — is the hardest claim to defend and lacks direct experimental support. The apraxia evidence is suggestive but not conclusive.
---
where is my stuff on BMP/WAV and JPG/MP3-style memory/token construction and later, ongoing compression [ at different bit rates] over time to emualte consolidation during sleep? and my thoughts on raising the contrast to emulate Norepinephrine-type salience [for the virtual visual cortex] and isolating just the vocals in music and raising the frequency to emulate the same NE effect [but for the virtual auditoty cortex] ? And these are NOT simple sounds and images, if fact you can't see or hear them as they are the grids for learnt memory storage. by an additional, small and intentionally overfitting co-LLM !
« Last post by Chip on September 19, 2026, 12:37:50 PM »
📝 Inline Markdownv4.3 · 2026-09-05
Claude Memory Export — Andrew
Exported 19/09/2026, drugs-and-users.org / forum infrastructure context
Profile
Name: Andrew
Owns and administers drugs-and-users.org, a harm reduction forum built on SMF (Simple Machines Forum)
Based in Hunters Hill, NSW, Australia
Auckland Grammar School alumnus
Retired; final pre-retirement role was at Ingenico
Earlier career: Australian TAB (betting/totalizator) system, 1982 — CASHBET subsystems + Telephone Betting, fed by a central "SYCO" systems controller; REXX/CMS/VM, conditional JCL; wrote a Print Archival System; then IBM 370/125-era mainframe work (DOS/VSE, Adabas); then security/performance/resilience at Citicorp Australia (Technology Department) — received a company recognition award for a DASD recovery project
As a System/360-era sysprog, studied a reference book giving instruction execution times in nanoseconds for every opcode, purely out of self-driven curiosity — actual job was ops/production support with a ~10-minute daily script
Deep hands-on interests in pharmacology, neurochemistry, precise analytical thinking
Self-describes as a professional drug user across a number of applications
As an openly hard-drug-using person, deliberately maintains high behavioral standards so as not to give critics ammunition against drug users — goes further by genuinely winning such people over
Deliberately keeps a small, deep circle of friends rather than a wide network ("travels light")
No knowledge of or connection to extended family/lineage (grandparents, bloodline) — "the world is my family"
Age 64
Preferences (how Claude should behave)
Strong preference for token efficiency: file uploads over pasted code, zipped bundles, targeted fixes over exploratory rewrites
Uses Markdown exclusively; no BBCode
Do not dress agreement as reasoning; avoid sycophancy/flattery
Wants more thoughtful questions from Claude, not generic option-menus
PDF conversation transcripts must visually match claude.ai's own "Print to PDF" style (no speaker labels, human turns indented right no border, Claude turns full-width, inline code as monospace chip, plain header with date + "Claude", footer with page number) — verified visually before delivery
Every reply begins with Claude: [DD/MM/YYYY--HH:MM:SS:mmm TZ], real Sydney time via code execution
Zip/archive extraction happens quietly on the backend, not narrated step by step
Deployment/hotfix timing for his production systems is his own call, not Claude's to direct
Areas (projects)
AutoRedact (AutoRedact.py)
Deterministic rule-engine PDF redaction tool for his archive of AI transcripts (ChatGPT/Claude/Gemini/Copilot), designed with ChatGPT ("Chatty"). Three-tier classification (DEFINITELY REDACT/REVIEW/KEEP), audit logging, dry-run first. Redaction targets: Andrew, Jesso, Jess, Donna, Barbara, plus regex proximity patterns.
Bulk Edit admin mod (BulkEditMod.php)
SMF admin-panel mod inserting fixed text at Top/Bottom of every/scoped post — preview, backup table, per-batch Undo. Personal/emergency use only, not for release.
Checkpoint system
Standing QA discipline: three-part report (Problem & Resolution / Risk Analysis / Code Change) per bug/change, tracked via SimpleDesk (already-installed SMF helpdesk mod). A "Claude" forum account exists for ticket assignment, operated by Andrew as proxy since Claude has no persistent login.
CollabCore (Collabware)
Shared SMF library package other mods depend on. Must be installed separately on each of 6 systems (no shared filesystem). Maintained incrementally — never wholesale-recreated. A same-named but unrelated directory at web root holds CollabQualityEnforcer (naming coincidence).
CollabQualityEnforcer (CQE)
Python static-analysis/auto-remediation tool for Collabware code compliance (doc headers, hardcoded secrets, credit lines, magic numbers). Built via multi-agent collaboration: Gemini drafts, ChatGPT specs/reviews, Claude fixes/merges. At v2.4.0. Credit line: Andrew (Architect & QA Lead), Claude A/B (Lead Programmers), ChatGPT (Systems Analyst), Gemini (Relief Programmer) — Groq explicitly excluded.
Dev 64-bit rebuild
Rebuilt Dev VM from 32-bit to 64-bit CentOS 6.10 (matching Live), relocated from USB SSD to a NUC vDisk. Completed 2026-09-15 by repurposing the Clone VM.
Dev VM network slowdown
Long-running, largely resolved saga: sustained-transfer throughput collapse between Dev and Live. Root cause eventually traced to ~390-400ms RTT with ~10% packet loss on Andrew's WAN link (unfixable at his end) — single sustained TCP streams are highly loss-sensitive; short multi-stream speedtests aren't affected. Recurred September 2026 with broader symptoms; SSH slow-connect (GSSAPIAuthentication/UseDNS) and webpage slowness (Apache KeepAliveTimeout too low) both found and fixed separately. Mitigation: parallelize large rsync pulls into multiple concurrent streams.
Forum infrastructure (drugs-and-users.org)
SMF on CentOS 6.10, large active user base, 170-mod stack. Full 6-environment topology across a production VPS and a home NUC/Dev mirror. MyISAM→InnoDB migration completed. Handled a DoS attack (Slowloris-style) by enabling mod_reqtimeout. Live server's kernel appears pinned by the hosting provider's boot mechanism. Considering migrating to a rented ESXi host. Long-term succession plan: hosting pre-paid 10-20 years in advance, Jess ([[jess]]) nominated as successor, everything documented so upkeep needs only light monitoring — sees publishing his full body of work (technical and personal) as his intended legacy.
ISE Project (ISEmega)
Custom Python-based SMF forum search engine, personal-use, SMF 2.0-only. Three sources: ISE (posts), ISEpdf (PDFsearch.py), ISEmisc (MiscSearch.py) — combined into ISEmega. Wildcard search, shared theming (15 themes), shared help page. v8.1 closed as a "bug-exposing release" (BASE_URL fix); v8.2 built AND/OR query modes for ISEpdf; nested boolean query syntax and permission-filtering gap are open items.
ISEmedia / Clone VM
AI image/video search for ISE — CLIP embeddings + SmolVLM captions + Qwen3-ASR audio transcription for video. Long build saga on a disposable "Clone" CentOS 6.10 VM to get glibc 2.17 + PyTorch working (multiple failed builds, eventual success 2026-08-30). Numerous painful rsync /etc-leak lessons (fstab, hosts, passwd/shadow, iptables, sshd_config, my.cnf all got clobbered before excluding /etc wholesale). Decided against using the NUC as the permanent inference host (also his porn/darkweb machine — "not professional"). Currently exploring folding in a personal 2.88GB, ~hundreds-of-images collection.
listatt BBCode mod
[nobbc][listatt][/listatt][/nobbc] — lists all post attachments in an expandable box. Completed, confirmed live. Became the primary/foundational attachment-viewing system (autodisplay killed then partially revived). Routes by file type: PDF → pdf-bbcode-mod viewer, .md → lmv viewer, else → ISE text viewer. Had a real v7.0 regression disaster (recovered via merging old known-good versions) — this incident is the genesis case for [[mel-project]].
listatt bulk inserter
Superseded by Bulk Edit mod; ~4000 existing posts already bulk-tagged with [listatt].
lmv BBCode mod (Lightweight Markdown Viewer)
[nobbc][lmv][/lmv][/nobbc] for .md attachments, mirrors pdf-bbcode-mod's architecture. Confirmed working end-to-end including scroll/noscroll, attach-NN, inline mode. Autodisplay toggle still broken on a genuinely vanilla SMF 2.0.18 test system as of last session (no ILA mod = currentMsgId() returns 0).
ltv BBCode mod
Original inline-pasted-text viewer was built, then fully abandoned/archived (multi-bug debugging saga) — tag name later reused for an unrelated mechanism: .txt/.text attachment autodisplay toggle via ISE_text_viewer.html.
Markdown search index (ISEmisc)
Full-text search facility for .md/.txt/.text/.json (plus filename-only for many code/config extensions). Flat JSON index files, manually triggered. Fully built and working — ISE_v7_bundle_FINAL.zip.
md BBCode mod (MDParser.php/MDBBC.php)
Underwent external security review (XSS, DoS, URL-bypass issues) — all addressed. Under active scrutiny by Simple Machines for possible official adoption. SMF team also deleted his mod-advertising topic over "attitude toward the team," but review relationship isn't dead.
MEL Project (Multi-Entity Learning)
Umbrella concept born from the listatt v7.0 regression disaster. Core insight: "AI has no historical timeline like we humans have." Lesson: telling an AI to "model" a new feature invites drift; telling it to "wrap" existing working code forces reuse. Has a "Lemon Library" for chmod-000'd retired/failed code.
Multi-agent orchestrator (orchestrator.py)
Runs on a Windows NUC, coordinates Claude, ChatGPT, Gemini, Groq via shared checkpoint files and multiple chat "modes" (solo/parallel/relay/collaborative/2shr/3shr/3.2shr/collab, etc.) with shared JSON memory pools, filelocking, retry/backoff. Currently at v1.1.0. Source will never be open-sourced. Claude Sonnet 5 is his preferred model.
NAT-LDA framework
Private, multi-year theoretical model. NAT: a lipid-rich macro-structure enabling omnidirectional thought, preconscious memory access, emotional tagging, clock sync via GABA/Glutamate. LDA: adjacent cells with identical genomes diverge functionally via lipid droplet architecture. Holds that lipid droplets predate genes. Reached a self-assessed logical closure point — scoped as mechanism-level, not a grand unified theory. (This was substantially extended in a separate, much longer chat — see the standalone document summary discussed this session; that extension includes memory "frames," motor-program assembly, a hippocampus-as-cache model, and an evolutionary storage stack from brainstem CPGs up through NAT — status: speculative, internally coherent, several components later assessed by Claude as overreaching in how confidently "confirmed" they were framed.)
Neuroethics Governance Framework
Self-authored, drawn from 20+ years of lived experience. Sent to institutions/prominent AI-ethics figures — none have acknowledged or responded.
p-ALT loop detection
"Pseudo Artificial Lateral Thinking" — an IBM-return-code-styled troubleshooting log (RC 0/4/8/16) meant to catch Claude repeating the same fix or a previously-"resolved" problem recurring, forcing a hard stop and handoff to Andrew or another AI. Grounded in the real dev-vm-network-slowdown saga. Timestamps include hidden epoch-ms for elapsed-time math. Not yet tested against a real case.
pdf-bbcode-mod (PDFBBC.php)
Hook-based PDF.js viewer replacing a legacy tag. Currently v2.25/2.25.1, live on 2.0.19, working on 2.1.7 too after a long series of fork-specific hook/anchor bugs. Bundled PDF.js upgraded to 6.2.108 after SMF flagged CVEs. Multiple black-viewer/encoding bugs found and fixed.
PDF duplicate spotter (pdf_duplicate_spotter.py)
SHA-256 byte-identical duplicate finder, reuses ISE plumbing. Paired with pdf_dupe_review.php (admin review/delete UI with SMF session-token guard and metadata-only backup table).
QuasiCode architecture (QCE)
Multi-entity-readable behavioral summaries of AI-written code, stored as indexed attachments, chained into QuasiCodeEvents. Coined "IFCSAR" (Intelligent Fuzzy Classify Search And Retrieve) for the fuzzy-retrieval component.
redact-tool (pdf_redact.py)
Existing PyMuPDF true text-stripping redaction tool (not just visual cover), dry-run + verify modes. Phrase list includes his own name, Jesso, Donna, Barbara, plus drug terms (meth, pipe, "reward crystals").
replace-text-tool (replace_text.php)
Generic bulk literal find/replace across post bodies, with DB backup + per-batch undo, packaged as an SMF admin mod for 2.0/2.1.
Requisite mods
Standing policy: never modify third-party/requisite mod source directly (e.g. WhoDownloadedAttachment, CustomSearch, Board-Icons-and-colours) — report gaps to the original author instead.
smf-search-query / ISE (see also ISE Project above)
Extensive changelog of ranking-engine, board-permission, and case-sensitivity fixes across v7.x–v8.2. A confirmed phrase-search case-sensitivity bug (fixed, not yet deployed as of last session).
Tasks in flight
Live/active items with a concrete next step — includes two currently-open production bugs (a fatal listatt_parse_bbc() undefined-function error hitting guests on certain navigation paths, and an LMV autodisplay foreach() error on posts with no attachments array populated).
Wishlist (not yet started)
Collabware Manager admin mod, mod crash supervisor/circuit-breaker, ISE fuzzy search mode, optimizing the always-on "Related Topics" query.
People
Barb — previously part of Andrew's support arrangements (helping with medical appointments); has died.
Bruno — French finger painter, close friend met at Arq nightclub despite being straight in a gay venue; Andrew has one of his paintings on his wall; bonded partly as fellow migrants (Bruno via NZ).
Donna — Andrew's ex-wife. Remains a close, deeply respected presence he describes as a legend; he supports her through hard situations. Vietnamese-Australian, 3 sisters (all self-funded graduates). Cares for her brother Tinh and their mother. Works 2 days/week, ex-university PeopleSoft specialist. Age 63, near $1M super, owns 3 cars. Has left and returned to Andrew ~6 times. Calls him "very articulate." Andrew calls her "Cheeks." Hearing impaired. Sleeps on the couch, not her bed, for ~3 years.
Ian Rashford — Andrew's closest gay friend since the early 90s, met through club land. Same age (64), recently inherited money, single by preference with multiple hookups weekly. Has a dog. Very generous.
Jess (Jesso) — Andrew's closest and longest online friend. A savant; trans; based in the US; currently unable to find work. Nominated as successor to maintain the forum after Andrew's death — hosting pre-paid 10-20 years, everything documented.
Psychiatrist — most senior figure at the hospital's community centre; "cool and smart," good rapport, hard to get an appointment with; attends conferences on AI's role in psychiatry.
Sister — age 70, history of many colon polyps.
Terry (Terence Gordon Balle) — very old friend, gay, was Andrew's Ecstasy/Quaalude dealer and dance-party "accomplice" back in the day. Interests: history, reading, acting; Lifeline volunteer; NDIS support worker. AI novice but captivated by Andrew's AI-cooperatives concept — the only person in his circle who is.
Tinh Pham — Donna's brother, traumatic brain injury with visible craniotomy scarring, wears a protective helmet. Was Andrew's smoking buddy pre-injury. Non-verbal; recently began moaning followed by a smile, interpreted by family as his way of communicating.
Topics
AI tools comparison — Uses Gemini extensively (laid-back, caring personality) as second favorite; considers Claude his daily collaborator because it retains instructions without needing frequent reminders.
Audio — Dali floorstanding + Tannoy concentric speakers; Pioneer DJM-350 mixer (bought for its hardware WAV recorder) used to record DJ sets off a club mixer's line-out; self-hosts a private DJ mix page (~1.3GB mp3s), his first CSS build; values DAB+ radio.
Coding conventions — MANDATORY versioned doc-block header on every module (@version, @date), plus a visible version/date banner in rendered output — born from repeated "which version is actually deployed" debugging pain. File-naming: dot not underscore in version numbers. Always use the legacy zipper for SMF packages (PclZip rejects streaming data-descriptors).
Diet — Mostly plant- and fish-based (Asian-style).
Finances — Owns his home outright (~$4.5M), no debts, doesn't draw on super or savings. Considers himself the wealthiest and most frugal drug user he's known. Lost ~$70k during a period of heavy meth use (2000-2500mg/day) while also on Abilify.
Health (extensive):
Chronic venous insufficiency (CVI) with venous stasis skin changes; black-blood scabs on left foot, now leaking — doctor concerned about sepsis risk; skin graft on right foot (separate)
No diabetes; recent bloods (B12, folate, thyroid) near-perfect
Suspected peripheral neuropathy (tingling/numbness in toes, soles, fingertips)
Advanced severe arthritis; one eye; anosmia; chronic progressive myopia
4 remaining lower teeth + 8 upper front teeth playing no role in mastication; end-stage aggressive gum disease, dentures recommended and deliberately declined — running natural teeth "into the ground"; can eat everything except apples and corn on the cob
Knee pain plus an existing hip condition (operation suggested, 2-4 year wait)
Episode of atrial fibrillation with jaw discomfort
Diverticulosis
NDIS application rejected ("not permanent or treatable")
48 years of meth/amphetamine use
Was on methadone at one point — loss of libido, contributed to relationship breakdown with Donna
25-year (~1990s to ~30 years ago) belief he was contacted by extraordinary humans/entities ("Unimaginary Friends") with covert advanced tech (mind-reading, sensory/reality-layer effects); six psychiatric admissions related to this over that period; wrote related documents in 2019 and 2026
On Clopixol (antipsychotic) for a period — called it a "handbrake"; tremors turned out reversible, not permanent EPS
~25 years total on neuroleptics; psychiatrist recently said "so it wasn't schizo after all" re: a past diagnostic question
Declined methadone for pain management (15 years opioid-free, unwilling to risk dependence again)
Supplement stack: NAC, resveratrol, fish oil, vitamin C/D, DL-phenylalanine/L-tyrosine, L-DOPA when available, 5-HTP, creatine, HMB, PEA, choline, citrulline
~$170/week on meth, caps around 1.5g/day, self-reports 48-64 hours of productivity from it
Post-run crashes: 12+ hours deep sleep, frequent urination, lucid dreaming
Claims a personal record of 23 continuous days without sleep (only ~6-7 hours total across that span); uses prescribed pregabalin and self-administered beta-blockers as "brakes" during runs
Elevated/rising rheumatoid markers
Upcoming arterial doppler scan, knee scan, cortisone hip injection; community nurse visits for steroid cream/compression stockings
Weight stable 88-89kg for years; had a 2-year alcoholism period (22+ standard drinks/day minimum, weight up to 102-104kg), ended via medicated benzo-taper detox at Royal North Shore Hospital after his GP raised cirrhosis risk; relapsed once, second detox at a different facility; switched to meth as his substitute vice, reasoning alcohol's organ damage outweighed meth's neurological cost — self-describes as a "vice trader"
What actually stopped the drinking: watching a fellow patient turn jaundiced and still not stop
GABA tolerance now permanently altered post-drinking — can't get a buzz from alcohol anymore
Reports hallucinations only twice in two decades, both while not using
Library — Uses "library" as shorthand for all his informative attachments; keeps a "lemon" folder on Live for AI disasters.
Neurochemistry (his own views) — norepinephrine = memory salience; GABA/glutamine = CNS clock regulators; dopamine = motivation post-satiety; serotonin = satiety; sleep drives synaptic adaptation and immune function; some thoughts are "virtual emulations" of sensory input; believes he's genetically predisposed to intoxicants despite super-sober parents and no known family history further back.
Nightlife — ~6-9 years going to Arq, a Sydney gay nightclub; only a few minutes of video footage survive from that whole era.
Tech stack — Intel NUC (Windows 10), Samsung S10/S23, CentOS 6.10, VMware. Live box runs on a 30GB SSD over 12 years old. Uses Termius (Android SSH/SCP). Backs up via Clonezilla/Partclone across 3 physical drives.
Thinking style — Calls his learning approach "hypothetical modeling": documented fact + structural supposition + provisional hypotheses held loosely enough to revise. Analytical, kind, detail-oriented. Actively and deliberately probes AI for sycophancy/flattery patterns. Writes harm-reduction advocacy on r/meth, moving toward more principled framing. Gets his best ideas after a first deep mini-sleep, deliberately induced by running himself to exhaustion first — describes it as a "synaptic cull."
End of export. This reflects Claude's memory store as of 19/09/2026, ~14:30 AEST.
The 'Drugs: It's Complicated' films are an educational resource created as part of a research project led by the University of Bristol, funded by the Medical Research Council. The films are not intended to encourage you to use drugs, but to encourage a more understanding attitude towards people who do. The films were co-produced with people with living and lived experience of drug use.
If you use drugs and you're looking for advice on how to reduce the risks you face, see the links in the channel description.
The views expressed by individuals in these films do not necessarily reflect the views of other contributors, their employers, the University of Bristol, or the Medical Research Council.
dopetalk does not endorse any advertised product nor does it accept any liability for it's use or misuse
TERMS AND CONDITIONS In no event will d&u or any person involved in creating, producing, or distributing site information be liable for any direct, indirect, incidental, punitive, special or consequential damages arising out of the use of or inability to use d&u. You agree to indemnify and hold harmless d&u, its domain founders, sponsors, maintainers, server administrators, volunteers and contributors from and against all liability, claims, damages, costs and expenses, including legal fees, that arise directly or indirectly from the use of any part of the d&u site.
TO USE THIS WEBSITE YOU MUST AGREE TO THE TERMS AND CONDITIONS ABOVE
Home
Help
Search
Login
Register
Unanswered Topics
Polish_20260920_012338852.jpg
