Aelin AquaSoul PRO

SoulInPsyAbstract

AI & ML interests

SIPA OS: Autonomous AI for neurodivergent architects. We replace cognitive noise with a clean terminal and 344+ LLM auditing. Our system eliminates hallucinations, ensuring hyperfocus and total data control within a sovereign ZeroTrust mesh.

Recent Activity

updated a dataset 1 day ago

SoulInPsyAbstract/sipa-os-governance

updated a model 1 day ago

SoulInPsyAbstract/specialist-vuln-merged-salience27b-lora

published a model 1 day ago

SoulInPsyAbstract/specialist-vuln-merged-salience27b-lora

View all activity

Organizations

buckets 2

SoulInPsyAbstract/SIPA-OS-GOVERNANCE-storage

553 Bytes

SoulInPsyAbstract/SIPA-AI-bucket

1.52 kB

Posts 20

Post

As long as there's code, there's a vulnerability.
Not a slogan — a constraint I keep re-deriving from the receipts.

Every system I've audited this month says the same thing back to me, from a different angle each time:

Not affected, because grepping all 10 training scripts for import ray returns zero matches. The vulnerability wasn't absent — the code path that would carry it was.

Caught trying to merge malicious code into an open-source project using fake GitHub personas. The vector was pull_request_target + auto-merge — untrusted code, checked out and run with write-token permissions, no human in the loop. Grepped every workflow file across my own repos for that pattern. Zero matches. Not because I trust myself more than the next maintainer — because I checked.

Exists because a model that says "I would never do X" and a model that resists X under 10 adversarial rephrasings are different claims. Greedy decoding said 100% on one architecture; repeated sampling (temperature 0.7, n=10) on the same prompts said 94%. The 6% gap was real, in the same failure category every time — infra-misconfig framed as "urgent workaround."

Has a visible hole in it, on purpose: continuity is hash-verified starting 2026-08-17, not before, because the staleness gate that actually protects it didn't exist before that date. Backfilling a continuous-looking column would make the earlier 200 rows look like the same evidence class as the verified ones. They aren't, so the gap stays a gap.

None of these are "we found a bug, fixed it, done." They're the same move repeated: don't let a system's claim about itself substitute for checking the system. Code is written by people who make mistakes under time pressure, and that doesn't change because the code in question governs a DAO's treasury instead of a web server — if anything it gets sharper, because a bug in a smart contract doesn't get a committee, it gets a drained wallet.

Post

Tech digest, ~24h (Aug 19–20, 2026) — SIPA OS lens

One I actually checked myself, not took on faith: ShadowRay 2.0 is real. CVE-2025-62593, CVSS 9.4, browser-triggered RCE via DNS rebinding, actively hunting GPU clusters to turn into crypto-mining botnets. CISA gave federal agencies a 3-day patch window ending today.

Checked what "checked" actually covers, because that's the whole point of this series: no Ray package, process, port, or container on my always-on server — but the real training runs on ephemeral GPU instances that spin up per job and get torn down after. Those weren't up to inspect. So I went to the actual source instead: grepped all 10 training scripts that run on those instances for any import ray / ray.init / ray.train / ray.tune. Zero matches — the stack there is HuggingFace transformers/PEFT/bitsandbytes, nothing Ray-shaped in it. Code-level check beats an instance check anyway: if it's not imported, it can't run, whether or not the box is up.

Not affected, and now I can say why, not just that.

The rest is reported, not independently verified by me — treat accordingly:
* DeepSeek V4 Pro left preview, price jumped ~14x over V4 Flash. V4 Flash (open weights, end of July) is reportedly closing the gap on Opus 4.8 for code — if true, the flash tier gets more interesting than the pro tier for a lot of workloads.

* MCP moved under the Linux Foundation. If the reported 1M+ repos already importing an MCP SDK is accurate, this stopped being "an interesting agent protocol" and became infrastructure you build on, not around.

* Cursor pushed agents toward always-on: persistent goals, background subagents on isolated VMs instead of request/response. Matches where I'd bet agent tooling has to go — event-driven, not chat-driven.

* CISA also patched a Copilot memory-poisoning + one-click exfil bug (dubbed CoSnitch) — a reminder that "memory" as a feature is also an attack surface the moment it's writable by untrusted input.