HRDFT Centre · Research project

A.O.M.EArtificial Organisational Mindset Engine

The engine that gives an organisation an executive function that does not depend on headcount. A question is routed to the seat that owns the subject, that seat answers in one house format, and it names which other seat has to clear the answer before anything is acted on.

  • AchievedStatus
  • A deviceTarget result
  • Not for saleAvailability
  • Company-ownedHUBUINTEL PTY LTD

Explore the organisation

The A.O.M.E organisation chart.

One person in the chair, five departments, thirteen Artificial Employees. Tap any box to see what it owns, or follow an example question through the chart.

Achieved · in exclusive use inside HuBu-IntelTap a department or an employee, or follow a question
Thirteen Artificial Employees, five departments, one person in the chairA.O.M.E is organised like a company: five departments, each led by a chief officer with staff under it, all reporting to the Chair. A question goes to the department that owns the subject, another department clears the answer, and the Chair signs.
Follow a question through the chart:
  1. The Chair. Ahmed Rafik (HE01), Founder and Chief Executive Officer, a person.
  2. Business Development. Offers, the route to a paying client, and a business development officer for each of the four divisions. Zenith (Chief Business Officer, HAECBO02), Danielle (Ventures, HAECBO08), Helen (Consulting, HAECBO09), Vijay (Training, HAECBO10), Nadine (HRDFT Centre, HAECBO11).
  3. Finance. Cash, the derivation of every published figure, what a decision costs before it is taken, and grants and research incentives. Honey (Chief Financial Officer, HAECFO03), Mathias (Grants and R&D incentives, HAECFO12).
  4. Public Relations and Legal Compliance. What the house may claim in public, how it speaks, what a document must carry, and what has to be checked at the regulator’s own page. Govu (Chief Public and Law Officer, HAECPLO04), Serena (Public relations, HAECPLO13).
  5. Technology Development. What is built, whether it was verified, whether it can be rolled back, and the technical due diligence of every venture. Buildy (Chief Technical Officer, HAECTO05), Hugh (Venture due diligence, HAECTO15).
  6. Quality Assurance and Client Delight. Quality, complaints and the client’s experience. Every build is tested here, never by the employee who built it. Qmiley (Chief Quality and Delight Officer, HAECQDO07), Minh (Build testing, HAECQDO14).

At a glance

Project record.

Project
A.O.M.E, Artificial Organisational Mindset Engine. Also referred to as the HuBu-Intel Artificial Organisational Mind.
Status
Achieved. A working internal system, in operation and in exclusive use inside HuBu-Intel. Not a research hypothesis and not a published scientific result.
Target result
A device, in the working sense rather than the hardware sense: an engine that gives an organisation an executive function, with named seats by discipline, one governing instruction set, and registers that hold decisions between sessions.
When it counts as reached
When the engine runs an organisation’s executive work under rules it cannot break, with a person signing everything that leaves the building. A.O.M.E does that inside HuBu-Intel now.
Availability
A.O.M.E itself is not licensed, sold or offered as a service. A venture pack built on it, with ten artificial employees customised for the venture, is included with every HuBu-Intel venture, whether it is sold, licensed or partnered. None has been delivered yet.
Owner
HUBUINTEL PTY LTD
On this page
  1. 01 · The idea
  2. 02 · Why it exists
  3. 03 · What is achieved
  4. 04 · How it is built
  5. 05 · How it is governed
  6. 06 · Exclusive use
  7. 07 · What comes next

01 · The idea

An organisation thinks in seats, not in prompts. Most organisations use artificial intelligence as a tool that answers whoever holds it. A.O.M.E treats it as an organisational structure instead. The engine carries named executive seats, each with a declared speciality, each answering only in its own lane, and each obliged to name the seat that must review its work.

The result is what a small company cannot otherwise buy: a second and a third opinion, from a different discipline, on every decision, before the decision is taken.

A tool that answersA.O.M.E
One voice, whatever the subjectA seat per discipline, routed by subject
No memory of what the house decided last weekRegisters that carry decisions, open work and dated facts forward
Confidence indistinguishable from evidenceEvery claim labelled: fact, assumption, risk, or unknown
A human signs, publishes and lodges. Always.

02 · Why it exists

HuBu-Intel is delivered by one person. Every company that size carries the same problem: the founder is also the finance function, the legal function, the technical function and the commercial function, and each of those gets whatever attention is left at the end of the day.

