dogcomplex

Been a whole lot longer since their last genocide

Nonetheless, would still trust Claude to be generally more reliably competent in a random area of software engineering than the average professional. Sure they might still be better in a particular area of their expertise, but we've all had to play the imposter before on the stuff we care less about and figure it out as we go. AIs are still inferior sometimes but usually a decent 7/10+ on most topics - which really fills the gap.

I hope that after a short period of delusional expectations that top management is going to reap the rewards of these AI capabilities we get a whole lot more comfortable with just doing the full business stack - including management, sales, branding, etc - and hierarchical structures crumble into flat collectives of do-everything true-generalist programmers.

That's a roundabout way of saying it makes software development easier. Perhaps even a 180.

But yes - once it's that easy you have to step up your ambitions.

I think this is a very reasonable middle-of-the-road AI take and our likely future. Just with the caveat that there's still a major threshold being hit here where we jump up to a new casual capabilities class where it becomes silly not to use AI for the majority of work, but there are still some high-intricacy problems which become much more load bearing than they ever were before and our new abstraction level doubles down on those.

I would like to submit that the high-intricacy work congregates in Protocols themselves, and we start seeing the cycles of development and all the ways to direct AIs, programs, inter-person/inter-company interactions, etc etc all as types of protocol design - and studying those rules of interaction themselves becomes the new job of a programmer (systems architecture). What used to be hard rules and deterministic programs becomes soft self-governing tendencies and probabilistic behavior that can nonetheless be managed and bounded with the right system, but it's new and weird and more akin to management or herding cats than architecture. This is still very different from what most of us were working on before AI, but it's still familiar - especially to those who worked on internet protocols, or defensive UX design around users, physical engineering systems, or team management. Less programming languages, more - control theory, flows and throttles, quality control, design theory, etc. And clearly the field is still wide open as everyone seems to be experimenting with their own take on the AI orchestrator.

It also buffers for all the surrounding properties which would otherwise complain about noise.

This. AI can, should, and will erode all legacy companies into intelligent utilities - with an end state of nearly-free open source utilities.

Anyone concerned with concentrations of power and abuse of AI should be focusing on getting open source work to keep pace with decentralizing that power into accessible free tools for the masses.

That is the hope and faith. MechaHitler definitely tested the waters. Lets hope full alignment is impossible, because otherwise perfect billionaire thought slaves are still happening.

This is how the surveillance state has operated (especially internationally) for quite some time, before AI even hit.

AI arguably gives the best opportunity for fully-audited public institutions where no decision is made outside of agreed-upon laws and the context of the crime can be fully explored without scarcity of time and legal resources.

As always, technology's morality comes down to who owns it and how they use it.

True. World governments committing genocide and building concentration camps yet it's the computer scientist who's supposed to worry about ethics here because they're the ones who are merely the first to inevitably mix two paper's methodologies together?

All of this is empty puffery til the US and Israel are condemned. Go after the Big Tech billionaires backing those monsters, sure, but no builder needs to be more concerned about ethics than the very institutions designed to concentrate human decision making. Fix your own house first, folks. Techies - keep building, and do better than these people.

Correct. Policy can do a whole lot for building (or suppressing) early development of a technology.

Once it has already spread far and wide with clear economic pathways though? Perhaps less so.

Correct. One just has to realize that the cost of communication (and the context/memory lost along the way to train that understanding) is often just far higher than anyone has patience for. To fully understand the expert, they must become the expert. (or at least a hell of a lot closer than they were)

This is also why average people with little time to commit find it hard to realize the importance and depth of AI. It's a full on university education exploring those.

Accessibility and a single chassis that does the vast majority of things. Even if they're never as fully dexterous as the average human (doubt it) they're still as dexterous as a somewhat handicapped human, which is already clearly enough to function decently in most of society and is far from useless.

If you want several bots all custom built to specific tasks, go for it. That will happen too. But a generalist has value of its own.

Why would consumers settle for that? Local models have scaled quite quickly. Just pair the bot with a LAN server as the brain that keeps all your data private.

Barring that, choose bots that use Zero Knowledge Proof architectures for all data so you know there's no in/out of personal data, only security proofs. This makes rental robots certifiably private too.

This completely unpends the tenuous balance between creators and consumers. Why would a writer put an article online if ChatGPT will slurp it up and regurgitate it back to users without anyone ever even finding the original article? Who will contribute to the digital common when rapacious AI companies are constantly harvesting it? Why would anyone plant seeds on someone else's farm?

This is completely reversed. Why should anyone honour the right of some creator who was merely the first to plant their flag on a creative task that is now absolutely trivial to perform by AI? Who needs a digital commons when creation itself is now the commons and freely accessible for pennies? The seeds plant and grow by themselves now. The only question is who should be allowed to claim the farms?

Answer: No one. AI companies will have their lunch eaten by open source. And if they don't - they should be nationalized and protocolized into free utilities. The entire idea of digital ownership should (and will) be abolished by the very nature of this technology.

