Typed action
A defined command with a specific result that can be read back.
Product / the ticket flow
A support loop that can finish the work.
Axiōma connects the employee portal, Axel’s reasoning, enterprise infrastructure, and the employee’s laptop. Every run ends in a checked fix or an informed human handoff.
Ticket flow
- 01Portal
The employee opens a ticket.
The report starts in the portal. Axiōma attaches the context available for that employee, device, and prior history, rather than asking the report alone to explain the cause.
- 02Agent run
Axel routes by investigating.
Axel reads the ticket, chooses relevant read tools, and gathers evidence. The work of deciding what to try also reveals which system or team owns the issue.
- 03Infrastructure / device
The fix follows the problem.
For infrastructure, Axel uses an available connector. For a laptop issue, it sends a typed action to axel-cli over the device’s live connection.
- 04Closure / escalation
The outcome carries its evidence.
A fix is checked before closure. When no permitted fix is available, the ticket reaches IT staff with the transcript, observations, and proposed next step attached.
A deliberate order
Use the narrowest tool that can solve the problem.
Device remediation starts with typed actions. Computer-use is reserved for GUI-only paths. When the available action would make a policy decision, Axel escalates instead.
Computer-use
For the tail of GUI-only tools where no programmatic path exists.
Human handoff
A complete escalation when action is unavailable or inappropriate.
One system / three views
Clear work for every person in the loop.
Employee
Open a ticket, follow progress in plain language, and see what changed.
IT support
See the queue, inspect Axel’s evidence, and take over escalations.
Platform engineer
Define the connectors and device actions available to Axel.
Start a conversation