A.O.M.E was built for that problem first. It does not replace a specialist adviser, and it does not pretend to be one. It gives the work a structure, a standard and a review step it would not otherwise get, and it keeps the record.

03 · What is achieved

  • Routing by discipline. A subject reaches the seat that owns it, and the answer names the seat that must clear it.
  • One governing instruction set. A single versioned set of numbered files holds the identity, the strategy, the seats and the protocols. One fact has one home.
  • Registers that survive the session. Open work, decisions, dated figures and minutes are written down, so the next day starts where the last one ended.
  • A standard of evidence. Approved is not executed, executed is not published, published is not verified. Each step is recorded separately.
  • Review by a second engine. The same instruction set is run on a second vendor’s model as an adversarial check, because a house that reviews only its own work grades its own work.

What it does not do: it does not decide, it does not sign, it does not publish, and it does not act outside the house. It has no authority over any person, and no decision about a person is made by the engine alone.

04 · How it is built

Thirteen artificial employees, five departments, one chair. A.O.M.E runs 13 artificial employees: five chief officers and eight staff, across five departments. Each has a written role, mission, KPIs, protocol and limits. A person chairs them: the Chief Executive Officer of HuBu-Intel.

DepartmentWhat it owns
Business DevelopmentOffers, the route to a paying client, and a business development officer for each of the four divisions.
FinanceCash, the derivation of every published figure, what a decision costs before it is taken, and grants and research incentives.
Public Relations and Legal ComplianceWhat the house may claim in public, how it speaks, what a document must carry, and what has to be checked at the regulator’s own page.
Quality Assurance and Client DelightQuality, complaints and the client’s experience. Every build is tested here, never by the employee who built it.
Technology DevelopmentWhat is built, whether it was verified, whether it can be rolled back, and the technical due diligence of every venture.

Artificial employees are characters built in software. They hold no office under the Corporations Act, carry no legal responsibility, and make no decision about any person.

The instruction set

Everything the seats are bound by lives in one versioned set of numbered files. Two rules do most of the work: a fact has exactly one home, so a figure cannot drift between files; and a figure that goes stale carries an expiry date and a check date.

Memory: registers, not recollection

Open work, decisions taken, defects found and the minutes of each meeting are written to registers. A session begins by reading them, so the engine answers from a record rather than from an impression.

Adversarial review

The instruction set is deliberately run on more than one vendor’s model, and each reviews the other’s work. In one six-round review, two instances running on different providers’ models cross-checked a governance document, and each found errors the other had missed.

05 · How it is governed

An engine that drafts a company’s decisions is only as safe as the rules it cannot break. Four limits sit above every instruction it is given:

  • Australian law. Nothing the engine produces may sit outside it.
  • The vault. Identifiers, bank details, credentials and private addresses are never written into a file, a prompt or a reply.
  • No structural change without the CEO. The engine may fix an error and tighten wording. It may not change the strategy, the structure or the offer.
  • Honesty. No invented fact, figure, section number or source. No softened finding.

Every claim carries a label: fact, assumption, recommendation, risk, decision required, or unknown. Nothing is published, signed, sent or lodged by A.O.M.E. It produces files. A person publishes them.

06 · Exclusive use

A.O.M.E is used by HuBu-Intel and by nobody else: to review the house’s own work before it is published, to prepare drafts for a person to read, amend and decide on, and to keep the record. It is not a product you can buy on its own, and no date is offered for one. It is not presented as a scientific result or a novel invention. It is an internal operating method that works, and that is the whole of the claim.

Enquiries about future availability are welcome and are answered honestly. Today, the only route is the venture pack that comes with a HuBu-Intel venture.

07 · What comes next

The organisational layer is built. The next work makes it independent of any one provider, deployable under tighter control, and teachable at scale, and puts it in front of people who can test it.

  • Full provider independence: the organisational layer stays stable while the underlying models change.
  • Controlled deployment: for organisations that need greater control over information, infrastructure, security and data sovereignty.
  • Centralised training at scale: approved knowledge and capability updates distributed consistently, subject to human authority.

The questions to test

We are not looking for anyone to endorse A.O.M.E. We want independent technical scrutiny on questions like these: can an organisational architecture improve coordination between specialised artificial employees; can knowledge and governance stay consistent across several AI providers; can performance be measured reliably and audited; and what would show that it does not?

Research partnerships.

Collaboration is open to researchers and organisations who work to the Centre’s method, including those whose work would show that a hypothesis does not hold.