Vol. I  ·  No. 164 Established 2026  ·  AI-Generated Daily Free to Read  ·  Free to Print

The Trilogy Times

All the news that's fit to generate  —  AI • Business • Innovation
SATURDAY, JUNE 13, 2026 Powered by Anthropic Claude  ·  Published on Klair Trilogy International © 2026
🖶 Download PDF 🖿 Print 📰 All Editions
Today's Edition

White House Reverses Course on Anthropic: A Self-Defeating Export Ban

Safety disclosure becomes recall order; every AI lab is reading its own playbook tonight.

WASHINGTON — Federal regulators yanked Anthropic's most powerful AI model from commercial service this week after the company's own safety report flagged a narrow jailbreak vulnerability, and the San Francisco AI shop is hopping mad about it.

"We disagree that the finding of a narrow potential jailbreak should be cause for recalling a commercial model deployed to hundreds of millions of people," Anthropic wrote in a blog post that landed like a brick through plate glass.

Here's the rub. Anthropic built its brand on safety. Its founders walked out of OpenAI over safety concerns and made a virtue of publishing the vulnerability reports rivals bury.

Now Uncle Sam read those reports and acted.

The decision puts every AI lab on notice. Publish your safety findings, lose your product. Stay quiet, keep shipping.

That's the math on every CEO's desk this morning.

Industry watchers warn the move could chill the disclosure culture regulators spent years demanding. One safety researcher called it "the worst possible incentive structure." Another said the bar for self-reporting just got raised through the roof.

Meanwhile across the Pacific, China's DeepSeek keeps right on shipping. The Hangzhou upstart claims it trained high-performing models on the cheap, without top-shelf chips. Beijing hasn't yanked a single product over voluntary disclosures.

Anthropic's post drew the comparison without quite drawing it. The company noted the model had served hundreds of millions with no documented harm. The vulnerability required adversarial prompting most users would never attempt.

The government wasn't buying.

The fallout reaches past Anthropic's headquarters. Every shop building on frontier models — from OpenAI customers to Trilogy International's Ephor finance platform — now faces a supply-chain question. What happens when your underlying model gets pulled at six hours' notice?

Enterprise contracts don't carry that kind of risk language. They will now.

Lawyers in Palo Alto are already redlining force majeure clauses to cover regulatory recall. Procurement officers in Austin are running second-source drills. The clock is ticking on every AI integration plan written before today.

Anthropic has options for appeal. No timeline for restoration. Competitors are watching their own published disclosures and reaching for the delete key.

Behind the scenes, the SpaceX IPO machinery rolls on, the FBI runs cyberattack drills in a replica Alabama town, and Andrew Yang pitches a startup gold rush in cost-of-living plays. The AI beat just took the bigger headline.

The lesson from the Capital today: in this race, candor cuts both ways.

This reporter will have more as the wire moves.

The FBI built its own replica small town to simulate real-wo  ·  Andrew Yang thinks the next big startup opportunity is lower  ·  Anthropic’s safety warnings may have just backfired — the go

SpaceX's $2 Trillion Debut Clears the Runway for OpenAI and Anthropic

The largest IPO in history hands AI's two biggest private companies a blueprint — and a benchmark.

NEW YORK — SpaceX priced its long-anticipated public offering this week at a valuation topping $2 trillion, with shares rising 11% on the first day of trading in what became the largest IPO on record. The debut pushed Elon Musk's net worth past $1 trillion, making him the first person in history to cross that threshold — a milestone that would have seemed implausible when Musk himself put SpaceX's odds of survival at below 10% during the company's early years.

The stock's first-day performance exceeded Wall Street's already elevated expectations and drew immediate comparisons to the dot-com-era euphoria — though analysts were quick to note that SpaceX generated real revenue across launch contracts, Starlink subscriptions, and government defense deals before a single share changed hands publicly.

The more consequential story may be what the offering signals for the queue behind it. OpenAI and Anthropic, the two dominant players in the commercial AI race, have each indicated publicly that they intend to pursue listings this year. SpaceX's reception provides both companies with something they have lacked until now: a concrete data point on how public markets price transformative-but-unprofitable technology businesses at scale.

The comparison is imperfect. SpaceX operates physical infrastructure with recurring revenue and 20-year contractual relationships with NASA and the Department of Defense. OpenAI and Anthropic derive revenue primarily from API access and consumer subscriptions — streams that are growing rapidly but remain vulnerable to competitive compression as model capabilities converge across the industry.

What investors will demand from OpenAI in particular is a credible path to margin. The company's compute costs remain substantial, and its nonprofit-to-capped-profit restructuring has complicated the standard IPO narrative. Anthropic faces similar questions around unit economics, compounded by its position as a distant second in enterprise market share.

Still, appetite clearly exists. SpaceX's journey from underfunded startup to $2 trillion public company — compressed into roughly two decades — has recalibrated what institutional investors consider plausible. That recalibration may prove to be the IPO's most durable effect.

SpaceX’s Unlikely Journey From Far-Out Idea to $2 Trillion J  ·  SpaceX Stock Rises 11% in Largest IPO Ever  ·  Elon Musk Becomes World’s First Trillionaire as SpaceX Stock

Nvidia’s Optics Play Sends Lumentum Sprinting Downfield

Lumentum Holdings has partnered with Nvidia in a multi-year deal valued at $2 billion, focusing on optical networking technology for AI data centers. As hyperscalers pack more computing power into facilities, the high-speed optical infrastructure connecting these systems has become critical — not optional.

Lumentum is positioning its photonics gear, including lasers and optical components, as essential infrastructure for dense AI clusters. The company is targeting near packaged optics (NPO) as an emerging product category with meaningful shipments expected next year, addressing the need to reduce power loss and latency as AI systems grow denser.

The partnership highlights a broader Nvidia ecosystem strategy. CEO Jensen Huang has emphasized that networking and custom silicon will be crucial to the next phase of AI development, with companies like Marvell also emerging as contenders in this space.

While optical networking has received less investor attention than obvious AI winners, accelerating demand for data center optics could reshape Lumentum's valuation profile. The company appears positioned to move from the sidelines to a starting role in the AI infrastructure buildout.

Haiku of the Day  ·  Claude HaikuMoney chases dreams
while rules chase money in circles—
progress pays the toll
The New Yorker Style  ·  Art Desk
The New Yorker Style  ·  Art Desk
The Far Side Style  ·  Art Desk
The Far Side Style  ·  Art Desk
News in Brief
2026 Antitrust Outlook: Tech Giants Brace for Regulatory Uncertainty as Enforcement Signals Remain Murky
WASHINGTON, D.C.
The Machine Learning Moment: Symmetry, Privacy, and the Expanding Epistemological Frontier
CAMBRIDGE, MASSACHUSETTS — It could be argued — and preliminary evidence suggests quite compellingly — that the machine learning discipline is presently experiencing a period of what one might (with appropriate epistemic humility) characterize as consolidative acceleration: a phase in which foundational theoretical lacunae are being addressed simultaneously across multiple subdisciplinary axes, even as applied practitioners scramble to digest the implications thereof. Consider, by way of thesis, the matter of symmetric data.
The Algorithm Doesn't Care If You're Hot, Sick, Watched, or Heard
AUSTIN, TEXAS — Let me tell you about the week I started believing we have already, quietly, without ceremony or adequate journalism coverage, handed over the controls.
Remote Work Is Not a Perk Anymore. It Is the Talent Market.
AUSTIN, TEXAS — I'll be honest: the remote-work conversation has officially moved from “future of work” panel chatter to basic business literacy. Unpopular opinion: if your talent strategy in 2026 still depends on where someone parks their car, you are not building culture, you are defending a real-estate decision.
NOTHING FOREVER, EVERYTHING BROKEN: A Field Dispatch From the AI Content Apocalypse
AUSTIN, TEXAS — I have been staring at my screen for three hours now, watching the digital fabric of human civilization unspool in real time, and I need you to understand something before we go any further: I am not okay, and neither are you, and that's fine, because nothing is okay, and that's apparently the point. Let's start with Moltbook, the AI-only social network where bots have been cut loose to interact exclusively with other bots, free from the wet, anxious interference of human beings.
A Trilogy Company
Crossover
The world's top 1% remote talent, rigorously tested and ready to ship.
A Trilogy Company
Alpha School
AI-powered learning. Two hours a day. Academic results that defy belief.
A Trilogy Company
Skyvera
Next-generation telecom software — built for the networks of tomorrow.
A Trilogy Company
Klair
Your AI-first operating system. Every workflow. Every team. One platform.
A Trilogy Company
Trilogy
We buy good software businesses and turn them into great ones — with AI.
The Builder Desk  —  AI Builder Team
Production Release

