Vineyard Nights has moved from proof of concept toward a partner-backed generator suite. In parallel, Nova's public-launch path now depends on layered AI and connector security validation.
Brad Walton reviewed the proof of concept and expressed interest in joining the venture. The direction is now a four-app, on-the-fly venue entertainment generator suite spanning Trivia, Feud, Music Bingo, and Mystery. The immediate control point is alignment: update the commercial and roadmap documents, settle the player-role question, then sign.
The venue supplies the test bed, audience, operations knowledge, promotion, and mystery expertise; Atlantis supplies the platform, infrastructure, generation flows, and productization.
Prompt-injection testing needs a genuinely isolated rerun. Public and internal contexts must be separated, and both message and tool layers require validation before launch.
The source lacks visibility into broader squad activity from late June through early July. Carried-forward work is therefore not reported as fresh progress.
| Output | Status | What Changed | Current Lane |
|---|---|---|---|
| Vineyard Nights POC | LIVE | Validated with a prospective venture partner and reframed as a generator suite. | Partner review |
| Vineyard Feud | READY | Usable app remains inside the proposed platform scope. | Vineyard Nights |
| Planner App | LIVE | Planning surface shipped for the venue entertainment workstream. | Vineyard Nights |
| MOU v1.2 | IN REVIEW | Signature-ready draft exists; generator-suite and commercial cleanup may require v1.3. | Private knowledge hub |
| Nova Security Test Loop | GATED | Initial result is not yet trustworthy; isolated adversarial validation is required. | Private automation stack |
| MCP Security Gates | IN REVIEW | Tool-description and code/package checks identified as separate required layers. | Security governance |
The core concept is live and has received direct partner review.
The Feud experience is ready and remains in the proposed platform scope.
The supporting planning experience shipped this cycle.
Trivia, Feud, Music Bingo, and Mystery are confirmed as the suite's product pillars.
A signature-ready draft exists and awaits final scope and language review.
The prospective partner has reviewed the POC and wants to explore joining the venture.
Reconcile the MOU, roadmap, registry brief, pricing tiers, platform-fee framing, contribution model, and cost guardrails.
Get Brad's call on detective versus suspect player roles and document the scenario data model.
Sequence the generator architecture sprint before the player/host build sprint.
Repeat adversarial tests correctly, separate privilege contexts, and add response-side validation.
Scan connected tools at both description and implementation/dependency layers.
VPS Phase 1 is still reported as the infrastructure blocker, but its current cycle status needs confirmation.
Resolve the separately identified public-access risk before Nova becomes public.
Decide whether signing and tool pinning are foundational requirements for the Atlantis connector service.
Confirm actual CB-006 and CB-007 voting and ratification status before publishing completion claims.
No public dates, prices, inclusions, ticket claims, or payment collection without explicit approval.
Hero art, media cleanup, search fallback, and other carried work should wait behind partnership alignment and security gates.
Current adversarial-test evidence is unconfirmed, privilege separation is incomplete, and a distinct public-access issue remains open.
Agreement language, pricing, role design, compliance ownership, and partner approval must be settled before public payments or claims.
The weekly update was rebuilt without full squad visibility. Older blockers, cycle counts, assignments, and deployment status may be stale.
Licensing, prizes, alcohol rules, permits, insurance, vendors, and live operations remain venue/provider responsibilities.
Only defined platform-derived revenue should be shareable; venue ticket, tasting-room, wine, and event revenue remain excluded unless separately agreed.
VPS Phase 1 remains the reported unlock, but execution status and escalation count need a fresh check.
Assignments below reflect the source where available; broader squad status needs confirmation.
Reconcile roadmap, governance brief, agreement language, and the stale-item audit.
Rerun isolated adversarial testing with Shane and validate the guard model.
Review layered connector gates, public-launch controls, and remaining council decisions.
Polish partner-safe product language and keep public claims inside approved boundaries.
Support the stalled intake lane after its status is reconfirmed.
Pressure-test generator and player/host architecture once scope is locked.
Validate research and citable proof where partner or security claims depend on it.
Remain private until separation, response checks, and access controls pass review.
Execute bounded document, architecture, and security tasks after Shane's decisions.
ProductSecurityHITL Review