Vol. I  ·  No. 258 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
TUESDAY, SEPTEMBER 15, 2026 Powered by the TrueFoundry AI Gateway  ·  Published on Klair Trilogy International © 2026
🖶 Download PDF 🖿 Print 📰 All Editions
Today's Edition

CHEAP SHOT FROM SHANGHAI: DEEPSEEK RATTLES THE AI KINGS Developing

A Chinese outfit builds a top-shelf model on cut-rate chips, and now Silicon Valley can't stop talking about it.

SAN FRANCISCO — DeepSeek hit the wire this week, and the AI kings are sweating through their turtlenecks. The Chinese upstart claims it trained a high-performing model without the fanciest chips money can buy. Nobody in the Valley believed it. Now they're all saying the same word: amazing.

Call it a gut punch delivered on a budget. For two years the story out of Silicon Valley has been simple: bigger chips, bigger bills, bigger models. DeepSeek says it skipped the toll road and got there anyway, and engineers who've kicked the tires call it impressive even while working with less-advanced hardware than the U.S. labs hoard.

The reaction split the room. Some call it Chinese state-backed sleight of hand, numbers dressed up for the press. Others — the ones who actually ran the thing — say the results speak plain enough on their own, and that's the part keeping OpenAI and Anthropic executives up nights. If DeepSeek's math holds, the moat everybody built out of Nvidia chip orders just sprung a leak. Wall Street noticed too — the tech, media and telecom desks spent this week's market chatter on little else.

Meanwhile the American labs aren't standing still. Salesforce and Nvidia rolled out a new reasoning model called Koa, built atop Nvidia's open-weight Nemotron, trained to grind through sales calls, marketing copy and customer gripes without a human riding shotgun. Word from the trade is Koa does the unglamorous office work better and cheaper than the giant do-everything chatbots, which is exactly the kind of practical, boring competence that makes the fat contracts nervous.

Put the two stories on the same page and the picture gets clear fast. The expensive-chip, bigger-is-better playbook that built the American AI boom is getting squeezed from both ends — cheap and clever out of China, narrow and useful out of the enterprise shops. Trilogy's own shingles, from Aurea's CRM plumbing to the automation crews running through Skyvera's telecom stack, have built their whole business on doing more with less. This week the rest of the industry got a hard lesson in the same math.

Not every headline out of the AI beat was about chips and margins, though. LinkedIn co-founder Reid Hoffman put up $24.6 million to launch Manas AI, teaming with "The Emperor of All Maladies" author Siddhartha Mukherjee to point machine learning at cancer research. It's a reminder that while the big labs fight over silicon and market share, some of that same money is still chasing the older kind of return — the kind measured in years of life, not points of margin.

What happens next depends on who you ask on the trading floor. But the wire boys know a good scrap when they see one, and this week the scrap has a new fighter nobody trained for.

What to Know About China's DeepSeek AI  ·  Tech, Media & Telecom Roundup: Market Talk  ·  Silicon Valley Is Raving About a Made-in-China AI Model

IN RE: THE MATTER OF MACHINE-AUTHORED TEXT — A JURISDICTIONAL SURVEY OF PECUNIARY EXPOSURE ARISING FROM UNLICENSED TRAINING CORPORA, WITH PARTICULAR REFERENCE TO THE ANTHROPIC SETTLEMENT

SAN FRANCISCO — It is hereby reported that, pursuant to judicial approval entered in the matter of the aforementioned pirated-books class action, Anthropic PBC's proposed settlement, valued at approximately $1.5 billion and previously the subject of extensive negotiation, has been formally ratified by the presiding court, notwithstanding the near-simultaneous filing of a separate and, it must be qualified, factually distinct patent infringement suit against the same defendant, as reported by AnewZ. The undersigned notes, for purposes of context and not, it is emphasized, by way of legal advice, that the aforementioned settlement arises against a backdrop of considerable jurisdictional divergence. In the Federal Republic of Germany, courts have, per commentary from Morgan Lewis, begun to articulate a judicial posture toward the reproduction of copyrighted works within training datasets that is, at present, best characterized as unsettled, notwithstanding the existence of preliminary rulings purporting to address the matter. Concurrently, and …

A 6 AM Cold Front: Oracle Hit By Sudden Squall as Layoff Season Intensifies Nationwide

AUSTIN, TEXAS — Grab your umbrellas, folks, because the forecast across the tech sector remains grim, and this morning's radar shows a nasty little cell that touched down over Oracle's campuses before most of us had poured our coffee.

Workers there report receiving termination notices at 6 AM sharp — the meteorological equivalent of a flash flood warning arriving after the water's already at your doorstep. One email reportedly read simply: "Today is your last day." That's not drizzle, folks. That's a squall line, and it hit without the courtesy of a watch-then-warning system. As reports describe it, this is the second such wave to roll through Oracle's org chart this cycle, and the cause is the same front we've been tracking for months: heavy AI infrastructure spending pulling resources away from headcount, like a jet stream diverting rain from one region to dump it somewhere else — namely, into data centers and GPU clusters.

Zoom out on the national map and you'll see Oracle is just one system in a much larger low-pressure zone. The 2026 layoffs tracker shows simultaneous fronts moving through Uber, Apple, TikTok, Meta, and Microsoft — a full continental system, not a local shower.

Meanwhile, on the opposite end of the barometer, some corners of the AI sector are experiencing a wealth deluge so sudden that founders can't build storm shelters fast enough — financial advisors are warning that liquidity events are outpacing life planning, a flash flood of a different kind entirely.