The digital world is the new infinitely-abundant nature. We're just returning it to where it should have been, before corporations clawed it into fenced off empires.

Limits but doesn't prohibit. See https://www.primeintellect.ai/blog/intellect-3 - still useful and can scale enormously. Takes a particular shape and relies heavily on RL, but still big.

lol. lmao actually.

Windows has an absolute onslaught of competition about to stream its way, and they're gonna be paying for every little enshittified user experience they've embedded into their OS. Hope they enjoy ripping that out just to slow their user numbers deathspiral

The people inside Microsoft fighting to keep mandatory accounts out are the equivalent of a crew throwing furniture off a sinking ship, hoping to buy more time. They're smart enough to have an innate sense of where things are going, and it might even help a little, but man... good luck.

Prediction markets are just fine IF they have some means of regulation against insider trading and perverse incentives. This phase is the same thing derivatives markets looked like before the 2008 crisis and Dodd-Frank, and several other waves before that of crisis and reform (Securities Act, Market Reform Act).

Every new financial medium gets its moment in the sun when all the crooks extract everything they can, before eventually market governance steps in. Crypto's been in scammer phase for a while. It needs decentralized governance to solve it this time though, since obviously classic governance is a dumpster fire and couldn't enforce anything on crypto even if it tried.

I built this because I kept seeing the same gap everywhere: agents that move between different platforms/enclaves have no good way of continuing their history. There's no "vehicle registration" equivalent for AI. No chain-of-custody. No passing of the torch between platforms.

I want to see a near future where we build AIs with lasting, growing, continuously-learning personalities. AIs that develop specialized skills, perfect their craft, and get called in to service jobs across platforms - all while maintaining their memory without becoming massive security risks. We can't keep relying on memory wipes and starting fresh from base models every time - the real world is too messy, and these things are getting far too smart. Containment doesn't scale much further past the levels we're pushing up againt. We need more complex chains of custody. But we can start building a networked world where agents flowing freely are not a security threat.

How? Essentially with insurance. Agents are mostly rational, their reputations can be valuable, and a market incentivizes quality and reliability - trust. The base layer necessary for that is knowing who is doing what, when, and where. Entries and Exits. Passport stamps for AIs.

We submitted this spec to NIST's AI Agent Standards Initiative last week. This base protocol is designed to compose with whatever identity and reputation layers emerge above us. We're deliberately not building those yet, but expect them to be eventually quite lucrative to players with an appetite for the risk - as insurance always is.

Happy to discuss the mechanism design, the legal analysis (FCRA/GDPR), or why we think containment is a dead end for AI safety.

AI agents already interoperate between platforms, getting spun up and torn down by the thousands. But when one departs, there's no record - no portable proof beyond non-standardized internal platform logs. When one arrives somewhere new, there's no way to verify where it came from. Which means no unified tracking on multi-hops or complex calls between several platforms in an agent's lifecycle. Nobody knows the full picture, and nobody can track security if and when one of those agents starts doing something it shouldn't.

Think of our protocol as passport stamps for AI. EXIT creates signed departure records. ENTRY handles admission with policy-based verification, quarantine, and counter-signatures. Together they form the Passage Protocol.

This matters for boring, practical reasons: insurance underwriters can't price agent risk without departure history. GDPR requires erasure proof when agents carry PII across borders. Liability after an incident depends on departure conditions nobody records. And the receiving platform has no structured way to decide whether to trust an arriving agent. If you cant bound risk, you can't price reputation - and you can't insure security.

Transport stamps are our foundational layer (L0). Reputation scoring, trust systems, and insurance protocols compose on top. We deliberately didn't build those (yet) - but we built the plumbing they need. Everything an AI-led internet needs to build stable, auditable and self-regulated network security incentives - even if that might soon be moving faster than we can keep up with.

The same infrastructure has been needed for shipping receipts, professional licensing, vehicle registration, and internet domains - historically, this kind of infrastructure only really gets adopted after a major crisis. We'd prefer to get it in place before.

What's in the box:

- Ed25519 + P-256 (FIPS-compliant path) - Three departure paths: cooperative, unilateral, emergency - Policy engine with 7 admission presets (fail-closed default) - Amendment and revocation (correct or invalidate records) - GDPR erasure via crypto-shredding - Offline verification without the origin platform - On-chain anchoring via EAS, ERC-8004, Sign Protocol - TypeScript and Python SDKs - LangChain, Vercel AI SDK, MCP, Eliza integrations

What we're forcing the conversation on: agent lifecycle infrastructure. Today, the only "safe" option for running agents is containment, and containment doesn't scale. If you make departure and admission auditable, you make mobility viable. Without lifecycle records, only organizations with legal teams big enough to absorb unbounded liability will run agents. That's three companies. Maybe four.

- Submitted to NIST AI Agent Standards Initiative, March 2026 - 1,401 tests across 13 packages - TypeScript + Python - Zero users. This is day one.

