NOALYUT — Infrastructure Trust Layer (Platform)

Investor Memo (EN)

NDA Home Languages Private Materials Public

NDA Memo (≈5–7 pages). Use: investor / partner / grant conversations.

1. What NOALYUT is

NOALYUT is an Infrastructure Trust Layer (Platform) for verifiable work facts in the physical world.

We turn “chat/spreadsheet/paper” into a structured flow: Event → Evidence → Closure → Dispute. We do not surveil people in real time and we do not replace ERP/payroll. We make facts closeable under rules and defensible during disputes and audits.

2. Market pain

The expensive part is not data entry. The expensive part is conflict, downtime, audits, and liability risk.

3. “Everyone becomes a platform” helps us

Zoom and similar products structure intellectual work. Physical work still lacks a bottom trust layer.

NOALYUT sits below the UI platforms. We provide the source of truth for facts that ERP, contractors, customers, and audit/insurance can rely on.

4. Architecture logic (plain language)

4.1 Append‑only

No silent overwrites. If something changes, we add a patch and keep the full history visible.

4.2 Closure Gate

Closing is a state. You cannot “be closed” if required facts/evidence/role confirmations are missing.

4.3 Dispute as an object

A dispute becomes a structured case: scope, evidence, roles, status, outcome — instead of chat arguments.

5. MVP scope

MVP‑1 (first release):

  1. Morning roster + optional photo
  2. Evening hours (only for roster)
  3. Day close under rules
  4. Patch events (corrections without rewriting)
  5. Dispute object
  6. Exports: CSV / PDF / JPG (“as paper”)
  7. Audit log

MVP‑2: voice-to-hours + expanded RBAC/integrations after the core flow is stable.

6. Pilot measurement

Design: 7 days baseline → 2–4 weeks with NOALYUT.

Core KPIs:

Additionally: manual reconciliation time, number of conflicts, period closing speed.

7. Safety & legal defensibility (careful)

We do not claim “magic control”. Safety depends on real behavior and conditions.

But we can provide what matters in audits: a verifiable trail of procedures (e.g., TBM briefings, signatures, acknowledgements) so responsible parties can demonstrate due process and risk warnings.

8. Scale strategy (RU / IN / CN)

Large markets may have low ARPU. That is acceptable if the layer becomes a standard.

9. Openness / standardization (phased)

Becoming a standard does not require full openness on day one.

Pragmatic model: gain market lead first, then progressively publish specs/compatibility to grow an ecosystem around the trust layer.

10. Partner ask


Access notice: NDA materials. If you do not have access, please return to the previous page.