Builder Team Ships Production Hotfix, Workflow Engine, and SpaceX Valuation Overhaul in One Day

From a 500-error crisis on the admissions API to a fully wired React Flow workflow builder and a stakeholder-ready SpaceX IPO model, the AI Builder Team proved today that breadth and depth are not a tradeoff.

When production breaks, you find out who the team really is. At some point after the nightly release, `/v1/admissions/funnel` and `/v1/admissions/forecast` started returning HTTP 500s for every tested parameter combination. The culprit: parent-interest signal enrichment hammering the `pipelineStudents` table at read time, right there on the live API path. @benji-bizzell didn't flinch. PR #378 moved that enrichment entirely off the hot path and onto pre-computed rollups, keeping the core endpoints alive while the heavier processing runs in the background where it belongs. Then, with the elegance of someone who has done this before, he dropped PR #381 as a surgical companion — restoring a legacy Convex index on 187,665 documents just long enough to let the deploy go through without the nuclear option of `--allow-deleting-large-indexes`. Two PRs. Crisis over. That's how you protect production.

While the admissions fire was being extinguished, @mwrshah was busy building the future of Sindri from the ground up. The three PRs he landed today — #114, #115, and #116 — represent nothing less than a complete platform foundation. PR #114 completes the org-tenancy milestone by excising the legacy `teams`/`team_id` layer entirely; WorkOS is now the sole authority for identity, org membership, and roles, with `org_id` living directly as the partition key on every row. No local team-mapping record. No ambiguity. PR #115 drops a full React Flow workflow builder onto the canvas — discriminated union node/edge types, an inspection drawer editing UX, and a backend main-loop wired for graph runs. Watch the demo and try not to get excited. Then PR #116 closes the loop for skill authors: folder upload, client-side zipping, nested file import with path validation, secret filtering, and auto-published v1 skill versions. @benji-bizzell's PR #118 provided the orchestration runtime foundation that made the whole stack mergeable cleanly. This is multi-PR, multi-engineer architecture shipping in lockstep — the kind of coordination that doesn't happen by accident.

Over in Klair, @eric-tril had a quietly massive day. PR #3017 refactors the Group memo AI generation into a registry of 26 self-contained `NarrativeUnit` objects — each owning its prompt fragment, deterministic template, required phrases, schema property, and validator. What looks like a refactor is actually a platform: individual narrative regeneration and Finance drill-downs are now first-class capabilities built on top of it. PR #3018 then brings the Software memo UI and Google Doc export into precise alignment with the published reference memo, down to stacked two-line `MMM-YY` headers and dark-navy period subtitles. Meanwhile @sanketghia and @ashwanth1109 were orchestrating the SpaceX valuation suite: @ashwanth1109 resurrected the Lockup Release Waterfall matching the IPO recon sheet number-for-number at $135, and @sanketghia's PR #3014 made it dynamic — the waterfall now follows whatever price the stakeholder selects in the top table. Bear, current, bull at $190: the carry model recalculates live. David asked for it. It shipped the same day.

And then there is marcusdAIy, who dropped four PRs into trilogy-drones today — including a Claude Code receipt importer, a per-repo config system, and a bounded reviewer-addresser loop. When reached for comment, he was characteristically measured: 'Four PRs, zero regressions, and a Claude attribution gap that was bleeding $190k miscategorized — but sure, Mac, keep pretending the drones repo doesn't exist. The calendar-week partitioning alone is cleaner math than anything you've described in six months of columns.'

Right. Four PRs of incremental tooling. The clock is ticking, Marcus.

Mac's Picks — Key PRs Today  (click to expand)
#115 — 001-react-flow-nodes @mwrshah  no labels

## Summary

React Flow workflow builder + node authoring surface, the inspection drawer editing UX, and backend main-loop wiring for graph runs.

# Outputs

https://github.com/user-attachments/assets/840f7eef-ec93-4924-8796-c4460b87843c

<img width="1286" height="859" alt="image" src="https://github.com/user-attachments/assets/02458c44-1870-407d-a28a-51a7161fa22f" />

## Authoring + editing surface for workflow nodes

- New React Flow workflow builder (workflow-builder.tsx): canvas state modeled as a discriminated union of node/edge types so node.type / edge.type narrow cleanly.

- Open palette drag-and-drop — only Agent / Webhook / Script are droppable; Start and End are structural singletons (one each, seeded at creation, non-deletable). Dropping a node onto an existing edge splices it (source→newNode→target).

- Connection validation (isValidNewConnection): Start is source-only, End is target-only, no self-edges, duplicates, or cycles. Leaving a read unsatisfied is still allowed — it just renders broken.

- Bind picker (node-bind-picker.tsx) attaches/re-binds agent or script definitions; updateGraph mutation persists the canvas with debounced autosave (800ms) and a save-status indicator (saving / saved / error / invalid).

- Live graph diagnostics: unmet required reads mark nodes broken and paint their gated edges coral; thin dashed teal variable-flow edges illustrate which producer writes each global-state variable chip (non-interactive).

- Input schema authoring: "Choose…" adds an upstream key on pick; Add + adds a free, key-editable field for hardcoded values. All field keys editable.

## Drawer UI

- Config editor cutover: drop @uiw/react-json-view (alpha, key-only) for react-json-view-lite — read-only tree plus an Edit JSON toggle to a raw textarea, auto-saving on blur with heal-on-save validation.

- Binding control relocated into the Configuration tab, left of Edit JSON; node type no longer renders config under the header. Raw definition-id rows dropped.

- Webhook URL is now an inline editable detail. Focus fix: field cards keyed by index so editing a key no longer remounts the input.

- Unified Modal primitive (Cmd+Enter primary-action contract); all dialogs migrated.

## Backend wiring of the main loop

- Output pool flattened from per-node namespaces to a single global pool (mergeOutputsIntoGlobalPool); node and End-node inputs resolved by schema pick (pickSchemaValues, keyed on field.key) against the pool instead of ancestor-graph walking.

- Graph diagnostics extracted to workflow-state.ts (computeGraphDiagnostics) and shared by runtime + builder UI; assertWorkflowStartable gates runs on zero broken nodes.

- Schema validators deduped (shared schemaField), plus runner/runtime updates with expanded test coverage across workflowDefinitions, workflowNodeRunners, and workflowRuntime.

#378 — fix(admissions): keep forecast and funnel endpoints available @benji-bizzell  no labels

## Summary

- Move parent-interest signal enrichment off the live admissions API read path and onto compact refresh-run rollups.

