Antz Operations architecture
19 Nov 2026
What this is
Whole-system architecture for Antz operations: Inventory, warehouses, sites, assets, GRC, Helpdesk, maintenance, work orders, procurement, approvals, tasks. A vision only, never built / missing status.
Briefs
- Sourav, 18 Nov: how these modules link, "like how we made for GRC".
- Architecture brief, 19 Nov: top-down hierarchy, Inventory as the backbone, other systems branching off, Tasks / Approvals / People as cross layers, visual only, validated against builds.
Files
| File | What | Status |
|---|---|---|
architecture.html | The map | Basic version |
gen_architecture.py | Builds the map | current |
ARCHITECTURE.md | Full written vision, D1–D10 | current |
bounded-contexts.html | Card sort | earlier |
system-flow.html | GRC-style flowchart | earlier |
system-map.html | Four-view page | rejected |
sop.css | Shared styles | required |
council/2026-11-19-visuals/, council/2026-11-19-warmth/ | Visual councils | done |
Preview: ops-architecture, port 3037.
Settled
| # | Decision |
|---|---|
| D1 | A breakdown is always an incident first |
| D2 | One Approvals inbox per person |
| D3 | Spare parts are stock, issued to work orders, costed to the asset |
| D4 | Built places get a place asset |
| D5 | Checked-out asset custody is a person or a place |
| D6 | Asking a store is an item request, never a ticket |
| D7 | GRC risk is findings only |
| D8 | Mismatched invoice is flagged, not blocked |
| D9 | Many cost centres per department |
| D10 | Tasks is its own module; AMC / warranty / licence are alerts; My work is one screen |
- Goods receiving belongs to Inventory.
- One product catalogue, in Inventory.
- Visuals: colour by domain (GRC green, Tasks orange, money soft navy, work teal, Inventory dark navy).
Working rules
- Match the scope and form of what he points at.
- One-line answers when asked. Don't build more than asked.
- Review as rendered pages. Council before visual craft changes.
- Keep colour that carries meaning. No emojis, no accent stripes.
Open
- Not on the map (left for now): Kitchen, Gate & security, Visitor management, Animal movement; enclosure headcount, missing / found, notes, announcements, reports, animal exchanges, carcass disposal.
- Two line crossings remain on the map.
Module pages
Inventory · Procurement · Finance · Helpdesk · Maintenance · Assets · GRC · Tasks · Approvals · Foundations
Inventory
Last updated 19 Nov 2026. Paths are under Studio/projects/.
On the map
The backbone (the only dark navy header), with 14 parts:
- Catalogue ("one master"): domain → category → product → variant / SKU → package.
- Tracking mode: consumable, spare part, asset, service.
- Storage: warehouse → zone → rack → shelf / bin.
- Store kinds: central (feeds department stores), pharmacy, kitchen, scrap yard.
- Stock: stock → batch / expiry → container; reorder level; valuation.
- Stock status: in stock, low or out, expiring or expired, in transit, quarantined.
- Inbound ("moved in"): gate entry → delivery (DC) → inspection → GRN; return to supplier.
- Outbound: item request → issue / dispense to a person, animal or work order; return to store.
- Transfers: request → dispatch → in transit → receive; gate pass.
- Control: stock count → variance → adjustment or waste; stock ledger and its entry types.
- Pharmacy: controlled-drug register, dispense to an animal, pharmacist sign-off.
- Stations: gate station, scan kiosk, packing kiosk.
- Masters: unit of measure, brand / manufacturer, generic / salt / class, storage condition, attribute set.
- Insights: low or out of stock, expiring, stock value, consumption.
Also:
- Draws stock box below it: Kitchen diets, Pharmacy and hospital, departments, work orders, animals.
- Who · on: store managers, store staff, pharmacist, gate · web, tablet, kiosk, scanner.
Binding decisions
- Boundary changes made by checking builds:
- Goods receiving moved in from Procurement. Kitchen has
/inventory/receive, and Bill Desk reads Inventory › Goods Received. - One product catalogue lives here, for stock and assets alike.
- Goods receiving moved in from Procurement. Kitchen has
ARCHITECTURE.md:- §2.1: every stock change is one ledger entry, and stock in transit is held in escrow until received.
- §2.3: a GRN line becomes stock or an asset depending on its tracking mode.
- §3.3: the movement types.
Design work
| Path | What | Status |
|---|---|---|
Antz/design-tab-library/Projects/Inventory-v1/ | Tablet (834×1194), look-up only: products, stock by store, reorder level, variants, batch and expiry, "Request this". Receiving, issuing, transfers and reorder stay on the web | 23 Oct |
Antz/design-tab-library/Projects/Item-requests-v1/ | Item requests tablet module, a modules page, an Antz Home landing, masters views (no README) | 22 Oct |
Antz/procurement/Procure-v1/ #/inventory | Stock report and inventory section | 14 Oct |
Antz/kitchen-diet/ | Kitchen research | — |
Code knowledge (atlas capabilities.md; Kitchen SRC-KI / KA / KB-20261118, Antz SRC-AM / AW-20261118; all "not deepened")
- Stock (Kitchen): iPad
/stock, kiosk scan,/operations/inventory/*, locations, kiosks. - Receiving (Kitchen): iPad
/receiving; admin/inventory/receive, with AI reading of the delivery-note photo and QR labels. - Transfers (Kitchen): request → approve → pick → dispatch → receive.
- Gate (Kitchen): vehicles in and out, delivery notes, signed delivery-note paperwork.
- Pharmacy (Antz): mobile Pharmacy, PharmacyRequest and DispenseMedicine; 100 web screens.
- There is no atlas module file for Inventory.
Settled
- Procure-v1
DECISIONS.mdPH1–PH14 (13 Oct):- a domain › category tree
- variants are attributes, and packages are kept separate
- PH8: batch and expiry stay in Pharmacy
- PH2: indents stay in Pharmacy
- PH10: reorder is raised by hand
Open
- Q-d: "keep for stock" needs the store screens, which aren't built (procure-web-lite README).
- PH8 and PH2 keep batch, expiry and indents in Pharmacy. The map puts batch and expiry in shared Stock. Needs a ruling.
- No atlas module file yet. It's the first one to write for the backbone.
- Which Kitchen branch each zoo runs is unknown (atlas manifest U8).
Procurement
Last updated 19 Nov 2026. Paths are under Studio/projects/.
On the map
Money domain (soft navy).
- Requests: purchase request → PR line → linked tickets and work orders.
- Sourcing: quotes L1 · L2 · L3 → chosen vendor; rate history.
- Ordering: PO request → purchase order → PO line.
- Contracts: rate contract → auto reorder; AMC and service contracts; disposal sale.
- Line status: approved → sourcing or ordered → delivered or partial → paid or closed short.
- Who · on: the procurement team, raisers, cost centre owners · web.
- Links:
- in: purchase requests from tickets, work orders and renewal alerts (top lane); low stock, from Inventory; licence renewal, from GRC
- out: PO due in → Inventory; PO → Finance
- budget check, with Finance
Binding decisions
- Goods receiving (DC, inspection, GRN) is Inventory's, not Procurement's.
- The target chain (
ARCHITECTURE.md§3.4) is PR → sourcing L1/L2/L3 → PO request (one vendor, many lines) → PO → DC → GRN → invoice with three-way match → payment request → payment. - D9: a purchase request is raised against one cost centre, and a department can have many cost centres.
- D2: approvals A11 (purchase request) and A12 (PO) go to the one inbox.
Design work
| Path | What | Status |
|---|---|---|
Antz/procurement/project.json | Timeline from concept (May) to offline portal, Procure-v1, v2, v3 and web lite | "build", 30 Oct |
Antz/procurement/00-concept/ (brief.md, Procurement-PRD.pdf) | PRD draft v0.1: request → quote → review → order → invoice → delivery | 9 May |
Antz/procurement/Procure-v1/ (README, HANDOFF, DECISIONS.md) | Clickable prototype (Help Desk tablet, Procurement tablet and web), Phase 1 / 2 switch; local at localhost:8789/Procure-v1/ | Phase 1 built 14 Oct; nothing committed |
Antz/procurement/procurement-v2/ + design-baseline/ | Offline portal v1.37 restyled to "Design system v0", with a logic guard | 16 Oct |
Antz/procurement/procure-web-lite/ | V3 screens for requester, approver, procurement team and finance; live: https://procure-web-lite.vercel.app | 23 Oct; inventory and store screens not built |
Antz/procurement/docs/ | Review packs (budgets read; others not opened) | — |
Code knowledge
Kitchen only (CAP-kitchen-procurement, SRC-KA / KB): /procurement/*, procurement items, vendors, rate card, forecast, weekly and monthly plans. Antz mobile and web have none.
Settled (Procure-v1 DECISIONS.md)
- M1–M3: Help Desk stays as it is. Procurement is a linked record with its own approval.
- §12h / 12i (13 Oct):
- Phase 1: P&C approval recorded offline → PO → GRN by the store → stock in and issue → payment request per GRN → CEO approval recorded.
- Phase 2: Finance tiers, QC, three-way match.
Open
- §14 Q-a…Q-d are "assumed, not yet confirmed".
- HANDOFF (14 Oct): 18 rule questions plus parked parts W-17 and W-133 are waiting for Sourav.
- Conflicts with the target (inferred):
- A9 "approvals only in the Procure portal" vs D2 (one inbox).
- A14 "nothing happens if an approver doesn't act" vs escalation in §4.1.
Finance
Last updated 19 Nov 2026. Paths are under Studio/projects/.
On the map
Money domain (soft navy).
- Bill desk: vendor invoice → three-way match → discrepancy flag.
- Payments: payment request → payment.
- Budgets: cost centre budget → limits, spend vs budget.
- Asset accounting: capitalisation → book value; total cost of ownership (TCO) roll-up; write-off.
- Who · on: bill desk, finance team, management · web.
- Links:
- in: GRN, from Inventory; PO, from Procurement; capitalisation and TCO, from Assets
- out: budget check → Procurement
Binding decisions
- D8: an invoice that doesn't match its PO and GRN is flagged, not blocked. The bill desk head accepts it with a reason or returns it.
- D9: many cost centres per department, each with an owner and limits.
- Cost roll-up (shared engine): every spend lands on a cost centre. Spend on an asset also lands on the asset, as total cost of ownership.
- Approvals: A13 (invoice) and A14 (payment).
Design work
| Path | What | Status |
|---|---|---|
Antz/procurement/bill-desk-lite/ (docs/framing.md, DECISIONS.md, docs/context-pack.md) | Delivery note → invoice → Finance, with browser storage; seed from Kitchen delivery notes 1–15 Oct; port 3021; repo Sourav-Tambe/Procurement_Billdesk | GRN build deployed 5 Nov |
Antz/procurement/finance-setup-lite/ | Budget heads, sites, staged releases (50/25/25), commitment ledger; port 3022; council outputs and open questions | built 2 Nov, awaiting review |
Antz/procurement/budgets-demo/ | Budgets rebuilt in the Antz shell, current and next financial year; port 3023 | — |
Antz/procurement/docs/budgets-review-3/ | Decisions and open questions; budgets admin spec | 21 Oct |
Code knowledge
Kitchen only (CAP-invoices-reconciliation): receipt reconciliation, invoices, vehicle reconciliation. Antz has pharmacy purchase invoices. No Antz finance or budget capability exists.
Settled
- Bill Desk, by Sourav on 31 Oct:
- BD-2: the received quantity is the truth.
- BD-4: whole delivery notes only.
- BD-6: outcomes are Approved, Rejected or Deferred.
- BD-23 / 24: the UI follows the Compliance module's data grid.
- alert at 80%
- money counts as spent when the invoice is recognised
- amounts include GST
- Finance always decides first
- FS-3: money is committed at the PO's final approval.
- FS-12: an invoice up to 2% over its PO passes.
Open
- BD-8: what happens after Rejected. BD-5: the Excel is a default until Finance shares its sheet.
finance-setup-lite/docs/open-questions.md: 14 questions for Vantara Finance (heads, thresholds, who releases, the 2% variance, the ₹5 L CFO limit).- Conflicts (inferred):
- D8 "flagged, not blocked" vs PR3 / PR4 (a bill on hold can't be sent).
- Budgets review 3 commits money at PO creation, while FS-3 commits it at PO approval.
- Bill Desk has no PO or GRN upstream, but the target needs a three-way match.
Helpdesk
Last updated 19 Nov 2026. Paths are under Studio/projects/.
On the map
Work domain (teal).
- Requests: department queue → ticket → costing → sign-off.
- Setup: department type, cost limits, issue categories, service categories.
- Raised from: any staff, an incident, an asset (scan).
- Ticket life: awaiting costing → pending approval → in progress → completed → locked after 48 h.
- Who · on: any staff, the department in-charge and team · mobile, web.
- Links:
- out: item request → Inventory; work order → Maintenance; purchase request → Procurement (top lane); ticket on asset → Assets
- in: incident → ticket, from GRC
Binding decisions
- D1: a breakdown is always an incident first. A ticket raised directly is for a new need (make, move, install, service).
- D6: asking a store for items is an item request, never a ticket.
- D10: ticket steps (cost it, start it, sign off) are "your turn" items in My work, not task records.
Design work
| Path | What | Status |
|---|---|---|
Antz/helpdesk/case_study.md, project.json | Requirements: 7 statuses, department and zoo cost limits, 48 h revert window | "requirements", updated 2 May 2026; design pending |
Antz/helpdesk/flows/type-a-with-costing/, type-b-without-costing/ | The two department-type flows (v0001–v0002); the 7 generic IT flows are archived | — |
Antz/helpdesk/docs/reference_frappe_helpdesk.md | Study of Frappe Helpdesk | 14 Aug 2026 |
Antz/procurement/helpdesk-only/ | Help Desk lite prototype: list, search, filters, form, detail, settings; from Figma VPKybj9jCMEQKKPynTu7Zo | Hub entry help-desk/requests-list-detail-new-request; Phase 1 built 14 Oct |
Code knowledge (atlas Meta/atlas/modules/help-desk.md)
- Snapshots: SRC-AM-20261118 (mobile) and SRC-AW-20261118 (web dev-release).
- Mobile: full module (present, code-observed). Screens RequestList, CreateRequest, RequestDetails, CostAdd, CompleteRequest, Departments and Request Approvers. Key
add_request. - Web: a full port on dev-release only. Not on prod-release or release/vantara, and not run against a backend.
- What a person may do on a request comes from the server's button-status flags.
- A request points only at a site. Job in-charge is free text, not a user.
Settled
- Two department types (with and without costing), not a 4-flow matrix (case study, 2 May).
- Request, approval and resolution are separate records. The 48 h revert is an explicit timed step (case study, 2 May).
- Lifecycle as in
ARCHITECTURE.md§3.1.
Open
- Atlas U1–U5: server transition rules, approver site scope, push triggers, which zoos run web Help Desk,
entity_typevalues. - A ticket needs a place and an asset field. Today it is site only (atlas §11; the map assumes "ticket on asset").
- "Costing mandatory" is not set on mobile (atlas §11).
- Case study: discovery, metrics and design are marked "needs Sourav".
Maintenance
Last updated 19 Nov 2026. Paths are under Studio/projects/.
On the map
Work domain (teal).
- Planned: maintenance plan → visit → missed or escalated; plans run by date or by meter.
- Work: work order → a line per asset, permit, parts and labour, downtime.
- Vendor work: outside service, AMC visit, gate pass out.
- Work order life: draft → approved → in progress → partly done → closed.
- Who · on: technicians, maintenance in-charge, vendors · mobile, tablet, web.
- Links:
- in: work order, from Helpdesk; maintenance plan, from Assets
- out: parts → Inventory; work on asset → Assets; a part or service not in stock → Procurement
Binding decisions
- D1: breakdowns start as incidents. The incident raises the work order.
- D3: spare parts are stock, issued to the work order and costed to the asset.
- D4: built places (fences, cold rooms, borewells) get a place asset, so maintenance works on them.
- D10: doing a work order or a visit is a your-turn step, not a task record.
Design work
There is no Maintenance project of its own. It lives inside Asset Management.
| Path | What |
|---|---|
Antz/asset-management/flows/maintenance-wo/, flows/ticket-wo/ | Maintenance-to-work-order and ticket-to-work-order flows |
Antz/asset-management/research/flows/F03-maintenance-to-workorder.md | Research flow (17 Jul 2026) |
Antz/asset-management/research/patterns/P05-work-order-model.md | Work order model pattern; evidence E05–E08 |
Antz/asset-management/docs/antz-asset-prd/Antz_Asset_Management_Entities_StateMachines.md | PRD state machines (listed, not read) |
operations-architecture/ARCHITECTURE.md §3.2, F1, F2 | Plan, visit, work order and task records; reactive and preventive flows |
Code knowledge (atlas Meta/atlas/modules/asset-management.md, SRC-AW-20261118)
- Web dev-release only.
- Work orders: list and detail, with per-asset In Progress / Complete / Reject.
- A ticket can raise a work order.
- Maintenance schedules exist but are hidden from the sidebar, and their generated records are empty.
- A failed audit item raises nothing.
- No mobile.
Settled
- Asset PRD ideation (15 Apr):
- D5: a work order covers many assets, tracked per asset.
- D6: missed maintenance is auto-marked.
- D13: an asset goes to Under Maintenance when work starts.
- D14: ticket and work order are peers; completing a work order doesn't resolve the ticket.
- D19: maintenance can be logged without a work order.
Open
- Work order approval has no UI or endpoint in the build (atlas §11).
- Does a schedule generate work orders (atlas U2)?
- The built ticket statuses differ from the PRD and from
ARCHITECTURE.md(atlas §10). - Neither the PRD nor the build has maintenance visits (inferred).
- Should Maintenance get its own project folder? Today it's spread across the asset work.
Assets
Last updated 19 Nov 2026. Paths are under Studio/projects/.
On the map
Work domain (teal).
- Register: asset → tag and ID, component; place asset; meter readings.
- Custody: check-out and check-in, reservation, lease, asset transfer.
- Cover: warranty, AMC, expiry alert.
- Value: depreciation → book value, decommission → disposal.
- Status: available, checked out or leased, under maintenance, missing or damaged, disposed.
- Audit: asset audit → variance; life history.
- Who · on: asset owners, custodians · mobile, web, scan.
- Links:
- in: asset GRN, from Inventory; ticket on asset, from Helpdesk
- out: product master from Inventory (dashed); maintenance plan → Maintenance; disposal → Inventory scrap yard; AMC or warranty renewal → purchase request; capitalisation and total cost of ownership → Finance; breakdown or asset audit → an incident in GRC
Binding decisions
- Boundary: there is one product catalogue, in Inventory. The Asset PRD's own Product entity is dropped.
- D4: built places get a place asset.
- D5: custody is a person or a place. The form leads with person, and the place's owner is accountable.
- D10: AMC, warranty and licence expiry are alerts, not tasks.
- Assets are created from a GRN line whose tracking mode is "asset" (
ARCHITECTURE.md§2.3, F4).
Design work
| Path | What | Status |
|---|---|---|
Antz/asset-management/ (project.json, case_study.md) | PRD v1: 28 entities, 12 state machines, 36 screens, 10 flows | PRD published 20 Apr 2026 |
Antz/asset-management/docs/antz-asset-prd/ | PRD, IA, UX flows, entities and state machines, ideation decisions, doctrine resolutions | — |
Antz/asset-management/docs/antz-asset-ui-prototype/, ui-host/antz-asset-ui/ | Static HTML prototype, about 196 screens | Apr 2026 |
Antz/asset-management/research/ | Design research built on EZO | 17 Jul 2026 |
Antz/asset-management-build/ | Build plan (waves), data model, spec copies; Figma 679IijiM9ZvnmAdMSNOyrJ ("asset-with-design-system") | — |
Antz/asset-management-build-research/ | Phase 1 scope: register, custody, transfer, missing/found; maintenance, tickets, audit and requests deferred | 28 Jun 2026 |
Code knowledge (atlas Meta/atlas/modules/asset-management.md)
- Web dev-release only: 46 routes and 18 masters. Absent from prod-release and Vantara, no mobile, not in Kitchen.
- Lease, transfer and dispose are TODO stubs.
- Reports use mock data, and several detail tabs are commented out.
- The build quotes PRD decisions D7 and D14, so it follows the PRD (inferred).
Settled
- PRD ideation D1–D22 (15 Apr), including:
- D7: a ticket's asset is optional.
- D15: disposal approval by threshold.
- D16: check-out to a place.
Open
- Build forks (
asset-management-build/CLAUDE.md§6):- the approval model (not settled)
- the custody target (answered by D5)
- how much vendor management to build first
GRC
Last updated 19 Nov 2026. Paths are under Studio/projects/.
On the map
Assurance domain (green).
- Governance ("owns rules"): policy → standard → rule → procedure.
- Assurance: check definition → schedule → session → finding → action (CAPA).
- Incidents: incident → investigation → CAPA, then an effectiveness check.
- Incident kinds: injury or escape, near miss or spill, theft or missing, breakdown.
- Compliance: outside inspection → finding; evidence pack; licences and returns.
- Competency: training → competency; permit to work.
- Who · on: auditors, safety officer, place owners, any staff · tablet, mobile, web.
- Links:
- out: audits, checklists and CAPA → Tasks; counts and audits → Inventory; incident → ticket → Helpdesk; licence renewal → Procurement
- in: breakdowns and asset audits from Assets, as incidents
Binding decisions
- D1: every breakdown is an incident.
- D7: risk is findings only. There is no hazard register.
- D10: audits, assessments, checklists, CAPA actions, finding fixes, investigations and read-and-sign are task records in Tasks, and a task can carry a checklist, assessment or audit form. Licence expiry is an alert.
- F6: schedule → session → finding → fix (CAPA, work order or ticket) → verified by another person → rule status → evidence pack.
- F7: report → investigate → CAPA → root cause pointing at the rule that failed → closure by severity.
Rules (Define)
- Design:
Antz/design-tab-library/Projects/GRC-v2/grc-v2/docs/presentation/ia-map-v2.html, the full six-part GRC map (17 Nov).grc-flowchart.html, the G → R → C loop (17 Nov).sop-lifecycle-v1.2.html(10 Oct), the style reference for this whole architecture, and the SOP series v2–v7.
- Pass/fail criteria live with the requirement, not the audit (
GRC-v1/GRC-Tablet-Prototype/README.md). - Reports for the director or a regulator sit in Policies & Standards (grc-v2 I-2).
- ia-map-v2 proposes a Risk register, which conflicts with D7.
- Training & competency is marked "proposed".
Checks and audits (Verify)
- Design:
GRC-v1/GRC-Tablet-Prototype/(the model reference), plus earlier builds; live at antz-grc.pages.dev and antz-grc-mobile.pages.dev (which URL matches which folder is inferred).GRC-v2/grc-v2/, the audits tablet prototype, live at https://antz-grc-v2.pages.dev. Last commit 18 Nov; developer pack inhandoff/.Antz/audit-management-research/, IA indocs/ia-v2.md. It uses older words like "Run" and "Fix task".
enclosure-audit.md, the mobile headcount check (count match / mismatch); assessments.md, assessment types. Both from SRC-AM / AW-20261118, with client-side permission keys.grc-v2/docs/decisions.md):- G-1: tabs are Dashboard · Governance · Audits · Risk · Compliance, problems are called Findings, and one run is a Session.
- AF-1…10: an audit is a template, and entities are attached when it's scheduled.
- S-1…10 (4 Oct): findings are raised at Complete, offline is out of scope, and a reopen keeps the completion time.
- I-1…9: insights default to 30 days.
- G-7 / 8: severity shows as a dot plus a tag.
- AF-9: should "When" leave the creation form?
- audit-management HANDOFF §3: PM-Q1, Q-A, Q-B, Q-C, Q-E, Q-G.
- Rulings G-2, G-6 and G-9…17 are in
plan-grc.md, which wasn't read.
Incidents (Report)
- Design (
Antz/incident-report-system/):app/: the old build; its dashboard is on the hub (18 Nov).app-v2/: Help Desk kit, port 3032; the listing variant isn't picked yet.app-uui/: Untitled UI, 20 screens, port 3033, QA 41 pass / 5 warn; not deployed.council/:decisions.md(5 Nov),irs-untitled-ui/register.md,ehs-grc-parallels/(provisional, 18 Nov).
missing-animal.md (INC- records); notes-observations.md (priority Low to Critical).- Severity: Low / Medium / High / Critical.
- Statuses: Open → Under Investigation → CAPA Pending → Awaiting Approval → Closed.
- Fields are mandatory only at the step that fills them.
- Missing / found animal becomes part of incidents (Sourav, 18 Nov).
register.md§8 has 8 decisions for Sourav, including whether near miss is a flag or a type.- Back navigation and deploy approval (TASKS-IN-HAND).
Compliance (Prove)
- Design:
Code/compliance-lite/is the source of truth since 30 Oct; port 3024; live at https://antz-compliance-lite.pages.dev (v2.1, 12 Nov).Antz/web-compliance-v2/HANDOFF.md: a 9-stage transfer workflow; FigmamZdOa24hp5TQhhPpbp7Hp0.
compliance.md, deep, web): 30 screens in v1; Parivesh 7 screens.compliance-exchanges.md, decisions from 12 Nov (sourav-20261112-*).- Licences & returns in the GRC IA isn't linked to Animal Exchanges (inferred).
- Animal exchanges and PARIVESH aren't on the map yet.
Tasks
Last updated 19 Nov 2026. Paths are under Studio/projects/.
On the map
People domain (orange). Orange is used only for what a person does today.
Tasks box, above Inventory:
- From GRC: audit, assessment, checklist, CAPA action, finding fix, investigation, read & sign / training.
- Other sources: own or assigned, recurring routine, handover checklist, pre-use checklist.
- Task: steps; a form (checklist, assessment or audit); photo proof; skip with a reason.
- Assign to: a person, a team (one claims it, or all do it), a role at a place.
- Task life: open, in progress, done or late, missed or skipped.
- Views: team view, calendar.
- Who · on: everyone, with managers and modules assigning · mobile, tablet, web.
My work band (one screen): my tasks · your turn (tickets, work orders, PRs, GRNs, invoices) · my approvals · my alerts.
Binding decisions
- D10 (19 Nov):
- Tasks is its own module, and only the sources above become task records.
- Steps inside tickets, work orders, PRs, GRNs and invoices are your-turn items.
- Approvals stay in the Approvals inbox.
- AMC, warranty and licence expiry, low stock and overdue returns are alerts.
- This supersedes the "where to-dos come from" table in
ARCHITECTURE.md§4.2.
Design work
| Path | What | Status |
|---|---|---|
Antz/task-management/docs/Antz_Task_Management_PRD_v2.0.md | PRD: 22 screens, 5 state machines, 17 notifications, 10 flows | PRD v2, 20 Apr 2026 |
Antz/task-management/task-management-ui/ | Hi-fi: V1 frozen in v1/; V2 composer v2.html; four listing / detail lines (list.html, list-v2.html, list-v3.html, detail-v2.html); card galleries; tab.html tablet plan | v1 complete, 22–24 Sep; Untitled UI since 21 Sep |
Figma VPKybj9jCMEQKKPynTu7Zo (sections 4097:50701, 4387:96273, 4428:97059), 3ThgDnFwHu9F3ie1zlPgwW | Tasks screens and draft | — |
Antz/design-tab-library/Projects/Antz-Home/ | Home with My work and approval widgets | 23 Oct |
Code knowledge
There is no tasks module in the atlas.
Settled (PRD §14)
- D1: a rolling 14-day lookahead.
- D2: claim on start.
- D4: 24 h re-submit, 4 h for medical.
- D5: 1–5 photos, camera only for medical.
- D7: 15-minute overdue grace.
- D8: the approver is a role pool, with an optional named override.
- D9: one instance per location.
- D10 (PRD): a selective audit log.
Open
- The listing and detail line isn't picked yet (memory note).
docs/tablet-portrait-plan.md:- left rail or top tabs
- landing on the hub or on the first task
- detail v1 or v2
docs/detail-v2-concept.md: the verb in the band or in a sticky footer.docs/listing-replan-agenda.md §7: four agenda questions.Approvals
Last updated 19 Nov 2026. Paths are under Studio/projects/.
On the map
A shared engine band at the top: one inbox · approval policy · amount bands · steps and decisions · delegation. "My approvals" is part of the My work screen.
Binding decisions
- D2: one Approvals inbox per person, across every module.
ARCHITECTURE.md§4.1: one policy engine (record type + condition + route).- Amount bands:
- up to the department or cost centre limit: automatic, or the owner decides
- up to the zoo limit: escalation or site approver
- above the zoo limit: management group
- Amount bands:
- Decisions: approve, reject with a reason, send back, or decide line by line.
- Also covers: re-route when the band changes, holds, a self-approval guard, escalation, delegation, a trail.
- A1–A3: tickets and work orders.
- A4–A10: issue, asset use and transfer, stock transfer, adjustment, count, new product.
- A11–A14: purchase request, PO, invoice, payment.
- A15–A16: decommission, disposal.
- A17: policy. A18: task. A19: CAPA verification. A20: incident close. A21: sign-off.
Design work
| Path | What |
|---|---|
Antz/procurement/Procure-v1/DECISIONS.md | Procurement approvals A1–A14; Help Desk T17 / T18 |
Antz/helpdesk/case_study.md | Help Desk department and zoo cost limits (requirements stage) |
Antz/design-tab-library/Projects/Antz-Home/ | Home approval widgets: pending, queue, priority, pipeline (grep only) |
| Task PRD screen A1 | Approvals queue, with stuck rejections |
There is no approvals project of its own.
Code knowledge (atlas, SRC-AM / AW-20261118)
- Mobile Approvals tile: opens
ApprovalTask, which is for animal transfers only. Gated byapproval_move_animal_externaland the zoo settingANIMAL_TRANSFER_REQUIRES_APPROVAL. The server decides the buttons. - Web: approve and reject are dead code; view and comment only.
- Help Desk settings:
request_management_approval_threshold,request_management_approvers, and per-departmentmax_cost_for_auto_approval(masters-config.md).
Settled
- Procure-v1: only the highest level that applies decides, and the cost centre owner replaces the department approver.
- Help Desk T17 / T18: approve or reject only, with one decider per ticket.
Open (conflicts with the target, inferred)
- Procure A9 "approvals only in the Procure portal" vs D2 (one inbox).
- Procure A14 "nothing happens if an approver doesn't act" vs escalation in §4.1.
- Help Desk T17 "no send-back" vs send-back in §4.1.
- There's no design for the one inbox or for the policy setup screen.
Foundations
Last updated 19 Nov 2026. Paths are under Studio/projects/.
On the map
Four bands at the bottom ("Foundations"), shared by every system:
- People & Permissions: person, department, role, permission per site or store, cost centre, leave and delegation.
- Sites & Places: site, zone, area, spot, "store is an area", animals from Antz.
- Vendors: supplier, service provider, buyer (disposal), rate history, rate contract, scorecard.
- Rules library: policy, standard, rule, procedure, licence and return, training and competency (owned by GRC).
Binding decisions
ARCHITECTURE.md§1: five shared trees every module reads; "nothing in a module re-creates them".- §1.1 Places:
- One tree: group → zoo → site → zone / section → typed area → spot.
- A store is an area type, with racks and bins.
- Every record carries one place, and the place owner is the default approver.
- Roles are bundles of permissions (
can:transfer.approve). - Permissions are granted per zoo, site and store, and a person can hold several roles.
- Leave and delegation live here.
People & Permissions
- Design: none beyond
ARCHITECTURE.md§1.2. - Code (atlas
users-roles-access.md, SRC-AM / AW / KI / KA / KB-20261118):- Users have the tabs Users · Sites · Permissions.
- One role per user, with per-module levels from None up to View + Add + Edit + Delete.
- Location access is per site or section.
- Mobile role values override user settings, while web doesn't merge them.
- The web Users module isn't on prod-release. Kitchen has a separate role system.
- All checks are client-side.
- Atlas U1–U5: where the permission tree is defined, server enforcement, merge vs replace, auto-creating Kitchen users, designations.
- There is no per-site role, which blocks GRC (atlas §11).
Sites & Places
- Design: Drill Down picker at
Antz/design-tab-library/antz-ui-standards/components/drill-down/;Antz/web-housing/(analysis). - Code (atlas
housing.md):- Hierarchy: cluster (optional) → site → section → enclosure, with sub-enclosures.
- No capacity or area fields.
- Mobile has one shared picker; web has five local pickers.
- In-charges per level; transfer and security teams per site.
- Atlas U1–U6: what site access grants, what "system-generated" means, containment rules, how QR codes are made, whether clusters are in use, keeper areas.
- The target tree adds buildings, rooms and stores to the Antz tree. That join isn't designed.
Vendors
- Design: vendor views inside Procure-v1 (by vendor, vendor page, scorecard);
procurement/docs/vendors-review-1.zip(not opened). - Code:
- Kitchen: vendors, rate card, brands (SRC-KA / KB).
- Antz Pharmacy: its own supplier list.
- Masters: two vendor lists and two UOM lists today (
masters-config.md).
- One vendor master, and Pharmacy suppliers merge into it.
- Kept separate from Help Desk vendors.
- Managed by the procurement team and admin.
- The vendor page has a scorecard: on-time %, short deliveries, average delay.
- No vendor onboarding, approval or KYC flow exists.
- Rate contracts aren't designed.
- Help Desk vendors being separate (Procure U6) conflicts with one vendor master (§1.4).
Masters
- Code (atlas
masters-config.md):- 15 masters on mobile and web, with different gates.
- Zoo settings arrive at sign-in, and most have no editor.
- Most masters are dev-release only.
ARCHITECTURE.md §8 Settings: places · departments and cost centres · approval policies · masters · catalogue.client_id, branch per zoo).