o9

Classifies and gates o9 planning operations across versions, scenarios, solvers, and ERP releases.

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/MetaFloor-AI/metafloor-scm-plugin-openai --skill o9-metafloor-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: o9
Source: https://github.com/MetaFloor-AI/metafloor-scm-plugin-openai/tree/main/skills/platforms/planning/o9
Command: npx skills add https://github.com/MetaFloor-AI/metafloor-scm-plugin-openai --skill o9-metafloor-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Working in o9's Enterprise Knowledge Graph, a single edit can silently propagate across dependent measures, and a baseline overwrite or plan release to ERP is irreversible without a snapshot. This Skill gives an AI agent the operational judgment to classify every o9 action as read, reversible write, committing write, or destructive, and to gate consequential ones for human approval. ## Core Features & Use Cases - Operation classification matrix: Maps o9 operation families (measure edits, solver runs, scenario commits, version promotion, ERP release) to read/write/destructive gates with reclassification rules based on target version, scope, and snapshot state. - Edge-state and gotcha playbook: Covers 23 real failure modes such as graph propagation, empty spreading bases, shared version-independent measures, concurrent last-write-wins saves, and silent permission drops. - Recovery patterns: Decision tables for undoing bad commits via snapshots, offsetting commits, scenario discards, and ERP-side correction of released orders. - Use Case: Before running a supply solver into the baseline, the agent checks the target version and scope, takes a snapshot, routes a named approver, and re-reads the data to avoid overwriting concurrent planner work. ## Quick Start Ask the agent to run the o9 demand forecast into the baseline version and have it classify the action, take a snapshot, and request approval before executing.

Frequently Asked Questions about o9

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely run an o9 solver on the baseline version?

Confirm the target version and scope filter, take a snapshot or backup version first, get a named approver, and re-read the data before executing. A solver run is a replace over its whole scope, so without a snapshot the prior baseline values are unrecoverable.

What is the difference between simulating and committing an o9 scenario?

Simulating recomputes only inside the scenario and persists nothing shared, making it a safe read-class action. Committing writes the scenario deltas into the version's data as a one-way write, and committing into the baseline is destructive.

Can I undo a plan released from o9 to ERP?

No, a release cannot be undone from o9 because it creates real documents like planned orders and purchase requisitions in ERP. Recovery means canceling or correcting those documents in the receiving system and fixing the driving plan data so the next run does not re-release the error.

Why did my o9 measure edit affect numbers I never touched?

o9 is built on a knowledge graph, so editing a driver measure or IBPL rule re-derives every dependent measure along the relationships automatically. The blast radius is the dependency chain, not the single cell you edited.

When should I use Kinaxis or SAP IBP guidance instead of o9?

Use the Kinaxis skill for RapidResponse or Maestro planning, and the sap-ibp skill for SAP time-series or Response planning. The o9 skill applies only when the connected planning system is o9's Digital Brain and Enterprise Knowledge Graph.