Our definition starts with a separation of responsibilities.
In ORYH, the software's core job is to preserve enterprise facts: what was requested, which document changed and who approved each step. Authorized agents interpret published company rules, work through business exceptions and coordinate the actions that produce those facts.
This changes more than the interface. Adding answers, suggested fields or a chat window to an application does not by itself move business logic into agents. The architectural innovation behind ORYH is separating agent-executed business logic from the company's durable system of record. That is our test of whether an ERP is truly designed for agents.
| Model | How work happens | What to evaluate |
|---|---|---|
| AI assistance | AI summarizes, answers questions or suggests values while a person operates the application. | Answer quality, source evidence and the handoff to action. |
| Agentic workflows | An agent carries out a sequence of tasks, sometimes across existing systems. | Tool permissions, execution boundaries and recovery when a step fails. |
| ORYH's AI-native ERP | Software keeps the records; agents execute business logic under company rules. | Where logic executes, whose authority it uses, and whether records and safeguards remain independent of the agent. |
These models can coexist. The useful question is whether the system supports the business outcome you need, including corrections and exceptions.
Let the logic evolve. Keep the business facts.
- Software keeps the records
- Customers, products, quotations, timesheets, approval facts and change history. ORYH provides structured records and bounded operations, enforcing identity, permissions, required fields, amount consistency, valid transitions and audit constraints.
- Agents run the business logic
- Agents understand requests, read published company rules, identify missing information and propose how to handle commercial exceptions. An authorized workflow agent coordinates the next step. This is business execution, not just clicking an application for a person.
- People retain the authority
- The company sets goals, rules and access. Employees confirm proposed writes; authorized approvers make consequential decisions. An agent cannot invent company policy or grant itself more authority.
Agent-executed logic does not remove server-side validation or turn ORYH into an unrestricted database. Business judgment and orchestration can adapt; the boundary for writing facts must remain dependable. An agent saying "approved" is not a saved approval fact.
Rules, skills and historical records remain company-owned. A new agent or model still needs validation, but changing it does not erase the facts already recorded. Neither the records nor the execution model needs to depend on one proprietary agent interface.
People work with agents. Agents work with the ERP.
ORYH represents a headless direction for enterprise software: routine work moves from application-specific screens to the agent a person already uses. The ERP provides business capabilities, permissions, records and workflow rules behind that interaction.
The person owns the intent and the decision. The agent prepares and coordinates the work. ORYH determines which requested actions are accepted and preserves the resulting facts.
Human control remains visible. Administrators manage access, approvers review consequential decisions, and auditors inspect evidence. Headless describes how routine execution reaches the system; people still have responsibilities and control surfaces.
Agent choice belongs to the company and its users. ORYH supports compatible clients such as Codex, Claude Code, Hermes and OpenClaw. A company can use several clients against the same records. Other clients, including Claude Cowork, need an evaluated connection path; client compatibility and validation of a particular workflow are separate checks. See the agent connection guide.
Five questions to ask before letting an agent act.
Whose authority does the agent use?
Identify the employee and device behind a request. Check that changing the prompt cannot expand their permitted capabilities or records.
What becomes a company record?
Inspect the saved quotation, timesheet or purchase request. Verify that structured facts survive a new conversation or a different agent.
Where must a person confirm or approve?
Separate the agent's proposal, the employee's confirmation and the authorized approver's decision. Inspect the company's configured exception path.
Which rules govern a business action?
Try missing information, an unauthorized request and an invalid state transition. Confirm that the server enforces the applicable constraints.
Can the company reconstruct and recover the work?
Follow who changed what and which decision advanced the workflow. Test a retry or interruption and check for duplicate business actions.
Ask for a demonstration that includes a returned record or refused action. A successful path alone leaves important questions unanswered. ORYH describes these boundaries on its security and audit page and platform page.
Start with work your team recognizes.
A customer quotation
A salesperson asks for a renewal quotation. The agent reads customer, product, price and company-rule records, proposes the discount and exception path, and presents the complete quotation for confirmation. An authorized workflow agent coordinates approval. ORYH validates access and amount consistency, then preserves the lines, revisions, approval facts and order references. Interpretation and orchestration belong to the agent; the facts belong to the company's records.
Follow the customer quotation workflow →
A week of time and a manager's decision
An employee gives an agent the week's work. The agent prepares daily entries and asks the employee to review the whole period. After submission, the manager reviews the source record and approves or returns it using their own authorized access.
Adopt one bounded workflow first.
Choose a recurring process with a clear owner, known source records and an explicit approval policy. Project and professional services teams can start with quotations or timesheets. Bring a redacted example and define what should be accepted, returned, refused and traceable.
Evaluate broader ERP requirements separately: accounting, local tax obligations, payroll, inventory, migration and external delivery may require additional capabilities or integrations. A working quotation or timesheet flow demonstrates that process; replacing your entire ERP requires a wider assessment.
The enterprise adoption guide explains how to scope a pilot. The workflow overview lists current availability and agent scenario validation separately.
Common questions
How does agentic ERP relate to AI-native ERP?
Agentic ERP emphasizes agents taking action. AI-native ERP describes how the underlying system is designed for that work. Evaluate the actual records, permissions and execution model behind either label.
Does every employee have to use the same agent?
ORYH allows compatible, company-approved agents to share the same governed business system. Each employee still operates within their own access. Switching clients does not transfer another person's authority.
Can an agent approve its own work?
Approval authority comes from the company's workflow and role configuration. An agent can act for an authorized approver, but using an agent does not itself grant approval rights. Validate assigned-approver and separation-of-duty rules during setup.