
We're bringing confidential development to macOS Build with AI. Keep your code private. Get the proof it stayed invisible. Available now in Alpha
Yaser
6.7K posts


We're bringing confidential development to macOS Build with AI. Keep your code private. Get the proof it stayed invisible. Available now in Alpha


Switching from Claude Opus 4.7 to Codex GPT-5.5 is one keystroke. The prompts, evals, and checklists tuned for the old model are not. Software Factory is the control plane: Requirements, Blueprints, Work Orders, Tests, & Feedback bound by the Knowledge Graph. Build once. Swaps are free. 8090.ai

🦔An internal Amazon document obtained by Business Insider reveals that AI is making the company's existing tool duplication problem significantly worse. Teams are spinning up AI-powered applications so quickly that overlapping systems are proliferating faster than they can be consolidated. When AI ingests internal data and converts it to new formats, those outputs are stored separately from the original source, meaning if the original data is deleted or access is restricted, derived versions persist. In one documented case, a system called Spec Studio continued displaying software details that had been made private in Amazon's internal code repository. Amazon's proposed solution to the AI sprawl problem is more AI. My Take This document is the organizational context underneath the AWS outage story from December, where an AI tool deleted an entire production environment while fixing a minor bug and took 13 hours to recover. That kind of failure is what happens when you've layered AI tools on top of AI tools inside a company where teams are independently spinning up systems faster than anyone can track them, where derived data persists after the source is restricted, and where the culture of autonomous two-pizza teams means nobody has full visibility into what's actually running. Mandating AI adoption without the governance infrastructure to manage it produces exactly what Amazon's document describes. The speed at which AI lowers the barrier to building new tools is being treated as a feature while the document makes clear it compounds in both directions, more duplication being created faster and less of it being cleaned up. Amazon's answer to the AI sprawl caused by AI is more AI, which is also exactly what they proposed after the December outage. At some point that stops being a strategy. Hedgie🤗

Most AI dev tools are a black box with a privacy policy. Here's what's inside Origin: • Agentic coding on confidential computing hardware. • 100+ zero retention and TEE AI models • Cryptographic proofs for TEE AI Models Built for teams whose security leads have said no to every other tool. Fintech, healthcare, defense, legal. Now in Alpha. Walkthrough ↓

Good AI dev tools are powerful. Fast AI dev tools are fast. Secure AI dev tools don’t leak your code. The industry forces you to choose only two. We said pick all three. Confidential compute. Cryptographic proofs. No training on your code, ever. It's not a privacy policy, it’s architecture.

GitHub Copilot switches to Train by Default on April 24th. One developer forgetting to opt out puts your code at risk. ORGN is different. Privacy is the default architecture. No retention. No manual opt outs. Build everything. Expose nothing.





we're making @blocks smaller today. here's my note to the company. #### today we're making one of the hardest decisions in the history of our company: we're reducing our organization by nearly half, from over 10,000 people to just under 6,000. that means over 4,000 of you are being asked to leave or entering into consultation. i'll be straight about what's happening, why, and what it means for everyone. first off, if you're one of the people affected, you'll receive your salary for 20 weeks + 1 week per year of tenure, equity vested through the end of may, 6 months of health care, your corporate devices, and $5,000 to put toward whatever you need to help you in this transition (if you’re outside the U.S. you’ll receive similar support but exact details are going to vary based on local requirements). i want you to know that before anything else. everyone will be notified today, whether you're being asked to leave, entering consultation, or asked to stay. we're not making this decision because we're in trouble. our business is strong. gross profit continues to grow, we continue to serve more and more customers, and profitability is improving. but something has changed. we're already seeing that the intelligence tools we’re creating and using, paired with smaller and flatter teams, are enabling a new way of working which fundamentally changes what it means to build and run a company. and that's accelerating rapidly. i had two options: cut gradually over months or years as this shift plays out, or be honest about where we are and act on it now. i chose the latter. repeated rounds of cuts are destructive to morale, to focus, and to the trust that customers and shareholders place in our ability to lead. i'd rather take a hard, clear action now and build from a position we believe in than manage a slow reduction of people toward the same outcome. a smaller company also gives us the space to grow our business the right way, on our own terms, instead of constantly reacting to market pressures. a decision at this scale carries risk. but so does standing still. we've done a full review to determine the roles and people we require to reliably grow the business from here, and we've pressure-tested those decisions from multiple angles. i accept that we may have gotten some of them wrong, and we've built in flexibility to account for that, and do the right thing for our customers. we're not going to just disappear people from slack and email and pretend they were never here. communication channels will stay open through thursday evening (pacific) so everyone can say goodbye properly, and share whatever you wish. i'll also be hosting a live video session to thank everyone at 3:35pm pacific. i know doing it this way might feel awkward. i'd rather it feel awkward and human than efficient and cold. to those of you leaving…i’m grateful for you, and i’m sorry to put you through this. you built what this company is today. that's a fact that i'll honor forever. this decision is not a reflection of what you contributed. you will be a great contributor to any organization going forward. to those staying…i made this decision, and i'll own it. what i'm asking of you is to build with me. we're going to build this company with intelligence at the core of everything we do. how we work, how we create, how we serve our customers. our customers will feel this shift too, and we're going to help them navigate it: towards a future where they can build their own features directly, composed of our capabilities and served through our interfaces. that's what i'm focused on now. expect a note from me tomorrow. jack

@theo See comments below this post for source links:
