PlayLatticeInside The Content Engine
Local models find the evidence. A coordinated agent crew prepares the story. Deterministic code renders and delivers the content.
Solid arrows show processing order. Storage and control support every stage.
Supplied footage and downloaded clips
Five-video daily target → licensed source evidence → bounded gameplay excerpt
Probe, register source, queue analysis
Player detections, pose, and tracks
Basketball and hoop observations
Candidate selection → FFmpeg render → media checks
Leads the video specialists and the Outreach customer-conversation role
Source context, clip choices, captions, consistency checks, and distribution handoff. The coordinator assembles a structured package.
Customer asks for recommendations or requests a clip by email
Matches published catalog entries, asks clarifying questions, and returns a structured clip request
Local code checks source times and tracks, renders the clip, and replies through AgentMail. See the email workflow ↗
Source replay, captioned stories or quiz moments, answer cards, reveal, and selected music
Policy checks, saved request journal, media upload, and receipt reconciliation
External provider delivers the prepared content
Daily discovery is bounded by source availability, camera evidence, quality gates, and the existing budget; five usable outputs are a target, not a guarantee. The crew’s baseline analysis contract is metadata-only; a successful package does not prove visual verification. Publishing is conditional on policy and provider availability.
| Step | Execution | Result |
|---|---|---|
| 1. Check & Import | Local API validates input, probes media, and records the source hash. | A game record linked to registered media. |
| 2. Analyze | Player and basketball models share a decode loop. Tracking and camera boundaries organize observations. | Timestamped tracks, object observations, and analysis reports. |
| 3. Export Candidates | Local heuristics select moments. FFmpeg renders clips and checks decoding, bounds, duration, and alignment. | Source-linked candidate clips. Media QA does not establish a made or missed shot. |
| 4. Coordinate The Crew | The dispatcher builds source-bound evidence and starts Naive specialist sessions. | A validated package of clip IDs, captions, reasons, and uncertainty notes. |
| 5. Render The Format | Local rendering uses the selected clip and quiz or storytelling configuration. | A captioned portrait story or a replay with a prediction question and reveal. |
| 6. Publish If Enabled | The publisher checks policy and provenance, saves requests, and reconciles provider receipts. | A confirmed post, a pending delivery, or a recorded error. |
AgentMail receives customer messages. Naive’s outreach specialist interprets the request; local code validates the result, renders requested clips, and delivers replies.
New inbound mail → durable intake ledger and sender checks
Metadata-based recommendations, clarification, and structured clipping requests
Validate catalog IDs, original-source times, explicit tracks, and request limits
FFmpeg cuts requested source bounds; optional boxes follow recorded observations
Media QA, expiring opaque links, saved reply bodies, and delivery receipts
Return results to the original sender with source credit
Outreach belongs to the CEO’s team but is separate from the five video-analysis specialists. AgentMail credentials stay in the local worker; Naive receives bounded message and catalog data. Email requests do not enable social publishing. Live intake requires a separately authenticated worker and an online app for preview links. Local integration checks and a live metadata-only outreach recommendation have passed. Provider rate limits may delay requests; this check did not send an email or publish a post.
This page, the product overview, bundled assets, and the quiz illustration are static files in docs/html/.
No Python server, video models, database, or Naive credentials run on Cloudflare Pages. The project website is deployed at playlattice-project.pages.dev.
A shared Sites URL forwards requests through a tunnel to the Mac’s gateway. The gateway routes UI requests to Vite and analysis requests to FastAPI.
The app depends on the Mac and its services remaining online.
| Local Service | Port | Responsibility |
|---|---|---|
| Vite | 5173 | Live React UI during development. |
| FastAPI | 8000 | Upload, analysis, media, reviews, and production UI build. |
| Naive Integration | 8011 | Workflow feed, session activity, previews, and batch controls. |
| Sharing Gateway | 8002 | A single entry point for the shared app’s requests. |
Architecture describes the current prototype. It does not imply recognition accuracy, official basketball statistics, verified athlete identity, or guaranteed social delivery.
