Curriculum / Application Developer
Application Developer & Ontology Engineering
Turn the supply-chain Ontology into an operational app suite for the command-center operators: deep object/link/action modeling, a RiskEntity interface with private-vs-shared placement, reusable TypeScript-v2 and Python Functions, function-backed Actions that safely edit the Ontology, an advanced Workshop command center, and embedded Quiver analytics.
Analysts→builders, ontologists, and app developers (coding-capable — TypeScript + Python).
The 8-unit arc
- Unit 1: Ground the app's Ontology: object types, properties, link typesfoundational
Confirm the five supply-chain object types (primary keys, app-required properties, navigable links) the operator app will read.
- Unit 2: Shape with interfaces: a RiskEntity interface and private-vs-shared placementintermediate
Define a RiskEntity interface (riskScore, status) implemented by Shipment and DisruptionEvent, and decide private vs shared ontology placement.
- Unit 3: Reusable Functions: TypeScript v2 functions on objectsintermediate
Author and publish a TypeScript-v2 query function (shipmentRiskRollup) that reads objects/links and returns a structured risk summary.
- Unit 4: Python functions and cross-language consumptionintermediate
Publish a Python query function (reorderSuggestion over InventoryItem) and note TS-v2 vs Python feature support for the app.
- Unit 5: Function-backed Actions: edit the Ontology safelyadvanced
Publish an Ontology-edit function and a function-backed Action (triageDisruption) that sets owner and status on a DisruptionEvent.
- Unit 6: Assemble the Workshop command-center app: layouts, pages, widgets, variablesadvanced
Build a Workshop Command Center with a risk-list page, a detail page, function-backed metric variables, and the triage action via a Button Group.
- Unit 7: Embed analytics: Quiver dashboards in the appadvanced
Build a Quiver dashboard (late-shipment trend + exposure metrics) and embed it in the Command Center, with headline metrics reproducible via aggregation.
- Unit 8: Capstone: the operating app suite end-to-endcapstone
An operator opens a disruption, runs analysis, triages via the function-backed action, and the published function returns a structured next step — end to end on one Ontology.
Ground the app's Ontology: object types, properties, link types
Confirm the five supply-chain object types (primary keys, app-required properties, navigable links) the operator app will read.
Shape with interfaces: a RiskEntity interface and private-vs-shared placement
Define a RiskEntity interface (riskScore, status) implemented by Shipment and DisruptionEvent, and decide private vs shared ontology placement.
Reusable Functions: TypeScript v2 functions on objects
Author and publish a TypeScript-v2 query function (shipmentRiskRollup) that reads objects/links and returns a structured risk summary.
Python functions and cross-language consumption
Publish a Python query function (reorderSuggestion over InventoryItem) and note TS-v2 vs Python feature support for the app.
Function-backed Actions: edit the Ontology safely
Publish an Ontology-edit function and a function-backed Action (triageDisruption) that sets owner and status on a DisruptionEvent.
Assemble the Workshop command-center app: layouts, pages, widgets, variables
Build a Workshop Command Center with a risk-list page, a detail page, function-backed metric variables, and the triage action via a Button Group.
Embed analytics: Quiver dashboards in the app
Build a Quiver dashboard (late-shipment trend + exposure metrics) and embed it in the Command Center, with headline metrics reproducible via aggregation.
Capstone: the operating app suite end-to-end
An operator opens a disruption, runs analysis, triages via the function-backed action, and the published function returns a structured next step — end to end on one Ontology.