Skip to the brief
Iwan Bhakti SetiawanAI operating systems Demo workspace, sample data Start a brief

The assistant was never the hard part.

I build the layer between the model and the business: the channels it answers on, the tools it may touch, the rules it cannot break, and a record of every action it takes.

workspace sample data

Queue

    Current run

      Artefacts

        4 scheduled runs3 channels1 approval pending

        The work sits between the systems.

        1. quote

          Typed into the chat, then typed again into the sheet.

        2. supplier

          A price change that only one person in the company knows how to answer.

        3. report

          Rebuilt every Monday morning from the same four files.

        4. stock

          A list that lives in a photo on somebody's phone, and is wrong by Thursday.

        5. handover

          Everything above stops when that person takes leave.

        None of it is a model problem. It is a missing layer between the model and the company, and that layer is buildable.

        Live surface · sample data · not a customer system

        One task, end to end, and one place it stops.

        Brief

        Weekly operations summary

        From the sales sheet, the stock file and the WhatsApp thread. Monday, 06:30.

        Tools
        4
        Approvals
        1
        Output
        3 files
        1. 01

          Read the brief

          Three files and one thread, opened in their native formats.

          files.read
        2. 02

          Reconcile

          Match the totals. Two numbers disagree, and both are kept.

          sheet.diff
        3. 03

          Draft

          The summary in the format the ops group already reads.

          doc.render
        4. 04

          Check against the rules

          Nothing published that is not costed. Nothing invented to fill a gap.

          rules.check
        5. 05

          Ask you

          The run does not guess which of the two numbers is right. It stops here and waits.

          Run paused. Nothing leaves the building.

          human.approve
        6. 06

          Send and log

          Summary to the ops group, entry in the audit log, both reversible.

          wa.send · log

        The same run, as a record.

        Each line is written when the step completes. The approval line is written when you press it.

        Nothing has run yet.

          Seven parts. Miss one and the assistant stalls.

          Nothing here is a model. It is the ordinary engineering around one.

          01

          Channel

          WhatsApp Business, email, Telegram. The customer writes where they already write, and the business answers with one identity.

          one number, one inbox, one voice

          02

          Memory

          The facts your team repeats: prices, terms, names, how a complaint is handled. Written down once, so nobody re-explains them.

          read from files you own

          03

          Tools

          The systems it may touch, each with a written scope: read this sheet, draft this document, never send without approval.

          permission written next to the tool

          04

          Schedule

          Work that runs on a clock instead of a memory: the Monday summary, the daily price refresh, the month-end pack.

          runs without anyone pressing send

          05

          Guardrails

          What it may never do, who it must ask, and what has to be true before money or a customer is involved.

          stops on purpose, by design

          06

          Audit log

          Every action, every approval, every change, readable by the person who carries the risk. Not a chat history.

          who did what, and who said yes

          07

          Server

          Runs on a machine you control, with your keys and your backup. Self-hosted by default, so it survives the consultant.

          your hardware, your data

          An assistant with no channel is a demo. With no log, it is a liability.

          How a build goes

          Small, boring, and measured. The interesting part is what the business keeps at the end.

          1. Week 1

            One workflow, chosen because it eats the most repeatable hours. Not the whole company, and not a proof of concept nobody uses.

          2. Weeks 2-4

            It runs beside the person who owns the work, in the channel they already use, with a human check on anything that leaves the building.

          3. Week 5

            We read the log together and cut whatever did not earn its place. Fast, blunt, and cheaper than defending it.

          4. Handover

            The runbook, the keys, the access list, and the names of the two people who can stop it. You are not dependent on me to keep it running.

          Your server. Your keys. Your data.

          Self-hosted by default, so the system stays in your building after I leave, and so a shutdown of somebody's API is a Tuesday problem rather than the end of your operations.

          Next step

          Name one task your team repeats every week.

          Opens WhatsApp with your note already written. Nothing is sent until you press send there, and this site stores nothing you type.

          Based in
          Jakarta, GMT+7