{
 "about": "Knowledge catalog of https://www.automatiqa.io - everything the lab has published, as structured data, generated from the live site. Model-facing index: https://www.automatiqa.io/llms.txt.",
 "url": "https://www.automatiqa.io/catalog.json",
 "dateModified": "2026-10-18",
 "organization": {
  "name": "Automatiqa Lab",
  "url": "https://www.automatiqa.io/",
  "description": "Automatiqa Lab is a one-person open-source lab run by Aleks Sidorecs. It is not a company, a consultancy, an agency or a nonprofit, it has no employees and it sells nothing. It is unrelated to Automata, Automatiq Labs, Automatika and any other similarly named organisation. Founded 2025. Aleks Sidorecs is Global Head of Supply Chain at ED&F Man Commodities (Volcafe Business Unit); the lab is his own work and is not a Volcafe project.",
  "founder": {
   "name": "Aleks Sidorecs",
   "url": "https://www.sidorecs.com/about/",
   "catalog": "https://www.sidorecs.com/catalog.json"
  }
 },
 "changelog": {
  "url": "https://www.automatiqa.io/changelog/",
  "feed": "https://www.automatiqa.io/changelog/rss/"
 },
 "projects": [
  {
   "name": "Supply Chain Operations Planning & Execution in Commodities (SCOPEC)",
   "url": "https://www.automatiqa.io/scopec/",
   "summary": "SCOPEC is a supply chain operations planning and execution tool for commodities: one planning kernel runs S&OP and S&OE on the same data model, commodity families live as data profiles, and agents act on exceptions under an autonomy ladder they earn.",
   "status": "In development 20%",
   "license": "Apache-2.0",
   "repository": "https://github.com/automatiqa-lab/scopec",
   "n8n_templates": [],
   "published": "2026-10-11",
   "updated": "2026-10-18",
   "changelog": "https://www.automatiqa.io/scopec/#log-title",
   "sections": [
    {
     "heading": "Commodity planning lives between two kinds of software",
     "url": "https://www.automatiqa.io/scopec/#commodity-planning-lives-between-two-kinds-of-software"
    },
    {
     "heading": "One kernel, two horizons, commodity families as data",
     "url": "https://www.automatiqa.io/scopec/#one-kernel-two-horizons-commodity-families-as-data"
    },
    {
     "heading": "How SCOPEC works",
     "url": "https://www.automatiqa.io/scopec/#how-scopec-works"
    },
    {
     "heading": "Built for physical commodity flows, not for SKUs",
     "url": "https://www.automatiqa.io/scopec/#built-for-physical-commodity-flows-not-for-skus"
    },
    {
     "heading": "Where SCOPEC is heading",
     "url": "https://www.automatiqa.io/scopec/#where-scopec-is-heading"
    }
   ],
   "answers": [
    {
     "question": "Why don't planning tools fit commodity operations?",
     "url": "https://www.automatiqa.io/scopec/#commodity-planning-lives-between-two-kinds-of-software"
    },
    {
     "question": "How do you run S&OP and S&OE on one plan?",
     "url": "https://www.automatiqa.io/scopec/#one-kernel-two-horizons-commodity-families-as-data"
    },
    {
     "question": "How does SCOPEC work?",
     "url": "https://www.automatiqa.io/scopec/#how-scopec-works"
    },
    {
     "question": "How is commodity planning different from SKU planning?",
     "url": "https://www.automatiqa.io/scopec/#built-for-physical-commodity-flows-not-for-skus"
    },
    {
     "question": "What is on the SCOPEC roadmap?",
     "url": "https://www.automatiqa.io/scopec/#where-scopec-is-heading"
    }
   ]
  },
  {
   "name": "Auspex",
   "url": "https://www.automatiqa.io/auspex/",
   "summary": "Auspex is a prediction and forecasting harness for supply chain operations. Connect a table, pick a model, read the signs. Zero-shot tabular prediction and time-series forecasting behind one interface, with confidence intervals on every prediction, exposed as an MCP server.",
   "status": "In development 10%",
   "license": "Apache-2.0",
   "repository": "https://github.com/automatiqa-lab/auspex",
   "n8n_templates": [],
   "published": "2026-07-27",
   "updated": "2026-09-02",
   "changelog": "https://www.automatiqa.io/auspex/#log-title",
   "sections": [],
   "answers": []
  },
  {
   "name": "OODAA",
   "url": "https://www.automatiqa.io/oodaa/",
   "summary": "OODAA is a small, readable self-improving agent loop. Observe, Orient, Decide, Act, and the second A, Adjust: the phase that makes an agent get smarter across runs instead of only faster within one.",
   "status": "Live",
   "license": "MIT",
   "repository": "https://github.com/automatiqa-lab/oodaa",
   "n8n_templates": [],
   "published": "2026-06-26",
   "updated": "2026-10-18",
   "changelog": "https://www.automatiqa.io/oodaa/#log-title",
   "sections": [
    {
     "heading": "OODA makes an agent faster, not smarter",
     "url": "https://www.automatiqa.io/oodaa/#ooda-makes-an-agent-faster-not-smarter"
    },
    {
     "heading": "Add the second A: Adjust",
     "url": "https://www.automatiqa.io/oodaa/#add-the-second-a-adjust"
    },
    {
     "heading": "One screen, five blocks",
     "url": "https://www.automatiqa.io/oodaa/#one-screen-five-blocks"
    },
    {
     "heading": "Small enough to read, real enough to build on",
     "url": "https://www.automatiqa.io/oodaa/#small-enough-to-read-real-enough-to-build-on"
    },
    {
     "heading": "From a toy grid to operational triage",
     "url": "https://www.automatiqa.io/oodaa/#from-a-toy-grid-to-operational-triage"
    }
   ],
   "answers": [
    {
     "question": "Why doesn't an OODA loop make an AI agent smarter?",
     "url": "https://www.automatiqa.io/oodaa/#ooda-makes-an-agent-faster-not-smarter"
    },
    {
     "question": "What does the Adjust step add to OODA?",
     "url": "https://www.automatiqa.io/oodaa/#add-the-second-a-adjust"
    },
    {
     "question": "What are the five phases of OODAA?",
     "url": "https://www.automatiqa.io/oodaa/#one-screen-five-blocks"
    },
    {
     "question": "Does OODAA work with any LLM?",
     "url": "https://www.automatiqa.io/oodaa/#small-enough-to-read-real-enough-to-build-on"
    },
    {
     "question": "Where can OODAA be used in operations?",
     "url": "https://www.automatiqa.io/oodaa/#from-a-toy-grid-to-operational-triage"
    }
   ]
  },
  {
   "name": "Sample Trail",
   "url": "https://www.automatiqa.io/sample-trail/",
   "summary": "Sample Trail is a sample management workflow for the agri-food and soft-commodities sectors - coffee, cocoa, grain, sugar, cotton. It runs the quality approval decision on a physical sample, from dispatch to verdict, on the phone the person is already holding.",
   "status": "Live",
   "license": "MIT",
   "repository": "https://github.com/automatiqa-lab/sample-trail",
   "n8n_templates": [
    "https://n8n.io/workflows/18128-route-commodity-sample-quality-approvals-with-telegram-claude-and-spreadsheets/?ref=automatiqa.io"
   ],
   "published": "2026-06-20",
   "updated": "2026-10-18",
   "changelog": "https://www.automatiqa.io/sample-trail/#log-title",
   "sections": [
    {
     "heading": "The contract hangs on a sample. The approval hangs on an inbox",
     "url": "https://www.automatiqa.io/sample-trail/#the-contract-hangs-on-a-sample-the-approval-hangs-on-an-inbox"
    },
    {
     "heading": "The approval decision, run on the phone already in hand",
     "url": "https://www.automatiqa.io/sample-trail/#the-approval-decision-run-on-the-phone-already-in-hand"
    },
    {
     "heading": "Dispatch, arrival, evaluation, verdict",
     "url": "https://www.automatiqa.io/sample-trail/#dispatch-arrival-evaluation-verdict"
    },
    {
     "heading": "Built for sample rooms and quays, not laboratories",
     "url": "https://www.automatiqa.io/sample-trail/#built-for-sample-rooms-and-quays-not-laboratories"
    }
   ],
   "answers": [
    {
     "question": "Why are commodity sample approvals hard to defend later?",
     "url": "https://www.automatiqa.io/sample-trail/#the-contract-hangs-on-a-sample-the-approval-hangs-on-an-inbox"
    },
    {
     "question": "How do you approve a commodity sample from a phone?",
     "url": "https://www.automatiqa.io/sample-trail/#the-approval-decision-run-on-the-phone-already-in-hand"
    },
    {
     "question": "What are the steps of a sample approval?",
     "url": "https://www.automatiqa.io/sample-trail/#dispatch-arrival-evaluation-verdict"
    },
    {
     "question": "Is Sample Trail a LIMS?",
     "url": "https://www.automatiqa.io/sample-trail/#built-for-sample-rooms-and-quays-not-laboratories"
    }
   ]
  },
  {
   "name": "Ship-Doc",
   "url": "https://www.automatiqa.io/ship-doc/",
   "summary": "Ship-Doc is shipment document control for physical trade: the pack checked against the shipping instruction, drafts approved by a named person, originals chased via Outlook. The model reads, fixed rules decide, a person approves.",
   "status": "Live",
   "license": "MIT",
   "repository": "https://github.com/automatiqa-lab/ship-doc",
   "n8n_templates": [
    "https://n8n.io/workflows/18911-check-shipping-documents-against-sharepoint-instructions-with-onedrive-and-claude/?ref=automatiqa.io"
   ],
   "published": "2026-08-31",
   "updated": "2026-10-18",
   "changelog": "https://www.automatiqa.io/ship-doc/#log-title",
   "sections": [
    {
     "heading": "The pack is checked by eye, at the worst possible moment",
     "url": "https://www.automatiqa.io/ship-doc/#the-pack-is-checked-by-eye-at-the-worst-possible-moment"
    },
    {
     "heading": "The model reads. Fixed rules decide. A person approves",
     "url": "https://www.automatiqa.io/ship-doc/#the-model-reads-fixed-rules-decide-a-person-approves"
    },
    {
     "heading": "Scan, compare, approve, chase",
     "url": "https://www.automatiqa.io/ship-doc/#scan-compare-approve-chase"
    },
    {
     "heading": "Built for the desk that owns the shipment, not the IT department",
     "url": "https://www.automatiqa.io/ship-doc/#built-for-the-desk-that-owns-the-shipment-not-the-it-department"
    }
   ],
   "answers": [
    {
     "question": "Why do shipping document checks go wrong?",
     "url": "https://www.automatiqa.io/ship-doc/#the-pack-is-checked-by-eye-at-the-worst-possible-moment"
    },
    {
     "question": "How do you check shipping documents against the shipping instruction?",
     "url": "https://www.automatiqa.io/ship-doc/#the-model-reads-fixed-rules-decide-a-person-approves"
    },
    {
     "question": "How do you chase missing original documents?",
     "url": "https://www.automatiqa.io/ship-doc/#scan-compare-approve-chase"
    },
    {
     "question": "How do you add a new contract type to Ship-Doc?",
     "url": "https://www.automatiqa.io/ship-doc/#built-for-the-desk-that-owns-the-shipment-not-the-it-department"
    }
   ]
  },
  {
   "name": "PPWR Compliance Screener",
   "url": "https://www.automatiqa.io/ppwr-screener/",
   "summary": "PPWR Compliance Screener: checks supplier packaging declarations against Regulation (EU) 2025/40 for completeness and internal consistency. Deterministic verdicts. Suppliers get a signed link and a rule engine screens what comes back; no model issues a pass or a fail.",
   "status": "Live",
   "license": "MIT",
   "repository": "https://github.com/automatiqa-lab/ppwr-screener",
   "n8n_templates": [
    "https://n8n.io/workflows/18024-collect-packaging-declarations-from-csv-with-forms-ai-agents-and-email/?ref=automatiqa.io"
   ],
   "published": "2026-08-10",
   "updated": "2026-10-18",
   "changelog": "https://www.automatiqa.io/ppwr-screener/#log-title",
   "sections": [
    {
     "heading": "The regulation asks your suppliers questions. You collect the answers",
     "url": "https://www.automatiqa.io/ppwr-screener/#the-regulation-asks-your-suppliers-questions-you-collect-the-answers"
    },
    {
     "heading": "Suppliers get a signed link. A rule engine screens what comes back",
     "url": "https://www.automatiqa.io/ppwr-screener/#suppliers-get-a-signed-link-a-rule-engine-screens-what-comes-back"
    },
    {
     "heading": "Invite, declare, screen, report",
     "url": "https://www.automatiqa.io/ppwr-screener/#invite-declare-screen-report"
    },
    {
     "heading": "It screens documents. It refuses to pretend it certifies packaging",
     "url": "https://www.automatiqa.io/ppwr-screener/#it-screens-documents-it-refuses-to-pretend-it-certifies-packaging"
    }
   ],
   "answers": [
    {
     "question": "What supplier declarations does PPWR require?",
     "url": "https://www.automatiqa.io/ppwr-screener/#the-regulation-asks-your-suppliers-questions-you-collect-the-answers"
    },
    {
     "question": "How do you collect packaging declarations from suppliers?",
     "url": "https://www.automatiqa.io/ppwr-screener/#suppliers-get-a-signed-link-a-rule-engine-screens-what-comes-back"
    },
    {
     "question": "What are the steps of PPWR supplier screening?",
     "url": "https://www.automatiqa.io/ppwr-screener/#invite-declare-screen-report"
    },
    {
     "question": "Does the PPWR Compliance Screener certify packaging?",
     "url": "https://www.automatiqa.io/ppwr-screener/#it-screens-documents-it-refuses-to-pretend-it-certifies-packaging"
    }
   ]
  },
  {
   "name": "Global Operations Risk Monitor",
   "url": "https://www.automatiqa.io/risk-monitor/",
   "summary": "Operations Risk Monitor is a multi-agent framework that watches operational risk across freight, fuel, labour, weather and geopolitics, then turns what it finds into briefings you can actually use. Seven specialist agents collect and filter the feeds into one weekly briefing.",
   "status": "Live",
   "license": "MIT",
   "repository": "https://github.com/automatiqa-lab/risk-monitor",
   "n8n_templates": [],
   "published": "2026-06-25",
   "updated": "2026-10-18",
   "changelog": "https://www.automatiqa.io/risk-monitor/#log-title",
   "sections": [
    {
     "heading": "Operational risk hides in a hundred feeds at once",
     "url": "https://www.automatiqa.io/risk-monitor/#operational-risk-hides-in-a-hundred-feeds-at-once"
    },
    {
     "heading": "Seven specialist agents, one briefing",
     "url": "https://www.automatiqa.io/risk-monitor/#seven-specialist-agents-one-briefing"
    },
    {
     "heading": "Collect, filter, summarize, compose, save",
     "url": "https://www.automatiqa.io/risk-monitor/#collect-filter-summarize-compose-save"
    },
    {
     "heading": "Specialist depth, model-agnostic, config-driven",
     "url": "https://www.automatiqa.io/risk-monitor/#specialist-depth-model-agnostic-config-driven"
    },
    {
     "heading": "Where the Risk Monitor is heading",
     "url": "https://www.automatiqa.io/risk-monitor/#where-the-risk-monitor-is-heading"
    }
   ],
   "answers": [
    {
     "question": "Why is supply chain risk hard to monitor?",
     "url": "https://www.automatiqa.io/risk-monitor/#operational-risk-hides-in-a-hundred-feeds-at-once"
    },
    {
     "question": "Which risks does the Risk Monitor track?",
     "url": "https://www.automatiqa.io/risk-monitor/#seven-specialist-agents-one-briefing"
    },
    {
     "question": "How does the Risk Monitor collect and summarise news?",
     "url": "https://www.automatiqa.io/risk-monitor/#collect-filter-summarize-compose-save"
    },
    {
     "question": "Which AI models does the Risk Monitor work with?",
     "url": "https://www.automatiqa.io/risk-monitor/#specialist-depth-model-agnostic-config-driven"
    },
    {
     "question": "What is next for the Risk Monitor?",
     "url": "https://www.automatiqa.io/risk-monitor/#where-the-risk-monitor-is-heading"
    }
   ]
  },
  {
   "name": "Procezio - Process Navigator",
   "url": "https://www.automatiqa.io/process-navigator/",
   "summary": "Procezio is a guided canvas for finding automation opportunities in the way you already work, with an AI agent working alongside you on the same board. Map the process, mark the friction, assess it, decide what to automate - the agent drafts in pencil and a human accepts.",
   "status": "Live",
   "license": "Apache-2.0",
   "repository": "https://github.com/automatiqa-lab/procezio",
   "n8n_templates": [],
   "published": "2026-07-03",
   "updated": "2026-10-18",
   "changelog": "https://www.automatiqa.io/process-navigator/#log-title",
   "sections": [
    {
     "heading": "You can feel the friction. You have no structured way to act on it",
     "url": "https://www.automatiqa.io/process-navigator/#you-can-feel-the-friction-you-have-no-structured-way-to-act-on-it"
    },
    {
     "heading": "A guided canvas, with an agent working the board beside you",
     "url": "https://www.automatiqa.io/process-navigator/#a-guided-canvas-with-an-agent-working-the-board-beside-you"
    },
    {
     "heading": "Map, mark, assess, decide",
     "url": "https://www.automatiqa.io/process-navigator/#map-mark-assess-decide"
    },
    {
     "heading": "Built for the people who run the process, not the people who code it",
     "url": "https://www.automatiqa.io/process-navigator/#built-for-the-people-who-run-the-process-not-the-people-who-code-it"
    },
    {
     "heading": "Shipped, and what comes next",
     "url": "https://www.automatiqa.io/process-navigator/#shipped-and-what-comes-next"
    }
   ],
   "answers": [
    {
     "question": "Why is it hard to decide what to automate?",
     "url": "https://www.automatiqa.io/process-navigator/#you-can-feel-the-friction-you-have-no-structured-way-to-act-on-it"
    },
    {
     "question": "How does an AI agent help you map a process?",
     "url": "https://www.automatiqa.io/process-navigator/#a-guided-canvas-with-an-agent-working-the-board-beside-you"
    },
    {
     "question": "What are the steps from process map to automation decision?",
     "url": "https://www.automatiqa.io/process-navigator/#map-mark-assess-decide"
    },
    {
     "question": "Do you need to code to use Procezio?",
     "url": "https://www.automatiqa.io/process-navigator/#built-for-the-people-who-run-the-process-not-the-people-who-code-it"
    },
    {
     "question": "What has Procezio shipped so far?",
     "url": "https://www.automatiqa.io/process-navigator/#shipped-and-what-comes-next"
    }
   ]
  },
  {
   "name": "Orchestriq Core",
   "url": "https://www.automatiqa.io/orchestriq-core/",
   "summary": "Orchestriq Core is the kernel for agents that run real operations. Evals, approvals, earned autonomy and EU AI Act transparency live in the runtime, so every module inherits them. Spec, gate, park, earn - autonomy is a ladder climbed per action type on measured accuracy.",
   "status": "In development 15%",
   "license": "MIT",
   "repository": "https://github.com/automatiqa-lab/orchestriq",
   "n8n_templates": [],
   "published": "2026-06-22",
   "updated": "2026-10-18",
   "changelog": "https://www.automatiqa.io/orchestriq-core/#log-title",
   "sections": [
    {
     "heading": "Every agent project bolts the controls on last",
     "url": "https://www.automatiqa.io/orchestriq-core/#every-agent-project-bolts-the-controls-on-last"
    },
    {
     "heading": "The controls live in the kernel, so every module inherits them",
     "url": "https://www.automatiqa.io/orchestriq-core/#the-controls-live-in-the-kernel-so-every-module-inherits-them"
    },
    {
     "heading": "Spec, gate, park, earn",
     "url": "https://www.automatiqa.io/orchestriq-core/#spec-gate-park-earn"
    },
    {
     "heading": "Governance in the runtime, not in the habits of the team",
     "url": "https://www.automatiqa.io/orchestriq-core/#governance-in-the-runtime-not-in-the-habits-of-the-team"
    },
    {
     "heading": "Where Orchestriq Core is heading",
     "url": "https://www.automatiqa.io/orchestriq-core/#where-orchestriq-core-is-heading"
    }
   ],
   "answers": [
    {
     "question": "Why do agent projects add their controls too late?",
     "url": "https://www.automatiqa.io/orchestriq-core/#every-agent-project-bolts-the-controls-on-last"
    },
    {
     "question": "How does Orchestriq Core keep agents under supervision?",
     "url": "https://www.automatiqa.io/orchestriq-core/#the-controls-live-in-the-kernel-so-every-module-inherits-them"
    },
    {
     "question": "How does an AI agent earn more autonomy?",
     "url": "https://www.automatiqa.io/orchestriq-core/#spec-gate-park-earn"
    },
    {
     "question": "Which models does Orchestriq Core run on?",
     "url": "https://www.automatiqa.io/orchestriq-core/#governance-in-the-runtime-not-in-the-habits-of-the-team"
    },
    {
     "question": "What is being built in Orchestriq Core now?",
     "url": "https://www.automatiqa.io/orchestriq-core/#where-orchestriq-core-is-heading"
    }
   ]
  },
  {
   "name": "FlowTwin",
   "url": "https://www.automatiqa.io/flowtwin/",
   "summary": "FlowTwin turns a recording of any operational process into editable process maps and runbooks that are adjustable, auditable, and kept current. The capture layer for tribal knowledge. Watch the process once; FlowTwin captures, segments, structures and publishes what it sees.",
   "status": "In development 70%",
   "license": "MIT",
   "repository": "https://github.com/automatiqa-lab/flowtwin",
   "n8n_templates": [],
   "published": "2026-06-20",
   "updated": "2026-10-18",
   "changelog": "https://www.automatiqa.io/flowtwin/#log-title",
   "sections": [
    {
     "heading": "Operations run on knowledge that was never written down",
     "url": "https://www.automatiqa.io/flowtwin/#operations-run-on-knowledge-that-was-never-written-down"
    },
    {
     "heading": "Watch the process once. Get living process maps",
     "url": "https://www.automatiqa.io/flowtwin/#watch-the-process-once-get-living-process-maps"
    },
    {
     "heading": "Capture, segment, structure, publish",
     "url": "https://www.automatiqa.io/flowtwin/#capture-segment-structure-publish"
    },
    {
     "heading": "Not a static document. A system that keeps itself honest",
     "url": "https://www.automatiqa.io/flowtwin/#not-a-static-document-a-system-that-keeps-itself-honest"
    },
    {
     "heading": "Where FlowTwin is heading",
     "url": "https://www.automatiqa.io/flowtwin/#where-flowtwin-is-heading"
    }
   ],
   "answers": [
    {
     "question": "Why is undocumented process knowledge a problem?",
     "url": "https://www.automatiqa.io/flowtwin/#operations-run-on-knowledge-that-was-never-written-down"
    },
    {
     "question": "What does FlowTwin produce from one recording?",
     "url": "https://www.automatiqa.io/flowtwin/#watch-the-process-once-get-living-process-maps"
    },
    {
     "question": "How does FlowTwin turn a video into steps?",
     "url": "https://www.automatiqa.io/flowtwin/#capture-segment-structure-publish"
    },
    {
     "question": "How does FlowTwin check its own process maps?",
     "url": "https://www.automatiqa.io/flowtwin/#not-a-static-document-a-system-that-keeps-itself-honest"
    },
    {
     "question": "What is on the FlowTwin roadmap?",
     "url": "https://www.automatiqa.io/flowtwin/#where-flowtwin-is-heading"
    }
   ]
  }
 ],
 "series": {
  "title": "Intelligent Orchestration",
  "url": "https://www.automatiqa.io/intelligent-orchestration/",
  "feed": "https://www.automatiqa.io/intelligent-orchestration/rss/",
  "summary": null,
  "sections": [
   {
    "heading": "The argument",
    "url": "https://www.automatiqa.io/intelligent-orchestration/#v1"
   },
   {
    "heading": "Reflections",
    "url": "https://www.automatiqa.io/intelligent-orchestration/#v2"
   },
   {
    "heading": "Why this series exists",
    "url": "https://www.automatiqa.io/intelligent-orchestration/#v3"
   },
   {
    "heading": "Where the argument gets tested",
    "url": "https://www.automatiqa.io/intelligent-orchestration/#v4"
   }
  ],
  "entries": [
   {
    "title": "Why process maps don't tell you what to delegate to an AI agent?",
    "url": "https://www.automatiqa.io/intelligent-orchestration/why-process-maps-dont-tell-you-what-to-delegate-to-an-ai-agent/",
    "summary": "The supply chain unit that decides agentic AI readiness.",
    "published": "2026-09-19",
    "updated": "2026-09-21",
    "sections": [],
    "answers": []
   }
  ]
 },
 "manifesto": {
  "title": "The Intelligent Orchestration Manifesto",
  "url": "https://www.automatiqa.io/manifesto/",
  "summary": null,
  "published": "2026-09-17",
  "updated": "2026-09-17",
  "sections": [
   {
    "heading": "What is intelligent orchestration?",
    "url": "https://www.automatiqa.io/manifesto/#thesis"
   },
   {
    "heading": "The 2,300-Year-Old Routing Problem",
    "url": "https://www.automatiqa.io/manifesto/#alexander"
   },
   {
    "heading": "MRP and the First Planning Layer",
    "url": "https://www.automatiqa.io/manifesto/#mrp"
   },
   {
    "heading": "ERP as the Organisational Chart",
    "url": "https://www.automatiqa.io/manifesto/#erp"
   },
   {
    "heading": "Lean and Six Sigma - Optimising the Routing Layer",
    "url": "https://www.automatiqa.io/manifesto/#lean"
   },
   {
    "heading": "The Control Tower - Operations Gets Its Matrix",
    "url": "https://www.automatiqa.io/manifesto/#tower"
   },
   {
    "heading": "The Digital Twin as World Model",
    "url": "https://www.automatiqa.io/manifesto/#twin"
   },
   {
    "heading": "The Intelligence Layer - Composing Decisions",
    "url": "https://www.automatiqa.io/manifesto/#intelligence"
   },
   {
    "heading": "The Edge - What Stays Human",
    "url": "https://www.automatiqa.io/manifesto/#edge"
   },
   {
    "heading": "What This Is About",
    "url": "https://www.automatiqa.io/manifesto/#what-this-is-about"
   },
   {
    "heading": "Frequently Asked Questions",
    "url": "https://www.automatiqa.io/manifesto/#faq"
   }
  ],
  "answers": [
   {
    "question": "What is intelligent orchestration?",
    "url": "https://www.automatiqa.io/manifesto/#thesis"
   },
   {
    "question": "How does this differ from Sequoia's From Hierarchy to Intelligence?",
    "url": "https://www.automatiqa.io/manifesto/#alexander"
   },
   {
    "question": "What can a supply chain control tower not do?",
    "url": "https://www.automatiqa.io/manifesto/#tower"
   },
   {
    "question": "What is a digital twin in supply chain?",
    "url": "https://www.automatiqa.io/manifesto/#twin"
   },
   {
    "question": "Which supply chain decisions stay human?",
    "url": "https://www.automatiqa.io/manifesto/#edge"
   },
   {
    "question": "How is intelligent orchestration different from automation?",
    "url": "https://www.automatiqa.io/manifesto/#faq"
   }
  ]
 },
 "glossary": {
  "url": "https://www.automatiqa.io/glossary/",
  "summary": null,
  "schedules": [
   {
    "schedule": "Projects",
    "url": "https://www.automatiqa.io/glossary/#v1",
    "terms": [
     {
      "term": "Auspex",
      "definition": "Auspex is a prediction and forecasting harness for supply chain operations: zero-shot models behind one interface, exposed as an MCP server.",
      "url": "https://www.automatiqa.io/glossary/#auspex",
      "source": "https://www.automatiqa.io/auspex/"
     },
     {
      "term": "Automatiqa Lab",
      "definition": "Automatiqa Lab is an open-source project lab by Aleks Sidorecs, publishing the tools he builds while experimenting with AI on the messy parts of real operations.",
      "url": "https://www.automatiqa.io/glossary/#automatiqa-lab",
      "source": "https://www.automatiqa.io/"
     },
     {
      "term": "FlowTwin",
      "definition": "FlowTwin turns a recording of any operational process into editable process maps and runbooks that are adjustable, auditable and kept current.",
      "url": "https://www.automatiqa.io/glossary/#flowtwin",
      "source": "https://www.automatiqa.io/flowtwin/"
     },
     {
      "term": "OODAA",
      "definition": "OODAA is a self-improving agent loop: Observe, Orient, Decide, Act, and the second A, Adjust, the phase that makes an agent get smarter across runs instead of only faster within one. Some sources, including the Canadian Forces, expand OODAA as Observe, Orient, Decide, Act, Assess. The difference is not cosmetic: Assess judges the outcome of a cycle, while Adjust changes how the next cycle decides.",
      "url": "https://www.automatiqa.io/glossary/#oodaa",
      "source": "https://www.automatiqa.io/oodaa/"
     },
     {
      "term": "Operations Risk Monitor",
      "definition": "Operations Risk Monitor is a multi-agent framework that watches operational risk across freight, fuel, labour, weather and geopolitics, then turns what it finds into briefings.",
      "url": "https://www.automatiqa.io/glossary/#operations-risk-monitor",
      "source": "https://www.automatiqa.io/risk-monitor/"
     },
     {
      "term": "Orchestriq",
      "definition": "Orchestriq is the kernel for agents that run real operations, where evals, approvals, earned autonomy and EU AI Act transparency live in the runtime so no module can opt out of them.",
      "url": "https://www.automatiqa.io/glossary/#orchestriq",
      "source": "https://www.automatiqa.io/orchestriq-core/"
     },
     {
      "term": "PPWR Compliance Screener",
      "definition": "PPWR Compliance Screener checks supplier packaging declarations against Regulation (EU) 2025/40 for completeness and internal consistency. It is a screening tool, not a conformity assessment.",
      "url": "https://www.automatiqa.io/glossary/#ppwr-compliance-screener",
      "source": "https://www.automatiqa.io/ppwr-screener/"
     },
     {
      "term": "Procezio",
      "definition": "Procezio is a guided canvas for finding automation opportunities in the way you already work, with an AI agent working alongside you on the same board.",
      "url": "https://www.automatiqa.io/glossary/#procezio",
      "source": "https://www.automatiqa.io/process-navigator/"
     },
     {
      "term": "Sample Trail",
      "definition": "Sample Trail is a sample management workflow for agri-food and soft commodities that runs the quality approval decision on a physical sample, from dispatch to verdict.",
      "url": "https://www.automatiqa.io/glossary/#sample-trail",
      "source": "https://www.automatiqa.io/sample-trail/"
     },
     {
      "term": "SCOPEC",
      "definition": "SCOPEC (Supply Chain Operations Planning & Execution in Commodities) runs S&OP and S&OE on one planning kernel and one data model, with commodity families held as data profiles - soft commodities first, hard commodities next.",
      "url": "https://www.automatiqa.io/glossary/#scopec",
      "source": "https://www.automatiqa.io/scopec/"
     },
     {
      "term": "Ship-Doc",
      "definition": "Ship-Doc is shipment document control for physical trade: the pack checked against the shipping instruction, drafts approved by a named person, originals chased via Outlook.",
      "url": "https://www.automatiqa.io/glossary/#ship-doc",
      "source": "https://www.automatiqa.io/ship-doc/"
     }
    ]
   },
   {
    "schedule": "Concepts",
    "url": "https://www.automatiqa.io/glossary/#v2",
    "terms": [
     {
      "term": "Decision loop",
      "definition": "A decision loop is the unit a process map leaves out: the point where work stops and waits on a judgement, who or what makes that judgement, how long the wait runs, and whether the call still holds under load. A process map records how work moves; the decision loop records where it stops and why, which is what determines whether a task can be handed to an agent. The phrase is occupied from three directions: decision cycle as the encyclopaedic term, Decision Loops as a 2024 consulting methodology for translating business problems into AI solutions, and The Decision Loop as a publication name. The sense here is narrower than any of them - one named point in a flow where work stops and waits on a judgement, and the properties of that point.",
      "url": "https://www.automatiqa.io/glossary/#decision-loop",
      "source": "https://www.automatiqa.io/intelligent-orchestration/why-process-maps-dont-tell-you-what-to-delegate-to-an-ai-agent/"
     },
     {
      "term": "Decision orchestration",
      "definition": "Decision orchestration is a vendor category in supply chain planning: aligning demand, supply and finance so that one decision is made once and then expressed consistently across every system that touches it. It is sold in sales and operations planning terms by Board, LeanDNA and Cleo, and a 2026 paper extends it to orchestrating AI capabilities across global value chains. It is the nearest neighbour to Intelligent Orchestration and the easiest to confuse with it, because both carry decision and orchestration and both sit in supply chain. The line between them is who routes: decision orchestration makes a human decision consistent everywhere, and Intelligent Orchestration moves the routing itself off people.",
      "url": "https://www.automatiqa.io/glossary/#decision-orchestration",
      "source": "https://www.automatiqa.io/manifesto/"
     },
     {
      "term": "Digital twin",
      "definition": "A digital twin is not a 3D visualisation but a decision substrate: a machine-readable representation of inventory, capacity, demand signals, supplier state and constraints that answers what is happening without being asked.",
      "url": "https://www.automatiqa.io/glossary/#digital-twin",
      "source": "https://www.automatiqa.io/manifesto/"
     },
     {
      "term": "Intelligence layer",
      "definition": "The intelligence layer does not just observe, it composes: it assembles capabilities that already exist across the value chain into responses no individual planner would have constructed.",
      "url": "https://www.automatiqa.io/glossary/#intelligence-layer",
      "source": "https://www.automatiqa.io/manifesto/"
     },
     {
      "term": "Intelligent Orchestration",
      "definition": "Intelligent Orchestration, in supply chain and physical operations, is the argument that the coordination layer - human for twenty-three centuries - is moving to systems. The term is used here in that sense, not in the IT sense of orchestrating workloads or containers.",
      "url": "https://www.automatiqa.io/glossary/#intelligent-orchestration",
      "source": "https://www.automatiqa.io/manifesto/"
     },
     {
      "term": "Supply chain orchestration",
      "definition": "Supply chain orchestration is the coordination of demand, supply, logistics and finance across a value chain from one view: the control tower generation, where software makes the state visible and people still route every decision. Intelligent Orchestration is the same function after the routing itself moves to systems.",
      "url": "https://www.automatiqa.io/glossary/#supply-chain-orchestration",
      "source": "https://www.automatiqa.io/manifesto/"
     },
     {
      "term": "The Edge",
      "definition": "The Edge is the boundary where the intelligence system meets human judgment - supplier relationships, crisis calls, ethical sourcing, market entry, talent - the work that stays human once coordination moves to systems.",
      "url": "https://www.automatiqa.io/glossary/#the-edge",
      "source": "https://www.automatiqa.io/manifesto/"
     }
    ]
   }
  ]
 },
 "elsewhere": {
  "note": "Moved to the author's own site on 2026-09-26; linked here, never duplicated.",
  "catalog": "https://www.sidorecs.com/catalog.json",
  "heuristics": {
   "title": "Heuristics",
   "url": "https://www.sidorecs.com/heuristics/",
   "feed": "https://www.sidorecs.com/heuristics/rss.xml"
  },
  "notebooks": [
   {
    "title": "Zero-shot prediction models in supply chain",
    "url": "https://www.sidorecs.com/notebooks/zero-shot-models-in-supply-chain/",
    "project_url": "https://www.automatiqa.io/auspex/"
   },
   {
    "title": "Supply chain planning and execution in commodities",
    "url": "https://www.sidorecs.com/notebooks/commodities-supply-chain-planning/",
    "project_url": "https://www.automatiqa.io/scopec/"
   },
   {
    "title": "Citizen Developers in Supply Chain",
    "url": "https://www.sidorecs.com/notebooks/citizen-developers-in-supply-chain/",
    "project_url": null
   }
  ],
  "glossary": "https://www.sidorecs.com/glossary/"
 }
}