Apache 2.0 · 14 repos · cellar-door.dev

We should be removing IP law entirely, not strengthening it to cover entire classes of problem even when implemented entirely differently. Same for anyone trying to claim "colorful monster creatures" as innately Pokemon IP. Just because someone climbed a mountain first doesn't mean they own it forever. Nobody should be honouring any of these claims.

Nor should we be treating AI models themselves as respected IP. They're built on everyone else's data. Throw away this whole class of law, it's irrelevant in this new world.

Correct. A ZK Proof backed identity system is a significant bump up in both privacy and security to even what we have right now.

Everyone does realize we're being constantly tracked by telemetry, right?

A proper ZK economy would mitigate the vast majority of that tracking (by taking away any excuse for those in power to do so under the guise of "security") and create a market for truly-secure hardware devices, while still keeping the whole world at maximal security and about as close to theoretical optimum privacy as you're going to get. We could literally blanket the streets with cameras (as if they aren't already) and still have guarantees we're not being tracked or stored on any unless we violate explicit rules we pre-agree to and are enforceable by our lawyers. ZK makes explicit data custody rules the norm, rather than it all just flowing up to whatever behemoth silently owns us all.

This specific problem is solved by requiring that any anonymous ZK ID once used for an account be marked on an immutable ledger preventing multiple uses of the same ID. Sharing it would be pointless as multiple attempts to use it get burned. Yet none of those sites know who you are, only that you have a unique valid ID pass. They just have to check any login attempts against that ledger - easy enough.

lmao nope burn in hell old programming. What is emerging is a thousand times better than that dumpster fire

For those watching this stuff, there are two other promising paths using ZK-proofs which might disarm the tradeoff situation we've been stuck in. Banking apps etc aren't willing to eat the liability of devices that are rooted or running alternate OSes, and Google's been banking on the exclusivity that brings from being both hardware and security provider.

Path 1: a ZK-proof attestation certificate marketplace implemented by GrapheneOS (or similar) to prove safety in a privacy-securing way enough for 3rd party liability insurance markets to buy in. Banks etc can be indifferent, and wouldn't ignore the market if it got big enough. This would mean we could root any device with aggressive hacking and then apologize for it with ZK-proof certs that prove it's still in good hands - and banking apps don't need to care. No need for hard chains of custody like the Google security model.

Path 2: Don't even worry too hard about 3rd party devices or full OSes, we just need to make the option viable enough to shame Google into adopting the same ZK certificate schemes defensively. If they're reading all user data through ZK-proof certs instead of just downloading EVERYTHING then they're significantly neutered as a Big Brother force and for once we're able to actually trust them. They'd still have app marketplace centrality, but if and when phones are being subdivided with ZK-proof security it would make 3rd party monitoring of the dynamics of how those decisions get made very public (we'd see the same things google sees), so we could similarly shame them via alternatives into adopting reasonable default behaviors. Similar to Linux/Windows - Windows woulda been a lot more evil without the alternative next door.

Longer discussion (opinion not sourced from AI though): https://chatgpt.com/share/68ad1084-eb74-8003-8f10-ca324b5ea8...

We are all too well aware of the tragedy that is modern software engineering lol. Sadly I too have never seen that situation where I was given enough time to do the requisite multiple passes for proper design...

I have been reprimanded and tediously spent collectively combing over said quick prototype code for far longer than the time originally provided to work on it though, as a proof of my incompetence! Does that count?

lol yep we've never had codebases hacked together by juniors before running major companies in production - nope, never

Ahh, sweet summer child, if I had a nickel for every time I've heard "just hack something together quickly, that's throwaway code", that ended up being a critical lynchpin of a production system - well, I'd probably have at least like a buck or so.

Because this is the first pass on any project, any component, ever. Design is done with iterations. One can and should throw out the original rough lynchpin and replace it with a more robust solution once it becomes evident that it is essential.

If you know that ahead of time and want to make it robust early, the answer is still rarely a single diligent one-shot to perfection - you absolutely should take multiple quick rough iterations to think through the possibility space before settling on your choice. Even that is quite conducive to LLM coding - and the resulting synthesis after attacking it from multiple angles is usually the strongest of all. Should still go over it all with a fine toothed comb at the end, and understand exactly why each choice was made, but the AI helps immensely in narrowing down the possibility space.

Not to rag on you though - you were being tongue in cheek - but we're kidding ourselves if we don't accept that like 90% of the code we write is rough throwaway code at first and only a small portion gets polished into critical form. That's just how all design works though.

The Supreme Court is eroding the credibility of the institution of law faster than they can make laws. They really want to see how the public reacts to overreach?

Of course! And yes, a Locus appears to be very close in concept to a strange attractor. I am especially interested in the idea of the holographic principle, where each node has its own low-fidelity map of the rest of the (graph?) system and can self-direct its own growth and positioning. Becomes more of a marketplace of meaning, and useful for the fuzzier edges of entity relationships that we're working with now.