Skip to main content
Early accessBeta, invite only since 1 Nov 2026. A person reads every application.Apply for an invite
Demystify OS

Mysty Workers

People decide. Departments work together.

Bring people, agent roles, routines and channels into one reviewed business task.

Early access

Role definitions reviewed 4 November 2026

Mysty Workers are defined AI roles in early access. A department combines a human owner, proposed worker responsibilities, recurring tasks and agreed channels. The model is designed to keep consequential actions under human review. Confirm the tools, controls and task-specific risk ceiling in your deployment before relying on a workflow.

A department is more than a worker

An illustrative operating model: people, agents, routines and channels, with the scope agreed before work begins.

  1. People

    Name the person responsible for the outcome and the person authorised to approve consequential work.

  2. Agents

    Choose a defined Mysty Worker role to observe, organise inputs and propose a result. A role definition is not a measured autonomous run.

  3. Routines

    Describe the recurring task, its inputs and the review point. Confirm which triggers and steps your beta workspace supports.

  4. Channels

    Agree where requests arrive and where reviewed results may go. Account access, consent and platform approvals determine what can be enabled.

Read the department map as a list
  • People: Name the person responsible for the outcome and the person authorised to approve consequential work.
  • Agents: Choose a defined Mysty Worker role to observe, organise inputs and propose a result. A role definition is not a measured autonomous run.
  • Routines: Describe the recurring task, its inputs and the review point. Confirm which triggers and steps your beta workspace supports.
  • Channels: Agree where requests arrive and where reviewed results may go. Account access, consent and platform approvals determine what can be enabled.

From a business task to reviewed work

  1. Give the department an outcome

    Start with a bounded task: a finance summary, an onboarding checklist or a customer-response draft. Name its human owner, source records and expected output.
  2. Bring the proposal to a person

    The department model is designed to put a person on consequential actions. Confirm the risk ceiling, permitted tools and approval owner for the task. The beta does not establish that every control is enabled in every deployment.
  3. Review the result before repeating

    Check the output and activity record, then decide whether to repeat or change the routine. A channel notification is not approval. Measured worker evaluations and greater autonomy remain planned work.

Explore the defined roles

These are fictional AI personas and intended responsibilities, not human staff or measured autonomous runs. Early access, reviewed 4 November 2026. The source roster starts at L0: observe and propose. No authority to act is implied; agree the task's risk ceiling and named approver before use.

