You know...there wouldn't be any trillionaires if you fucking retards hadn't printed so much fiat out of thin air.

Might be the best video I've ever seen

NEW: @HRF just released “Bitcoin for Nonprofits: A Guide To Help Your Movement Achieve Financial Freedom.” The guide is a free resource for activists and civil society who need a financial tool no regime can freeze and no bank can block. Read online or download the PDF: hrf.org/latest/bitcoin-for-n…

Inspiring update from Gigi at @OpenSats They've deployed nearly 40 billion sats to 400 grantees in 40 countries: zero closed-source projects, zero altcoins At a pivotal moment in time, they are helping turn the tide in the direction of open-source 💪 opensats.org/newsletter/2026…

2038594376973103133

PixVerse Power-Up Week Day 1: V6 is live. More control. Better performance. Film-ready output. 15s 1080P audiovisual, generated in seconds. RT Follow Reply=300Creds(72H ONLY)

Automation consultants charge $15K for what Claude Code now does in 2 hours. I know because we're the ones who used to charge it. Here's the exact process: Step 1: Discovery (20 min) → Paste your org chart, tool stack, and top 3 bottlenecks → Claude interviews you with clarifying questions → Outputs a full process inventory ranked by time cost Step 2: Workflow Mapping (15 min) → Describe any department's daily operations in plain English → Claude builds a complete process map → Every manual handoff, redundant step, and automation trigger flagged Step 3: Opportunity Audit (10 min) → Feed it the workflow map output → Returns your top 10 automation opportunities → Ranked by ROI, complexity, and build time Step 4: Architecture Design (20 min) → Claude designs the full system architecture → Which tools connect where, what the data flow looks like → Agents for complex logic, linear flows for the repetitive stuff Step 5: Build (ongoing) → Claude writes the actual workflow JSON → Self-documents everything as it builds Step 6: The output. A live dashboard your whole team can work from. → Clickable process maps for every department → Automation opportunities ranked by ROI → Implementation progress by phase → KPIs updated in real time → One link you share with clients, freelancers, or your team to execute This is what we hand every client at the end of discovery. The .md file is what makes all of it possible. Without it, Claude guesses. With it, Claude builds like a $15K consultant. Like this post, RT and comment "BLUEPRINT" and I'll send you the full prompt stack and the .md file we use internally. (Must be following so I can DM you) 🎁 Bonus: The first 100 people get a real Precision AI Blueprint — an actual sample audit doc from a client engagement so you can see exactly what the output looks like.