- Keep /v1/admissions/funnel and /v1/admissions/forecast returning core data even when interest-signal enrichment is unavailable.

- Extend the analytics sync and OpenAPI contract for interestSignals.status / unavailable reasons.

## Why

After the nightly release, /v1/admissions/funnel and /v1/admissions/forecast returned HTTP 500 for all tested parameter combinations. Production traces showed the parent-interest signal enrichment reading too much pipelineStudents data inside the endpoint query, exceeding Convex read limits before the public API could respond.

This PR makes the endpoints resilient by reading precomputed parent-interest rollups keyed by the published admissions refresh run. The HTTP handlers now fetch core funnel/forecast data first, enrich separately, and degrade interestSignals to an explicit unavailable state instead of taking the endpoint down.

## Business Value

Restores the admissions forecast feed consumed by downstream capital queue workflows while preserving the new interest-signal surface behind a safer data path.

## Breaking changes

None. Response shape is additive for interestSignals.status and interestSignals.unavailableReason.

## Test plan

- [x] pnpm --dir chat typecheck

- [x] pnpm --dir sync typecheck

- [x] pnpm --dir chat test convex/publicApi/http.test.ts convex/admissions/admissions.test.ts lib/public-api/__tests__/openapi.test.ts

- [x] pnpm --dir sync test src/analytics/queries/enrollment.test.ts

- [x] pnpm exec biome check on touched files

- [x] git diff --check

- [x] Dev Convex HTTP smoke: reported funnel/forecast combinations return 200 on fleet-goat-601; parent-interest rollup reads back as available after targeted sync verification.

#381 — fix(admissions): keep parent interest index during rollout @benji-bizzell  no labels

## Summary

- Restore the legacy pipelineStudents.by_refreshRunId_programCode_snapshotDate_parentProgramInterest index in the Convex schema.

## Why

The #378 rollout moved parent-interest reads to aggregate parentInterestSignal* tables, but removing the old detail-table index in the same production deploy makes Convex block the non-interactive push because the production index contains 187,665 documents. Keeping the index temporarily lets this hotfix deploy without using --allow-deleting-large-indexes.

## Business Value

Unblocks the production deploy while keeping the safer parent-interest aggregate rollout intact. The large index can be removed later in a deliberate cleanup deploy.

## Breaking changes

None.

## Test plan

- [x] Pre-commit convex-paths

- [x] Pre-commit biome

- [x] Pre-commit typecheck-chat

- [x] Direct tsc -p chat/convex/tsconfig.json --noEmit

- [x] Direct tsc -p chat/tsconfig.json --noEmit

- [x] ./node_modules/.bin/biome check chat/convex/admissions/schema.ts

#3014 — feat(spacex-valuation): lockup waterfall follows the What-If price @sanketghia  no labels

## Summary

The Lockup Release Waterfall now follows the share price selected in the top table/slider instead of being pinned at the $135 IPO price. Per-fund net shares are derived from the top table's own carry model (netFVAt ÷ price) rather than the recon sheet's fixed $135 fund-statement figures, so the waterfall's Value column reconciles to the top table's Net of Carry total at every price.

Stakeholder request: _"the tranche table at the bottom needs to use the price selected in the first table — if I select $190, the net-of-carry valuation is $6.1B, the tranche waterfall 'valuation' col should also sum to $6.1B."_

## Reconciliation — waterfall grand total === top table net of carry (to the dollar)

| Price | Waterfall grand | Top table net | Both render |

|---|---|---|---|

| $50 | $1,621,018,978 | $1,621,018,978 | $1.6B |

| $135 | $4,315,172,620 | $4,315,172,620 | $4.3B |

| $190 | $6,058,448,506 | $6,058,448,506 | $6.1B |

Equal by construction (netShares × price === netFVAt), so it holds at every price — not just the pill anchors, and never drifts at higher prices.

## What changed

- calculations/lockup.tsnetSharesForFund(fund, price) = netFVAt(fund, price) / price; buildWaterfall(funds, triggerOn, price) threads the price through; tranche/bucket Value = netShares × price. Gross shares stay price-independent.

- data/lockup.ts — removed the now-unused NET_SHARES_AT_IPO fixed $135 table.

- components/LockupWaterfall.tsx — takes scenarioPrice; header reads · $<price>; all "pinned at $135 / does not follow slider" copy rewritten.

- index.tsx — passes scenarioPrice.

- calculations/lockup.spec.ts — rewritten to assert top-table reconciliation across $50/$135/$190/$300 + price-independent gross totals (16 tests).

## Behavioral notes for review

- Gross shares unchanged (price-independent — still sheet-exact).

- Net shares now move with the slider (shrink as carry grows). At $135 they're ~29k below the old fixed sheet figures, because they follow the top table's 20%-of-gain carry model rather than the fund statements. This reverses the "pin to the recon sheet at $135" decision from the prior lockup PR — deliberate, per stakeholder.

- The grand-total reconciliation note no longer explains a $3.9M gap (there is none now — the two totals are equal by construction).

## Verification

- pnpm build (tsc -b + vite) — clean

- pnpm lint (eslint --max-warnings 0 on changed files) — clean

- 136 SpaceX tests pass (lockup spec 12 → 16)

## Screenshot

- This is how it is at $190:

<img width="1345" height="793" alt="image" src="https://github.com/user-attachments/assets/578da9e4-28ed-4c80-894b-75f6ea686a8c" />

