YTF Agent Runbook
Cloud-first work order for agents, IT/data, and Dell edge review
Current run state
Release / alias check
Before sharing a new YTF feature, confirm whether this host is the custom domain or only a verified artifact alias. This prevents managers opening an older build while agents use a newer one.
Board / Plant / Manager lens
Use this before long dashboards. Board gets decision-grade questions, plant clears signed source authority, department managers make one owner action, and agents stay cloud-first.
Current goal rotation
One active YTF goal, one small production slice at a time. Do not mark the big goal complete until every gate is proven.
Autonomous decision room — do this next
Use this as the short control room before any broad dashboard, chat review, desktop/computer-use, or premium model run: one goal, one decision, one evidence gate, then one YTF output.
Autonomous goal stack
This is the CEO-agent control loop: what can keep running cheaply, what must wait for human authority, what source lane is being learned from, and which R&D module should move next.
Macro / micro data learning map
Use this to decide what YTF should learn next from company data. Macro lanes find patterns and questions; micro lanes produce one owner action, one packet, one module, or Not reported.
Loading data learning map…
Lean CEO agent model
Make the system cheaper and more sustainable: cloud checks first, Dell only when visible review is truly needed, and premium model work only for high-value decisions.
Cost control ladder — cheapest first
Use this before any desktop/computer-use or premium model run. The default YTF path is browser-only packet, status APIs, cloud metadata, then Dell only for exact visible windows.
Execution router — cheapest safe runner
Use this before computer-use or premium models. It maps each YTF source/task to cloud API, exact cloud watchlist, local-lightweight review, Dell visible window, or human gate.
Repeatable CEO-agent runtime
Use this as the operating contract for continuous work: pick the cheapest safe tier, move one useful module, and write a safe receipt before handing off.
Chat capture playbook
Every agent starts from the source contract. Use /chat for Viber/LINE safe receipts. Viber/LINE stay visible-window, context-only, and local-lightweight-first unless escalation is justified.
Source packet handoff
Use this before team sharing: /sources prepares the lane, /packets#packet-builder creates the safe packet locally, /brief copies the manager update, and /signoff remains required for KPI authority.
Claim QA quality bridge
Use this only for live claim queue status, corrective action, production trace, and closure routing. It shows protected summary status and manager actions; it never closes claims or approves evidence.
Copy-safe run receipt
Generated from live safe endpoints. Paste this into Operations Hub, Viber/LINE/email, or a Codex handoff as context only.
Run order for every YTF agent
- 1Open the map, then this runbook
Start at /map to understand the YTF surface collection, then use this page to execute the cloud-first order.
- 2Read safe status endpoints
Use delegation, cloud readiness, collector packets, chat receipts, source packets, receipts, Claim QA when quality or claims are relevant, GA4 config, and pipeline.
- 3Fix one small product or data-routing gap
Prefer cloud code, tests, docs, status APIs, and share-safe dashboards. Keep this Dell for visible-window review and light handoff only.
- 4Validate before handoff
Run the narrow gate first, then live validation after deploy.
npm run test:surfaceYTF_VALIDATE_LIVE_URL=https://ytf.supermega.dev npm run test:surface:liveYTF_BASE_URL=https://ytf.supermega.dev node tests/liveSmoke.mjs - 5Write the handoff where humans can see it
Update Operations Hub with the URL, commit, deploy proof, current blockers, and exactly what the team should do next.
Cloud vs Dell split
YTF app, status APIs, CI/CD, scheduled digests, private feed publication, GA4 route usage, and share-safe dashboards.
Use the laptop for visible-window Viber/LINE review, OneDrive offload checks, and operator photo review. Avoid heavy local indexing.
Set YTF_GA_MEASUREMENT_ID in Vercel production. GA4 measures page use only; it never approves production, sales, quality, or board KPIs.
Plant manager or source owner must confirm source, site/scope, period, totals, reference, and approver before any material KPI publication.
Allowed agent work
Agents can improve the app, create run receipts, summarize source status, and route work to owners.
Agents can prepare Gmail, Drive, OneDrive, iSolution manager packets, GA4, and collector workflows when connector access is authorized.
Blocked operations
No autonomous message sends. Approved chat captures are context and follow-up signals, not transaction authority.
Do not write to ERP, close claims, approve evidence, or publish board KPIs from an agent run.
Do not publish raw chat/email text, customer identity, claim evidence, private file locations, or credentials.
If a source is missing, stale, or unsigned, label it blocked or context-only. Never fill with zero unless the source says zero.
Current delegation queue
These cards come from the live delegation endpoint and are safe for routing, not for KPI approval.
Share this page with IT/data and any Codex/cloud worker before asking it to continue YTF work. For managers, start at /start. For source authority, use /signoff.