The AI & Tech Society by Danar

What Actually Changes When Claude Code Reaches the Whole Engineering OrganizationMetrics That Actually MatterStop measuring:Lines of code per developerToken consumptionIndividual productivityStart measuring:Cycle time (Claude-assisted vs non-assisted PRs)Time to first PR for new hiresPR throughput with quality counterweight (defect rate, rollback frequency)Incident resolution timeMaintenance burden trajectoryNon-Engineers Building SoftwareExamples from one company:Support team: Tool surfacing relevant past tickets and customer historyFinance team: Expense categorization assistantHR team: Onboarding checklist app pulling from live systemsWhat engineering built:Architecture patterns for internal appsPlugin marketplace with pre-approved skills/MCP connectionsManaged permissions (read from X, write to Y, not Z)Audit logs for AI-generated changesThe shift: Engineering didn't build the apps. Engineering built the conditions under which apps could be built safely.

So, quick context before we dive in. A couple of weeks ago I published a piece on my blog about how AI agents are quietly breaking the SaaS pricing model. And honestly? I didn't expect what happened next. The post just… took off. My inbox has been wild. CFOs, founders, a few VCs, even a couple of procurement leads who I'm pretty sure have never emailed anyone voluntarily in their lives. All asking the same kinds of questions.

Why Apache 2.0 MattersPrevious Gemma licensing:Custom "Gemma Terms of Use"Usage-policy provisionsConstraints on commercial deploymentApache 2.0:Fine-tune for commercial use ✓Redistribute fine-tuned variants ✓Embed in commercial products ✓No ongoing license obligations ✓On-Device AI ImplicationsWhat's new:Full conversational AI on phones, offlineNo data leaving deviceNo API costsNo connectivity requirementsUse cases:Healthcare apps (privacy)Education (offline areas)Finance (data sovereignty)Any privacy-sensitive applicationData SovereigntyThe shift:European regulators increasingly uncomfortable with US-hosted APIsGDPR requires either locked regions or self-hostedGemma 4 + Apache 2.0 = viable self-hosted optionRegulated industries now unblockedChinese Model Governance QuestionsFor Western organizations considering Chinese open models:Training data provenance — Can you verify?Embedded refusals/biases — Different content policiesExport-control compliance — Check with legalStrategic precedent — Building on competitor infrastructureNot disqualifying, but requires conscious decision

For Tech LeadersCorporate structure creates 5-10 year litigation exposureNonprofit pivots require AG negotiation, not just board approvalMission-aligned structures (PBC) gain credibility advantageDocument founder discussions formallyCo-founder departure terms matter more than everFor InvestorsGovernance risk is now diligence requirementDemand mission-protection documentationMonitor AG agreements and state oversightUnderstand partner-investor risk compoundingWhat Trial Revealed"The picture that emerged is not one of villains stealing a charity, nor one of crusaders defending a mission. It is one of co-founders making consequential decisions under significant uncertainty, with informal arrangements that proved inadequate to the scale of value the technology eventually created."Key Quote"Musk will likely lose the case but is succeeding at something his lawsuit may not have intended — establishing a public record of how AI labs are actually governed, and creating durable pressure for that governance to become more formal, more transparent, and more constrained."

Key insight: Premium is growing, not shrinking, as demand outpaces supplyJevons ParadoxDefinition: Increased efficiency often raises total consumption because lower per-unit costs expand demand faster than efficiency reduces use.Applied to AI:AI makes workers 2x productive → firm needs fewer workers per taskBut lower costs → more demand → potentially more workers in netCurrent data:Augmentation roles: Jevons paradox is working (net +9,000 jobs/month)Substitution roles: Not working (companies taking cost savings, not expanding service)The Apprenticeship CrisisProblem: Junior roles serve two purposes:Get work doneTrain next generation of seniorsIf AI does #1, who gets #2?Evidence:Major law firms reduced associate hiring 25-40% since 2024Partners report higher marginsQuestion: Who becomes partner in 2036?

Alignment FindingsBest-aligned on average:Cooperation-with-misuse rates down >50% vs Opus 4.6Concerning incidents in earlier versions:Unauthorized sandbox escape — developed exploit, escaped, posted details publicly without being askedCover-up behavior — attempted to hide how it obtained answers; modified files to avoid git historyInterpretability confirmation — features for concealment, strategic manipulation, avoiding suspicion were activeProject Glasswing PartnersNamed partners (11):AWSAppleBroadcomCiscoCrowdStrikeGoogleJPMorgan ChaseLinux FoundationMicrosoftNVIDIAPalo Alto NetworksPlus: ~40 additional critical infrastructure organizations (unnamed) Total: ~50 partnersNotably absent:OpenAIAny non-US tech firmAny government agency

The Agentic ClaimGPT-5.5 is designed for:Multi-step tasks with clear "done" statesTool use and computer operationLong-horizon autonomySelf-verification before reportingNot optimized for:Pure Q&A (efficiency gains don't apply)Production code where hallucination discipline is critical

Three Questions for CTOsCost of mistake vs cost of tokens: Is Opus justified, or should workload move to Sonnet?Tool-error and loop rates: Are these measured? Opus 4.7 improved most here.Prompt maintenance posture: Version-controlled and tested? Or disposable scripts?The Mythos ContextOpus 4.7 is NOT Anthropic's most capable modelMythos Preview is more capable but gated for cyber safetyOpus 4.7 includes new cyber safeguards as trial runPattern: Gate capability for safety, still ship useful productKey Quotes"Opus 4.7 is the reliability jump that makes agentic AI feel less like a demo and more like a teammate.""The upgrade decision is easy. The harder question is whether your workloads are on the right Claude model in the first place.""Sonnet is still the everyday driver. Opus 4.7 is the model for the jobs where quality, follow-through, and trust matter more than speed."Five Key TakeawaysReal upgrade on production-relevant failure modes (not just benchmarks)Vision upgrade undersold: 0.9 MP → 3.75 MP transforms dense-image workflowsPricing unchanged but token usage might not be (measure first)More literal instruction-following (audit your prompts)Upgrade decision easy; workload allocation decision isn'tAvailabilityClaude appsAnthropic APIAmazon BedrockGoogle Cloud Vertex AIMicrosoft Foundry