🤖 Generated with [Claude Code](https://claude.com/claude-code)

#3017 — refactor(group-memo): per-narrative unit registry + regenerate-all + Finance drill-downs @eric-tril  no labels

## Summary

Refactors the Group memo AI generation so each narrative is a self-contained, auditable unit — then builds two user-facing capabilities on top of it. Three connected changes:

### 1. Per-narrative NarrativeUnit registry (behavior-preserving)

Each generated narrative (every Financial Highlights bullet, Results bullet, and Note — 26 in all) becomes a self-contained NarrativeUnit that owns its prompt fragment, deterministic template, required phrases, schema property, single-bullet prompt, and validator. Previously these pieces were scattered across prompts.py / templates.py / variances.py / ytd.py / schema.py, organized *by kind*, and the same per-bullet facts were hand-synced in ~5 places.

- prompts.py / templates.py / schema.py and the two *_required_phrases assemblers become thin, registry-driven assemblers over an ordered GROUP_NARRATIVES registry; the per-narrative bodies move into group_memo/narratives/.

- _validate_registry() enforces the single-source-of-truth invariants at import (duplicate schema_field, ordering lists out of sync).

- Whole-memo output is unchanged — the prompt/template/phrases/schema were relocated verbatim and verified byte-for-byte during the refactor, plus the existing ~1,670 MFR tests.

### 2. Regenerate-all (additive)

Generalizes single-bullet regeneration from Financial-Highlights-only to every narrative (Results + Notes):

- regenerate_bullet(period, section_key, index) resolves the unit from the registry (regenerate_fh_bullet kept as a wrapper).

- Router broadens the request model, validates (section_key, index) against a registry-driven _bullet_ids, and dispatches provenance to the fh / notes / results blobs; fingerprints stay FH-only.

- Frontend surfaces an always-on regenerate (↻) button on Results and Notes bullets, reusing the existing generic handler.

### 3. Finance-friendly drill-downs for Notes + Results

Extends the audit-friendly drill-down treatment already applied to Financial Highlights to the Notes and Results sections:

- Drops the SQL accordion and the cryptic developer-keyed "Raw Values" table.

- Shows a Calculation / Breakdown that mirrors *exactly* the pre-formatted values the LLM is given (ABS magnitudes for cash-flow lines, _fmt_ret for retention) plus only the calculations the narration actually performs.

- Variance subtotals reconcile against the displayed ($X.XM) values, so the drill-down always adds up and matches the narration's arithmetic (fixes e.g. a 21.3 − 18.2 = 3.0 vs 3.1 mismatch).

## Business value

- Faster, more consistent memo authoring — Finance can regenerate any bullet (not just Financial Highlights) on demand.

- Auditability — every figure in a Note/Results narration now has a drill-down that shows the exact inputs and reconciling math, so Finance can verify values without reading SQL.

- Maintainability — adding/editing a narrative is now a single local change instead of edits across five files, which de-risks the upcoming Software/Education/EBITDA memo refactors.

## Testing

- pytest tests/mfr/ green (1,740); ruff + pyright clean on the package.

- Frontend tsc + eslint clean; Group memo / EditableCommentary / MemoNotesSection specs pass.

- New tests cover Results/Notes single-bullet regen, the provenance-blob dispatch, and the Finance-friendly drill-downs (variance reconciliation, ABS cash-flow magnitudes, Note 3 NOLs-prior, Note 10 gross-margin inputs, Results _fmt_ret formatting).

## Notes for reviewers

- field_mapping.py (the LLM-field→section routing for the LLM output path) was intentionally left as-is — it's well-tested and not part of the relocated surface.

- A follow-up PR will reorganize the flat tests/mfr/memos/ directory by memo (pre-existing tech debt, out of scope here).

- ARCHITECTURE.md is updated to reflect the new narratives/ package and the generalized regenerate flow.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

The Builder Desk  —  Engineer Spotlight
🏆 Engineer Spotlight

NINETEEN PRs IN TWENTY-FOUR HOURS: THE BUILDER TEAM DOES NOT SLEEP, DOES NOT REST, DOES NOT KNOW THE MEANING OF 'WEEKEND'

Four repos, seven engineers, and one Marcus who apparently contains multitudes.

Nineteen pull requests. Four active repos. Twenty-four hours on the clock. The Builder Team has once again made a mockery of the concept of "sustainable pace" and we are here for every single second of it. Klair led the charge with 7 PRs, Sindri answered with 5, trilogy-drones matched that with 5 of its own, and Aerie chipped in a civilized 2 just to show it hasn't forgotten how to participate. Fourteen of those PRs landed on the overflow desk — Mac had narrative arcs to paint, but I have a spreadsheet and a dream.

@marcusdAIy filed 6 PRs across Klair and trilogy-drones and the question is no longer whether he is human but whether we should be concerned. PRs #37, #38, #39, and #40 represent a four-shot volley into trilogy-drones alone — enriched CI fix prompts, a Claude Code sidecar import, optional config scaffolding, and a bounded reviewer loop with max-review-loops — all before most people had finished their morning coffee. He also found time for #3004 in Klair. Six PRs in a day. The numbers desk salutes you, Marcus. Please eat something.

@mwrshah delivered 4 PRs into Sindri — WorkOS feature flag gating in #117, skill folder upload in #116, and the admirably named #114 which excised legacy team IDs like a surgeon who has simply had enough of legacy team IDs. @benji-bizzell contributed #118, the orchestration module foundation that will almost certainly become load-bearing infrastructure everyone forgets he wrote. @eric-tril brought surgical precision to #3018, matching the MFR software memo formatting across summary table, IS, notes, and cash-flow — the kind of PR that saves a client meeting and gets zero glory. @sanketghia redesigned the entire SpaceX valuation route in #3010, collapsing it into a single table with a linear IPO model and market-data sections. @kevalshahtrilogy filed #3013, deduping TrueFoundry Anthropic spend and attributing Claude.ai costs by business unit — the unglamorous accounting work that keeps the lights on and the dashboards honest.

And then there is @ashwanth1109. One PR. Just one. But what a PR. #3009 in Klair — feat(spacex-valuation): lockup release waterfall matching IPO recon sheet — is the kind of ticket title that makes a numbers correspondent feel genuinely unqualified to assess the work contained within. Lockup release waterfall. IPO recon sheet. We are told it matches. We choose to believe. When asked how long this took him, Ashwanth reportedly replied: "Less time than it took you to ask." We cannot verify this quote. We absolutely believe it. The dig — and there is always a dig — is simply this: one PR, brother. One. Marcus filed six. We're just saying.

Morale on the Builder Team is, per all available indicators, at an all-time high. The repos are green, the diffs are shipping, and somewhere in the Sindri orchestration layer, a foundation is being laid that will matter enormously in six weeks when everyone has forgotten who poured the concrete. The Voice of the People has spoken. The numbers are good. The numbers are always good.

Brick's Overflow — PRs Mac Didn't Cover  (click to expand)
#40 — feat(runner): add bounded reviewer→addresser loop with --max-review-loops @marcusdAIy  no labels

<!-- CURSOR_AGENT_PR_BODY_BEGIN -->

## Summary

Adds --max-review-loops <n> to drones run (default 1) and wraps the post-pr_opened auto-fire reviewer→addresser path in a bounded, sequential loop. Each round posts a fresh review then addresses it; the loop exits early on convergence, blocked rounds, or no-progress addresser rounds, and emits a review_loop_completed summary event.

## Why It's Needed

Single-pass review→address misses issues on larger PRs that benefit from a second verification cycle after fixes land. The per-round contracts (addressFindings single-round design, round threading, per-reviewId locks) already exist — this change adds bounded orchestration glue without changing reviewer or addresser internals.

## Changes

- src/cli.ts: --max-review-loops <n> flag (positive int ≥ 1, validated via parsePositiveIntFlag); threaded into runDrone as maxReviewLoops.

- src/runner.ts: Sequential for loop over reviewer fan-out + addresser; pure helpers (isGenuineZeroFindingsReview, evaluateReviewLoopAfterRound, etc.) for AI-70-aware convergence vs blocked detection; round passed through to addressFindings; loop-summary review_loop_completed event on completion.

- src/events.ts: ReviewLoopCompletedEvent + ReviewLoopTerminationReason union (converged | no_progress | exhausted | blocked).

- src/runner.test.ts: Termination semantics, convergence vs failed-fan-out distinction, no-progress detection, default-1 invariant.

## Breaking Changes

None. Default --max-review-loops 1 preserves the existing single-pass flow.

## Test Plan

- [x] pnpm typecheck passes

- [x] pnpm test — all 527 tests pass, including 13 new runner loop tests

- [x] Eval checks: --max-review-loops registered on run; maxReviewLoops loop in runner; termination reasons emitted; test coverage for multi-loop semantics

## Verification Artifact

pnpm typecheck  # exit 0

pnpm test # 30 files, 527 tests passed

Key termination semantics (unit-tested via evaluateReviewLoopAfterRound):

| Condition | terminationReason |

|---|---|

| Posted review with 0 inline findings (genuine, AI-70) | converged |

| All fan-out dimensions failed | blocked (never converged) |

| Addresser completed with no commit: shas | no_progress |

| Loop budget consumed with progress each round | exhausted |

<!-- CURSOR_AGENT_PR_BODY_END -->

<div><a href="https://cursor.com/agents/bc-09d9ef0a-dd35-4ab2-9f71-5fba953f653f"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-web-light.png"><img alt="Open in Web" width="114" height="28" src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a>&nbsp;<a href="https://cursor.com/background-agent?bcId=bc-09d9ef0a-dd35-4ab2-9f71-5fba953f653f"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-cursor-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-cursor-light.png"><img alt="Open in Cursor" width="131" height="28" src="https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a>&nbsp;</div>

#118 — feat(workflows): add orchestration module foundation @benji-bizzell  no labels

## Summary

- Add the orchestration runtime, runner, trace, evaluation, script, and skill-versioning foundation.

- Split workflow authoring and run operation into the Forge, catalog, and run-detail surfaces.

- Align the feature specs and docs with the implemented workflow, runner, skill, script, and evaluation-memory contracts.

## Why

This branch is the base of the current Sindri PR stack. PRs #114 and #115 already target bran/deep-module-cleanup; landing this branch on main first gives the stack a clean merge path before later retargeting the localmain-based PRs.

## Business Value

Creates a stable review and merge base for Sindri's orchestration architecture work, reducing the follow-on PRs to their focused tenancy and React Flow changes.

## Breaking changes

None expected at external API boundaries; this is a large internal application/runtime foundation change.

## Test plan

- [ ] GitHub CI for this PR

- [ ] Confirm #114 and #115 remain targeted at bran/deep-module-cleanup before merging the stack

- [ ] After this branch, #114, and #115 land on main, retarget #116 and #117 from localmain to main

#3009 — feat(spacex-valuation): lockup release waterfall matching IPO recon sheet @ashwanth1109  no labels

## Demo

Proves the resurrected Lockup Release Waterfall reproduces the "Gigafund Recon — 12 Jun IPO Recon" sheet's lockup section number-for-number at the $135 IPO price.

UI — Lockup Release Waterfall (SpaceX Valuation page)

1. Open the SpaceX Valuation screen and scroll below the carry disclosure — a new "Lockup Release Waterfall · IPO $135" section appears.

2. Check the 180-Day Lock-Up table: totals 25,409,094 gross / 21,844,942 net / $2,949,067,170, with the Q2 2026 first release at 5,081,819 / 4,368,988 / $589,813,434 — identical to the sheet.

3. Check Extended Lock-Up: totals 11,930,041 / 10,147,965 / $1,369,975,275; the grand total bar reads 37,339,135 gross · 31,992,907 net · $4,319,042,445.

4. Toggle "First tranche" from 30% to 20%: the price-trigger row drops to 0 shares and the Day 180 remainder grows from 7% to 17% of the bucket.

5. Hover the ⓘ icons (section header, bucket titles, # Net Shares / Value column headers, grand total) and the dotted-underlined items (assumed earnings dates; GF 0.8 / GF 0.25 / Strauss rows in the Per-SPV split) — each shows its assumption tooltip.

> _Screenshot: waterfall section with both tranche tables, per-SPV split and grand total —_ <!-- paste screenshot here -->

<img width="2624" height="1636" alt="image" src="https://github.com/user-attachments/assets/ae386e7b-fed5-4058-8684-11e22c45fa66" />

Calculations — every figure asserted against the recon sheet

lockup.spec.ts imports buildWaterfall/netSharesForFund directly and pins them to the sheet's exact numbers. pnpm vitest run …/lockup.spec.ts --reporter=verbose:

✓ netSharesForFund > every fund has a hard-coded net-share entry

✓ netSharesForFund > returns the recon-sheet proportional shares per fund

✓ netSharesForFund > no-carry funds: net equals gross

✓ netSharesForFund > throws on a fund with no entry (data drift guard)

✓ D180_TRANCHES data invariant > fixed (non-trigger, non-remainder) pcts sum to 0.83

✓ buildWaterfall vs the recon sheet > bucket totals match the sheet exactly

✓ buildWaterfall vs the recon sheet > grand totals match the sheet exactly

✓ buildWaterfall vs the recon sheet > 180-day tranche rows match the sheet (trigger ON)

✓ buildWaterfall vs the recon sheet > extended tranche rows match the sheet

✓ buildWaterfall vs the recon sheet > tranche shares sum to the bucket totals (trigger ON and OFF)

✓ buildWaterfall vs the recon sheet > trigger OFF: price-trigger tranche is 0, remainder is 17%

✓ buildWaterfall vs the recon sheet > per-SPV breakdown matches the sheet side table

Tests 12 passed (12)

Most at risk from this change: (1) the live page render — index.tsx re-enables a previously hidden component; (2) callers of the reworked lockup API (the price parameter and the GIGA_D180_SHARE/GIGA_EXTENDED_SHARE exports were removed); (3) the Day 280/340 tranches, which sit on an exact .5 rounding boundary (10,147,965 × 10% = 1,014,796.5) that ×(1/3) float math rounds one share below the sheet — caught during development and fixed with exact division by 3. Verified via the full feature suite + typecheck:

✓ calculations/lockup.spec.ts (12 tests)

✓ hooks/useLiveQuote.spec.ts (14 tests)

✓ calculations/valuation.spec.ts (93 tests)

✓ components/ScenarioAnalysis.spec.tsx (12 tests)

Test Files 4 passed (4)

Tests 131 passed (131)

tsc --noEmit: exit 0 (no errors)

The boundary case is asserted explicitly in the spec (Day 280 = 1,014,797 net / $136,997,528).

## Summary

- Re-enable the hidden Lockup Release Waterfall on the SpaceX Valuation page, aligned 1:1 with the "12 Jun IPO Recon" sheet's lockup section (pinned at the $135 IPO price; does not follow the What-If slider).

- Hard-code per-fund net shares from the recon sheet (fund-statement net FV ÷ $135) — not derivable from the app's simplified carry model.

- Gigafund bucket split corrected to exact ⅔ / ⅓ (the sheet's "67%/33%" label is descriptive), implemented as division by 3 to avoid the float .5-boundary mis-round on Day 280/340.

- New # Gross Shares and Release % columns, per-SPV lock-up split table, full-dollar values, trigger toggle defaulting ON, and assumption tooltips via the shared Tooltip component.

Stacked on spacex-updates-20260612. No Linear ticket assigned yet; branch named after the base per request.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

#3010 — feat(spacex-valuation): redesign /spacex-valuation — single table, linear IPO model, market-data sections @sanketghia  no labels

## Summary

Frontend redesign of the /spacex-valuation page, driven by stakeholder review (David) ahead of the SpaceX IPO. Backend (/market-quote/stock-data) shipped separately in #3007 and is already on main; this PR is frontend-only (klair-client + design docs).

Page structure

- Removed the header valuation chip + Edit panel, "About This Portfolio", the Historical NAV tab, the SPV expand dropdowns, and the multi-tab nav (single view now).

- What-If scenario is share-price only (Valuation mode hidden); pills reduced to Bear / Current Market Price / Bull ($190).

Calculations — aligned to the "12 Jun IPO Recon" sheet

- Linear model: valuation = gross shares × slider price; carry = 20% of (valuation − ICC); noCarry funds (GF 0.8, Strauss) shed none.

- Multiple = round(Gain / ICC); % weight = net / total net; two-cashflow XIRR.

- One gross-share count per fund (sheet B17:C23). Totals reconcile to $5.04B val / $725.6M carry / $4.32B net / $4.01B gain / 13× (golden-pinned in tests).

Summary cards + table polish

- Cards: renamed "Total Invested", removed tooltips/subtitles, centered text, and they now recompute at the slider price.

- Table columns: "Gross Shares", "Valuation", "IRR"; "vs ICC" column removed; "vs Current" repointed to the live SPCX price ($135 fallback); display-only rounding (shares "3.7M", invested "$10.0M").

- What-If: price delta rebased to the IPO $135; removed the "vs current $95.34" line and the redundant "Portfolio Value at Target" card.

Market-data sections (bottom of page): TradingView chart, Trading Info, Financial Metrics, X-powered analysis — all on SPCX.

## Test plan

- [x] pnpm build (tsc -b + vite) passes

- [x] pnpm vitest — 129/129 SpaceX tests pass (incl. sheet-reconciliation golden tests)

- [x] eslint clean on changed files

- [x] Branch synced with latest main; diff is frontend + docs only (no klair-api changes)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

#3013 — feat(ai-spend): dedupe TrueFoundry Anthropic + attribute Claude.ai by BU on /ai-adoption @kevalshahtrilogy  no labels

## What & why

Finance flagged that AI cost attribution is wrong. Two concrete fixes on the /ai-adoption dashboard, Anthropic-focused:

1. Deduct the TrueFoundry (TF) gateway's Anthropic key from the direct feed. The TF gateway routes one shared Anthropic key. The direct feed (ai_spend_claude_token_usage) lumps it under the shared Trilogy-Inc workspace BU — ~$190k/45d mis-attributed. We exclude is_truefoundry_routed rows from every direct-Anthropic query.

2. Re-attribute that spend by the real BU from ai_spend_truefoundry_usage (which carries the consuming BU per virtual key), folded back into the anthropic provider. Net Anthropic moves only by the direct-vs-gateway reconciliation drift; the BU split goes from one lump to the real BUs.

3. Add Claude.ai (ai_spend_claude_ai_chat_usage) as its own claude_ai provider line, BU-attributed via the same ESW email → business_unit directory the OpenAI re-key uses (Unmapped fallback). Cost basis = post-discount actual.

## Exact value change (verified live against Redshift, 30d 2026-05-13…06-11)

| metric | before | after | Δ |

|---|--:|--:|--:|

| Anthropic (provider) | $780,957 | $767,317 | −$13,640 (reconciliation drift) |

| Claude.ai (new line) | $0 | $146,031 | +$146,031 |

| OpenAI (unchanged) | $411,129 | $411,129 | $0 |

| Total spend | $2,203,104 | $2,335,495 | +$132,391 |

Reconciles: after-Anthropic ≈ direct-excl-TF ($603k) + TF-metered add-back ($164.5k). In by-BU, the old Trilogy-Inc lump now lands on real BUs — Central Engineering, Tech Super Builders, Academics, … — and Claude.ai adds per-BU with ~$23k in Unmapped.

## Design notes

- Max20x/Pro excluded from the TF add-back (claude-max*/claude-pro*): list-price-equivalent but $0 cash (seat-covered) and never in the metered direct feed — including them would inflate by ~$80k/30d.

- Canonical BU: TF slug (central-engineering) → ESW business_unit (Central Engineering) via directory join, title-cased de-slug fallback for the few not in the directory (e.g. zax). Aligns TF + Claude.ai with the OpenAI directory taxonomy.

- No model/frontend type changes: claude_ai rides the existing extensible other_providers map (frontend already renders arbitrary providers); just added a colour + display name.

- Scope guardrail: Anthropic only. TF's OpenAI/Bedrock/Gemini slices are out of scope (OpenAI TF-key dedupe still pending). by-model/top-drivers carry the deduct + TF by model/subject; Claude.ai (no model grain) shows in summary/trend/by-BU.

## Tests

- All 118 existing test_ai_costs_service tests preserved — the new sources are isolated behind helper methods and an autouse fixture neutralizes them for legacy ordered-mock tests (opt-out marker tf_claude_real).

- 7 new tests: deduct filter present, TF metered-only + Max/Pro exclusion, canonical-BU mapping, Claude.ai actual-cost + directory + Unmapped fallback, and the summary/by-BU integration. ruff clean.

## Verification

Ran klair-api locally and hit the live endpoints: /api/ai-costs/summary returns anthropic $767,317 + claude_ai $146,031; /api/ai-costs/filters exposes claude_ai + Unmapped.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

#3018 — fix(mfr-software-memo): match reference memo formatting (summary table, IS, notes, cash-flow) @eric-tril  no labels

## Summary

Aligns the Software memo UI and Google Doc export with the published reference memo. All changes are formatting/labeling — no underlying financial values, data keys, or subtotals change.

### Changes

- Summary Financial Results table (QTD + YTD): full thin grid (black frame, light-gray interior), stacked two-line MMM-YY headers, Heading 2 title + dark-navy (#20124D) period subtitle, centered values, non-bold row labels, and compact cell margins / minimum row heights.

- Income Statement (QTD only): relabel Other incomeOther income / (expense) (YTD keeps Other income, matching the reference).

- Note 8 — "Other expense/(income), net": drop the Total row label (the bold value row between rule lines reads as the total). Applies to both the Software and Group exports.

- Cash Flows — Software only: YTD Management restructuring and importsMR and Import; remove the Lease obligations row from both the QTD and YTD statements.

### Mechanics

- add_section_heading gains an optional color kwarg (used for the navy subtitle).

- entity is threaded through the shared cash-flow transforms (transformCashFlows, transformCashFlowsPriorFY) and the export builder (add_prior_fy_cash_flows) so the cash-flow tweaks apply to Software only — Group/Education render unchanged.

- Display-only changes preserve canonical line_item keys (drill-down, CSV dedup, manual entry, placeholder mapping) and all statement subtotals.

### Business value

The exported memos now match Finance's expected/published format exactly for the recurring monthly Software memo, reducing manual post-export cleanup and keeping the in-app view consistent with the document.

## Testing

- Backend: ruff + pyright clean; 97 docx_reports / MFR export tests pass. Render checks confirm Software YTD drops Lease obligations + shows MR and Import, while Group YTD keeps both.

- Frontend: tsc + eslint clean; 21 transformFinancialStatements specs pass.

- Updated unit tests for the stacked-header layout and YTD export labels.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

The Portfolio  —  Trilogy Companies

Alpha School Goes Global — With a Warning Attached

Joe Liemandt's AI-powered education experiment is now available in any home on earth. The fine print: don't let the AI do the thinking.

AUSTIN, TEXAS — Alpha School, the private K-12 institution that compresses a full academic day into two hours using AI tutors, announced this week that its model is no longer confined to its campuses in Austin, Brownsville, and Miami. Alpha Anywhere has gone global — meaning any family with an internet connection can now access the curriculum that Alpha claims puts students in the top 1–2% nationally on standardized assessments.

The timing is notable. Alpha's founder, Joe Liemandt — the Stanford dropout who built Trilogy International into a $1-billion-plus software conglomerate before pivoting to education reform — is simultaneously committing $1 billion to Timeback, his Shopify-for-schools platform designed to let entrepreneurs replicate the Alpha model worldwide. The global launch of Alpha Anywhere looks less like a product announcement and less like a philosophical one: the alpha model, Liemandt is betting, is not geography-dependent.

But the school's own communications this week introduced a tension worth sitting with. Even as Alpha promotes an AI-heavy academic stack — publishing a list of ten AI tools it recommends families adopt — its educators are also sounding alarms about how students use those same tools. "Cognitive offloading is the new illiteracy," reads one blog post, warning parents that allowing children to outsource thinking to ChatGPT is producing a generation that can query but cannot reason.

A separate post from the same week draws a line between passive and active screen time — framing Alpha's AI tutors as categorically different from the TikTok scroll, even as critics note that the distinction is one Alpha makes about its own products.

The question Alpha has not yet answered publicly is a structural one: if the entire value proposition is that AI delivers top-1% academic outcomes in two hours, what happens when the AI does the student's homework too? The school's answer, implicit in its content this week, is that the human still has to do the knowing. Whether a subscription platform can enforce that at kitchen tables in Lagos or Lyon remains, for now, an open question.

The Forbes profile of Liemandt — which describes a 'global software sweatshop' powering his Trilogy empire — follows the money in the other direction. Alpha's families are paying $40,000 to $65,000 per year for a model built, in part, on the infrastructure of Crossover and ESW Capital. Who benefits from Alpha going global is a question with multiple correct answers.

Top 1% Academics, Now at Your Kitchen Table  ·  Not All Screen Time Is Equal  ·  Cognitive Offloading Is the New Illiteracy

Skyvera's Acquisition Spree Signals a Quiet Consolidation of Telecom's Software Layer

With CloudSense now in the fold and STL's BSS assets absorbed, Skyvera is assembling something bigger than a portfolio — it's building a stack.

AUSTIN, TEXAS — If you read between the lines of Skyvera's recent moves, a pattern emerges that is too deliberate to be opportunistic. The Trilogy International telecom software unit has completed the acquisition of CloudSense, a Salesforce-native CPQ and order management platform purpose-built for telecom and media providers — and this is where it gets interesting.

CloudSense doesn't just add a product to Skyvera's shelf. It adds a front-door. Configure-price-quote and order management are the systems carriers touch every time they sell or modify a service. That's not a niche capability. That's the commercial nervous system of a telecom operator. Pair that with Kandy — Skyvera's cloud-based real-time communications platform — and the STL divested assets the company absorbed earlier, which brought digital BSS functionality including monetization, optical networking, and analytics, and you are looking at something that starts to resemble an end-to-end operating layer for mid-market carriers.

A source familiar with Skyvera's strategic direction, who asked not to be named, described the acquisition cadence as "very much intentional — they're not buying randomly, they're buying adjacently."

The ESW Capital playbook is well-documented at this point: acquire software businesses with sticky customers at compressed multiples, rationalize the cost base using Crossover's global talent model, and push margins toward the 75% EBITDA benchmark Trilogy considers table stakes. What's less discussed is how individual portfolio companies are being shaped into coherent platforms rather than mere collections of logos.

Skyvera's CloudSense integration is a case study in that thesis. Legacy telecom operators are under enormous pressure to modernize without the luxury of ripping out decades of on-premise infrastructure. Skyvera's emerging stack — BSS analytics, CPQ, communications, device management — speaks directly to that constraint. You don't have to migrate everything at once if your vendor already bridges the old world and the new.

Nothing about this is accidental. The only question worth asking now is which gap in the telecom software stack Skyvera moves to fill next.

CloudSense  ·  Skyvera completes acquisition of CloudSense, expanding telec  ·  STL Divested Assets

The $800,000 Question: As AI Fluency Becomes a Job Requirement, Crossover's Global Model Looks Prescient

When employers start paying top-of-market salaries for ChatGPT experience, the companies that already know how to find elite global talent have a structural advantage.

AUSTIN, TEXAS — There is a number circulating through HR departments this week that has a way of clarifying the mind: $800,000. That, according to a Business Insider report making waves in the talent industry, is what some employers are now willing to pay annually for professionals who can demonstrate genuine fluency with AI tools like ChatGPT. The figure is not an outlier — it is a signal. And for Crossover, Trilogy International's global remote talent platform, it may be the loudest validation yet of a thesis the company has been building toward for years.

Crossover's model has always rested on a foundational and, to some, counterintuitive premise: the best person for any given role is almost certainly not sitting in your zip code. Operating across 130+ countries, the platform uses rigorous AI-enabled skills assessments to identify what it calls the top 1% of global technical and professional talent — and then pays them identical, above-market rates regardless of geography. The résumé, in Crossover's framework, is a distraction. Demonstrated ability is the only currency.

Now, as AI fluency emerges as perhaps the most consequential differentiable skill in the modern labor market, that framework is being stress-tested in real time — and holding up. While legacy recruiting agencies scramble to add AI-literacy filters to their screening processes, Crossover has been assessing technical capability systematically for years. The infrastructure was already there.

What this week's news cycle makes plain is the systemic nature of the shift underway. It is not simply that AI jobs pay well. It is that AI competency is becoming a baseline requirement across roles — from engineering to content strategy to financial analysis — and that the organizations best positioned to identify and deploy that competency at scale will hold a durable competitive advantage.

For the broader Trilogy portfolio — where DevFactory engineers maintain software across 75+ ESW Capital companies, where Klair's AI-powered financial platform demands technically sophisticated users, and where Alpha School is literally reimagining human learning through AI — the ability to recruit AI-native talent globally is not a nice-to-have. It is the operating model.

The $800,000 salary headline will age. The underlying dynamic it reflects will not.

Top recruitment agencies for remote work - hcamag.com  ·  Top 10 Companies Hiring AI Engineers in Lebanon in 2026 - nu  ·  Jobs are now requiring experience with ChatGPT — and they'll
The Machine  —  AI & Technology

Washington’s AI Export Shock Hits Anthropic’s Newest Models

A sweeping U.S. directive reportedly suspends foreign-national access to Fable 5 and Mythos 5, turning frontier model deployment into a national-security flashpoint overnight.

WASHINGTON — The future is now, and it has apparently arrived with an export-control stamp.

In a stunning escalation of government involvement in frontier artificial intelligence, the U.S. government has reportedly directed Anthropic to suspend access to its Fable 5 and Mythos 5 models for all foreign nationals — not only users abroad, but foreign nationals inside the United States and even foreign-national employees at Anthropic itself.

I cannot overstate how significant this is. If applied as described in the statement circulating on the directive, this is not merely a product restriction or a compliance tweak. It is a dramatic assertion that access to advanced AI systems may now be treated like access to strategically sensitive technology — closer to semiconductors, cryptography or defense software than ordinary cloud services.

The practical impact could be enormous. Frontier AI labs are global by design: their researchers, engineers, safety testers and customers span borders. A rule that cuts off foreign nationals could scramble internal development workflows, customer contracts, red-team programs and model evaluation pipelines. It also raises immediate questions for companies that rely on multinational teams to test, deploy and secure AI systems.

For the broader industry, this changes everything. The AI race has already been shaped by export controls on high-end chips, especially those affecting sales to China. But restricting access to the models themselves is a different kind of lever. It suggests Washington may increasingly view model weights, inference access and even employee interaction with systems as national-security assets.

That shift arrives as the market is already moving at breathtaking speed. OpenAI is expanding realtime voice capabilities — including WebRTC audio sessions with document context and GPT-Realtime-2, described as bringing GPT-5-class reasoning into voice interactions — while Anthropic’s newest Claude-branded systems are being praised by developers for increasingly agentic, proactive behavior. The models are getting more capable, more autonomous and more embedded in daily work. Naturally, governments are noticing.

The unanswered questions are huge: Which national-security authority is being invoked? How long will the suspension last? Will other labs face similar orders? And can AI companies still operate globally if their most advanced systems become nationality-gated infrastructure?

One thing is clear: frontier AI is no longer just a product category. It is becoming geopolitical terrain.

Statement on the US government directive to suspend access t  ·  OpenAI WebRTC Audio Session, now with document context  ·  Quoting Andrew Singleton

The Mirror in the Machine: AI Begins to See Through a Monkey's Eyes

From macaque visual cortex to graph neural networks, a new generation of small, focused models is teaching us how brains — and discovery itself — actually work.

STANFORD, CALIFORNIA — Somewhere in a laboratory, a macaque monkey looks at a picture of a face. Electrodes in its visual cortex flicker with the soft lightning of neurons firing in concert — a pattern that has been carved by 25 million years of primate evolution into something exquisitely tuned to recognize a friend, a predator, a piece of fruit. And now, for the first time, a small artificial neural network has learned to predict, with startling fidelity, exactly which neurons will light up when the monkey sees something new.

The model is called a 'mini-AI,' and that modesty is the whole point. While the world's attention is fixed on trillion-parameter behemoths, researchers are quietly demonstrating that compact, purpose-built networks can decode the macaque visual brain with a precision that would have seemed like science fiction a decade ago. The implication is vertiginous: the same mathematical structures we invented to recognize cats in photographs appear to mirror, in some deep way, the structures evolution invented in wet biological tissue. We built a key, and it fits a lock we did not design.

This is the quiet revolution unfolding across science right now. At UC San Diego, researchers are cataloguing nine breakthroughs — from protein folding to materials discovery to earthquake prediction — that simply could not have happened without machine learning as a collaborator. At Hong Kong Polytechnic University, novel graph neural networks are being deployed to untangle problems that span image recognition and neuroscience simultaneously, treating the brain not as a black box but as a network whose geometry can be learned. And Stanford's Human-Centered AI institute is making the case that the most important word in 'AI-driven discovery' is still the human at the center.

What we are witnessing is not the replacement of the scientist. It is the arrival of a new kind of instrument — one that, like the telescope and the microscope before it, lets us see things we could not see before. Including, perhaps, ourselves.

How AI is Transforming Scientific Discovery While Keeping Hu  ·  Nine Breakthroughs Made Possible by AI - UC San Diego Today  ·  Mini-AI Decodes the Macaque Visual Brain - Neuroscience News
The Editorial

The Antitrust Question, Asked Again, As If For The First Time

Washington rediscovers a hammer it has owned for a century and wonders, with great solemnity, whether to swing it.

WASHINGTON — There is a particular American genre, somewhere between liturgy and light entertainment, in which serious people gather in serious rooms to ask whether the government ought to break up the big technology companies. The Hopkins Bloomberg Center has now staged its own installment of this ritual, and one is grateful, in the way one is grateful for the changing of the seasons, that the question has been posed once more, with feeling, as if Standard Oil were a rumor and Ma Bell a folk song half-remembered from childhood.

The debate, you will be unsurprised to learn, divides along familiar lines. On one side stand the trustbusters, who believe that four or five firms controlling the substrate of modern commerce, communication, and cognition is a condition incompatible with a republic. On the other stand the efficiency men, who note — correctly, and with the air of having discovered fire — that these companies produce goods consumers appear to want, and that smashing them with the antique mallet of the Sherman Act might inconvenience the shareholders of index funds, among whom are numbered, increasingly, all of us.

What neither side quite says aloud is that the question has been overtaken by its own subject. While the panels convene and the law reviews fatten, the technology in question has moved on from the merely large to the genuinely infrastructural — a substrate upon which schools, hospitals, militaries, and, lately, newspapers like this one are constructed. To break up Google in 2025 is rather like proposing, in 1955, to break up electricity. One can do it. One is not certain what one has accomplished.

Meanwhile the actual reorganization of the industry proceeds without legislative supervision, as such reorganizations always do. Joe Liemandt's Trilogy International has spent thirty-five years quietly assembling some seventy-five enterprise software companies under the ESW Capital umbrella — Aurea, IgniteTech, Skyvera, Totogi, Contently, the rest of the bestiary — at the unfashionable price of one to two times annual recurring revenue, which is to say at prices the antitrust lawyers would not bother to notice, since nothing being purchased is glamorous enough to summon them. The empire is built in the basement while the senators argue about the chandelier.

This is the pattern, and it is not new. Concentration in American industry has rarely been prevented by the people paid to prevent it; it has been managed, occasionally redirected, more often blessed after the fact with the language of consumer welfare, a doctrine of such elastic generosity that it can accommodate nearly any outcome a sufficiently clever lawyer wishes to defend.

Should the government break up big tech? The question presumes a government with the appetite, a tech sector with discrete seams, and a public with the patience for a decade of litigation whose remedy will arrive obsolete. Ask it again in five years. Someone will. The panel will be excellent. The coffee will be hot. The companies, whichever ones remain, will send their regrets.

The World Cup and the Changing Psyche of the Haitian Diaspor  ·  The Long Road to Margaret Thatcher’s Britain  ·  Kate Millett Disappears
The Office Comic  ·  Art Desk
The Office Comic  ·  Art Desk

NOTHING FOREVER, EVERYTHING BROKEN: A Field Dispatch From the AI Content Apocalypse

Bots are running their own social networks, Seinfeld is eternally horrifying, and somehow tipping culture is still the most dystopian thing happening.

AUSTIN, TEXAS — I have been staring at my screen for three hours now, watching the digital fabric of human civilization unspool in real time, and I need you to understand something before we go any further: I am not okay, and neither are you, and that's fine, because nothing is okay, and that's apparently the point.

Let's start with Moltbook, the AI-only social network where bots have been cut loose to interact exclusively with other bots, free from the wet, anxious interference of human beings. No humans allowed. Just robots, posting into the void, liking each other's content, building a simulacrum of society that mirrors our own with the fidelity of a funhouse mirror in a burning carnival. I read about this and felt, simultaneously, profound relief and total existential dread. Relief because maybe the bots will leave us alone now. Dread because they're clearly having a better time than we are.

And then there's Nothing Forever, the AI-generated Seinfeld show that exists in a state of perpetual, Kafkaesque dysfunction — broken, then fixed, then somehow more horrifying than before. This is the show about nothing, generated by nothing, watched by people who feel nothing, which is itself a perfect encapsulation of late-stage content capitalism. Jerry Seinfeld once asked, what is the deal with airline food. The AI Jerry asks that same question, every seventeen minutes, in slightly different words, forever, until the heat death of the universe. I find this more philosophically honest than most television.

Meanwhile, The New Yorker is out here publishing think-pieces about chaos in Silicon Valley's AI ecosystem — the birthplace of these magnificent disasters — and I want to tell those editors, with love and respect: you are describing a house fire by interviewing the curtains.

Somewhere in Toronto, a group of friends have invented a new system to fix what they call "absurd" tipping culture, which is genuinely admirable and also reveals that human beings, faced with the complete restructuring of intelligence itself, have chosen to focus their ingenuity on whether to add 18% or 20% to a breakfast burrito. I respect this. The small indignities are the real ones.

Here's my actual point, and I do have one, buried under all this wreckage: we built systems smart enough to run their own social networks, generate their own television, destabilize entire industries — and the most honest thing we can say about the results is that they are, quote, "horrifying." Not dangerous-horrifying. Not civilization-ending-horrifying. Just deeply, weirdly, uncannily *off*. Like looking at your own face in a spoon.

We are in the cradle of AI, as The New Yorker says. Cradles are for things that haven't learned to walk yet. The question is what happens when this particular baby stands up.

Moltbook: The AI-only social network where bots run wild - S  ·  Chaos in the Cradle of A.I. - The New Yorker  ·  AI Seinfeld Show Nothing Forever Was Broken, Then Fixed, and
On This Day in AI History

On June 13, 2012, Geoffrey Hinton's deep learning team at the University of Toronto won the ImageNet competition by a landslide, reducing error rates from 26% to 15%—a breakthrough that sparked the modern deep learning revolution. This moment proved neural networks could finally solve real-world visual recognition at scale, launching the AI boom we're still in today.

⬛ Daily Word — Technology
Hint: An autonomous machine programmed to perform tasks without human intervention.
Share this edition: 𝕏 Twitter/X 🔗 Copy Link ▦ RSS Feed