01The ask

OrbitronAI · Black box to glass box · 2026

One framework. Any industry. Same page.

Software stopped asking and started acting, and trust broke. OrbitronAI needed one north star for any industry, and one formula for every business requirement, so design, business, and engineering read the same sentence.

OrbitronAI · Nova suite/Framework + toolkit/Design framework

My role Solo: the Glass Box model, six pillars, Task Definition Formula, and the artifacts that carry it. Shaped with GTM, business, product, and design; aligned with the founders.
Outcome Adopted as OrbitronAI's shared language across all four product lines. Held against Anthropic and OpenAI's published guidance: aligned on principles, no equivalent formula found.
02The direction

Put the mechanism behind glass, not behind a wall.

Transparency plus intervention equals confidence. The framework builds it as a display case: a sealed base, a lit shelf, a clear surface. Read it top to bottom.

Black boxWorks, until it doesn't

A decision comes out. Nothing about how it got there is visible. When it's wrong, there's nowhere to look.

Glass boxWorks, and shows its work

The same decision comes out, but every part that produced it, the mechanism below, can be examined.

The surface · clearwhat the end user touches
ExecuteConfirm, undo, doneUpload · Accept · Cancel
OverseeScan, then drill inQueues · Dashboards · Reports
VerifyTrace it to the ruleEvery action · One thread
The worked shelf · litlit by what sits underneath
Experience340 / 500 to next tier
OperatorExecute and actTrust = Velocity
AnalystReview and judgeTrust = Evidence
The mechanism · sealedconfigured by admin, never hidden
Knowledgewhat it knows
Skillswhat it can do
Tools & Connectorswhat it can touch
Role Boundarieswhat it must never do

The box didn't get simpler. It got legible. And it never changes shape: a claim becomes a shipment, a supplier becomes a patient file. The industry changes the nouns. It never touches the glass.

Flow Nova · Logistics Comply Nova · GRC banking Lead Nova · Sales Asset Nova · Operations

The Task Definition Formula

Then one sentence writes the whole box down.

As a(n) Role , execute Action to get Outcome , using Skill , based on Knowledge , ensuring connectivity with Tools & Connectors , following Role Boundaries , optimizing for Business Metric , proving trust through Velocity / Evidence .

Sealed Visible Chosen once Derived, never written in

Change one bracket, nothing else moves. That is what lets the same shape capture business requirements in any industry, from client conversation to POC.

03Why & how
Why

The trust gap, measured

  • 65%trust AI to compare prices for them
  • 14%trust it to actually place the order
  • 40%of agentic AI projects predicted to fail, per Gartner
How · The thinking

Great AI agents are built like a new hire

A job: one clear thing to own/Tasks
A rulebook: what's allowed/Knowledge
Trained skills it's good at/Skills
Limited keys, nothing more/Tools & Connectors
Clear red lines/Role Boundaries
Trust that grows with the record/Experience
How

Trust is computed, never chosen

  • 01Faster clears at 75%
  • 02Cheaper clears at 75%
  • 03Safer needs 95%, always Evidence
  • 04Materiality caps the ceiling
How

One sentence, any number of agents

  • 01One sentence is one agent, always
  • 02The Tools slot can point at other agents
  • 03The orchestrator gets its own sentence
  • 04Trust rolls up on the weakest link
How · The journey

Built on a research wall, not a whiteboard

  • 01Five principles, each research-backed
  • 02Each translated to a user-lens analogy
  • 03The glass box unified the model
  • 04The formula made it operational
How · The UI framework

One surface that recomposes by role

Configure Assurance Admin, first run. Dashed until named, then locked.
Oversee Evidence Admin, returning. The cards report, not ask.
Execute Velocity Operator. Alerts, KPIs, a live work queue.
Verify Continuity Any role. One thread, traced to the rule.

Placement is chosen by posture, not by feature. Same components; the leading layer decides which comes forward.

Outcome

From framework to the company's shared language

  • 01Adopted across all four Nova product lines. Requirements travel in one shape, from client conversation to POC to agentic experience.
  • 02Five artifacts shipped: the story, the infographic, a 20-page formula reference, an interactive Story Builder, and the Experience Layer UI framework.
  • 03Three audiences, one sentence. Design reads artifacts to build, business reads questions to answer, and the accountable owner is named every time.
  • 04Held against Anthropic and OpenAI's published guidance. Aligned on principles; no published equivalent of the formula.
For reviewers

Short on time?

Ask anything: the role, the formula, the benchmark, the outcome.

Ask me anything
Proof · One of a kind

Held against Anthropic and OpenAI

  • 01Anthropic: simplicity, transparency, careful tool boundaries. Aligned on all three.
  • 02OpenAI: model, tools, instructions, guardrails, orchestration. Each has a home in the box.
  • 03The formula itself: no published equivalent found, anywhere.
The box didn't get simpler. It got legible.
Six principles · Two layers · One line of sight

Next case study