Founding membership costs were higher, but most offerings are now available to non‑Founding Members for $5k/yr A few Founding Memberships remain open for emerging members, though those require nomination

The group exists to protect craftsmanship and celebrate both the beauty of the wines and the places that produce them Today, "Drink With Me" opens to non‑Founding Members, offering most (but

As a result, lifelong relationships are being forged with some of the world’s most remarkable wineries, and when succession planning occurs the collective may be invited in as partners rather than seeing

The collective also aims to serve as a safe harbor for multi‑generational winemakers during succession transitions

Founding Members buy together, travel the world for shared dinners, and sell wine to each other at cost—often with discounts of 30–40% even on very exclusive bottles

Nearly 50 Founding Members joined with the goal of ensuring traditional winemaking isn’t lost amid accelerating technological processes

A California liquor license was obtained a year ago to enable direct purchasing from wineries and bypass much of the middleman fuss and markup

GBrain is suggested as an OSS retrieval layer

This is the actual bottleneck. The models are smart enough already. What is missing is the company-specific context locked in senior people heads. Whoever cracks knowledge extraction at the company level

Large enterprises increasingly seek a control plane that captures tribal knowledge while providing governance, safety and control. This trend appears to be accelerating as models asymptote on quality.

Agreed! Software Factory enables this — it organizes and produces the artifacts that guide downstream productivity.

Nothing truer has ever been said… Never interrupt your enemy when he is making a mistake

Read superficially, the result suggests convergence: three frontier systems reaching roughly the same level of capability

There is no single best model At the top of the leaderboard, Opus 4.7, GPT-5.5, and Sonnet 4.6 appear almost indistinguishable, separated by less than 0.3 percentage points overall

The idea that no single model dominates is becoming increasingly evident across a range of evaluations What explains this trend?

Which unified system do teams use today to reference context?

Coding tasks are passed to the IDE agent of choice to execute against that context (Claude, Cursor, Copilot, etc.) Agents can write code well today. The question is what they're writing it against

Software Factory's modules capture full business intent and engineering architecture in a unified, collaborative environment so all operators share the same context

Engineers then spend round after round correcting it — rework is what the token bill actually measures An agent builds correct code when it knows two things: what to build, and what to build it against

An agent gets a vague prompt and a "make no mistakes" instruction, guesses at an architecture that doesn't match the production stack, and ships the wrong thing