Feed
—
—
YTF System Map
One access guide for managers, agents, pipeline, data trust, and team handoff
Open first
Use this as the simple collection of YTF tools. The app is an AI-native operating layer around MES/DQMS context, source-control, daily handoff, and signed authority — not final accounting and not ERP replacement.
Trust
—
—Board KPI
Blocked
signed source authority requiredGA4
—
route usage onlyRole access map
Read the three first actions, then check whether board/plant KPI publication is allowed. If blocked, do not publish numbers.
Record owner-action acknowledgement first, then confirm source, site/scope, period, totals, signed reference, and approver before any material KPI use.
Use short role cards, turn Viber/LINE visible-window review into safe receipts, and route context from Gmail, Drive, OneDrive, Claim QA, and machine-health.
Run cloud packets first, keep Dell visible-window tasks separate, and record safe receipts before team handoff.
Page map
Source lanes
These lanes are context until a named operating record confirms the fact. Missing evidence stays null, never zero.
Current delegation
Agents prepare safe summaries and receipts. Human owners keep authority.
Cloud vs Dell operating model
YTF app, status APIs, scheduled reports, CI/CD, private feed publication, route usage analytics, and share-safe dashboards.
Visible-window Viber/LINE review, OneDrive metadata/offload checks, mobile/photo capture review, and operator handoff. Avoid heavy local indexing.
Set YTF_GA_MEASUREMENT_ID in Vercel production to learn which pages people use. GA4 never authorizes KPIs.
Board/plant KPI use requires signed source, site/scope, period, totals, reference, and approver. No agent self-approval.
Share this page with managers as the YTF access guide. For the actual source-to-decision SOP, open /how. For the copyable team update, open /brief.