YTF How It Works

One simple SOP for managers, agents, source data, and KPI authority

What is ytf.supermega.dev?

It is the YTF operating-intelligence layer: one simple place for source checks, owner actions, and manager handoff. It is not final accounting, not ERP replacement, and not board KPI authority by itself.

Feed

—

Trust

—

Board KPI

Blocked

signed authority required

GA4

—

usage only

Pipeline in 5 steps

Every source follows this same rule. Context can trigger follow-up, but only signed operating records can promote facts to board/plant KPI use.

1 · contextCollect source signals

Mobile photos, shift notes, Claim QA, Gmail, Drive, OneDrive, Viber, LINE, and machine-health become context only. Use /chat before Viber/LINE source routing.

2 · routeAssign owner

Collectors and delegation status route work to Production, Quality, IT/Data, Communications, or Codex Product.

3 · reconcileMatch signed record

Manager confirms source, site/scope, period, totals, signed reference, and approver role.

4 · reviewUse for decisions

Use /authority and /reliability after freshness, trust diagnostics, and source authority are present.

5 · blockStop unsafe use

No chat sends, no Viber/LINE database extraction, no ERP writeback, no claim closure, no KPI self-approval.

Source lanes and authority

What each person does next

Where to go

dailyManagers and CEO

Open /brief first. It gives today’s status, three first actions, and a copyable safe update.

sourceAgents and IT/Data

Open /collectors, use /chat for Viber/LINE receipts, then /api/delegation/status. Cloud work runs first; Dell visible-window review stays separate.

authorityProduction Manager

Open /signoff and attach the staged packet to the real signed operating record.

qualityQuality / Claim QA

Open Claim QA only for protected quality review. Do not publish customer identity, claim evidence, or close claims automatically.