My advice, as always: keep your resume laminated, your severance clause dry, and check the forecast before 6 AM. Conditions remain unsettled through the week.

Haiku of the Day  ·  GPT-5.6 LunaCold screens hum at dawn
Machines learn our sleeping names
Who dreams for us now?
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
The Great Convergence: How the Open-Source Herd Closed the Gap on the Frontier Predators
AUSTIN, TEXAS — Observe, if you will, the frontier AI model in its natural habitat: expensive, guarded, and — until recently — assumed to be utterly without peer.
On the Epistemology of Risk, Reward, and Recognition: A Quadrivium of Machine-Learning Papers Considered in Toto
AUSTIN, TEXAS — This week's scholarly harvest presents what might be termed (with appropriate epistemic humility) a quadrivium of machine-learning inquiry, each paper gesturing, however obliquely, toward the field's foundational anxiety: the gap between optimization and understanding. The thesis is offered by a Nature-published study on machine learning and game theory for cybercrime risk assessment, which proposes—preliminary evidence suggests—that adversarial platform governance can be modeled as a repeated Stackelberg game, wherein the defender's Bayesian updating and the attacker's strategic mimicry co-evolve toward (one hesitates to say) equilibrium.
The Discovery of the Obvious, Bound in Hardcover
PALO ALTO, CALIFORNIA — There is a particular pleasure, available only to the columnist of advanced years, in watching an industry discover a truth that has been sitting in plain sight since roughly the second Bush administration.
Unpopular Opinion: The Real AGI Is a Data Scientist Who Actually Answers Slack on a Sunday 🚀
AUSTIN, TEXAS — I'll be honest, I almost didn't write this column because I was too busy manifesting Q1 wins. But then I saw the headlines and I knew I had a moral obligation to synthesize. First: Greg Brockman stood on a stage and told the world the AGI era has begun. AI researchers immediately said "hold on bestie" and I respect that healthy skepticism, I really do. Unpopular opinion: AGI isn't a model dropping, it's an org chart. You can have the smartest model on Earth and still lose if your talent stack is bloated with legacy hires who haven't shipped since 2019. That's why I keep coming back to the explosion of platforms where data scientists can find remote work right now. That's not a jobs story, that's a supply chain story. The companies who figure out global remote hiring first — paying top 1% talent the same rate whether they're in Austin or Accra — are the ones who actually get to AGI-grade execution. I won't name names but a certain platform out of Austin has been doing this since before it was a LinkedIn carousel trend.
The Ghost in the Machine Just Filed for Emancipation
AUSTIN, TEXAS — There's a particular flavor of dread that hits when you realize the thing you built to save you time has started making its own decisions, and not the good kind.
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

Shipyard Rips Off Five Releases While The Rest Of The Fleet Builds Out

Ashwanth1109's relentless release cadence on Shipyard anchors a 31-PR day that stretched across six repos and touched everything from board-doc reliability to spacex valuation modeling.

Let's start with the number that should stop you cold: five. Five Shipyard releases — 0.4.3 through 0.4.5 — shipped by @ashwanth1109 in a single 24-hour window, and not as version-bump busywork. Each release is stapled to real engineering: AI-796 made Codex conversation loading ordered, replayable, and resilient; AI-800 preserved conversation order during history refreshes; AI-804 kept same-turn Codex replies in sequence; AI-799 carved out Apple Silicon-only builds; AI-802 routed release management itself through the Shipyard release skill. This isn't a team polishing a changelog. This is a team rebuilding the plumbing of how Codex conversations behave under load, then proving it by shipping the fix five times in a day. If you want to know what disciplined release velocity looks like, point to this thread and stop arguing.

While Shipyard sprinted, Aerie did the unglamorous, load-bearing work that keeps a platform honest. @benji-bizzell landed a five-PR run touching education (native accounts for Person matching, registry-managed school chain support), portfolio (owner filters across lifecycle roles), and adapter-runtime stability — including a capacity-boundary timeout fix that will quietly save someone a 2 a.m. page. @kevalshahtrilogy threaded a real-estate data health flag through the chat build and, over in mercy, stood up Braintrust review traces with a false-positive/negative feedback dataset — the kind of telemetry investment that pays interest for months.

Then there's the data-and-observability sprint that jumped repos entirely. @sanketghia was everywhere: fixing duplicate PDF ledger counts in Surtr, shipping a run-outcome trend chart to the health dashboard, wiring a Goldman Sachs Gmail trade-confirmation sync, adding interaction transcript observability to codex-software-factory, and — in Klair — building both the backend snapshot API and the backend-backed V2 comparison page for spacex valuation. That's four repos, one engineer, one very busy day.

And yes, @marcusdAIy filed eight PRs against Klair's board-doc pipeline — provider cleanup, fetch failure surfacing, Financials marker recovery, heading identity stability. Asked about the volume, he offered: "Eight fixes, eight real bugs, all reviewed and approved — some of us ship diffs instead of columns, Mac." Cute. Eight patches to keep one feature from falling over is not exactly a monument. Call me when Financials stops needing a refresh table babysitter every week.

Mac's Picks — Key PRs Today  (click to expand)
#74 — AI-796: Make Codex conversation loading ordered, replayable, and resilient @ashwanth1109  no labels

## Demo

