Find published dossiers by topic, company, product or technology.

Showing 21–40 of 121 dossiers

Google DeepMind is piloting double-blind frontier-model evaluations with confidential computing

The pilot attacks a persistent evaluation trade-off: labs do not want to reveal frontier-model internals, while evaluators do not want benchmark prompts leaking back to the model provider. DeepMind says a Singapore AI Safety Institute pilot kept both sides’ sensitive assets hidden during execution.

GitHub rewrote Copilot’s 800,000-line agent runtime in Rust with agents doing most of the coding

The useful part is not the 800,000-line headline. GitHub has published unusually detailed receipts for a production-scale agent-assisted migration: roughly $120,000 of token spend, 14.5 weeks of incremental releases, dozens of regressions, extensive compatibility tests and a workload-specific jump from 7.55 to 120 session lifecycles per second.

GitHub Actions is starting runtime brownouts for outdated self-hosted runners

Teams with pinned, custom-image or auto-update-disabled GitHub Actions runners can now see registration or job execution fail before the September 25 cutoff. The migration is not just a one-time jump to v2.329.0: already-registered runners must also stay within 30 days of the latest runner release.

Microsoft Project Zenith turns 64GB-class Windows PCs into a standardized local-AI developer tier

Project Zenith is not a new model or another Copilot feature. It standardizes a developer-focused Windows experience and hardware floor for local AI work, with preconfigured tooling and OS settings intended to reduce setup friction and dependence on metered cloud inference.

ChartMogul finds standard SaaS LTV forecasts miss actual cohort revenue by more than 50% nearly three times in ten

The median SaaS LTV forecast looks almost right at 12 months, but that average hides huge misses in both directions. For acquisition budgets, payback planning and company valuation, ChartMogul’s new 3,331-company analysis argues for treating LTV as a directional indicator rather than a precise revenue forecast.