docs(do-arm): HIRO Automation is OGAR's DO arm + the lossless-DO rule

[AdaWorldAPI]

What & why

"Can we lift actionable semantics from OGIT/MARS (HIRO)?" — yes, and the mapping is near-exact. The MARS import lifted the structural arm (A→R→S→M Classes); the OGIT Automation domain is HIRO's actuator vocabulary — the behavioral arm the structural import left on the table.

Read the NTO/Automation/entities/* TTLs directly (KnowledgeItem, ActionHandler, ActionCapability, ActionApplicability, Trigger, Intent, AutomationIssue, History, Variable): they map near-1:1 onto OGAR's DO arm (ActionDef / ActionInvocation / KausalSpec), and HIRO is a production, externally-validated instance of it.

The lossless-DO rule (the important answer)

A DO compiler is lossy when it flattens behavior into one target (a DDL DEFINE EVENT … WHEN … THEN). Behavior has three irreducible slices — identity (Class), contract+lifecycle (ActionDef + the StateMachine/UnifiedStep interface), executable body (adapter) — joined by classid.

DO is lossless iff the ActionDef points to the body (content-addressed) instead of compressing it into DDL — I-VSA-IDENTITIES applied to the DO arm. Export = ActionDef manifest (typed SoA, wire-truth per the Firewall) + an opaque payload table + ClassView. Never DDL-inline (that drops the lifecycle / guard-failure modality / SLA / the ActionDef÷ActionInvocation split).

HIRO already IS this shape: KnowledgeItem carries the contract as relations + lifecycle attrs, and knowledgeItemFormalRepresentation is the opaque body the schema references but never parses. ActionHandler connects Configuration (= auth_store 0x0B01) — so the DO arm and the auth/RBAC arm meet at ActionHandler. AutomationIssue generates History is literally "state history IS the version log."

Files

• docs/HIRO-DO-ARM-LIFT.md — the principle, the export shape, the full entity→ActionDef/ActionInvocation/KausalSpec mapping table, a worked KnowledgeItem → ActionDef example, and the do_arm producer plan.
• .claude/board/EPIPHANIES.md — E-HIRO-IS-OGAR-DO-ARM.

Status / fence

The mapping is a FINDING about shape ([G], grounded in the TTLs). The executable-equivalence claim — that a lifted ActionDef → adapter → execute reproduces the KI's behavior — stays CONJECTURE until PROBE-OGAR-DO-ARM-LIFT is green (same falsification discipline as PROBE-OGAR-RBAC-AUTHORIZE). Docs-only; no code, no producer brick in this PR.

🤖 Generated with Claude Code

---

Generated by Claude Code

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.