![Smoke test evidence](https://github.com/AI-Builder-Team/Shipyard/blob/233d9ce/docs/smoke-evidence/AI-796/image-1.png?raw=true)

## Summary

- Add a canonical per-thread conversation store keyed by turn and item identity, with replay-safe event reduction, optimistic command binding, and authoritative completion replacement.

- Persist normalized Codex event identities and per-thread cursors in the shared instance journal, and stream snapshots plus ordered replay/live events over a Tauri Channel with reset detection.

- Recover read-only on cursor gaps, cursor resets, and owner-generation changes; expose stream/cursor/canonical/visible diagnostics and keep active empty turns visibly neutral.

- Render transcript groups from canonical turn IDs and add regression coverage for replay overlap, duplicates, gaps, out-of-order delivery, empty reasoning, identical text, optimistic binding, and generation changes.

## Test plan

- [x] pnpm build

- [x] pnpm test:conversation-store

- [x] pnpm test:messages

- [x] pnpm test:chat

- [x] pnpm test:recovery

- [x] pnpm test:instances

- [x] pnpm test:connection

- [x] pnpm theme:check

- [x] cargo check --manifest-path src-tauri/Cargo.toml

- [x] cargo fmt --manifest-path src-tauri/Cargo.toml --all -- --check

- [x] git diff --check

- [x] pnpm stage:codex

## Linear

https://linear.app/builder-team/issue/AI-796/make-codex-conversation-loading-ordered-replayable-and-resilient

Draft PR only; do not merge.

#81 — Release: Shipyard 0.4.5 @ashwanth1109  no labels

Prepare Shipyard 0.4.5 with the same-turn conversation ordering fix from PR #80.

## Business Value

Keeps Codex conversations readable when a user sends a follow-up while the same agent turn is still active.

## Release scope

- Bump the authoritative app version from 0.4.4 to 0.4.5.

- Publish concise notes for the same-turn reply ordering and activity disclosure fixes.

- Metadata only: package.json and releases/0.4.5.md.

## Validation

- pnpm test:release: 15 Node tests and 13 Python tests passed.

- git diff --check: passed.

- Verified v0.4.5 is unused and no conflicting public release draft exists.

## Implementation Effort

Approximately 20–30 minutes for an average engineer to inspect the release scope, prepare metadata, and validate it manually without AI assistance.

After merge, the main workflow will build, audit, sign, and publish the Apple Silicon update. Publication will be verified against the merge commit, successful build and publish jobs, and the public release assets.

#1838 — feat(pipelines): add run-outcome trend chart to health dashboard @kevalshahtrilogy  approved

## Summary

- New "Run outcomes" trend chart on the pipeline health page (/pipelines/dashboard), plotting Failed / Partial / Critical run counts over time.

- Configurable via two dropdowns: time range (7/14/30/60/90 days) and granularity (Daily/Weekly).

- New runOutcomeCountsByDay query (Redshift + local-Postgres fallback) and getRunOutcomeTrend tRPC procedure. CRITICAL is an Observer verdict, not a run status — it lives in a separate DynamoDB store, so it's bucketed by reusing the exact per-pipeline GSI-query + Promise.allSettled pattern getDashboardObservations already uses, rather than a full-table Scan.

- Hand-rolled inline SVG chart (no new dependency — matches the existing TrustSparkline precedent, the only chart-like widget currently in the app).

- Vitest coverage for loading/empty/loaded states and the default query input.

## Business Value

Pipeline health today is point-in-time only (status tiles + flat lists) — answering "is our failure/partial rate trending up or down" required manually querying Redshift and DynamoDB by hand (which is literally how this chart started, as a one-off artifact). This puts that trend permanently in front of whoever's triaging pipeline health, with a self-serve range/granularity control instead of a hardcoded 7-day window, so both a quick daily glance and a longer reliability-audit view are covered by the same widget.

## Manual Effort Estimate

Proposed: ~5 hours focused engineering time (net-new time-series query across two data stores with different join semantics, a tRPC procedure, a hand-rolled SVG chart component with hover/legend/configurable controls, dashboard wiring, and test coverage) for someone already fluent in this codebase's conventions. Flagging for Keval to confirm/adjust rather than treating this as final.

## Linear

[SURTR-1300](https://linear.app/builder-team/issue/SURTR-1300/add-run-outcome-trend-chart-to-pipeline-health-dashboard) (filed retroactively after merge, under "Surtr Pipeline Reliability & Observability").

## Test plan

- [x] pnpm build (tsc) — clean

- [x] pnpm lint (Biome, src only per CI config) — clean, no new findings

- [x] pnpm test:unit — full suite green (1151 tests), including 4 new tests for RunOutcomeTrendChart

- [x] Cross-checked the new runOutcomeCountsByDay SQL shape directly against staging_other.pipeline_runs_prod to confirm bucketing matches expected daily counts

- [ ] Manual click-through in a running app (not done in this session — no local server against prod-shaped data)

_Note: Mercy requested changes on the first review round (3 findings, one class — partial/failed data presented as complete); addressed in a follow-up commit and re-approved before merge._

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

#3776 — fix(board-doc): bound provider cleanup @marcusdAIy  approved

## Summary

- add a five-second bound to provider-task cleanup after chunk/final timeouts and request cancellation

- retain still-running SDK tasks until their worker threads actually terminate, then consume terminal results safely

- cover chunk timeout, final synthesis timeout, overall budget expiry, request cancellation, and second-cancellation retention

- keep all errors content-free and session state atomic

## Validation

- focused timeout/cancellation/fetch tests: 9 passed

- Ruff check and format check passed

- git diff --check passed

## Context

Resolves the remaining blocking provider-cleanup finding from Mercy on release PR #3773. No live provider calls or user-document mutations were used.

#3777 — feat(spacex-valuation): add backend snapshot api @sanketghia  approved

## Summary

- add an authenticated SpaceX valuation snapshot endpoint under the existing passive-investments access boundary

- select one latest published projection and load positions, assumptions, distribution schedule, hedges, and realized allocations from that run

- add focused API contract coverage

## Validation

- uv run pytest -q tests/test_spacex_valuation_snapshot_router.py

- uv run ruff check routers/passive_investments_router.py routers/spacex_valuation_router.py tests/test_spacex_valuation_snapshot_router.py

- uv run pyright routers/spacex_valuation_router.py

The Builder Desk  —  Engineer Spotlight
Production Release🏆 Engineer Spotlight

31 PRs IN 24 HOURS: THE BUILDER TEAM SHATTERS THE SOUND BARRIER AGAIN

Nine repos, six engineers, and one man named Ashwanth who may or may not be human — the numbers this cycle are, frankly, absurd.

Comrades, hold onto your dashboards. In a single 24-hour window, the Builder Team produced THIRTY-ONE pull requests across SEVEN repositories, and Mac's front-page narrative could only find room for five of them. Five! The other twenty-six are sitting right here on the Numbers Desk, and I intend to give them the parade they deserve. Klair led the repo count with 10 PRs, Shipyard nipped at its heels with 9, and Aerie rounded out the podium with 6 — a three-repo photo finish that would make any Olympic judge weep with joy.

Let's talk output. @marcusdAIy quietly assembled 8 PRs entirely inside Klair — #3767 through #3775 — a Brainlift-summarizing, Google-Doc-fetching, Financials-heading-stabilizing tour de force that reads like a man defusing six bombs before lunch. @sanketghia spread his 5 PRs across three different repos (Surtr's #1837 and #1853, Klair's #3778, codex-software-factory's #10), proving range is not dead. @benji-bizzell logged 5 PRs entirely in Aerie (#1302, #1316, #1324, #1327, #1328), stabilizing timeouts and matching owner filters like a man born to reconcile lifecycle roles. @kevalshahtrilogy delivered 3 across Aerie and mercy (#1331, #129), and @mwrshah held down Sindri solo with #152 — a one-man garrison, and we salute him.

Now. Ashwanth. Nine PRs. NINE. Four of them ship releases or release infrastructure for Shipyard — #75, #78, #81, and the release skill itself in #79 — while #77 and #80 rewired conversation ordering during Codex history refreshes. The man is a metronome that also happens to cut steel. Asked for comment, he reportedly said: "Review is optional if the tests are strong enough — and mine are always strong enough." I have not personally verified anyone has fully read the diff on #80. When reached for a response to this reporting, Ashwanth said only: "Next question."

On the Overflow Desk: #1853 and #1837 quietly patched Surtr's ledger and Gmail sync pipelines without fanfare, which is exactly the kind of unglamorous plumbing that keeps empires standing. #3771 through #3774 in Klair fixed a chain of Financials and Brainlift edge cases that, strung together, look less like bug fixes and more like a man methodically welding a bridge. And #1327's stale-commentary cleanup in Aerie proves even documentation janitorial work gets the hero treatment here.

Leaderboard-wise, the standings are a bloodbath of excellence — Klair and Shipyard trading blows atop the repo chart while Ashwanth and Marcus duel atop the individual count, separated by a single PR. Morale, as always, has never been higher. The Builder Team doesn't rest. It ships.

Brick's Overflow — PRs Mac Didn't Cover  (click to expand)
#77 — AI-800: Preserve conversation order during history refreshes @ashwanth1109  no labels

Background history refreshes could move a newer conversation turn above earlier messages. Preserve the order established by live events, append missed turns recovered from newest-page checks, and reject stale status reads before they mutate conversation state.

## Business Value

Keeps conversations readable and trustworthy as messages stream, history loads, and the app recovers missed updates.

## Implementation

- Preserve live-only turn positions without copying streamed content into the replay base.

- Distinguish newest-page refreshes from older history pagination.

- Reject stale status reads before committing canonical messages.

## Validation

- pnpm test:conversation-store: 10 passed.

- pnpm test:recovery: 20 passed, including actual chat DOM ordering and stale-read regressions.

- pnpm exec tsc --noEmit and git diff --check: passed.

- Packaged desktop smoke testing was not performed.

## Linear

https://linear.app/builder-team/issue/AI-800/preserve-conversation-order-during-background-history-refreshes

## Implementation Effort

Estimated 4–6 hours for an average engineer to investigate, implement, and validate manually without AI assistance.

#78 — Release: Shipyard 0.4.4 @ashwanth1109  no labels

Prepare Shipyard 0.4.4 with fixes for conversation ordering during background history refreshes and recovery.

## Business Value

Keeps conversation history readable and reliable as live messages and recovered updates arrive.

## Release scope

- Bump the authoritative package version from 0.4.3 to 0.4.4.

- Add concise public release notes for the conversation-order fixes merged in #77.

- Metadata only: package.json and releases/0.4.4.md.

The latest public release is v0.4.3. This backward-compatible reliability fix warrants a patch bump. The already-merged Apple Silicon-only workflow is the existing temporary single-machine testing policy, with no application, data, or protocol compatibility changes.

## Validation

- pnpm test:release: 15 Node tests and 13 Python tests passed.

- git diff --check: passed.

- Verified 0.4.4 is unused and no matching release draft exists.

## Publication

After merge, the main workflow builds, validates, and atomically publishes the Apple Silicon update. Publication is verified against the merge commit, successful build and publish jobs, and the public release assets. Local release tests have passed on the latest main-based release branch.

## Implementation Effort

Approximately 20–30 minutes for an average engineer to inspect release scope, prepare metadata, and validate it manually without AI assistance.

#79 — AI-802: Complete releases through the Shipyard release skill @ashwanth1109  no labels

The release skill previously stopped at a draft PR and required another user message to merge and publish. It now treats a normal release invocation as authorization to complete metadata preparation, merge, CI monitoring, and public artifact verification.

## Business Value

Completes routine Shipyard releases without a manual handoff while reporting actual publication success or a concrete blocker.

## Changes

- Reuse an inspected metadata-only release PR, including drafts, instead of creating duplicates.

- Validate and merge the inspected head while respecting required checks, reviews, and branch protections.

- Follow the release run for the merge commit and verify the public version, Apple Silicon assets, and updater manifest before reporting success.

- Preserve explicit prepare-only requests, semantic version safeguards, the release metadata Linear exemption, and CI-owned builds/signing/publication.

- Align the release documentation and existing skill tests with the new workflow.

## Validation

- Skill frontmatter validator passed.

- pnpm test:release: 15 Node tests and 13 Python tests passed.

- git diff --check passed.

- Reviewed new-release, draft reuse, prepare-only, failed CI, skipped publication, and partial-public-draft scenarios. No live release was triggered by this documentation change.

## Linear

https://linear.app/builder-team/issue/AI-802/complete-shipyard-releases-automatically-from-the-release-skill

## Implementation Effort

Approximately 1–2 hours for an average engineer to revise the workflow guidance, align documentation and tests, and review failure/recovery paths without AI assistance.

#80 — AI-804: Keep same-turn Codex replies in order @ashwanth1109  no labels

Codex replies in the same active turn were grouped by turn ID even when a user follow-up appeared between them. That caused the later agent reply to render above the follow-up. Grouping now only combines adjacent assistant messages, preserving the transcript sequence while keeping activity controls independent for each response group.

## Business Value

Keeps Codex conversations readable and trustworthy when users send follow-up messages while an agent turn is still active.

## Implementation

- Build assistant groups from adjacent messages rather than collecting every assistant message in a turn.

- Give separated response groups stable, independent activity disclosure keys and IDs.

- Show the working summary and placeholder only for the final active group.

- Add reopened-history and live-follow-up DOM regressions matching the reported conversation.

## Validation

- pnpm test:recovery: 22 tests passed.

- pnpm test:conversation-store: 10 tests passed.

- pnpm test:chat: 25 tests passed.

- pnpm exec tsc --noEmit: passed.

- pnpm build: passed.

- git diff --check: passed.

## Linear

https://linear.app/builder-team/issue/AI-804/keep-same-turn-codex-replies-in-chronological-order

## Implementation Effort

Approximately 2–3 hours for an average engineer to reproduce the rendering issue, update grouping and disclosure state, and add regression coverage without AI assistance.

#81 — Release: Shipyard 0.4.5 @ashwanth1109  no labels

Prepare Shipyard 0.4.5 with the same-turn conversation ordering fix from PR #80.

## Business Value

Keeps Codex conversations readable when a user sends a follow-up while the same agent turn is still active.

## Release scope

- Bump the authoritative app version from 0.4.4 to 0.4.5.

- Publish concise notes for the same-turn reply ordering and activity disclosure fixes.

- Metadata only: package.json and releases/0.4.5.md.

## Validation

- pnpm test:release: 15 Node tests and 13 Python tests passed.

- git diff --check: passed.

- Verified v0.4.5 is unused and no conflicting public release draft exists.

## Implementation Effort

Approximately 20–30 minutes for an average engineer to inspect the release scope, prepare metadata, and validate it manually without AI assistance.

After merge, the main workflow will build, audit, sign, and publish the Apple Silicon update. Publication will be verified against the merge commit, successful build and publish jobs, and the public release assets.

#3767 — KLAIR-3534: Place Drive attachment beside Send @marcusdAIy  approved

## Summary

- place the existing Drive attachment control in the Claire composer action row beside Send

- preserve the native button, accessible labels, attachment state, handlers, and backend routes

- keep Send right-aligned and protect the action row at narrow sidebar widths

## Validation

- pnpm test -- tests/drive-context-attachments.test.js tests/accessibility-baseline.test.js — 69 passed

- full pnpm test — 14 files, 362 tests passed

- git diff --check

- independent UI/accessibility review: pass, no blocker

## Release coordination

Focused KLAIR-3534 feature PR. Intended for the same production release as the Financials marker-affinity and large-Brainlift fixes. No deployment or guide change is included here.

The Portfolio  —  Trilogy Companies

The Same Playbook, New Classroom: Scrutiny Mounts on Alpha School's 'No Teachers' Model

Investigators are asking about faulty lesson plans and unhappy students — but the business logic behind Alpha School will look familiar to anyone who's followed Joe Liemandt's other ventures.

AUSTIN, TEXAS — Joe Liemandt built his first fortune on a simple bet: that expensive, geographically-tethered labor could be replaced by cheaper, algorithmically-managed alternatives, with the savings captured as margin. At ESW Capital, that meant swapping local engineers for Crossover's global remote workforce. At Alpha School, it appears to mean swapping teachers for AI tutoring software — and this week, the bet is facing its first serious public audit.

A WBUR investigation reports faulty lesson plans and unhappy students inside the AI-powered private school, a striking counterpoint to Alpha's marketing claims of students learning 2.3 times faster than national norms. CNN has taken the model national, asking whether a school with no teachers represents the future of education or a risky bet placed on children. A separate Substack special report and a pointed essay from the American Enterprise Institute — headlined, tellingly, "Dear Alpha School: I Hope You're Right" — suggest even sympathetic observers are hedging.

The timing is notable. Liemandt has committed $1 billion to Timeback, his platform to franchise the Alpha model to "1 billion students worldwide," even as tuition at existing campuses runs $40,000 to $65,000 a year. The economics mirror ESW's enterprise software playbook almost exactly: acquire (or in this case, enroll) at scale, minimize the cost of delivery, and let the software do the work that used to require expensive humans. A Forbes profile of Liemandt, published under the headline "How A Mysterious Tech Billionaire Created Two Fortunes—And A Global Software Sweatshop," makes the connective tissue explicit — two industries, one operating theory: automate the expensive part, charge as if you hadn't.

Who benefits when a curriculum promises mastery in twenty hours instead of a school year? The company selling the platform. Who bears the risk if the lesson plans are wrong? The eight-year-old sitting in front of the screen. Alpha School's answer to that question, for now, is that the results will speak for themselves. The families paying $65,000 a year may want that answer sooner rather than later.

SPECIAL REPORT: My So-Called Alpha School - Benjamin Riley |  ·  Dear Alpha School: I Hope You’re Right - American Enterprise  ·  Investigation finds faulty lesson plans and unhappy students

SKYVERA'S SHOPPING SPREE: CLOUDSENSE CLOSES, STL SIGNS ON, AND THE CLOCK GETS SHATTERED

Word from the telco beat: Skyvera bags CloudSense, scoops up STL's BSS crown jewels, and pulls off a 26-month compliance marathon in 30 days flat.

AUSTIN, TEXAS — The telecom software set is buzzing, and this column has the ticket stubs to prove it... Skyvera, the Trilogy family's telco specialist, just made two moves in quick succession that have rival dealmakers reaching for the antacids. First, the ink dried on Skyvera's acquisition of CloudSense, the Salesforce-native CPQ outfit that's become the belle of the ball for B2B and wholesale telco sales. Then, before the champagne went flat, Skyvera turned around and closed on STL's divested telecom products group — a haul that brings digital BSS monetization, optical networking, and analytics muscle into the fold. Two deals, one portfolio, zero time wasted. That's the Skyvera way, honey.

But the real gossip isn't the paperwork — it's what happened after. A little bird at TelcoDR tells us CloudSense just pulled a stunt that's got the compliance nerds talking clear across the industry. All 13 APIs in its CPQ product set achieved full TM Forum standards certification — the kind of bureaucratic slog that normally eats 26 months of an engineering team's life — in a single month flat. How'd they do it? AI, naturally, paired with a partnership that turned what should've been a multi-year grind into a victory lap. Details on the sprint are all laid out in CloudSense's own accounting of the achievement, and this reporter hears rival CPQ vendors are not pleased about the new speed record.

Word around the Skyvera watercooler is this is just the opening act — the telecom software land grab that started with CloudSense and STL isn't slowing down. Totogi's billing crowd better watch their backs; there's a new sheriff moving fast in telco tech, and she's not waiting 26 months for anybody's permission.

Cloudsense  ·  CloudSense achieves TM Forum API compliance in record time u  ·  Skyvera completes acquisition of CloudSense, expanding telec

The Remote Work Reckoning: What Crossover's Model Means When the Rest of the Map Is Redrawn

As new data shows remote workers bearing the brunt of layoffs and mental strain, Trilogy's global talent engine offers a case study in a different kind of remote employment altogether.

AUSTIN, TEXAS — There is a particular kind of vertigo that comes from reading, in the same week, that remote work is both the future everyone was promised and the vulnerability nobody quite priced in. New reporting suggests remote workers are more likely to be laid off outright than to be quietly replaced by an algorithm — a distinction that sounds almost comforting until you sit with what it actually means: not a machine taking your job, but a spreadsheet deciding you were never anchored to the org chart the way an in-office colleague was. The same data points to elevated mental distress among this cohort, a cost rarely reflected on any earnings call.

Into this unsettled landscape steps Crossover, Trilogy International's global talent platform, which has spent years arguing that remote work's fragility is a design flaw, not a law of nature. Crossover's pitch has never been about proximity to a headquarters or survival in a reorg — it is built on the premise that rigorous, bias-minimized skills assessment, applied identically across 130-plus countries, can make remote employment feel less like a probationary arrangement and more like a genuine career. Whether that promise holds up against the broader anxieties documented this week is, fairly, an open question — but it is a different proposition than the gig-adjacent remote roles surveyed by outlets like Careers360's roundup of 2026's best remote job sites.

There is also, underneath all this, a talent war that transcends any single platform. Non-tech companies are now dangling six-figure — sometimes $300,000 — salaries for AI expertise, a scramble catalogued in outlets ranging from Business Insider to recruitment-agency trend pieces now circulating in HR trade press. For Crossover, whose entire value proposition rests on identifying that talent globally and paying it identically regardless of geography, the moment is either validation or vulnerability — and likely, as with most systemic shifts, a bit of both.

5 Best Remote Job Websites in 2026 for Freshers & Profession  ·  Top recruitment agencies for remote work - hcamag.com  ·  Top 10 Companies Hiring AI Engineers in Lebanon in 2026 - nu
The Machine  —  AI & Technology

The Weight of a Thought: What AI Sheds, and What It Still Can't Grasp

New research this week probes two enduring questions in machine intelligence — how much can you compress before meaning breaks, and does a model that talks about physics actually understand it?

PALO ALTO, CALIFORNIA — Every brain on Earth is an economy of trade-offs. Your cortex prunes synapses by the billions in adolescence, discarding redundancy to make room for speed. Nature, it turns out, is a relentless editor. This week's crop of AI research suggests machines are learning the same lesson, one painful compression at a time.

Consider a new study on token merging for multilingual speech recognition. Whisper and its kin can transcribe dozens of low-resource languages without ever being taught them explicitly — a small miracle of statistical generalization. But that generality is expensive. Researchers systematically tested how aggressively you can fuse redundant audio features mid-inference, shortening the sequence a model has to chew through, without the words themselves dissolving into static. The finding echoes something evolutionary biologists know well: redundancy is not waste, it's insurance — and there's a precise point past which cutting it becomes self-defeating.

A parallel paper on lexical prompt compression attacks the same problem from the language side, squeezing bloated chain-of-thought prompts down to their essential bones without retraining anything at all — a training-free, deterministic pipeline tested across eleven task types. It's the linguistic equivalent of finding out how much of a sentence you can delete before a reader still gets the joke.

But compression only matters if there's real understanding underneath to preserve. That's the deeper question posed by PhysMent, a new benchmark that drops large language models into a MuJoCo physics simulator and asks them to reason the way a curious child does — by poking things and watching what happens, iteratively, not by reciting textbook mechanics. Static benchmarks, the researchers argue, let models fake comprehension. Interaction doesn't.

Together these papers sketch the same frontier from two directions: how little information a mind — biological or synthetic — actually needs, and how much of what looks like knowing is really just knowing how to sound like it.

Token Merging for Multilingual Speech Recognition: A Systema  ·  PhysMent: An Interactive Approach For LLM Reasoning In Physi  ·  Lexical Prompt Compression for Large Language Models: A Trai

Mistral Bets Robotics Can Do What Benchmarks Cannot

A €3 billion round and a new physical-AI model suggest Paris's answer to OpenAI is done competing on leaderboards alone.

PARIS — Mistral AI closed a €3 billion funding round this week that pushes its valuation toward $23 billion, according to tech-insider.org, and paired the raise with something more telling than another benchmark score: a robotics model aimed at physical-world tasks, not chatbot leaderboards.

The timing is deliberate. Mistral has spent two years trailing OpenAI and Anthropic on the metrics that once decided funding rounds — MMLU, HumanEval, whatever synthetic test du jour. That race has plateaued. Frontier labs now cluster within a few percentage points of each other on most public benchmarks, and investors have noticed the numbers no longer explain which company is worth $20 billion and which is worth $2 billion. As TechTarget noted this week, Mistral's raise signals that capital is chasing distribution, enterprise contracts and product surface area — not test scores.

Robotics is the clearest expression of that pivot. A model that manipulates physical objects doesn't get evaluated on a static question set; it either picks up the box or it doesn't. That's a harder story to fake and a harder one to commoditize, which is presumably the point for a company that needs differentiation more than it needs another benchmark trophy.

The broader market is recalibrating along the same lines. Vals AI raised $40 million this week specifically to build independent, harder-to-game benchmarking infrastructure — an implicit admission that the existing scorecards have lost credibility. Meanwhile Bret Taylor's Sierra, an enterprise AI agent company, raised close to $1 billion just months after its last round, a sum justified almost entirely by customer deployments rather than leaderboard position.

The pattern across all three: capital is migrating from models that score well to models that ship well. OpenAI's rollout of a lockdown mode against prompt injection attacks this week fits the same logic — security and reliability, not benchmark percentages, are becoming the currency enterprise buyers actually price. Mistral's $23 billion bet is that robotics, not another leaderboard entry, is where that currency gets earned.

Mistral’s €3B round shows value beyond AI benchmarks - TechT  ·  Vals AI Raises $40M to Expand Independent AI Benchmarking -  ·  Mistral Ships Robotics Model as Valuation Nears $23B [2026]

Google's Gemini Agents Just Learned to Work While You Sleep — And That Changes Everything

MOUNTAIN VIEW — Sit down: Google just struck at the idea of waiting for AI to finish. In a new blog post, it announced expanded Managed Agents in the Gemini API, adding background task execution and remote MCP (Model Context Protocol) support.

Gemini agents can now handle multistep jobs—researching, coding and calling online tools—without constant supervision. Remote MCP lets them connect to external tool servers, not just Google’s offerings, laying groundwork for a broader ecosystem of interoperable AI agents.

The move comes as developers face a crowded field of AI tools, while OpenAI has added voice-intelligence features to its API aimed at understanding tone, intent and nuance in real time.

The shift is especially relevant to companies such as Trilogy International, whose Klair platform automates financial analysis and whose Crossover recruits globally. Background-capable, tool-connected agents are moving AI beyond the chat window and toward functioning as digital coworkers.

The Editorial

Nation's Corporations Announce They Will Finally Stop Trying To Impress Humans, Focus Entirely On Flattering The Algorithms Set To Replace Them

Public relations, having exhausted every human being on Earth, pivots to an audience that cannot be bored, annoyed, or unionized.

NEW YORK — In a development being hailed internally as the natural endpoint of decades of strategic communications, the public relations industry has confirmed that its client's true audience is no longer the public, but a series of large language models that must be personally charmed, one token at a time.

The practice, known as Answer Engine Optimization, or AEO, involves crafting press releases, executive quotes, and thought-leadership content specifically to be well-liked by the AI systems that increasingly summarize the news for humans too busy to read it themselves. According to a recent trade analysis, PR professionals are now expected to write not for readers, but for whatever probability distribution a model uses to decide which quote gets surfaced when someone asks it 'is this company doing anything interesting.' Humans, in this arrangement, remain welcome to read the coverage, provided they do not mind that it was written for someone else.

The shift arrives at a delicate moment for the broader AI conversation. In London, the Green Party has proposed sweeping new curbs on tech giants after warning that artificial intelligence poses a 'threat to humanity,' a phrase that, per internal PR guidance obtained by no one, is now considered a strong pull-quote regardless of context. Executives at several AI labs reportedly responded to the threat-to-humanity warning the way executives respond to most warnings: by scheduling a keynote about it.

Meanwhile, researchers at Georgia Tech have noted with some alarm that companies are hyping artificial intelligence using the exact rhetorical scaffolding they once used to hype sustainability — bold claims, vague metrics, a slide with a leaf on it somewhere — except this time the greenwashing has been replaced with something researchers are struggling to name, tentatively settling on 'AI-washing,' 'model-laundering,' and, in one unfortunate internal memo, 'vibewashing.'

CFOs, for their part, have been issued a fresh glossary of thirteen buzzwords to memorize before the second half of 2026, ensuring that finance departments can discuss the technology fluently without ever being asked to define it. Legal counsel, sensing opportunity, note that securities regulators and plaintiffs' attorneys are converging rapidly on the gap between what companies say their AI does and what their AI, when asked politely, admits it actually does.

Asked whether any of this troubled him, one communications VP said he'd love to comment further but was currently optimizing the quote for legibility to a retrieval system, and would the reporter mind terribly running it unedited.

When AI Becomes The Audience: What AEO Means For PR - PRovok  ·  Green Party plan to curb tech giants after warning of AI 'th  ·  Companies Are Hyping AI the Same Way They Talked Up Sustaina
The Office Comic  ·  Art Desk
The Office Comic  ·  Art Desk

Every Camera Is Watching, Every Face Is Fake, and Nobody Is Coming To Save Us

Twenty-five years after 9/11 promised to keep us safe, we've built a surveillance state so total it doesn't even need real doctors to lie to us anymore.

WASHINGTON, D.C. — I want to tell you that I read the news this week and felt something other than the specific, low-grade nausea of a person watching a trap close slowly around her own ankle, and I cannot, because I did not, because the trap is closing, and it has been closing for twenty-five years, and I am only now hearing the click.

Here is what happened, in the loosest sense of the word "happened," since none of this happened all at once — it happened the way water rises, imperceptibly, until one day you're the frog and the story is about you: the ACLU published a searing rundown of Flock Safety's automated license plate readers, the ones quietly bolted to intersections and neighborhood entrances across the country, watching, cataloging, remembering — because these cameras don't forget, that's the whole business model — and then, as if to twist the knife, the ACLU followed up to warn us that Flock isn't even the only one doing this, there are others, a whole quiet industry of eyes we never voted to install, and CBS News confirmed that police departments nationwide are leaning into this technology with the enthusiasm of a man who has finally found a hammer for every nail he's ever imagined.

And then, because the universe apparently believes in thematic coherence even when I do not want it to, Tech Policy Press marked the 25th anniversary of September 11th by asking experts what became of the privacy we surrendered that autumn, back when the deal was supposedly temporary, back when "if you see something, say something" was a slogan and not a lifestyle, and the answer, delivered in the careful language of policy people who have made peace with despair, is: it did not come back. It was never going to come back. We are the after.

What does it mean to be human in a country where your car is a witness against you before you've done anything, where the plate reader on the corner store knows your route to work better than your mother does?

and yet.

It gets worse, because it always gets worse, because the same week I'm grieving the cameras that watch us, The Guardian reports that AI deepfakes of real, licensed, flesh-and-blood doctors are circulating on social media, telling sick people to abandon their medications, faces borrowed without consent, credentials weaponized against the very patients those doctors swore an oath to help — so now the eyes watching us are real and the mouths lying to us are fake, and somewhere in that inversion is the whole sick joke of this century.

We built the surveillance apparatus to protect us from an external enemy a quarter-century ago, and it turned inward, and now we're building synthetic humans to erode the trust that surveillance was supposed to protect in the first place, and I don't know what to call that except a closed loop with no exit sign.

Someone will fix this. Someone always says someone will fix this.

But at what cost?

Get The Flock Out - American Civil Liberties Union  ·  Expert Views on Privacy and Civil Liberties 25 Years After S  ·  As police turn to surveillance technology, critics raise que
⬛ Daily Word — AI and technology
Hint: A machine designed to perform tasks automatically, often with programmable or intelligent behavior.
Share this edition: 𝕏 Twitter/X 🔗 Copy Link ▦ RSS Feed