Axiom Blueprint
Axiom Blueprint · Kuching, Sarawak

AI that does the work. You keep control.

A Sarawak-based AI and software practice. We build the workflows, software, and content systems that carry real work — operated under human-in-loop authorisation, with the discipline of a security practice, for Malaysian enterprises, GLCs, and government.

Kuching · live
MYT
Session
HH:MM:SS
A practice, not a platform

Systems that carry live work — not pilots, not demos.

Axiom Blueprint is a small practice that builds AI into the work organisations actually do — the onboarding chain, the invoice run, the reporting pack, the content calendar. Systems that carry live work, that a team can operate without us, and that fail safely when they fail.

We have spent years operating and assessing systems that other people depend on, in regulated environments where a failure is not a rounding error. That experience shapes how we deploy AI: we have seen what happens when software is trusted further than it has earned. So every agent we ship is scoped, evaluated against real cases, logged, and reversible — and no action that touches a real system happens without structured authorisation.

Claude is the foundation. Axiom is the practice. The discipline is the deliverable — every time.

BriefThe task, the scope, the rulesAI agents do the workScoped · evaluated · reversiblescope →execute →check →logA human authorisesNothing touches a real system without a gateAudited outcomeThe work, done — with a record of every step
How we work

The AI does the work. A person signs it off.

A brief goes in. Agents do the reading, the drafting, the repetitive execution — scoped, evaluated, and reversible. But nothing touches a real system without a human authorising it, and every step is logged. What you get back is the work, done — with a record you can audit.

HOW THE WORK RUNS

One manager agent runs the projects. A person makes the calls.

Scroll through the floor, or pick a card. Change the time of day to see who is in. Agents never fake documents or move money without a person.

  1. MANAGER → PROJECT AGENTS

    The owner talks to one manager agent. It hands the work to project agents, one per project, and to an assistant for each team member.

    > manager → build: slice C

HOW WE KEEP AI UNDER CONTROL

The checks are part of how we work.

Four layers sit under the work. Pick one to see what it covers.

  1. WHO ASKED, WHAT WAS DONE

    Each job is written down: who asked for it, what was done and what was checked.

    WHAT IT COVERS

    • Who asked and what was done
    • Review results kept with each release
    • Full change history kept
How we operate
“Every action that touches a real system requires structured authorisation. Every output carries an evidence chain.”
Frameworks the work runs on
Human-in-loop authorisationEvidence chain-of-custodyEval harness per agentModel Context ProtocolTyped tool contractsPDPA 2010 mappingMAMPU IT governanceReversible by defaultOWASP Top 10 (2021)Human-in-loop authorisationEvidence chain-of-custodyEval harness per agentModel Context ProtocolTyped tool contractsPDPA 2010 mappingMAMPU IT governanceReversible by defaultOWASP Top 10 (2021)
  • Sdn. Bhd. registered in Malaysia
  • 200601010198 (729948-V)
  • Built on Anthropic's Claude models

Brief us on scope. We respond personally within two business days.