Deck (EN)

Slide 1. Title

NOALYUT
Infrastructure Trust Layer (Platform) for Verifiable Work Events

Evidence → Closure → Dispute. Portable. Auditable. Human‑first.

Slide 2. Core problem

• Work facts are scattered across chats/spreadsheets/paper
• Evidence is missing or disconnected
• Edits happen silently
• Day/period closing is delayed
• Disputes and audits lack a reliable record

Slide 3. Root cause

The issue is usually not people, but process: there is no simple flow record → confirm → close.

Without closure, facts remain negotiable forever.

Slide 4. Why now

• Compliance and liability pressure is rising
• Platforms normalize “everything is an event”
• Physical work still runs on Excel + chat

Slide 5. What NOALYUT is

NOALYUT is a verifiable fact layer for physical work.

• Not surveillance, not micromanagement
• Not an ERP/payroll replacement
• Yes: facts + evidence + closing + transparent corrections + structured disputes

Slide 6. Daily flow (MVP)

1. Morning: roster declared + optional presence proof
2. Evening: hours (only for rostered workers)
3. Closure: day close under rules

Slide 7. Principle 1 — Append‑only

No silent overwrites. If something changes, we add a patch and preserve history.

Critical for trust, audits, and legal defensibility.

Slide 8. Principle 2 — Closure Gate

Closure is a state transition, not a checkbox.

• Missing required facts/evidence → cannot close
• Missing required role confirmations → cannot close

Slide 9. Principle 3 — Dispute as object

A dispute is not chat drama. It is a structured object:

• scope
• evidence requested
• roles
• status
• outcome

Slide 10. Data moat

Value is not volume. Value is closed, contextualized facts:

• day_closed exists
• patch history is known
• disputes are explicit
• rules are pinned in time

Slide 11. Platform logic

We do not compete with Zoom/ERP on the UI layer.

NOALYUT is the trust substrate that any system can build on top of.

Slide 12. Business model

• Pilots: low friction entry (discipline ↔ price)
• Production: subscription + strict/compliance modes + integrations
• Later: finance/insurance powered by reduced risk

Slide 13. GTM

• Phase 1: Korea-first pilots
• Phase 2: large markets (RU/IN/CN) via low‑friction shells
• Phase 3: standard + financial layer

Slide 14. Why big players won’t kill us

Big platforms optimize productivity and collaboration.

We optimize proof, closure, auditability — the layer they avoid due to liability.

Slide 15. Ask

• Pilot partners: 1–3 sites for 2–4 weeks
• Agree on minimum rules (closure / patch / dispute)
• Baseline “before/after” metrics