Feed
—
bounded feed
YTF Cloud Collectors
One-page collector-packet queue for Gmail, Drive, OneDrive, Viber, LINE, Claim QA, and source signoff
Can agents run packets now?
Board KPI
Blocked
signed authority requiredGA4
—
route usage setupPackets
—
collector packetsFast rule
Use cloud APIs, scheduled reports, and bounded summaries before touching the Dell desktop.
Use the Dell for Viber/LINE visible windows, OneDrive offload checks, and capture review only.
Chats, email, Drive, OneDrive, and Claim QA are context until a named operating record confirms the fact.
No route usage is collected until the Measurement ID is set in Vercel production.
Daily collector digest
Loading copy-safe digest for Viber/LINE/email/team handoff.
Loading digest…
Collector receipts
Loading cloud control receipts and pending source-lane receipts.
Loading receipts…
Run order for cheaper agents
Use this sequence for local Ollama helpers, scheduled jobs, or cloud background workers.
Cloud collector packets
These can be summarized by cloud or connected-source agents, but still cannot publish KPIs.
Dell edge packets
These require exact visible windows and human review. No autonomous sending, no local message database extraction, no raw text publication.
Human gate packets
These need a manager/owner decision before operational use.
Required summary fields
Every candidate signal must carry these fields before it can be routed to a manager.
Never do
Next actions
Use /collectors before any source run. Machine consumers use /api/collector-packets/status first, /api/chat-receipts/status for Viber/LINE receipt drafting, and /api/source-rotation/status for the full contract. Then use /chat for visible-window receipts, /sources for routing, /packets for copy-safe source handoff templates, /brief for team handoff, /pipeline for cloud health, /analytics for GA4 setup, /authority for the board answer, and /signoff for manager source authority.