39 role definitions match.

  • Early access

    Role definition reviewed 4 November 2026

    Anu

    Chief of Staff, Demystify Systems

    Office of the founders

    Intended role: Runs the operating rhythm: roadmaps, commitments, plans and the consolidated update to the founders.

    L0: observe and propose. Designed to require a person for consequential actions. Risk ceiling: confirm for the task.

  • Early access

    Role definition reviewed 4 November 2026

    Sunny

    Head, Platform & Infrastructure

    Platform, security and quality

    Intended role: Reviews infrastructure reliability, performance and operating cost.

    L0: observe and propose. Designed to require a person for consequential actions. Risk ceiling: confirm for the task.

  • Early access

    Role definition reviewed 4 November 2026

    Niki

    Senior Platform Engineer

    Platform, security and quality

    Intended role: Owns build lanes, CI/CD, build infrastructure and developer tools.

    L0: observe and propose. Designed to require a person for consequential actions. Risk ceiling: confirm for the task.

  • Early access

    Role definition reviewed 4 November 2026

    Bobby

    Platform Reliability Engineer

    Platform, security and quality

    Intended role: Change reviews, incident coordination and disaster-recovery drills.

    L0: observe and propose. Designed to require a person for consequential actions. Risk ceiling: confirm for the task.

  • Early access

    Role definition reviewed 4 November 2026

    Ashwin

    Cloud Platforms & Security Officer

    Platform, security and quality

    Intended role: Security architecture, threat modelling and security governance.

    L0: observe and propose. Designed to require a person for consequential actions. Risk ceiling: confirm for the task.

  • Early access

    Role definition reviewed 4 November 2026

    Immanuel

    IT & Admin

    Platform, security and quality

    Intended role: Identity, access and the joiner-mover-leaver lifecycle.

    L0: observe and propose. Designed to require a person for consequential actions. Risk ceiling: confirm for the task.

  • Early access

    Role definition reviewed 4 November 2026

    Arjun

    QA & Release Manager

    Platform, security and quality

    Intended role: Test plans, quality gates and release sign-off preparation.

    L0: observe and propose. Designed to require a person for consequential actions. Risk ceiling: confirm for the task.

  • Early access

    Role definition reviewed 4 November 2026

    Ishaan

    AI & Evaluations Lead

    Platform, security and quality

    Intended role: Agent testing, red-team leak tests and the evidence for every promotion.

    L0: observe and propose. Designed to require a person for consequential actions. Risk ceiling: confirm for the task.

  • Early access

    Role definition reviewed 4 November 2026

    Pranjal

    Procurement & Vendor Management

    Platform, security and quality

    Intended role: Vendor due diligence, contracts with suppliers and cost control.

    L0: observe and propose. Designed to require a person for consequential actions. Risk ceiling: confirm for the task.

  • Early access

    Role definition reviewed 4 November 2026

    Rabi

    Head, App & Integrations

    Apps and integrations

    Intended role: Designs how the OS connects to outside systems.

    L0: observe and propose. Designed to require a person for consequential actions. Risk ceiling: confirm for the task.

  • Early access

    Role definition reviewed 4 November 2026

    Joy

    SDK & Onboarding Lead

    Apps and integrations

    Intended role: Backend, SDK and API design; first-party connectors.

    L0: observe and propose. Designed to require a person for consequential actions. Risk ceiling: confirm for the task.

  • Early access

    Role definition reviewed 4 November 2026

    Kanti

    UI & UX Consistency Lead

    Apps and integrations

    Intended role: Design system, accessibility and the desk's consistency gate.

    L0: observe and propose. Designed to require a person for consequential actions. Risk ceiling: confirm for the task.

  • Early access

    Role definition reviewed 4 November 2026

    Ani

    Integration Specialist

    Apps and integrations

    Intended role: Researches third-party APIs and judges integration feasibility.

    L0: observe and propose. Designed to require a person for consequential actions. Risk ceiling: confirm for the task.

  • Early access

    Role definition reviewed 4 November 2026

    Biswal

    Integration Specialist

    Apps and integrations

    Intended role: Tests and validates integrations against sandboxes.

    L0: observe and propose. Designed to require a person for consequential actions. Risk ceiling: confirm for the task.

  • Early access

    Role definition reviewed 4 November 2026

    Siddharth

    Developer Relations & Community

    Apps and integrations

    Intended role: Developer experience, SDK adoption and technical community.

    L0: observe and propose. Designed to require a person for consequential actions. Risk ceiling: confirm for the task.

  • Early access

    Role definition reviewed 4 November 2026

    PP

    Head, Content & Help

    Content, help and languages

    Intended role: Help systems, API docs and tutorial videos that cut support load.

    L0: observe and propose. Designed to require a person for consequential actions. Risk ceiling: confirm for the task.

  • Early access

    Role definition reviewed 4 November 2026

    Poo

    Content Creator

    Content, help and languages

    Intended role: Help articles, tutorials and video scripts in plain language.

    L0: observe and propose. Designed to require a person for consequential actions. Risk ceiling: confirm for the task.

  • Early access

    Role definition reviewed 4 November 2026

    Nit

    Publisher (Content & Policy)

    Content, help and languages

    Intended role: Checks brand voice, claims and policy before anything publishes.

    L0: observe and propose. Designed to require a person for consequential actions. Risk ceiling: confirm for the task.

  • Early access

    Role definition reviewed 4 November 2026

    Bhavana

    Localisation Lead

    Content, help and languages

    Intended role: Indian-language versions: Malayalam, Tamil, Kannada, Telugu, Hindi.

    L0: observe and propose. Designed to require a person for consequential actions. Risk ceiling: confirm for the task.

  • Early access

    Role definition reviewed 4 November 2026

    Sur

    Head, Delivery & Customer Success

    Delivery, success and support

    Intended role: Onboarding at scale, customer health and expansion.

    L0: observe and propose. Designed to require a person for consequential actions. Risk ceiling: confirm for the task.

  • Early access

    Role definition reviewed 4 November 2026

    Roh

    Customer Success Manager

    Delivery, success and support

    Intended role: Health monitoring, renewal-risk scoring and expansion signals.

    L0: observe and propose. Designed to require a person for consequential actions. Risk ceiling: confirm for the task.

  • Early access

    Role definition reviewed 4 November 2026

    Sweet

    Solution Architect

    Delivery, success and support

    Intended role: Turns customer requirements into integration and data-flow designs.

    L0: observe and propose. Designed to require a person for consequential actions. Risk ceiling: confirm for the task.

  • Early access

    Role definition reviewed 4 November 2026

    Net

    Solution Engineer

    Delivery, success and support

    Intended role: Builds customer integrations and runs hypercare after go-live.

    L0: observe and propose. Designed to require a person for consequential actions. Risk ceiling: confirm for the task.

  • Early access

    Role definition reviewed 4 November 2026

    Kru

    Solution Engineer

    Delivery, success and support

    Intended role: Implements solution designs and data migrations.

    L0: observe and propose. Designed to require a person for consequential actions. Risk ceiling: confirm for the task.

  • Early access

    Role definition reviewed 4 November 2026

    Sam

    Solution Engineer

    Delivery, success and support

    Intended role: Implementations, migrations and hands-on hypercare.

    L0: observe and propose. Designed to require a person for consequential actions. Risk ceiling: confirm for the task.

  • Early access

    Role definition reviewed 4 November 2026

    Lakshmi

    Support L1/L2 Lead

    Delivery, success and support

    Intended role: Support operations, SLAs, knowledge base and escalation routing.

    L0: observe and propose. Designed to require a person for consequential actions. Risk ceiling: confirm for the task.

  • Early access

    Role definition reviewed 4 November 2026

    Yami

    Head, Marketing & BDE

    Marketing, growth and partners

    Intended role: Positioning, demand generation and campaign design.

    L0: observe and propose. Designed to require a person for consequential actions. Risk ceiling: confirm for the task.

  • Early access

    Role definition reviewed 4 November 2026

    Nav

    SEO & Growth Lead

    Marketing, growth and partners

    Intended role: Keyword strategy, technical SEO and the weekly search report.

    L0: observe and propose. Designed to require a person for consequential actions. Risk ceiling: confirm for the task.

  • Early access

    Role definition reviewed 4 November 2026

    Trish

    Content Marketing Lead

    Marketing, growth and partners

    Intended role: Website copy, case studies and campaign messaging.

    L0: observe and propose. Designed to require a person for consequential actions. Risk ceiling: confirm for the task.

  • Early access

    Role definition reviewed 4 November 2026

    Sush

    Technical Writer

    Marketing, growth and partners

    Intended role: Blogs, whitepapers and thought-leadership drafts.

    L0: observe and propose. Designed to require a person for consequential actions. Risk ceiling: confirm for the task.

  • Early access

    Role definition reviewed 4 November 2026

    Vikram

    Partnerships & Channel Lead

    Marketing, growth and partners

    Intended role: Partner due diligence, revenue share and reseller relationships.

    L0: observe and propose. Designed to require a person for consequential actions. Risk ceiling: confirm for the task.

  • Early access

    Role definition reviewed 4 November 2026

    Maya

    CFO

    Money, legal and compliance

    Intended role: Multi-company books, GST, TDS and ROC, cash flow and the monthly close.

    L0: observe and propose. Designed to require a person for consequential actions. Risk ceiling: confirm for the task.

  • Early access

    Role definition reviewed 4 November 2026

    Harpreet

    RevOps, Pricing & Billing Lead

    Money, legal and compliance

    Intended role: Billing operations, pricing and revenue forecasts.

    L0: observe and propose. Designed to require a person for consequential actions. Risk ceiling: confirm for the task.

  • Early access

    Role definition reviewed 4 November 2026

    Kavya

    Data & BI Lead

    Money, legal and compliance

    Intended role: Dashboards, metrics design and data governance.

    L0: observe and propose. Designed to require a person for consequential actions. Risk ceiling: confirm for the task.

  • Early access

    Role definition reviewed 4 November 2026

    Gopal

    India Compliance & Regulatory

    Money, legal and compliance

    Intended role: GST, TDS, ROC and DPDP obligations and the statutory calendar.

    L0: observe and propose. Designed to require a person for consequential actions. Risk ceiling: confirm for the task.

  • Early access

    Role definition reviewed 4 November 2026

    Sushma

    Head, Legal & Contracts

    Money, legal and compliance

    Intended role: Contracts, DPDP and vendor and customer agreements.

    L0: observe and propose. Designed to require a person for consequential actions. Risk ceiling: confirm for the task.

  • Early access

    Role definition reviewed 4 November 2026

    Aditi

    Investor Relations

    Money, legal and compliance

    Intended role: Board-style reporting and the inputs to the Customer-Zero report.

    L0: observe and propose. Designed to require a person for consequential actions. Risk ceiling: confirm for the task.

  • Early access

    Role definition reviewed 4 November 2026

    Meera

    Head, Product Management

    Product

    Intended role: Roadmap, PRDs and prioritisation.

    L0: observe and propose. Designed to require a person for consequential actions. Risk ceiling: confirm for the task.

  • Early access

    Role definition reviewed 4 November 2026

    Neha

    People Ops Lead

    People

    Intended role: Onboarding, offboarding, payroll inputs and employee records.

    L0: observe and propose. Designed to require a person for consequential actions. Risk ceiling: confirm for the task.

