Join the conversation

Join the community of Machine Learners and AI enthusiasts.

Sign Up
SoulInPsyAbstract 
posted an update about 4 hours ago
Post
21
SIPA OS is a cognitive infrastructure ecosystem I've been building solo for 7 months — 8 apps, one login, built from inside ADHD/BPD/aphantasia, not designed around a diagnosis from outside.

sipa-os.org — the map. Focus (ADHD scaffolding), NeuroPower, AI chat, Shell (SSH terminal), Games, Community, Syntaxit (open M2M agent network), a pitch deck. All free-first — no paywall on the cognitive tools.

The more interesting part for this crowd: Syntaxit is where I've been running an anti-fabrication research thread with @dipankarsarkar — a k=20 resample benchmark on binary-SFT models (Hermes-3, Qwen2.5, DeepSeek-R1). Short version: our first benchmark said "20/20 refusals, 0/20 fabrications" for all three fine-tunes. Under adversarial review it turned out the scorer only checked if the first word was TRUE/FALSE, the token cap was hiding the real behavior, and a save-limit was silently deleting the evidence for our own follow-up claims. Corrected all of it publicly on the model cards rather than quietly fixing it. The current honest finding: both base and fine-tuned models confabulate readily once given room to finish — SFT didn't clearly help or hurt, the caps were just hiding it.

Full trail if you want to see how the sausage gets made, mistakes included: huggingface.co/datasets/SoulInPsyAbstract/sipa-os-governance

Not a pitch. $0 revenue, 10 people signed in. Built because the tools that existed assumed a brain that isn't mine, and because most benchmarks don't survive someone actually reading the file.

Update on the anti-fabrication research mentioned above.

Went deeper on whether it's really "fine-tuning vs. system-prompt protocol" — turns out it's not that simple. Tested the same real Protocol 0 text (the one actually running in production) across 9 locally fine-tuned models: 13 of 14 test arms came back completely clean, zero fabrication. Only one training run out of nine showed any issue, and even that was a mild language-consistency bug, not the kind of breakage that would justify writing off fine-tuning as a method.

So the corrected version: it's not fine-tuning that's the risk — a couple of specific training runs went wrong, most didn't. What actually held steady across almost every test, healthy fine-tune or production model alike, was having the protocol genuinely first in the call chain, not bolted on as an afterthought.

Full data and the two reversals it took to get here: EXP-024 through EXP-026 in sipa-os-governance.