name: video-operations-setup description: Install the original video operations interface, run its retained processed retail sample, configure recipient providers privately and navigate its source modules.
Video operations setup
Read README.md, docs/get-started.md and docs/video-status.md. Start with make install and make dev. Use the private owner-code file for the recipient's new local state. Read docs/processed-sample.md. Confirm Home, nine trackers, the 45 recordings and the distinct Cosmos/dataset annotation layers. Choose Annual for the saved historical period.
Select the recipient company/account before provider, storage and runtime configuration. Use tools/configure.py with hidden input into an owner-only file outside source. The sample server clears ambient provider context, disables background processing and blocks provider networking. The connected server is an explicit separate command.
Read docs/video-setup.md for OpenAI managed execution, Modal workspace/billing identity, Qdrant, maintained PostgreSQL and separate source/executor brokers. Preserve all ownership, funding, approval, source-hash, clock and observation-admission gates. The Modal pilot requires the recipient's explicit workspace and actual owner billing identity. Model weights, private footage and provider grants stay with their owners.
Follow docs/workflows.md and docs/video-reference.md to the actual implementation. Keep publisher annotations and generated history distinct from model output, basket estimates distinct from till transactions and recorded playback distinct from live-camera qualification. Use make test for the network-fenced source contracts. Record precise local/provider verification before claiming an integration works.