← Back to Login

RAY Engine

Terms of Service — Effective immediately, retroactively, and in perpetuity.

Please read these terms carefully. Or don't — you're already using the app.

For Workers

Article 1: Clock In / Out

Tap your RFID card like you mean it. Weak taps, ghost taps, or asking your seatmate to tap for you while you are still on the commute are violations and will be logged, judged, and possibly discussed at the next KPI meeting.

Article 2: Tasks

"In Progress" does not mean "I opened the file once and then had lunch." Tasks should reflect the actual status of actual work. Lingering in In Progress for three weeks is a lifestyle choice, not a task status.

Article 3: Revisions

Each revision cycle reduces your Quality Score. The client is always right, even when they are objectively, demonstrably, cosmically wrong. You agree to revise gracefully and log the revision honestly.

Article 4: Leaderboard

You agree to be publicly ranked every Monday. Participation is mandatory. Jealousy is optional but understandable. Disputes about methodology will not be entertained before coffee.

Article 5: Violations

You may report violations anonymously through the Violations feature. Managers can still see who submitted the report. This is not a contradiction — it is a feature. You agreed to Article 2 about task statuses, so you understand how words work here.

Article 6: Announcements

You agree to read all WFH announcements before typing "are we WFH today?" in the group chat. RAY Engine has an Announcements feature. It is on the sidebar. It has been there the whole time.

For Managers

Article 1: Power

With great dashboard access comes great responsibility. Do not click Delete at 2 AM. If you do click Delete at 2 AM, do not message the developer at 2:01 AM.

Article 2: KPI Reports

You agree to actually read the KPI reports, not merely screenshot the graphs for presentations. The numbers have context. The context is in the table below the graph you cropped out.

Article 3: Finance

"Lainnya Expense" is not a valid long-term financial strategy. Transactions should have a real category. The Finance module supports up to fourteen categories. "Misc" is not one of them.

Article 4: Deadlines

You may extend project deadlines through the app. You may not extend them retroactively after the red badge has already appeared. The badge does not accept negotiations.

Article 5: Client Complaints

You agree to log client complaints honestly. Entering "Client is happy 😊" while the Kanban board is on fire and the delivery deadline was last month does not count. The Status field exists for a reason.

Article 6: Announcements

Use the Announcements feature in RAY Engine for official communications. Sending critical updates exclusively through WhatsApp and then being surprised when workers did not see them is a skill issue, not a worker issue.

General Terms

Article 7: Bugs

RAY Engine is provided as-is, built with Claude, coffee, and genuine intention. Bugs may exist. Report them politely and they will be fixed, eventually, probably before the next Monday leaderboard.

Article 8: Data

Your attendance records, task history, scores, and mild infractions are stored in Supabase. This was always the plan. Supabase stores it in PostgreSQL. PostgreSQL is a perfectly reliable database that has never done anything wrong.

Article 9: Amendments

These terms may be updated at any time. Updates will be announced via the Announcements feature — the one you agreed to read in Article 6. The irony is intentional.

Article 10: Governing Law

These Terms of Service are governed by common sense, reasonable professional behavior, and whatever Yoko decides on any given Friday. Fridays are non-negotiable.

By logging into RAY Engine, you agree to these terms.

By not logging in, you are marked Absent.

RAY Engine © 2026 — Built with ☕, Claude, and an unreasonable amount of Supabase SQL.

I Agree (reluctantly)