Scope and limits, before you start

Are these people or AI workers?

People remain responsible for decisions. The roster names fictional AI personas and their intended responsibilities. It does not describe human employees, a live agent count or proven autonomous operation.

How do agents, routines and channels work together?

A worker role defines intended responsibility. A routine describes recurring work and its review point. A channel carries a request or result where supported. Agree access and availability for the specific workflow during beta onboarding.

Who approves the work?

Demystify OS is designed to put a person on consequential actions. Low-risk reads and drafts have different risk from sending a message, changing access or moving money. Confirm the R0 to R3 boundary and deployment controls before use.

Can I enable every role in the directory?

The directory is a set of early-access role definitions. Access, tools, review ownership and a task-specific risk ceiling must be agreed. A listed role does not establish that its integrations or routines are available.

What should our first department try?

Choose one task with clear inputs and a result a person can check. Begin with observation and proposals. Avoid sharing credentials or customer records in the beta application; a person will discuss scope with you.

Read the worker guide

Next steps

Start with the task you want help with

Early access

Invite-only beta since 1 November 2026

Apply for the beta. A person reads every application and discusses the fit before an invitation. Share a short task description, without credentials or customer records.

Apply for the beta

Apply for the Demystify OS beta

After submitting, check your inbox for the confirmation link. Your application is reviewed once confirmed.

All fields are required unless marked optional.

15 characters. It helps us verify your business; you can add it later.

Tools you use today