Step one

What's your dna?

Pick an industry and see a living operating model.

Select your industry model
Step two

Now choose your lenses.

Different views over one model.

Operations

How the work actually runs — who owns what, in what order, under which rules.

Product

What gets built on top of it — the data, the screens, the API.

Technology

Where it runs and who can reach it.

Step three

One genome. Endless lenses.

Press Go and this fills in.

Step four

Now run it on something of yours.

Everything above is a model we wrote. Paste your own OpenAPI document and the reading is real: your endpoints, resolved to the acts and resources behind them. It happens in this tab. Nothing is uploaded.

Northwind Payments APIOAS 3.0Demo model

22 of 26 endpoints are governed. 4 gaps.

Payment 6 2 gaps
GET /v1/payments Payment Access
Operation
Payment.List
Rule
Payment Access
Required
Support.Agent, Finance.Admin
Scope
Organization
Audit
On write
POST /v1/payments Payment Authority
Operation
Payment.Create
Rule
Payment Authority
Required
Finance.Admin, Finance.Manager
Scope
Organization
Feature
payments_v2
Audit
Required
GET /v1/payments/{id} Payment Access
Operation
Payment.Read
Rule
Payment Access
Required
Support.Agent, Finance.Admin
Scope
Organization
Audit
On write
POST /v1/payments/{id}/capture Payment Authority
Operation
Payment.Capture
Rule
Payment Authority
Required
Finance.Admin, Finance.Manager
Scope
Organization
Feature
payments_v2
Audit
Required
POST /v1/payments/{id}/refund nothing governs this
Operation
Payment.Refund
Rule
none
Required
nobody — any caller the edge authenticates
Scope
unbounded
Audit
nothing is recorded

Not a weaker rule — no rule. Nobody decided this one was safe to leave open; it was never considered, and nothing in the stack was in a position to notice.

POST /v1/payments/{id}/void nothing governs this
Operation
Payment.Void
Rule
none
Required
nobody — any caller the edge authenticates
Scope
unbounded
Audit
nothing is recorded

Not a weaker rule — no rule. Nobody decided this one was safe to leave open; it was never considered, and nothing in the stack was in a position to notice.

Payout 3 1 gap
GET /v1/payouts Treasury Access
Operation
Payout.List
Rule
Treasury Access
Required
Finance.Admin
Scope
Organization
Audit
Required
POST /v1/payouts nothing governs this
Operation
Payout.Create
Rule
none
Required
nobody — any caller the edge authenticates
Scope
unbounded
Audit
nothing is recorded

Not a weaker rule — no rule. Nobody decided this one was safe to leave open; it was never considered, and nothing in the stack was in a position to notice.

GET /v1/payouts/{id} Treasury Access
Operation
Payout.Read
Rule
Treasury Access
Required
Finance.Admin
Scope
Organization
Audit
Required
Customer 5
GET /v1/customers Customer Access
Operation
Customer.List
Rule
Customer Access
Required
Support.Agent, Finance.Admin
Scope
Organization
Audit
On write
POST /v1/customers Customer Administration
Operation
Customer.Create
Rule
Customer Administration
Required
Finance.Admin
Scope
Organization
Audit
Required
GET /v1/customers/{id} Customer Access
Operation
Customer.Read
Rule
Customer Access
Required
Support.Agent, Finance.Admin
Scope
Organization
Audit
On write
DELETE /v1/customers/{id} Customer Administration
Operation
Customer.Delete
Rule
Customer Administration
Required
Finance.Admin
Scope
Organization
Audit
Required
PATCH /v1/customers/{id} Customer Administration
Operation
Customer.Update
Rule
Customer Administration
Required
Finance.Admin
Scope
Organization
Audit
Required
PaymentMethod 2
GET /v1/customers/{id}/payment-methods Customer Access
Operation
PaymentMethod.List
Rule
Customer Access
Required
Support.Agent, Finance.Admin
Scope
Organization
Audit
On write
POST /v1/customers/{id}/payment-methods Customer Administration
Operation
PaymentMethod.Create
Rule
Customer Administration
Required
Finance.Admin
Scope
Organization
Audit
Required
Invoice 6
GET /v1/invoices Billing Access
Operation
Invoice.List
Rule
Billing Access
Required
Finance.Admin, Billing.Clerk
Scope
Organization
Audit
On write
POST /v1/invoices Billing Authority
Operation
Invoice.Create
Rule
Billing Authority
Required
Finance.Admin
Scope
Organization
Audit
Required
GET /v1/invoices/{id} Billing Access
Operation
Invoice.Read
Rule
Billing Access
Required
Finance.Admin, Billing.Clerk
Scope
Organization
Audit
On write
PATCH /v1/invoices/{id} Billing Authority
Operation
Invoice.Update
Rule
Billing Authority
Required
Finance.Admin
Scope
Organization
Audit
Required
POST /v1/invoices/{id}/pay Payment Authority
Operation
Invoice.Pay
Rule
Payment Authority
Required
Finance.Admin, Finance.Manager
Scope
Organization
Feature
payments_v2
Audit
Required
POST /v1/invoices/{id}/send Billing Authority
Operation
Invoice.Send
Rule
Billing Authority
Required
Finance.Admin
Scope
Organization
Audit
Required
Dispute 3
GET /v1/disputes Dispute Handling
Operation
Dispute.List
Rule
Dispute Handling
Required
Support.Lead, Finance.Admin
Scope
Organization
Audit
Required
GET /v1/disputes/{id} Dispute Handling
Operation
Dispute.Read
Rule
Dispute Handling
Required
Support.Lead, Finance.Admin
Scope
Organization
Audit
Required
POST /v1/disputes/{id}/evidence Dispute Handling
Operation
Dispute.Evidence
Rule
Dispute Handling
Required
Support.Lead, Finance.Admin
Scope
Organization
Audit
Required
Unresolved 1
GET /v1/reports/latest resource or act?
Path
/v1/reports/latest
Why
resource or act?

The last segment could be a sub-resource or an act, and nothing in the document decides which.

x-dna:
  operation: resource.act

This is the first rung of API Operations, which is what the rest of the ladder looks like.