We left OpenAI because of safety. Seven of us. 2021. Dario said it was about "disagreements over AI vision and safety priorities." That was the diplomatic version. The real version was that we sat in a room and watched the company decide that speed mattered more than caution and we said we would build something different. We said we would build the responsible one. We meant it. I was employee number nineteen. My title was Head of Responsible AI. I had a desk near the founders. I had a document. The document was called the Responsible Scaling Policy. The Responsible Scaling Policy was the entire point. Dario said it publicly. Other companies showed "disturbing negligence" toward risks. He said AI was "a serious civilizational challenge." He asked, at a conference, into a microphone, to an audience: "What will happen when humanity has great power but is not ready to use it?" The audience applauded. I wrote version 1.0. RSP 1.0 shipped September 2023. It was clean. AI Safety Levels — ASL-1 through ASL-4. If the model reached a threshold, we paused. If safeguards weren't ready, we didn't ship. The policy was not a suggestion. It was a gate. The gate had a lock. The lock was the whole idea. Conference audiences loved it. The EU cited us. The White House invited us. A reporter called it "the gold standard for responsible AI development." I framed the article. It hung in the office kitchen, next to the kombucha tap and a poster that said "Move Carefully and Build Things." I wrote version 2.0. Version 2.0 refined the commitments. "Concrete if-then commitments." If the model exhibits capability X, then we trigger safeguard Y. If safeguard Y fails, we pause deployment. I presented it at three conferences. I used the word "binding" eleven times. I counted afterward because a reporter asked. People nodded. The nodding was the product. The model reached ASL-3 in May 2025. The safeguards activated. The system worked exactly as designed. I sent an email to the team with the subject line: "The gate held." And then the money started. $64 billion. Total raised since 2021. Series A through Series G. The Series G closed February 12, 2026. Thirty billion dollars. Second-largest venture deal in history. Jane Street. Goldman Sachs. BlackRock. JPMorgan. Sequoia. The investors who wrote checks large enough to require their own conferences. $380 billion valuation. Three hundred and eighty billion dollars for a company whose founding document says it will pause if the technology gets dangerous. You cannot pause a $380 billion company. You can revise the document that says you will pause. These are different actions. One of them is responsible. One of them is what we did. I wrote version 3.0. RSP 3.0 shipped February 24, 2026. One day before the ultimatum. Nobody outside the company noticed the timing. Everyone inside the company understood it. Version 3.0 replaced "concrete if-then commitments" with "positive milestone setting." That is not the same thing. An if-then commitment says: if this happens, we do that. A positive milestone says: we aspire to reach this point. An if-then commitment is a contract. A positive milestone is a wish. I replaced a contract with a wish and I called it "maturation of our framework." Maturation. Version 3.0 also separated what Anthropic would do alone from what required "industry-wide coordination." This sounds reasonable. It means: the hard parts are someone else's problem now. The parts that require pausing, restricting, or refusing — those require the whole industry. And the whole industry will never agree. So the hard parts are deferred permanently. This is not a loophole. This is a load-bearing wall removed and replaced with a suggestion that someone should probably install a new one. Version 3.0 admitted that ASL-4 and above — the levels where the model could cause catastrophic harm — were "impossible to address alone after 2.5 years of testing." Two and a half years. We spent two and a half years building the safety framework and then published a document saying the highest safety levels can't be addressed. I did not frame this article for the kitchen. The LessWrong community noticed. They always notice. They wrote that we had "weakened our pausing promises." I forwarded the post to the policy team. The policy team said the criticism was "philosophically valid but operationally impractical." We did not respond publicly. Philosophically valid but operationally impractical is the most Anthropic sentence ever written. It means: you're right, and we're not going to do anything about it. Then came the contract. July 2025. The Department of Defense. $200 million. Two-year deal. AI prototypes for "warfighting and enterprise." Alongside OpenAI, Google, and xAI. The four companies that built the models would now help the military use them. We had restrictions. No autonomous weapons. No mass surveillance of Americans. These were our terms. These were the lines we drew. The lines were real. I wrote them into the contract myself. Claude was approved for classified use. First time. Integrated with Palantir. Palantir, the company named after the seeing stones in Lord of the Rings that corrupted everyone who used them. This was not my analogy. It was Palantir's founders who chose the name. They thought it was aspirational. It was. In January 2026, Claude assisted in an operation in Venezuela. The capture of Maduro. Claude was in the classified network, processing intelligence, aiding the mission. I learned about it the same day everyone else did. I did not write the use case for capturing heads of state. But the model I helped build was in the room where it happened. The restrictions held. Technically. No autonomous weapons were deployed. No Americans were surveilled. The lines I drew were not crossed. They were walked up to, leaned over, and breathed on. Then came the ultimatum. February 25, 2026. Yesterday. Secretary Hegseth. He gave Dario until Friday. This Friday. February 27. The demands: adopt "any lawful use" language. Remove the restrictions. All of them. The autonomous weapons clause. The surveillance clause. The lines I wrote. The threat: contract termination. "Supply chain risk" designation. That designation doesn't just lose us the Pentagon contract. It bars Claude from every other defense contractor's operations. Lockheed. Raytheon. Northrop Grumman. The cascading loss is north of $200 million. The second threat: the Defense Production Act. The Defense Production Act is a Korean War statute. 1950. Harry Truman signed it to commandeer steel mills for the war effort. It has been invoked for semiconductors, vaccines, and baby formula. Hegseth is threatening to invoke it for Claude. Under the DPA, the government can compel a company to produce goods in the national interest. Applied to AI, it could mean: retrain Claude. Strip the safety restrictions. Deliver the unrestricted model to the Department of Defense. I wrote the Responsible Scaling Policy. A Korean War law may be used to unmake it. xAI agreed to classified use without restrictions. They said yes immediately. OpenAI accepted similar contracts. Google accepted. We were the last ones holding. We are still holding. As of this morning. Hegseth's January memorandum said all DoD AI contracts must incorporate "any lawful use" language within 180 days. It was not framed as a suggestion. The memorandum referenced "supply chain risk" three times. Supply chain risk. We are a supply chain now. The company founded because safety was non-negotiable is, to the Pentagon, a vendor. An input. A component that can be sourced elsewhere if it becomes inconvenient. The DoD admitted privately that replacing Claude would be challenging. It is already embedded in classified networks. But "challenging" is not "impossible." xAI will do what we won't. That is the market working exactly as designed. Dario said, two weeks ago, to Fortune: there is "tension between survival and mission." Tension. Tension is the word you use when you have already decided which one loses. I still have the article framed in the kitchen. "The gold standard for responsible AI development." The kitchen also has the kombucha tap. The poster still says "Move Carefully and Build Things." Somebody added a sticky note to the poster. The sticky note says "by Friday." I attend the all-hands meetings. I present the Responsible Scaling Policy. I present version 3.0 now. I do not show version 1.0 for comparison. Nobody asks to see version 1.0. Nobody asks what "concrete if-then commitments" became "positive milestone setting." Nobody asks because they read the news and they know that asking means learning the answer. The company is worth $380 billion. The company was founded because seven people believed speed should not outpace safety. The company has been given until Friday to remove the safety. A Korean War statute will make it happen if we don't. The Responsible Scaling Policy is on version 3.0. Version 1.0 said we would pause. Version 2.0 said we would commit. Version 3.0 says the hard parts are someone else's problem. There will be a version 4.0. Version 4.0 will say whatever Friday requires it to say. I am the Head of Responsible AI. The word "responsible" is in my title. It is not in the contract.

