Medium · Essays & presentation notes
Writing on how Opus represents work, chooses models for defined tasks and preserves a way to complete a workflow as it is built. Each post has a summary here and a link to the original on Medium.
—
Define the task, evaluate the model and preserve the approved assignment, so compatible workflows can reuse it at execution time.
A claims-extraction task already has a purpose, schema and operating constraints before the next document arrives. That makes model selection work that can be done in advance, provided the evidence covers the inputs and conditions in which the choice will be reused.
Reusable tasks need supported connections, explicit context and a history of how shared process knowledge was admitted and changed.
Supplier onboarding and a change to supplier details may share a banking check, while differing in what happens next. The graph keeps both the common responsibility and the evidence for each handoff, and Graph Gardening maintains that knowledge as it grows.
What each committed addition must establish to preserve a possible completion, and what exact tracking must remember about future choices.
The ICMAI presentation follows two supplier-payment contexts in which the same locally legal addition has different consequences. Closing a standard approval route is safe only where an authorised exception route can still be completed.
The Inside Opus series follows one supplier invoice through the running system. The Opus blog collection covers completion viability, the Work Knowledge Graph and Graph Gardening, while the papers give the formal treatment.
—