OPERATING CODE / A MARBELL PROJECT

The process is the program.

Teach the workflow once. Give agents the same rules, context, and checks. The system advances routine work, holds risky actions for people, and records what happened so its method can improve.

Explore the workspace

INTERACTIVE MODEL / THREE WORKFLOWS

Watch an operating loop.

A local simulation. No production systems or agent services are connected.

herdr/operatingcode/sec/identity-response
SIMULATIONLOCAL SESSION
/ ACTIVITY · SECURITY / SIEMRUNNING
01 / 03

A signal becomes a governed response.

Correlate sign-ins, cite the device evidence, and ask an analyst before containing a session.

    Try help for commands
    PLAYHEAD
    00 / 07
    01 — SELECT A WORKFLOW02 — INSPECT THE EVIDENCE03 — FOLLOW THE OUTCOME
    THE METHOD / AN OPERATING MODEL

    A process has a shape.
    Make it visible.

    State holds the information collected in this run. Guarded steps define what may happen next. A durable record keeps the reason, action, and correction available for review.

    01 / STATE

    Gather the records and context this run needs.

    02 / GUARDS

    Check policy and authority before a consequential action advances.

    03 / RECORD

    Keep evidence and decisions so a correction can be reviewed and replayed.

    SIGNALS FROM THE FIELD / SELECTED DISCUSSIONS

    The conversation,
    made executable.

    Independent discussions, selected by Marbell. Our response connects each idea to an executable workflow.

    01 / 03

    Rules that stay

    A new agent should meet the same rule as the last one.

    Instructions are a last resort.

    a “company operating system” or CompanyOS, designed for agent and human collaboration

    OPERATING CODE / RESPONSE

    The rule sits on the step it guards. Every caller meets the check, including a caller that goes straight to the action.

    Inspect the payables guard
    02 / 03

    A record of the run

    When an agent acts, the evidence and the decision have to remain legible.

    The model decides what to do next. The log ensures that the runtime can always reconstruct what has already happened.

    OPERATING CODE / RESPONSE

    The run records inputs, decisions, refusals, and effects. The case can be reviewed and resumed from what happened.

    Follow the response record
    03 / 03

    Agentic improvement

    A correction should help the next run without silently changing the rules.

    The reasoning model loops until the decision model says the answers meet the thresholds.

    Make sure to test your classifiers against human labels and don’t overfit.

    OPERATING CODE / RESPONSE

    A reasoning agent proposes a patch. A decision model judges bounded choices against recorded cases and labels. Code promotes or holds automatically.

    Inspect the autonomous rule change

    Marbell’s current Operating Code prototype runs a mocked refund workflow with guarded steps, a run record, and correction and replay. The three scenes above extend that method as an interactive model.

    Describe your workflow