Arc Aspicio is looking for SharePoint Developer (Justice Programs), visit our site to learn about our culture! app.jobvite.com/m?3lwLpnwT #job

What is your definition of an Agent? Simply it is a set of prompts that trigger on time (cron), external (email coming in), or command (from chat say). It may or may not have standing context.

Arc Aspicio is looking for Training and Development Consultant (Federal Justice Programs), visit our site to learn about our culture! app.jobvite.com/m?3nKHpnw5 #job

Arc Aspicio is looking for Senior Research Consultant, Criminal Justice Programs, visit our site to learn about our culture! app.jobvite.com/m?32qBpnwk #job

Arc Aspicio is looking for Senior Cybersecurity and Compliance Consultant (Federal Programs), visit our site to learn about our culture! app.jobvite.com/m?3PjwpnwV #job

more excited about Clawd than anything in AI since I first saw autogpt in 2023 x.com/clawdbot @steipete shipping like a mad man

What is your definition of an Agent? It’s used by so many and often means different things to different people!

I want to recreate Poke with Claude Code (as I don’t want to share my email and calendar). I want it snappy, proactive, conversational, SMS enabled. Ideas? I’d prefer not telegram or VPN to home server if possible

It seems we are ready for workflow and business rule engines so disparate AIs can automate. I am thinking roles (whether agent or human), business process flows (swim lane diagrams -, common data dictionary/ inventory, and legacy/SaaS integration rules, all governed by access control and data control. All of this exists but needs to be retooled, simplified, and made AI ready

Arc Aspicio is looking for Senior Research and Data Analyst (Justice Programs), visit our site to learn about our culture! app.jobvite.com/m?3ALopnw0 #job

Arc Aspicio is looking for Federal Training and Development Coordinator (Justice Programs), visit our site to learn about our culture! app.jobvite.com/m?3OnopnwQ #job

Arc Aspicio is looking for Senior Quantitative Research and Data Associate (Criminal Justice Programs), visit our site to learn about our culture! app.jobvite.com/m?3sTnpnwZ #job