Antz · Operations · Bounded contextsv1 · For review

Who owns what: the operations system sorted into contexts

Every thing in Antz operations is a card. Each card belongs to exactly one context, which owns its rules and its data. Other contexts only point at it. Approvals, tasks and the organisation sit in the middle, shared by all.

How to read the cards

The main record this context exists for
Owned here: its rules live in this context
Used here, owned by another context
1

GRC

What must be true, did we check it, and what went wrong?

Auditor · safety officer · policy owner

Incidentevery breakdown starts here Audit sessionone run of a check PolicyStandardRuleProcedure Audit formAudit scheduleFinding Action (CAPA)Licence and returnEvidence pack Assetfrom AssetsStorefrom InventoryPlacefrom Places
2

Helpdesk

Who is asked to do what, and has it been done?

Any staff · department in-charge

Ticketan outcome asked of a department Department queueIssue categoryCosting lines Tentative dateSign-offReopen window48 hours Incidentfrom GRCAssetfrom Assets
3

Maintenance & work

What job is done on which asset, by whom, with what parts?

Maintenance head · technician · vendor

Work ordera planned job Work order lineone per assetMaintenance planMaintenance visit Maintenance typePermit to workParts usedLabour and downtime Ticketfrom HelpdeskAssetfrom AssetsVendorfrom Procurement
4

Assets

What do we own, where is it, who holds it, what is it worth?

Asset owner · finance

Assetone thing, its own ID Place assetenclosure, cold roomTag and scanAsset category Check-out (custody)ReservationAsset transferLease WarrantyAMCDepreciationDecommissionDisposal GRN linefrom ProcurementPlacefrom Places
5

Places

Where is everything?

Admin

Site Zone / sectionAreaenclosure, building, roomSpot Place ownerStationgate, kiosk Animal, enclosurefrom Antz
0

Shared kernel: used by every context

Owns no business data. Every context hands its decisions and to-dos here, and reads people and money from here.

Approvals
Approval requestApproval policyAmount band Step and decisionDelegationApprovals inbox
Tasks
To-doMy workTeam view Proof and stepsEscalation rule
Schedules
RecurrenceDue, missed, done late
Record thread
Link between recordsHistoryAttachmentsNotification
6

Organisation

Who are we, who may do what, whose money is it?

Admin · finance

Person DepartmentTeamRolea bundle of permissions Cost centremany per departmentLimitsManagement group
7

Catalogue

What kinds of things exist, and how is each one tracked?

Domain in-charge · admin

Product DomainCategoryTracking modeconsumable, spare, asset, service Variant (SKU)PackageUnit of measureAttribute set New product approval
8

Warehousing & inventory

How much do we have, where, and where did it go?

Store manager · pharmacy in-charge

Stockvariant × store × batch Store (warehouse)Rack and shelfBatch and expiryReorder level Item requestIssue / dispenseStock transferStock count AdjustmentStock ledger Productfrom CatalogueGRN linefrom ProcurementWork orderfrom Maintenance
9

Procurement

What are we buying, from whom, at what price, and has it arrived?

Raiser · procurement team · cost centre owner

Procurement request Request lineSourcingQuoteL1, L2, L3 PO requestPurchase orderDelivery (DC)Goods inspection GRNVendorRate contractVendor scorecard Productfrom CatalogueTicketfrom Helpdesk
10

Bill desk & payment

Does the bill match what came, and has it been paid?

Accounts clerk · bill desk head · finance

Vendor invoice Three-way matchPO × GRN × invoiceDiscrepancy Payment requestPayment Purchase orderfrom ProcurementGRNfrom ProcurementVendorfrom Procurement

Where the contexts hand off to each other

FromWhat crosses the boundaryTo
1 · GRCAn incident or finding needs a department to fix something2 · Helpdesk
1 · GRCA fix needs a job on an asset or place3 · Maintenance & work
2 · HelpdeskAn approved ticket needs a job3 · Maintenance & work
2 · HelpdeskA ticket needs something bought9 · Procurement
3 · Maintenance & workA job needs parts from a store8 · Warehousing & inventory
3 · Maintenance & workA job changes an asset's status, condition and cost4 · Assets
8 · Warehousing & inventoryLow stock, or parts not in stock9 · Procurement
9 · ProcurementGoods received of a consumable or spare part8 · Warehousing & inventory
9 · ProcurementGoods received of an asset-tracked item4 · Assets
9 · ProcurementPO and GRN, for matching the bill10 · Bill desk & payment
4 · AssetsBreakdown, or a failed asset audit1 · GRC
4 · AssetsEnd of life, or an AMC or warranty due for renewal9 · Procurement
Every contextA decision someone must make · a job someone must do0 · Shared kernel

Rules of the boundaries

One owner per cardA record's rules and statuses live in one context. Others point at it by ID and never change it.
Handoffs, not shared editsA context asks another to act (raise, request, receive). It never edits the other's record.
The kernel owns no businessApprovals and tasks know who and when, not what a ticket or a PO means.
Places and people are read-onlyEvery context reads sites, stores, people and cost centres; only Places and Organisation change them.
Antz · Operations architecture · 19 Nov 2026Card names are design terms, not field names