markets:
  - name: Professional Services
    os:
      - name: "n-lawOS"
        buyer: "Managing partner / COO of a law firm or in-house General Counsel — pays per fee-earner seat."
        os_test: "Distinct buyer (law firm partners/GC), regulated state model (matters, conflicts, client money, privilege), unique vocabulary (matter, retainer, disbursement, Chinese wall) and thousands of repeatable firms — not a re-skin of any other OS."
        sectors:
          - name: "Litigation & Disputes"
            note: "Regulated: solicitors are licensed by the SRA; rights of audience, client-money and privilege rules apply."
            operating_domains:
              - Case matters and pleadings
              - Court deadlines and the litigation timetable
              - "Disclosure / e-discovery document sets"
              - Witness statements and evidence bundles
              - Counsel and expert instructions
              - Settlement and offer tracking
              - Costs budgets and recoverability
            vocabulary:
              - { term: Client, runtime_type: Actor }
              - { term: Opposing party, runtime_type: Actor }
              - { term: Instructed barrister, runtime_type: Actor }
              - { term: Matter, runtime_type: Object }
              - { term: Pleading, runtime_type: Artefact }
              - { term: Disclosure bundle, runtime_type: Artefact }
              - { term: Witness statement, runtime_type: Artefact }
              - { term: Hearing date, runtime_type: Event }
              - { term: Order received, runtime_type: Event }
              - { term: Limitation expired, runtime_type: State }
              - { term: Matter on hold, runtime_type: State }
              - { term: Settle or proceed to trial, runtime_type: Decision }
              - { term: Part 36 offer, runtime_type: Decision }
              - { term: Litigation timetable, runtime_type: Workflow }
              - { term: Judgment obtained, runtime_type: Outcome }
              - { term: Costs recovered, runtime_type: Outcome }
              - { term: Win rate by matter type, runtime_type: Learning }
          - name: "Corporate / M&A"
            note: "Regulated: SRA-authorised; anti-money-laundering source-of-funds checks mandatory on transactions."
            operating_domains:
              - Deal matters and transaction structure
              - "Due-diligence data rooms and findings"
              - "Transaction document suites (SPA, disclosure letter)"
              - Conditions precedent and the completion checklist
              - Signing and completion logistics
              - "Warranties, indemnities and disclosure"
              - "Post-completion filings (Companies House, Stamp Duty)"
            vocabulary:
              - { term: Buyer / seller, runtime_type: Actor }
              - { term: Deal lead partner, runtime_type: Actor }
              - { term: Deal (transaction), runtime_type: Object }
              - { term: Data room, runtime_type: Object }
              - { term: Share purchase agreement, runtime_type: Artefact }
              - { term: Disclosure letter, runtime_type: Artefact }
              - { term: "DD red-flag report", runtime_type: Artefact }
              - { term: Signing, runtime_type: Event }
              - { term: Completion, runtime_type: Event }
              - { term: Conditions precedent satisfied, runtime_type: State }
              - { term: Subject to contract, runtime_type: State }
              - { term: Proceed / walk away, runtime_type: Decision }
              - { term: "Price-adjustment call", runtime_type: Decision }
              - { term: Completion checklist, runtime_type: Workflow }
              - { term: Deal closed, runtime_type: Outcome }
              - { term: "Time-to-completion", runtime_type: Learning }
          - name: "Conveyancing & Real Estate"
            note: "Regulated: SRA + CLC; strict client-account rules and SDLT/Land Registry statutory deadlines."
            operating_domains:
              - Property files (sale/purchase/remortgage)
              - Title searches and Land Registry priority
              - Property enquiries and replies
              - The conveyancing chain
              - Client and completion monies (client account)
              - Exchange and completion dates
              - SDLT and registration
            vocabulary:
              - { term: Buyer / seller client, runtime_type: Actor }
              - { term: Conveyancer, runtime_type: Actor }
              - { term: Property file, runtime_type: Object }
              - { term: Title deed, runtime_type: Object }
              - { term: Local search result, runtime_type: Artefact }
              - { term: Contract pack, runtime_type: Artefact }
              - { term: Exchange of contracts, runtime_type: Event }
              - { term: Completion day, runtime_type: Event }
              - { term: Awaiting mortgage offer, runtime_type: State }
              - { term: Chain broken, runtime_type: State }
              - { term: Ready to exchange, runtime_type: Decision }
              - { term: Release completion funds, runtime_type: Decision }
              - { term: Completion workflow, runtime_type: Workflow }
              - { term: Keys handed over, runtime_type: Outcome }
              - { term: Title registered, runtime_type: Outcome }
              - { term: "Avg days exchange-to-completion", runtime_type: Learning }
          - name: "Private Client (Wills, Probate & Trusts)"
            note: "Regulated: reserved probate activity under SRA; IHT400 statutory filing and trustee fiduciary duties."
            operating_domains:
              - Will instructions and drafting
              - Estate administration matters
              - Lasting Powers of Attorney
              - Trust deeds and trustee duties
              - Inheritance Tax planning and accounts
              - Estate assets and liabilities register
              - Distributions to beneficiaries
            vocabulary:
              - { term: Testator / settlor, runtime_type: Actor }
              - { term: Executor, runtime_type: Actor }
              - { term: Beneficiary, runtime_type: Actor }
              - { term: Will, runtime_type: Artefact }
              - { term: Estate, runtime_type: Object }
              - { term: Grant of probate, runtime_type: Artefact }
              - { term: Trust, runtime_type: Object }
              - { term: Date of death, runtime_type: Event }
              - { term: Grant issued, runtime_type: Event }
              - { term: Estate in administration, runtime_type: State }
              - { term: IHT due / not due, runtime_type: Decision }
              - { term: Deed of variation, runtime_type: Decision }
              - { term: Administration workflow, runtime_type: Workflow }
              - { term: Estate distributed, runtime_type: Outcome }
              - { term: Final estate accounts, runtime_type: Artefact }
              - { term: Avg estate admin duration, runtime_type: Learning }
          - name: Employment Law
            note: "Regulated: SRA-authorised advice; statutory tribunal time limits (3 months less a day)."
            operating_domains:
              - Advisory matters and retainers
              - Tribunal claims and ET3 responses
              - Settlement agreements
              - Disciplinary and grievance processes
              - TUPE transfers and redundancy programmes
              - Contracts and policy drafting
              - ACAS early conciliation
            vocabulary:
              - { term: Employer client, runtime_type: Actor }
              - { term: Claimant employee, runtime_type: Actor }
              - { term: Tribunal claim, runtime_type: Object }
              - { term: ET1 / ET3, runtime_type: Artefact }
              - { term: Settlement agreement, runtime_type: Artefact }
              - { term: ACAS conciliation started, runtime_type: Event }
              - { term: Tribunal listing, runtime_type: Event }
              - { term: Claim defended, runtime_type: State }
              - { term: Out of time, runtime_type: State }
              - { term: Settle vs defend, runtime_type: Decision }
              - { term: "Without-prejudice offer", runtime_type: Decision }
              - { term: Grievance process, runtime_type: Workflow }
              - { term: Compromise reached, runtime_type: Outcome }
              - { term: Claim dismissed, runtime_type: Outcome }
              - { term: Settlement vs award gap, runtime_type: Learning }
          - name: Intellectual Property
            note: "Regulated: IPReg-registered attorneys; statutory renewal/annuity deadlines that void rights if missed."
            operating_domains:
              - Patent and trademark portfolios
              - Filing and prosecution actions
              - Renewal and annuity diary
              - Oppositions and disputes
              - Licensing and assignment agreements
              - "Freedom-to-operate / clearance searches"
              - Infringement enforcement
            vocabulary:
              - { term: Rights holder, runtime_type: Actor }
              - { term: Patent attorney, runtime_type: Actor }
              - { term: IP portfolio, runtime_type: Object }
              - { term: Trademark application, runtime_type: Object }
              - { term: Office action, runtime_type: Artefact }
              - { term: Licence agreement, runtime_type: Artefact }
              - { term: Filing date, runtime_type: Event }
              - { term: Renewal due, runtime_type: Event }
              - { term: Registered / pending, runtime_type: State }
              - { term: Lapsed, runtime_type: State }
              - { term: File / abandon, runtime_type: Decision }
              - { term: Oppose registration, runtime_type: Decision }
              - { term: Prosecution workflow, runtime_type: Workflow }
              - { term: Rights granted, runtime_type: Outcome }
              - { term: Renewal compliance rate, runtime_type: Learning }
      - name: "n-taxOS"
        buyer: "Tax partner or owner of a tax-advisory practice (or Head of Tax in-house) — pays per adviser seat plus volume of returns."
        os_test: "Own buyer and budget, a deadline-and-position state model driven by statute (filing windows, enquiries, elections), distinct vocabulary (computation, disclosure, relief, enquiry) and thousands of tax firms — not generic accounting."
        sectors:
          - name: "Personal Tax (Self-Assessment)"
            note: "Regulated: HMRC agent authorisation (64-8); AML supervision and PCRT ethical standards apply."
            operating_domains:
              - "Client self-assessment returns"
              - Income and gains schedules
              - "Filing and payment-on-account deadlines"
              - "Allowances, reliefs and elections"
              - HMRC correspondence and enquiries
              - Capital gains computations
              - Payments on account tracking
            vocabulary:
              - { term: Taxpayer client, runtime_type: Actor }
              - { term: Tax adviser, runtime_type: Actor }
              - { term: Tax return, runtime_type: Object }
              - { term: Tax computation, runtime_type: Artefact }
              - { term: Income schedule, runtime_type: Artefact }
              - { term: Return submitted to HMRC, runtime_type: Event }
              - { term: 31 January deadline, runtime_type: Event }
              - { term: Awaiting client records, runtime_type: State }
              - { term: Filed / overdue, runtime_type: State }
              - { term: Claim a relief, runtime_type: Decision }
              - { term: Disclose or not, runtime_type: Decision }
              - { term: Return preparation workflow, runtime_type: Workflow }
              - { term: Tax liability calculated, runtime_type: Outcome }
              - { term: Refund secured, runtime_type: Outcome }
              - { term: "On-time filing rate", runtime_type: Learning }
          - name: Corporation Tax
            note: "Regulated: HMRC agent; iXBRL/CT600 statutory filing and instalment-payment regime for large companies."
            operating_domains:
              - Company CT600 returns and computations
              - "Tax-adjusted profit and add-backs"
              - Capital allowances pools
              - Group relief and loss claims
              - "R&D and other relief claims"
              - iXBRL tagging and submission
              - Quarterly instalment payments
            vocabulary:
              - { term: Company client, runtime_type: Actor }
              - { term: Corporate tax manager, runtime_type: Actor }
              - { term: CT600 return, runtime_type: Object }
              - { term: Tax computation, runtime_type: Artefact }
              - { term: Capital allowances claim, runtime_type: Artefact }
              - { term: Accounting period end, runtime_type: Event }
              - { term: Filing deadline (12 months), runtime_type: Event }
              - { term: Draft computation, runtime_type: State }
              - { term: Filed with HMRC, runtime_type: State }
              - { term: Surrender group relief, runtime_type: Decision }
              - { term: Carry back / forward losses, runtime_type: Decision }
              - { term: CT compliance workflow, runtime_type: Workflow }
              - { term: Tax charge agreed, runtime_type: Outcome }
              - { term: Relief claimed, runtime_type: Outcome }
              - { term: Effective tax rate trend, runtime_type: Learning }
          - name: "VAT & Indirect Tax"
            note: "Regulated: Making Tax Digital mandatory; HMRC-supervised; penalties for late/incorrect returns."
            operating_domains:
              - VAT registrations and schemes
              - Periodic VAT returns (MTD)
              - Input/output VAT reconciliation
              - Partial exemption and special methods
              - "Cross-border and place-of-supply rules"
              - VAT inspections and assessments
              - Error correction disclosures
            vocabulary:
              - { term: Registered business, runtime_type: Actor }
              - { term: VAT specialist, runtime_type: Actor }
              - { term: VAT return, runtime_type: Object }
              - { term: VAT account, runtime_type: Object }
              - { term: MTD submission, runtime_type: Artefact }
              - { term: Return period end, runtime_type: Event }
              - { term: Payment deadline, runtime_type: Event }
              - { term: Repayment position, runtime_type: State }
              - { term: Under inspection, runtime_type: State }
              - { term: Choose a VAT scheme, runtime_type: Decision }
              - { term: Voluntary disclosure, runtime_type: Decision }
              - { term: Quarterly VAT cycle, runtime_type: Workflow }
              - { term: Return accepted, runtime_type: Outcome }
              - { term: Assessment resolved, runtime_type: Outcome }
              - { term: Reclaim accuracy rate, runtime_type: Learning }
          - name: "R&D and Tax Incentives"
            note: "Regulated: post-April-2023 mandatory claim notification + AIF; HMRC scrutiny regime under PCRT."
            operating_domains:
              - "R&D claim projects"
              - Qualifying expenditure capture
              - "Technical narrative and competent-professional input"
              - Additional information form (AIF)
              - Claim notification deadlines
              - HMRC compliance checks
              - "Patent Box and creative-industry reliefs"
            vocabulary:
              - { term: Claimant company, runtime_type: Actor }
              - { term: Competent professional, runtime_type: Actor }
              - { term: "R&D claim", runtime_type: Object }
              - { term: Qualifying expenditure, runtime_type: Object }
              - { term: Technical narrative, runtime_type: Artefact }
              - { term: Additional information form, runtime_type: Artefact }
              - { term: Claim notification window, runtime_type: Event }
              - { term: Submitted to HMRC, runtime_type: Event }
              - { term: Under enquiry, runtime_type: State }
              - { term: Claim approved, runtime_type: State }
              - { term: Scheme eligibility (merged/ERIS), runtime_type: Decision }
              - { term: Include / exclude a cost, runtime_type: Decision }
              - { term: Claim build workflow, runtime_type: Workflow }
              - { term: Credit received, runtime_type: Outcome }
              - { term: Claim acceptance rate, runtime_type: Learning }
          - name: "International & Transfer Pricing"
            note: "Regulated: OECD BEPS / Pillar Two and statutory TP documentation; penalties for non-arm's-length pricing."
            operating_domains:
              - "Cross-border entity structures"
              - "Transfer-pricing policies and benchmarking"
              - "Permanent-establishment risk"
              - "Double-tax treaty positions"
              - "Country-by-country and Pillar Two reporting"
              - Local file / master file documentation
              - Withholding tax management
            vocabulary:
              - { term: Multinational group, runtime_type: Actor }
              - { term: Group tax director, runtime_type: Actor }
              - { term: Intercompany transaction, runtime_type: Object }
              - { term: TP policy, runtime_type: Object }
              - { term: Local file, runtime_type: Artefact }
              - { term: Benchmarking study, runtime_type: Artefact }
              - { term: "Year-end true-up", runtime_type: Event }
              - { term: CbCR filing date, runtime_type: Event }
              - { term: "Arm's-length / at-risk", runtime_type: State }
              - { term: PE exposure, runtime_type: State }
              - { term: "Set the arm's-length price", runtime_type: Decision }
              - { term: Treaty relief claim, runtime_type: Decision }
              - { term: TP documentation cycle, runtime_type: Workflow }
              - { term: Position defended, runtime_type: Outcome }
              - { term: Effective group rate, runtime_type: Learning }
          - name: "Tax Investigations & Disputes"
            note: "Regulated: COP8/COP9 statutory procedures; legal-professional-privilege boundaries and PCRT obligations."
            operating_domains:
              - HMRC enquiry and investigation cases
              - "Disclosure facilities (WDF, CDF/COP9)"
              - Information notices and deadlines
              - Settlement and penalty negotiations
              - Voluntary disclosures
              - Alternative dispute resolution
              - Tribunal appeals
            vocabulary:
              - { term: Taxpayer under enquiry, runtime_type: Actor }
              - { term: HMRC inspector, runtime_type: Actor }
              - { term: Enquiry case, runtime_type: Object }
              - { term: Disclosure report, runtime_type: Artefact }
              - { term: Information notice, runtime_type: Artefact }
              - { term: Enquiry opened, runtime_type: Event }
              - { term: Closure notice, runtime_type: Event }
              - { term: Under investigation, runtime_type: State }
              - { term: Settled, runtime_type: State }
              - { term: Disclose vs contest, runtime_type: Decision }
              - { term: Accept the penalty, runtime_type: Decision }
              - { term: Disclosure workflow, runtime_type: Workflow }
              - { term: Liability agreed, runtime_type: Outcome }
              - { term: Penalty mitigated, runtime_type: Outcome }
              - { term: Avg penalty reduction, runtime_type: Learning }
      - name: "n-accOS"
        buyer: Practice principal / partner of an accountancy firm — pays per client portfolio and per accountant seat.
        os_test: "Distinct buyer (accountancy practice), a recurring period-and-ledger state model (year-end, month-end, statutory accounts), bookkeeping/compliance vocabulary and a vast repeatable firm population — separate from pure tax and from audit."
        sectors:
          - name: "Year-End Accounts & Compliance"
            note: "Regulated: Companies Act filing obligations; AML supervision and ICAEW/ACCA ethical code."
            operating_domains:
              - "Client year-end jobs"
              - Trial balance and adjustments
              - Statutory accounts preparation
              - Companies House filing
              - Disclosure checklists (FRS 102/105)
              - Accounts approval and signing
              - Confirmation statements
            vocabulary:
              - { term: Client business, runtime_type: Actor }
              - { term: Accounts preparer, runtime_type: Actor }
              - { term: "Year-end job", runtime_type: Object }
              - { term: Trial balance, runtime_type: Object }
              - { term: Statutory accounts, runtime_type: Artefact }
              - { term: Adjustment journal, runtime_type: Artefact }
              - { term: "Year-end date", runtime_type: Event }
              - { term: Accounts filing deadline, runtime_type: Event }
              - { term: Awaiting records, runtime_type: State }
              - { term: Approved for filing, runtime_type: State }
              - { term: Choose accounting basis, runtime_type: Decision }
              - { term: "Going-concern judgement", runtime_type: Decision }
              - { term: Accounts production workflow, runtime_type: Workflow }
              - { term: Accounts filed, runtime_type: Outcome }
              - { term: Job turnaround time, runtime_type: Learning }
          - name: "Bookkeeping & Management Accounts"
            operating_domains:
              - Transaction posting and coding
              - Bank reconciliations
              - Accounts payable / receivable
              - "Month-end close"
              - Management reporting packs
              - Cashflow and KPI dashboards
              - Nominal ledger maintenance
            vocabulary:
              - { term: Client business, runtime_type: Actor }
              - { term: Bookkeeper, runtime_type: Actor }
              - { term: Transaction, runtime_type: Object }
              - { term: Nominal ledger, runtime_type: Object }
              - { term: Management accounts pack, runtime_type: Artefact }
              - { term: Bank reconciliation, runtime_type: Artefact }
              - { term: "Month-end close", runtime_type: Event }
              - { term: Statement imported, runtime_type: Event }
              - { term: Unreconciled, runtime_type: State }
              - { term: Books closed, runtime_type: State }
              - { term: Code a transaction, runtime_type: Decision }
              - { term: Accrue or defer, runtime_type: Decision }
              - { term: Monthly close workflow, runtime_type: Workflow }
              - { term: Reconciled ledger, runtime_type: Outcome }
              - { term: "Days-to-close", runtime_type: Learning }
          - name: "Payroll & Pensions"
            note: "Regulated: HMRC RTI mandatory; The Pensions Regulator auto-enrolment duties enforced by penalty."
            operating_domains:
              - Employee payroll runs
              - PAYE / NIC calculations
              - RTI submissions to HMRC
              - "Auto-enrolment pension contributions"
              - Statutory pay (SSP/SMP)
              - "Year-end P60s and P11Ds"
              - Payslip and BACS processing
            vocabulary:
              - { term: Employer client, runtime_type: Actor }
              - { term: Payroll administrator, runtime_type: Actor }
              - { term: Pay run, runtime_type: Object }
              - { term: Employee record, runtime_type: Object }
              - { term: Payslip, runtime_type: Artefact }
              - { term: FPS / RTI submission, runtime_type: Artefact }
              - { term: Pay date, runtime_type: Event }
              - { term: RTI submitted, runtime_type: Event }
              - { term: Pending approval, runtime_type: State }
              - { term: Run finalised, runtime_type: State }
              - { term: Apply a deduction, runtime_type: Decision }
              - { term: "Re-enrol / opt-out", runtime_type: Decision }
              - { term: Payroll cycle, runtime_type: Workflow }
              - { term: Employees paid, runtime_type: Outcome }
              - { term: "RTI on-time rate", runtime_type: Learning }
          - name: Company Secretarial
            note: "Regulated: Companies Act 2006 statutory filing and PSC obligations; strike-off risk for non-compliance."
            operating_domains:
              - Statutory registers and records
              - "Companies House filings (CS01, AP01)"
              - Board and shareholder resolutions
              - Share allotments and transfers
              - PSC register maintenance
              - Registered office and director changes
              - Annual confirmation statements
            vocabulary:
              - { term: Company, runtime_type: Actor }
              - { term: Company secretary, runtime_type: Actor }
              - { term: Statutory register, runtime_type: Object }
              - { term: Share capital, runtime_type: Object }
              - { term: Board resolution, runtime_type: Artefact }
              - { term: Confirmation statement, runtime_type: Artefact }
              - { term: Filing made, runtime_type: Event }
              - { term: Confirmation date, runtime_type: Event }
              - { term: Up to date, runtime_type: State }
              - { term: Overdue filing, runtime_type: State }
              - { term: Allot or transfer shares, runtime_type: Decision }
              - { term: Pass a resolution, runtime_type: Decision }
              - { term: Filing calendar workflow, runtime_type: Workflow }
              - { term: Register updated, runtime_type: Outcome }
              - { term: Filing compliance score, runtime_type: Learning }
          - name: Outsourced Finance / Virtual CFO
            operating_domains:
              - Client finance functions
              - Budgets and forecasts
              - Cashflow management
              - Board reporting packs
              - Funding and fundraising support
              - KPI scorecards
              - "Scenario and what-if modelling"
            vocabulary:
              - { term: Client business owner, runtime_type: Actor }
              - { term: Fractional CFO, runtime_type: Actor }
              - { term: Budget, runtime_type: Object }
              - { term: Cashflow forecast, runtime_type: Object }
              - { term: Board pack, runtime_type: Artefact }
              - { term: "Three-way model", runtime_type: Artefact }
              - { term: Board meeting, runtime_type: Event }
              - { term: Forecast refreshed, runtime_type: Event }
              - { term: On budget, runtime_type: State }
              - { term: Cash runway critical, runtime_type: State }
              - { term: Approve spend, runtime_type: Decision }
              - { term: Raise / cut burn, runtime_type: Decision }
              - { term: Reporting cycle, runtime_type: Workflow }
              - { term: Funding secured, runtime_type: Outcome }
              - { term: Forecast accuracy, runtime_type: Learning }
          - name: "Insolvency & Restructuring"
            note: "Regulated: licensed insolvency practitioners (IPA/ICAEW); Insolvency Act statutory duties and SIP standards."
            operating_domains:
              - "Insolvency cases (CVL, administration, IVA)"
              - Statement of affairs
              - Creditor claims and meetings
              - Asset realisations
              - Statutory notices and reports
              - Distributions and dividends to creditors
              - Director conduct reporting
            vocabulary:
              - { term: Insolvent company / debtor, runtime_type: Actor }
              - { term: Insolvency practitioner, runtime_type: Actor }
              - { term: Creditor, runtime_type: Actor }
              - { term: Insolvency case, runtime_type: Object }
              - { term: Statement of affairs, runtime_type: Artefact }
              - { term: Proof of debt, runtime_type: Artefact }
              - { term: Appointment date, runtime_type: Event }
              - { term: "Creditors' meeting", runtime_type: Event }
              - { term: In administration, runtime_type: State }
              - { term: Case closed, runtime_type: State }
              - { term: Realise an asset, runtime_type: Decision }
              - { term: Trade on or cease, runtime_type: Decision }
              - { term: Realisation workflow, runtime_type: Workflow }
              - { term: Dividend paid to creditors, runtime_type: Outcome }
              - { term: "Pence-in-the-pound return", runtime_type: Learning }
      - name: "n-auditOS"
        buyer: Audit partner / engagement leader at an audit firm — pays per audit engagement and per auditor seat.
        os_test: "Distinct buyer and regulatory regime (FRC/ISAs), an evidence-and-risk state model (assertions, materiality, opinion) wholly unlike compliance accounting, independence-driven vocabulary, and a repeatable population of registered audit firms."
        sectors:
          - name: Statutory External Audit
            note: "Regulated: FRC/ISA (UK); auditor registration, independence and ethical-standard requirements."
            operating_domains:
              - Audit engagements and files
              - Risk assessment and materiality
              - Audit programmes by assertion
              - Test of controls and substantive testing
              - Audit evidence and working papers
              - "Review and partner sign-off"
              - Audit opinion and report
            vocabulary:
              - { term: Audited entity, runtime_type: Actor }
              - { term: Engagement partner, runtime_type: Actor }
              - { term: Audit engagement, runtime_type: Object }
              - { term: Audit file, runtime_type: Object }
              - { term: Working paper, runtime_type: Artefact }
              - { term: Audit report, runtime_type: Artefact }
              - { term: Planning meeting, runtime_type: Event }
              - { term: "Sign-off", runtime_type: Event }
              - { term: Fieldwork in progress, runtime_type: State }
              - { term: Cleared for review, runtime_type: State }
              - { term: Assess materiality, runtime_type: Decision }
              - { term: Modify the opinion, runtime_type: Decision }
              - { term: Audit methodology workflow, runtime_type: Workflow }
              - { term: Opinion issued, runtime_type: Outcome }
              - { term: Realisation vs budget, runtime_type: Learning }
          - name: Internal Audit
            note: Regulated where the entity is in a regulated sector; aligned to IIA standards.
            operating_domains:
              - Annual audit plan and universe
              - Audit reviews and fieldwork
              - Control testing
              - Findings and risk ratings
              - Management action plans
              - "Follow-up and remediation tracking"
              - Audit committee reporting
            vocabulary:
              - { term: Auditee / business owner, runtime_type: Actor }
              - { term: Internal auditor, runtime_type: Actor }
              - { term: Audit universe, runtime_type: Object }
              - { term: Audit review, runtime_type: Object }
              - { term: Audit finding, runtime_type: Artefact }
              - { term: Audit report to committee, runtime_type: Artefact }
              - { term: Fieldwork start, runtime_type: Event }
              - { term: Report issued, runtime_type: Event }
              - { term: Open finding, runtime_type: State }
              - { term: Remediated, runtime_type: State }
              - { term: Rate the risk, runtime_type: Decision }
              - { term: Accept the residual risk, runtime_type: Decision }
              - { term: Audit cycle workflow, runtime_type: Workflow }
              - { term: Control improvement delivered, runtime_type: Outcome }
              - { term: Finding closure rate, runtime_type: Learning }
          - name: "Assurance & Agreed-Upon Procedures"
            note: "Regulated: ISAE 3000/3402 and ethical independence standards govern reporting."
            operating_domains:
              - Assurance engagements (ISAE 3000)
              - Grant and covenant certifications
              - "Service-organisation reports (SOC/ISAE 3402)"
              - "Agreed-upon-procedures scopes"
              - Evidence gathering
              - Conclusions and certificates
              - "Restricted-use reporting"
            vocabulary:
              - { term: Reporting entity, runtime_type: Actor }
              - { term: Assurance practitioner, runtime_type: Actor }
              - { term: Assurance engagement, runtime_type: Object }
              - { term: Subject matter, runtime_type: Object }
              - { term: Assurance report, runtime_type: Artefact }
              - { term: Procedures schedule, runtime_type: Artefact }
              - { term: Scope agreed, runtime_type: Event }
              - { term: Conclusion reached, runtime_type: Event }
              - { term: Evidence outstanding, runtime_type: State }
              - { term: Concluded, runtime_type: State }
              - { term: Reasonable vs limited assurance, runtime_type: Decision }
              - { term: Qualify the conclusion, runtime_type: Decision }
              - { term: Engagement workflow, runtime_type: Workflow }
              - { term: Certificate issued, runtime_type: Outcome }
              - { term: Engagement margin, runtime_type: Learning }
          - name: "Forensic Audit & Fraud Investigation"
            note: "Regulated: chain-of-custody and expert-witness duties (CPR Part 35); admissibility standards."
            operating_domains:
              - Investigation cases
              - Evidence preservation and chain of custody
              - Forensic data analysis
              - Interviews and statements
              - Loss quantification
              - Expert reports
              - Litigation support
            vocabulary:
              - { term: Instructing party, runtime_type: Actor }
              - { term: Forensic accountant, runtime_type: Actor }
              - { term: Investigation case, runtime_type: Object }
              - { term: Evidence item, runtime_type: Object }
              - { term: Forensic report, runtime_type: Artefact }
              - { term: Expert witness statement, runtime_type: Artefact }
              - { term: Evidence seized, runtime_type: Event }
              - { term: Report served, runtime_type: Event }
              - { term: Under investigation, runtime_type: State }
              - { term: Findings substantiated, runtime_type: State }
              - { term: Quantify the loss, runtime_type: Decision }
              - { term: Refer to authorities, runtime_type: Decision }
              - { term: Investigation workflow, runtime_type: Workflow }
              - { term: Recovery achieved, runtime_type: Outcome }
              - { term: Loss recovery rate, runtime_type: Learning }
          - name: "Quality & Engagement Review"
            note: "Regulated: ISQM 1/2 quality-management standards and FRC/AQR inspection regime."
            operating_domains:
              - Engagement quality reviews (EQR)
              - Hot and cold file reviews
              - Independence and ethics monitoring
              - "Root-cause analysis of findings"
              - Methodology compliance
              - Regulatory inspection readiness
              - Remediation actions
            vocabulary:
              - { term: Engagement team, runtime_type: Actor }
              - { term: Quality reviewer, runtime_type: Actor }
              - { term: Reviewed engagement, runtime_type: Object }
              - { term: Quality finding, runtime_type: Object }
              - { term: EQR memo, runtime_type: Artefact }
              - { term: "Root-cause report", runtime_type: Artefact }
              - { term: Review completed, runtime_type: Event }
              - { term: Inspection visit, runtime_type: Event }
              - { term: Finding open, runtime_type: State }
              - { term: Cleared, runtime_type: State }
              - { term: "Clear or hold sign-off", runtime_type: Decision }
              - { term: Mandate remediation, runtime_type: Decision }
              - { term: Review workflow, runtime_type: Workflow }
              - { term: File grade achieved, runtime_type: Outcome }
              - { term: "Clean-file rate", runtime_type: Learning }
      - name: "n-compOS"
        buyer: "Chief Compliance Officer / MLRO / Head of Risk — pays per regulated-entity programme and per compliance-team seat."
        os_test: "Distinct buyer (CCO/MLRO), an obligations-and-attestation state model (controls, breaches, regulatory reporting) with sanctioning consequences, regulatory-register vocabulary, and a repeatable population of regulated firms — not advisory, not audit."
        sectors:
          - name: AML / Financial Crime
            note: "Regulated: MLR 2017 / NCA SAR regime; tipping-off offence and FCA/HMRC supervision."
            operating_domains:
              - Customer due diligence and KYC
              - "Risk-rating and EDD cases"
              - Transaction monitoring alerts
              - Sanctions and PEP screening
              - Suspicious activity reports
              - "Source-of-funds verification"
              - Periodic review cycles
            vocabulary:
              - { term: Customer, runtime_type: Actor }
              - { term: MLRO, runtime_type: Actor }
              - { term: Customer risk profile, runtime_type: Object }
              - { term: Monitoring alert, runtime_type: Object }
              - { term: CDD record, runtime_type: Artefact }
              - { term: Suspicious activity report, runtime_type: Artefact }
              - { term: Alert triggered, runtime_type: Event }
              - { term: Onboarding completed, runtime_type: Event }
              - { term: "High-risk flagged", runtime_type: State }
              - { term: Account frozen, runtime_type: State }
              - { term: Clear or escalate the alert, runtime_type: Decision }
              - { term: File a SAR, runtime_type: Decision }
              - { term: Screening workflow, runtime_type: Workflow }
              - { term: Customer onboarded, runtime_type: Outcome }
              - { term: "False-positive rate", runtime_type: Learning }
          - name: Regulatory Compliance (Conduct)
            note: "Regulated: FCA/PRA rulebook, SM&CR and RegData reporting; enforcement and fining powers."
            operating_domains:
              - Regulatory obligations register
              - Controls and attestations
              - "Conduct rules and SM&CR responsibilities"
              - "Regulatory change horizon-scanning"
              - Approvals and authorisations
              - Regulatory returns (RegData)
              - Conduct breach handling
            vocabulary:
              - { term: Regulated firm, runtime_type: Actor }
              - { term: Compliance officer, runtime_type: Actor }
              - { term: Obligation, runtime_type: Object }
              - { term: Control, runtime_type: Object }
              - { term: Attestation, runtime_type: Artefact }
              - { term: Regulatory return, runtime_type: Artefact }
              - { term: Rule change published, runtime_type: Event }
              - { term: Return due, runtime_type: Event }
              - { term: Compliant, runtime_type: State }
              - { term: In breach, runtime_type: State }
              - { term: "Self-report to regulator", runtime_type: Decision }
              - { term: Accept or remediate gap, runtime_type: Decision }
              - { term: Attestation cycle, runtime_type: Workflow }
              - { term: Return submitted, runtime_type: Outcome }
              - { term: "Control-coverage score", runtime_type: Learning }
          - name: "Data Protection & Privacy"
            note: "Regulated: UK GDPR / DPA 2018; 72-hour ICO breach notification and statutory DSAR deadlines."
            operating_domains:
              - Records of processing activities (RoPA)
              - Data subject access requests
              - Data protection impact assessments
              - "Consent and lawful-basis register"
              - "Personal-data breach handling"
              - "Third-party / processor agreements"
              - Retention and deletion schedules
            vocabulary:
              - { term: Data subject, runtime_type: Actor }
              - { term: Data protection officer, runtime_type: Actor }
              - { term: Processing activity, runtime_type: Object }
              - { term: DSAR case, runtime_type: Object }
              - { term: DPIA, runtime_type: Artefact }
              - { term: Breach report, runtime_type: Artefact }
              - { term: Breach detected, runtime_type: Event }
              - { term: DSAR received, runtime_type: Event }
              - { term: Within 72 hours, runtime_type: State }
              - { term: Reportable to ICO, runtime_type: State }
              - { term: Notify the ICO, runtime_type: Decision }
              - { term: Disclose or redact, runtime_type: Decision }
              - { term: DSAR fulfilment workflow, runtime_type: Workflow }
              - { term: DSAR fulfilled on time, runtime_type: Outcome }
              - { term: "On-time DSAR rate", runtime_type: Learning }
          - name: "Health, Safety & Environmental"
            note: "Regulated: HSWA 1974 / RIDDOR statutory reporting and HSE enforcement."
            operating_domains:
              - Risk assessments and method statements
              - "Incident and near-miss reporting"
              - Safety inspections and audits
              - "Permits, licences and certificates"
              - Corrective and preventive actions
              - Training and competency records
              - Environmental monitoring and ESG
            vocabulary:
              - { term: Worker / site team, runtime_type: Actor }
              - { term: HSE manager, runtime_type: Actor }
              - { term: Risk assessment, runtime_type: Object }
              - { term: Incident record, runtime_type: Object }
              - { term: Method statement, runtime_type: Artefact }
              - { term: RIDDOR report, runtime_type: Artefact }
              - { term: Incident occurred, runtime_type: Event }
              - { term: Inspection due, runtime_type: Event }
              - { term: Action open, runtime_type: State }
              - { term: Site shut down, runtime_type: State }
              - { term: Report under RIDDOR, runtime_type: Decision }
              - { term: Stop the work, runtime_type: Decision }
              - { term: CAPA workflow, runtime_type: Workflow }
              - { term: Hazard closed out, runtime_type: Outcome }
              - { term: "Lost-time injury rate", runtime_type: Learning }
          - name: "ESG & Sustainability Reporting"
            note: "Regulated where mandatory (CSRD/ISSB/SECR); modern-slavery statement obligations apply."
            operating_domains:
              - Emissions and carbon inventory
              - ESG metrics and KPIs
              - "Framework-aligned disclosures (TCFD/ISSB/CSRD)"
              - "Supply-chain and modern-slavery diligence"
              - Assurance readiness
              - "Targets and net-zero pathways"
              - Stakeholder and investor reporting
            vocabulary:
              - { term: Reporting organisation, runtime_type: Actor }
              - { term: Sustainability lead, runtime_type: Actor }
              - { term: Emissions inventory, runtime_type: Object }
              - { term: ESG metric, runtime_type: Object }
              - { term: Sustainability report, runtime_type: Artefact }
              - { term: "Net-zero target", runtime_type: Artefact }
              - { term: Reporting period close, runtime_type: Event }
              - { term: Disclosure published, runtime_type: Event }
              - { term: Data collection open, runtime_type: State }
              - { term: "Assurance-ready", runtime_type: State }
              - { term: Set a reduction target, runtime_type: Decision }
              - { term: Disclose Scope 3 or not, runtime_type: Decision }
              - { term: Reporting cycle, runtime_type: Workflow }
              - { term: Disclosure filed, runtime_type: Outcome }
              - { term: Emissions trajectory, runtime_type: Learning }
          - name: "Governance, Risk & Internal Controls"
            note: Regulated where the entity is in scope (UK Corporate Governance Code / sector rules).
            operating_domains:
              - Enterprise risk register
              - Policy library and lifecycle
              - Internal control framework
              - Board and committee governance
              - "Third-party / supplier risk"
              - Issue and exception management
              - Assurance mapping (three lines)
            vocabulary:
              - { term: Risk owner, runtime_type: Actor }
              - { term: "Risk & governance lead", runtime_type: Actor }
              - { term: Risk, runtime_type: Object }
              - { term: Policy, runtime_type: Object }
              - { term: Control matrix, runtime_type: Artefact }
              - { term: Board report, runtime_type: Artefact }
              - { term: Risk crystallised, runtime_type: Event }
              - { term: Policy review due, runtime_type: Event }
              - { term: Within appetite, runtime_type: State }
              - { term: Out of appetite, runtime_type: State }
              - { term: "Accept, mitigate or transfer", runtime_type: Decision }
              - { term: Escalate to the board, runtime_type: Decision }
              - { term: Risk review workflow, runtime_type: Workflow }
              - { term: Risk brought in appetite, runtime_type: Outcome }
              - { term: "Residual-risk trend", runtime_type: Learning }
      - name: "n-consultOS"
        buyer: Engagement partner / practice lead at a consulting firm (or Head of Delivery) — pays per consultant seat and per active engagement.
        os_test: "Distinct buyer (consulting partner), an engagement/utilisation state model (proposal → SOW → delivery → benefit) wholly unlike compliance or audit, deliverable-and-utilisation vocabulary, and a vast repeatable firm population."
        sectors:
          - name: "Management & Strategy Consulting"
            operating_domains:
              - Engagements and statements of work
              - Hypotheses and analysis workstreams
              - Deliverables and decks
              - Steering committee governance
              - Resourcing and utilisation
              - Benefits case and value tracking
              - Stakeholder management
            vocabulary:
              - { term: Client sponsor, runtime_type: Actor }
              - { term: Engagement manager, runtime_type: Actor }
              - { term: Engagement, runtime_type: Object }
              - { term: Workstream, runtime_type: Object }
              - { term: Statement of work, runtime_type: Artefact }
              - { term: Deliverable / final report, runtime_type: Artefact }
              - { term: "Kick-off", runtime_type: Event }
              - { term: Steering committee, runtime_type: Event }
              - { term: In delivery, runtime_type: State }
              - { term: On hold / descoped, runtime_type: State }
              - { term: Recommend an option, runtime_type: Decision }
              - { term: "Go / no-go gate", runtime_type: Decision }
              - { term: Engagement lifecycle, runtime_type: Workflow }
              - { term: Benefits realised, runtime_type: Outcome }
              - { term: Consultant utilisation, runtime_type: Learning }
          - name: "IT & Technology Consulting"
            operating_domains:
              - Solution design and architecture
              - Implementation projects and sprints
              - Requirements and backlog
              - Integration and data migration
              - Testing and cutover
              - Change and adoption
              - "Go-live and hypercare"
            vocabulary:
              - { term: Client product owner, runtime_type: Actor }
              - { term: Solution architect, runtime_type: Actor }
              - { term: Implementation project, runtime_type: Object }
              - { term: Requirement / user story, runtime_type: Object }
              - { term: Solution design doc, runtime_type: Artefact }
              - { term: Test report, runtime_type: Artefact }
              - { term: Sprint review, runtime_type: Event }
              - { term: "Go-live", runtime_type: Event }
              - { term: In build, runtime_type: State }
              - { term: In hypercare, runtime_type: State }
              - { term: Build vs buy, runtime_type: Decision }
              - { term: Approve the cutover, runtime_type: Decision }
              - { term: Delivery lifecycle, runtime_type: Workflow }
              - { term: System live in production, runtime_type: Outcome }
              - { term: Velocity / defect trend, runtime_type: Learning }
          - name: "HR & People Consulting"
            note: Regulated where collective redundancy/TUPE consultation triggers statutory obligations.
            operating_domains:
              - Organisation design and operating models
              - Reward and benchmarking
              - Talent and capability programmes
              - Change management and culture
              - Employee engagement and listening
              - Workforce planning
              - Policy and process redesign
            vocabulary:
              - { term: Client HR sponsor, runtime_type: Actor }
              - { term: People consultant, runtime_type: Actor }
              - { term: Operating model, runtime_type: Object }
              - { term: Role / job architecture, runtime_type: Object }
              - { term: Org design blueprint, runtime_type: Artefact }
              - { term: Reward benchmark report, runtime_type: Artefact }
              - { term: Consultation launched, runtime_type: Event }
              - { term: "Go-live of new structure", runtime_type: Event }
              - { term: In consultation, runtime_type: State }
              - { term: Embedded, runtime_type: State }
              - { term: "Pay-banding decision", runtime_type: Decision }
              - { term: Retain or redeploy, runtime_type: Decision }
              - { term: Change programme workflow, runtime_type: Workflow }
              - { term: Adoption achieved, runtime_type: Outcome }
              - { term: "Engagement-score shift", runtime_type: Learning }
          - name: "Financial & Transaction Advisory"
            note: "Regulated where reporting-accountant or regulated-investment-advice activities are engaged."
            operating_domains:
              - Financial and commercial due diligence
              - Valuations and modelling
              - Deal advisory mandates
              - "Working-capital and synergy analysis"
              - "Quality-of-earnings reviews"
              - Restructuring options
              - Reporting accountant work
            vocabulary:
              - { term: Deal client / acquirer, runtime_type: Actor }
              - { term: Transaction adviser, runtime_type: Actor }
              - { term: Advisory mandate, runtime_type: Object }
              - { term: Financial model, runtime_type: Object }
              - { term: "Due-diligence report", runtime_type: Artefact }
              - { term: "Quality-of-earnings report", runtime_type: Artefact }
              - { term: Management presentation, runtime_type: Event }
              - { term: Report delivered, runtime_type: Event }
              - { term: In diligence, runtime_type: State }
              - { term: Deal aborted, runtime_type: State }
              - { term: "Flag a deal-breaker", runtime_type: Decision }
              - { term: Adjust the valuation, runtime_type: Decision }
              - { term: Diligence workflow, runtime_type: Workflow }
              - { term: Deal supported to close, runtime_type: Outcome }
              - { term: Mandate win rate, runtime_type: Learning }
          - name: "Marketing, Brand & CX Consulting"
            operating_domains:
              - Brand and positioning strategy
              - Customer journeys and CX maps
              - Campaign and channel plans
              - Market research and insight
              - Creative deliverables
              - Performance measurement
              - "Go-to-market roadmaps"
            vocabulary:
              - { term: Client marketing lead, runtime_type: Actor }
              - { term: Brand strategist, runtime_type: Actor }
              - { term: Brand strategy, runtime_type: Object }
              - { term: Customer journey, runtime_type: Object }
              - { term: Brand playbook, runtime_type: Artefact }
              - { term: Campaign plan, runtime_type: Artefact }
              - { term: Campaign launch, runtime_type: Event }
              - { term: Research readout, runtime_type: Event }
              - { term: In flight, runtime_type: State }
              - { term: Live in market, runtime_type: State }
              - { term: Choose the positioning, runtime_type: Decision }
              - { term: "Channel-mix allocation", runtime_type: Decision }
              - { term: GTM delivery workflow, runtime_type: Workflow }
              - { term: Pipeline impact delivered, runtime_type: Outcome }
              - { term: ROAS / conversion lift, runtime_type: Learning }
          - name: "Engineering & Architecture (Built Environment) Consulting"
            note: "Regulated: chartered/licensed practice (ARB/RIBA/ICE); Building Safety Act and building-control approvals."
            operating_domains:
              - Project commissions and stages (RIBA)
              - "Designs, drawings and models (BIM)"
              - Site surveys and inspections
              - Specifications and schedules
              - Approvals and building control
              - Variations and instructions
              - Snagging and handover
            vocabulary:
              - { term: Client / developer, runtime_type: Actor }
              - { term: Project engineer / architect, runtime_type: Actor }
              - { term: Project commission, runtime_type: Object }
              - { term: Design / drawing, runtime_type: Object }
              - { term: Specification, runtime_type: Artefact }
              - { term: Inspection report, runtime_type: Artefact }
              - { term: Design freeze, runtime_type: Event }
              - { term: Practical completion, runtime_type: Event }
              - { term: At design stage, runtime_type: State }
              - { term: On site, runtime_type: State }
              - { term: Approve a variation, runtime_type: Decision }
              - { term: Sign off building control, runtime_type: Decision }
              - { term: RIBA stage workflow, runtime_type: Workflow }
              - { term: Project handed over, runtime_type: Outcome }
              - { term: "On-time / on-budget rate", runtime_type: Learning }
  - name: Financial Services
    os:
      - name: "n-insOS"
        buyer: "Insurance carriers, MGAs and brokers — the COO / Head of Underwriting or Claims pays for the policy-and-claims operating system."
        os_test: "Its own buyer (insurer ops), distinctive state model (risk → bound policy → in-force → claim → settled), unique vocabulary (binder, peril, subrogation, IBNR) and thousands of repeatable carriers/MGAs — not a relabelling of banking."
        sectors:
          - name: "P&C Underwriting"
            note: Regulated underwriting; carrier must hold an insurance licence and file rates with the state/PRA regulator.
            operating_domains:
              - Submission triage and risk appetite screening
              - Exposure and peril rating
              - Reinsurance treaty attachment
              - Binder issuance and policy bind
              - "Endorsements and mid-term adjustments"
              - Renewal pricing and retention
              - Facultative placement
            vocabulary:
              - { term: Submission, runtime_type: Object }
              - { term: Insured, runtime_type: Actor }
              - { term: Underwriter, runtime_type: Actor }
              - { term: Peril, runtime_type: Object }
              - { term: Quote issued, runtime_type: Event }
              - { term: Bound, runtime_type: State }
              - { term: "In-force", runtime_type: State }
              - { term: Decline or accept risk, runtime_type: Decision }
              - { term: Rating run, runtime_type: Workflow }
              - { term: Binder, runtime_type: Artefact }
              - { term: Policy schedule, runtime_type: Artefact }
              - { term: Loss ratio, runtime_type: Outcome }
              - { term: Endorsement, runtime_type: Event }
              - { term: Renewal retention rate, runtime_type: Learning }
          - name: Claims Management
            note: "Claims handling is a regulated activity; unfair-claims-practices rules and licensed adjusters apply."
            operating_domains:
              - First notice of loss intake
              - Coverage verification and reserving
              - Adjuster assignment and field inspection
              - Liability and damage assessment
              - Subrogation and recovery
              - Fraud referral and SIU
              - Settlement and payout
            vocabulary:
              - { term: Claim, runtime_type: Object }
              - { term: Claimant, runtime_type: Actor }
              - { term: Adjuster, runtime_type: Actor }
              - { term: First notice of loss, runtime_type: Event }
              - { term: Reserve set, runtime_type: State }
              - { term: Coverage decision, runtime_type: Decision }
              - { term: Adjudicate claim, runtime_type: Workflow }
              - { term: Loss adjuster report, runtime_type: Artefact }
              - { term: Subrogation recovery, runtime_type: Event }
              - { term: "Closed-paid", runtime_type: State }
              - { term: Settlement amount, runtime_type: Outcome }
              - { term: Denied, runtime_type: State }
              - { term: SIU fraud flag, runtime_type: Decision }
              - { term: Average cost per claim, runtime_type: Learning }
          - name: "Life & Annuities"
            note: Life insurance and annuities are regulated investment/insurance products requiring suitability and licensed agents.
            operating_domains:
              - Application and medical underwriting
              - Mortality and morbidity rating
              - "Policy issuance and free-look"
              - Premium billing and lapse management
              - Cash value and surrender handling
              - Beneficiary and death claim processing
              - Annuitization and income payout
            vocabulary:
              - { term: Application, runtime_type: Object }
              - { term: Policyholder, runtime_type: Actor }
              - { term: Underwriting class assigned, runtime_type: Decision }
              - { term: Medical exam ordered, runtime_type: Event }
              - { term: Lapsed, runtime_type: State }
              - { term: Premium paid, runtime_type: Event }
              - { term: Cash value, runtime_type: Object }
              - { term: Surrender request, runtime_type: Event }
              - { term: Death claim, runtime_type: Object }
              - { term: Beneficiary, runtime_type: Actor }
              - { term: Issue policy, runtime_type: Workflow }
              - { term: Illustration, runtime_type: Artefact }
              - { term: Death benefit paid, runtime_type: Outcome }
              - { term: Persistency rate, runtime_type: Learning }
          - name: "Specialty & Commercial Lines"
            note: "Subscription markets (e.g. Lloyd's) are regulated; binding authority and delegated underwriting require regulator approval."
            operating_domains:
              - Risk surveying and engineering reports
              - Layered and excess tower construction
              - Manuscript wording and clause negotiation
              - Aggregate exposure modelling (cat)
              - "Captive and self-insured programmes"
              - "Audit and exposure true-up"
              - Broker placement and slip signing
            vocabulary:
              - { term: Risk, runtime_type: Object }
              - { term: Broker, runtime_type: Actor }
              - { term: Slip, runtime_type: Artefact }
              - { term: Layer attached, runtime_type: Event }
              - { term: Subscribed, runtime_type: State }
              - { term: Set line size, runtime_type: Decision }
              - { term: Build excess tower, runtime_type: Workflow }
              - { term: Manuscript wording, runtime_type: Artefact }
              - { term: Aggregate exposure, runtime_type: Object }
              - { term: Premium audit, runtime_type: Event }
              - { term: Probable maximum loss, runtime_type: Outcome }
              - { term: Cat model output, runtime_type: Learning }
              - { term: Bound line, runtime_type: State }
              - { term: Surveyor, runtime_type: Actor }
          - name: "Health & Benefits Administration"
            note: "Health benefit administration is regulated (ACA/HIPAA in US, PHI handling) and requires licensed TPAs."
            operating_domains:
              - Group enrolment and eligibility
              - Plan design and network tiering
              - Claims adjudication against benefit rules
              - "Pre-authorisation and utilisation review"
              - Provider network and credentialing
              - Member appeals and grievances
              - "Premium and stop-loss reconciliation"
            vocabulary:
              - { term: Member, runtime_type: Actor }
              - { term: Benefit plan, runtime_type: Object }
              - { term: Enrolment, runtime_type: Event }
              - { term: Eligible, runtime_type: State }
              - { term: "Pre-authorisation decision", runtime_type: Decision }
              - { term: Adjudicate against plan, runtime_type: Workflow }
              - { term: Explanation of benefits, runtime_type: Artefact }
              - { term: Provider, runtime_type: Actor }
              - { term: Claim paid to provider, runtime_type: Event }
              - { term: Appeal filed, runtime_type: Event }
              - { term: Denied for coverage, runtime_type: State }
              - { term: "Out-of-pocket spend", runtime_type: Outcome }
              - { term: Medical loss ratio, runtime_type: Learning }
              - { term: Network adequacy, runtime_type: Outcome }
          - name: Reinsurance
            note: Reinsurance carriers are licensed and subject to solvency capital requirements (Solvency II / RBC).
            operating_domains:
              - Treaty negotiation and renewal
              - Cession and bordereau processing
              - Loss recovery and claims collection
              - Retrocession placement
              - Catastrophe bond and ILS structuring
              - Technical accounting and settlement
              - Capital and solvency modelling
            vocabulary:
              - { term: Treaty, runtime_type: Object }
              - { term: Cedant, runtime_type: Actor }
              - { term: Reinsurer, runtime_type: Actor }
              - { term: Cession, runtime_type: Event }
              - { term: Bordereau, runtime_type: Artefact }
              - { term: Attachment point reached, runtime_type: State }
              - { term: Accept the cession, runtime_type: Decision }
              - { term: Place retrocession, runtime_type: Workflow }
              - { term: Recoverable, runtime_type: Object }
              - { term: Settlement statement, runtime_type: Artefact }
              - { term: Loss recovered, runtime_type: Outcome }
              - { term: Cat bond trigger, runtime_type: Event }
              - { term: Combined ratio, runtime_type: Learning }
              - { term: "In-treaty", runtime_type: State }
      - name: "n-bankOS"
        buyer: "Retail and commercial banks / credit unions — the COO or Head of Retail Banking pays for the deposit, account-servicing and branch operating system."
        os_test: "Distinct buyer (bank ops, not lending desks), unique state model (account opened → KYC cleared → active → dormant → closed), deposit-and-ledger vocabulary (ledger, hold, overdraft, beneficial owner) and thousands of repeatable institutions — not insurance or markets."
        sectors:
          - name: Retail Deposit Accounts
            note: "Deposit-taking requires a banking licence; KYC/AML and deposit-insurance (FSCS/FDIC) rules apply."
            operating_domains:
              - Account opening and KYC onboarding
              - Ledger posting and balance maintenance
              - Overdraft and fee management
              - "Holds, freezes and disputes"
              - Statement generation and reconciliation
              - Dormancy and account closure
              - "Joint and authorised-user management"
            vocabulary:
              - { term: Account, runtime_type: Object }
              - { term: Accountholder, runtime_type: Actor }
              - { term: Deposit posted, runtime_type: Event }
              - { term: Available balance, runtime_type: State }
              - { term: Hold placed, runtime_type: Event }
              - { term: Overdraft decision, runtime_type: Decision }
              - { term: Open account, runtime_type: Workflow }
              - { term: Statement, runtime_type: Artefact }
              - { term: Dormant, runtime_type: State }
              - { term: Closed, runtime_type: State }
              - { term: Interest accrued, runtime_type: Outcome }
              - { term: Dispute raised, runtime_type: Event }
              - { term: Average balance trend, runtime_type: Learning }
              - { term: Beneficial owner, runtime_type: Actor }
          - name: "Commercial & Business Banking"
            note: Trade finance and letters of credit are regulated banking activities subject to sanctions screening.
            operating_domains:
              - Business onboarding and entity verification
              - Cash management and sweep accounts
              - Lockbox and receivables posting
              - Letters of credit and trade finance
              - Merchant services setup
              - Relationship and limit management
              - "Multi-entity hierarchy and pooling"
            vocabulary:
              - { term: Business account, runtime_type: Object }
              - { term: Relationship manager, runtime_type: Actor }
              - { term: Signatory, runtime_type: Actor }
              - { term: Sweep executed, runtime_type: Event }
              - { term: Letter of credit, runtime_type: Artefact }
              - { term: Approve credit line, runtime_type: Decision }
              - { term: Onboard entity, runtime_type: Workflow }
              - { term: Active relationship, runtime_type: State }
              - { term: Lockbox deposit, runtime_type: Event }
              - { term: Cash position, runtime_type: State }
              - { term: Facility utilised, runtime_type: Outcome }
              - { term: Mandate, runtime_type: Artefact }
              - { term: Deposit beta, runtime_type: Learning }
              - { term: Counterparty, runtime_type: Actor }
          - name: "Branch & Teller Operations"
            note: "Cash handling and currency exchange are regulated for AML and large-cash-transaction reporting (CTR/SAR)."
            operating_domains:
              - Cash drawer and vault management
              - Teller transactions and posting
              - Cheque processing and clearing
              - Currency exchange at counter
              - Cash ordering and replenishment
              - "End-of-day balancing"
              - "Customer in-branch servicing"
            vocabulary:
              - { term: Cash drawer, runtime_type: Object }
              - { term: Teller, runtime_type: Actor }
              - { term: Cash withdrawal, runtime_type: Event }
              - { term: Cheque deposited, runtime_type: Event }
              - { term: Drawer balanced, runtime_type: State }
              - { term: Override approval, runtime_type: Decision }
              - { term: "End-of-day balancing", runtime_type: Workflow }
              - { term: Vault, runtime_type: Object }
              - { term: Teller receipt, runtime_type: Artefact }
              - { term: Out of balance, runtime_type: State }
              - { term: Cash order placed, runtime_type: Event }
              - { term: Till variance, runtime_type: Outcome }
              - { term: Branch customer, runtime_type: Actor }
              - { term: Average transaction time, runtime_type: Learning }
          - name: "Treasury & Liquidity"
            note: Liquidity and capital management are regulated under Basel III (LCR/NSFR) reporting obligations.
            operating_domains:
              - Cash position forecasting
              - "Funding and money-market placement"
              - FX position management
              - "Interest-rate gap and ALM"
              - Liquidity coverage compliance
              - Intraday liquidity monitoring
              - "Internal funds-transfer pricing"
            vocabulary:
              - { term: Position, runtime_type: Object }
              - { term: Treasurer, runtime_type: Actor }
              - { term: Funding placed, runtime_type: Event }
              - { term: Cash forecast, runtime_type: Artefact }
              - { term: Liquidity breach, runtime_type: State }
              - { term: Set funding strategy, runtime_type: Decision }
              - { term: Run ALM cycle, runtime_type: Workflow }
              - { term: Counterparty limit, runtime_type: Object }
              - { term: Within appetite, runtime_type: State }
              - { term: LCR ratio, runtime_type: Outcome }
              - { term: Rate gap report, runtime_type: Artefact }
              - { term: Intraday liquidity used, runtime_type: Outcome }
              - { term: Net interest margin, runtime_type: Learning }
              - { term: Maturity ladder, runtime_type: Object }
          - name: "Financial Crime & AML"
            note: AML/CTF is a heavily regulated obligation; SAR/CTR filing and sanctions compliance are statutory.
            operating_domains:
              - Customer due diligence and screening
              - Transaction monitoring and alerting
              - Sanctions and PEP screening
              - Case investigation and SAR filing
              - Enhanced due diligence reviews
              - "Watchlist and fuzzy-match tuning"
              - Regulatory reporting and audit trail
            vocabulary:
              - { term: Alert, runtime_type: Object }
              - { term: Investigator, runtime_type: Actor }
              - { term: Subject, runtime_type: Actor }
              - { term: Alert triggered, runtime_type: Event }
              - { term: Under investigation, runtime_type: State }
              - { term: File a SAR, runtime_type: Decision }
              - { term: Run EDD review, runtime_type: Workflow }
              - { term: Suspicious activity report, runtime_type: Artefact }
              - { term: Sanctions hit, runtime_type: Event }
              - { term: Cleared as false positive, runtime_type: State }
              - { term: Risk rating assigned, runtime_type: Outcome }
              - { term: Watchlist match, runtime_type: Event }
              - { term: "False-positive rate", runtime_type: Learning }
              - { term: Customer risk profile, runtime_type: Object }
          - name: "Card Issuing & Servicing"
            note: "Card issuing falls under card-scheme rules and PCI-DSS plus consumer-credit regulation."
            operating_domains:
              - Card issuance and activation
              - Authorisation and limit control
              - "Statement and minimum-payment cycle"
              - Chargeback and dispute handling
              - Rewards and interchange accounting
              - Fraud blocking and reissuance
              - Collections handoff on delinquency
            vocabulary:
              - { term: Card, runtime_type: Object }
              - { term: Cardholder, runtime_type: Actor }
              - { term: Authorisation, runtime_type: Event }
              - { term: Active, runtime_type: State }
              - { term: Approve or decline auth, runtime_type: Decision }
              - { term: Run billing cycle, runtime_type: Workflow }
              - { term: Chargeback raised, runtime_type: Event }
              - { term: Card statement, runtime_type: Artefact }
              - { term: Blocked, runtime_type: State }
              - { term: Interchange earned, runtime_type: Outcome }
              - { term: Reissued, runtime_type: Event }
              - { term: Delinquent, runtime_type: State }
              - { term: Authorisation approval rate, runtime_type: Learning }
              - { term: Merchant, runtime_type: Actor }
      - name: "n-finOS"
        buyer: "Asset and wealth managers, RIAs and fund administrators — the CIO / COO of the firm pays for the portfolio, advice and fund-administration operating system."
        os_test: "Distinct buyer (investment managers), unique state model (mandate → allocated → rebalanced → reported), portfolio-and-advice vocabulary (NAV, drift, suitability, capital call) and many repeatable firms — clearly separate from deposits, trading venues or insurance."
        sectors:
          - name: "Wealth Management & Advice"
            note: "Investment advice is regulated; advisers must be authorised (FCA/SEC) and meet suitability/best-interest rules."
            operating_domains:
              - Client onboarding and risk profiling
              - "Goals-based financial planning"
              - Suitability and recommendation
              - Portfolio construction and allocation
              - Periodic review and rebalancing
              - Performance and fee reporting
              - Household and account aggregation
            vocabulary:
              - { term: Client, runtime_type: Actor }
              - { term: Adviser, runtime_type: Actor }
              - { term: Portfolio, runtime_type: Object }
              - { term: Risk profile set, runtime_type: State }
              - { term: Suitability decision, runtime_type: Decision }
              - { term: Recommendation issued, runtime_type: Event }
              - { term: Run financial plan, runtime_type: Workflow }
              - { term: Investment policy statement, runtime_type: Artefact }
              - { term: Rebalanced, runtime_type: State }
              - { term: Drifted from target, runtime_type: State }
              - { term: Goal funded, runtime_type: Outcome }
              - { term: Suitability report, runtime_type: Artefact }
              - { term: "Time-weighted return", runtime_type: Learning }
              - { term: "Held-away asset", runtime_type: Object }
          - name: Asset Management Operations
            note: "Discretionary asset management is a regulated activity with mandate-compliance and reporting duties."
            operating_domains:
              - Mandate and model maintenance
              - Order generation and rebalancing
              - "Cash and corporate-actions handling"
              - "Compliance pre-trade checks"
              - Performance attribution
              - Client reporting packs
              - Benchmark and index management
            vocabulary:
              - { term: Mandate, runtime_type: Object }
              - { term: Portfolio manager, runtime_type: Actor }
              - { term: Model portfolio, runtime_type: Object }
              - { term: Rebalance triggered, runtime_type: Event }
              - { term: "Pre-trade breach", runtime_type: State }
              - { term: Approve order list, runtime_type: Decision }
              - { term: Generate orders, runtime_type: Workflow }
              - { term: Corporate action, runtime_type: Event }
              - { term: "In-line with model", runtime_type: State }
              - { term: Attribution report, runtime_type: Artefact }
              - { term: Active return, runtime_type: Outcome }
              - { term: Tracking error, runtime_type: Learning }
              - { term: Benchmark, runtime_type: Object }
              - { term: Compliance officer, runtime_type: Actor }
          - name: "Fund Administration & Accounting"
            note: Fund administration and NAV oversight are regulated; depositary/administrator duties apply (AIFMD/UCITS).
            operating_domains:
              - Trade capture and reconciliation
              - NAV calculation and striking
              - "Pricing and fair-value review"
              - Expense and fee accrual
              - Investor subscriptions and redemptions
              - Income and distribution processing
              - "Financial-statement preparation"
            vocabulary:
              - { term: Fund, runtime_type: Object }
              - { term: Fund accountant, runtime_type: Actor }
              - { term: Investor, runtime_type: Actor }
              - { term: Trade captured, runtime_type: Event }
              - { term: NAV struck, runtime_type: State }
              - { term: Approve the NAV, runtime_type: Decision }
              - { term: Run NAV cycle, runtime_type: Workflow }
              - { term: Subscription received, runtime_type: Event }
              - { term: Redemption, runtime_type: Event }
              - { term: NAV pack, runtime_type: Artefact }
              - { term: Reconciled, runtime_type: State }
              - { term: Expense ratio, runtime_type: Outcome }
              - { term: Pricing exception, runtime_type: Object }
              - { term: NAV accuracy rate, runtime_type: Learning }
          - name: "Private Markets & Alternatives"
            note: "Private fund management is regulated (AIFMD / SEC private-fund rules) with LP reporting obligations."
            operating_domains:
              - Deal pipeline and sourcing
              - Due diligence and committee approval
              - Capital calls and drawdowns
              - Valuation and mark policy
              - Distributions and waterfall
              - LP reporting and capital accounts
              - "Fund-of-funds commitment tracking"
            vocabulary:
              - { term: Deal, runtime_type: Object }
              - { term: General partner, runtime_type: Actor }
              - { term: Limited partner, runtime_type: Actor }
              - { term: Capital called, runtime_type: Event }
              - { term: Committed, runtime_type: State }
              - { term: Investment committee approval, runtime_type: Decision }
              - { term: Run capital call, runtime_type: Workflow }
              - { term: Drawdown notice, runtime_type: Artefact }
              - { term: Distribution paid, runtime_type: Event }
              - { term: Realised, runtime_type: State }
              - { term: Net IRR, runtime_type: Outcome }
              - { term: Carried interest, runtime_type: Outcome }
              - { term: Capital account statement, runtime_type: Artefact }
              - { term: DPI multiple, runtime_type: Learning }
          - name: "Custody & Asset Servicing"
            note: "Custody is a regulated safeguarding activity with client-asset (CASS) segregation rules."
            operating_domains:
              - Safekeeping and position ledger
              - Settlement and trade confirmation
              - Corporate actions election
              - Proxy voting and entitlements
              - Income collection and tax reclaim
              - Reconciliation to depositories
              - "Asset transfer and re-registration"
            vocabulary:
              - { term: Holding, runtime_type: Object }
              - { term: Custodian, runtime_type: Actor }
              - { term: Beneficial owner, runtime_type: Actor }
              - { term: Settlement instruction, runtime_type: Event }
              - { term: Settled, runtime_type: State }
              - { term: Elect on corporate action, runtime_type: Decision }
              - { term: Process entitlement, runtime_type: Workflow }
              - { term: Proxy ballot, runtime_type: Artefact }
              - { term: Failed trade, runtime_type: State }
              - { term: Tax reclaim filed, runtime_type: Event }
              - { term: Income collected, runtime_type: Outcome }
              - { term: Safekeeping statement, runtime_type: Artefact }
              - { term: Settlement fail rate, runtime_type: Learning }
              - { term: Depository, runtime_type: Actor }
          - name: "Robo-Advice & Digital Wealth"
            note: Digital advice is regulated investment advice; suitability and disclosure duties still apply.
            operating_domains:
              - Automated risk questionnaire
              - Algorithmic portfolio assignment
              - "Auto-rebalancing and drift control"
              - "Tax-loss harvesting"
              - "Fractional and round-up investing"
              - Goal tracking and projections
              - Funding and recurring deposits
            vocabulary:
              - { term: Goal, runtime_type: Object }
              - { term: Investor, runtime_type: Actor }
              - { term: Risk score computed, runtime_type: State }
              - { term: "Auto-assign portfolio", runtime_type: Decision }
              - { term: Deposit funded, runtime_type: Event }
              - { term: "Run auto-rebalance", runtime_type: Workflow }
              - { term: Drift threshold hit, runtime_type: Event }
              - { term: Harvested loss, runtime_type: Outcome }
              - { term: On track, runtime_type: State }
              - { term: Off track, runtime_type: State }
              - { term: Projection chart, runtime_type: Artefact }
              - { term: Fractional share, runtime_type: Object }
              - { term: "Goal-completion likelihood", runtime_type: Learning }
              - { term: Recurring deposit set, runtime_type: Event }
      - name: "n-mortOS"
        buyer: "Mortgage lenders, brokers and servicers — the Head of Originations or Head of Servicing pays for the loan-origination-and-servicing operating system."
        os_test: "Distinct buyer (mortgage ops), a uniquely long state model (application → underwriting → conditional approval → clear-to-close → funded → serviced → paid-off/default), heavy property/title vocabulary (LTV, escrow, lien, foreclosure) and a large repeatable lender/servicer population — not generic lending."
        sectors:
          - name: Mortgage Origination
            note: "Mortgage origination is regulated (TILA/RESPA, FCA MCOB); licensed originators and affordability rules apply."
            operating_domains:
              - "Application intake and pre-qualification"
              - Document collection and income verification
              - Credit and affordability assessment
              - Property valuation ordering
              - Underwriting and conditioning
              - Rate lock and disclosure
              - "Clear-to-close and funding"
            vocabulary:
              - { term: Loan application, runtime_type: Object }
              - { term: Borrower, runtime_type: Actor }
              - { term: Loan officer, runtime_type: Actor }
              - { term: Application submitted, runtime_type: Event }
              - { term: Conditionally approved, runtime_type: State }
              - { term: Underwriting decision, runtime_type: Decision }
              - { term: Run underwriting, runtime_type: Workflow }
              - { term: Loan estimate, runtime_type: Artefact }
              - { term: Rate locked, runtime_type: Event }
              - { term: "Clear-to-close", runtime_type: State }
              - { term: "Loan-to-value", runtime_type: Outcome }
              - { term: Funded, runtime_type: State }
              - { term: "Pull-through rate", runtime_type: Learning }
              - { term: Appraisal, runtime_type: Artefact }
          - name: Loan Servicing
            note: "Servicing is regulated (CFPB servicing rules / MCOB); escrow and loss-mitigation handling are prescribed."
            operating_domains:
              - Payment processing and posting
              - Escrow analysis and disbursement
              - Statement and payoff handling
              - Insurance and tax tracking
              - Modification and assumption requests
              - Investor remittance and reporting
              - Customer servicing and inquiries
            vocabulary:
              - { term: Loan, runtime_type: Object }
              - { term: Servicer, runtime_type: Actor }
              - { term: Payment posted, runtime_type: Event }
              - { term: Current, runtime_type: State }
              - { term: Escrow account, runtime_type: Object }
              - { term: Approve modification, runtime_type: Decision }
              - { term: Run escrow analysis, runtime_type: Workflow }
              - { term: Payoff statement, runtime_type: Artefact }
              - { term: Escrow shortage, runtime_type: State }
              - { term: Investor remittance, runtime_type: Event }
              - { term: Principal balance, runtime_type: Outcome }
              - { term: Paid off, runtime_type: State }
              - { term: Prepayment speed, runtime_type: Learning }
              - { term: Mortgagor, runtime_type: Actor }
          - name: "Default & Loss Mitigation"
            note: "Foreclosure and loss mitigation are regulated; loss-mit options and timelines are mandated by CFPB/FCA."
            operating_domains:
              - Delinquency tracking and outreach
              - Forbearance and repayment plans
              - Loan modification underwriting
              - "Short sale and deed-in-lieu"
              - Foreclosure referral and timeline
              - Bankruptcy handling
              - REO and property disposition
            vocabulary:
              - { term: Delinquent loan, runtime_type: Object }
              - { term: "Loss-mitigation specialist", runtime_type: Actor }
              - { term: Missed payment, runtime_type: Event }
              - { term: In default, runtime_type: State }
              - { term: Workout decision, runtime_type: Decision }
              - { term: "Run loss-mit review", runtime_type: Workflow }
              - { term: Forbearance agreement, runtime_type: Artefact }
              - { term: Foreclosure referred, runtime_type: Event }
              - { term: In foreclosure, runtime_type: State }
              - { term: Reinstated, runtime_type: State }
              - { term: Loss severity, runtime_type: Outcome }
              - { term: REO inventory, runtime_type: Object }
              - { term: Cure rate, runtime_type: Learning }
              - { term: Trustee, runtime_type: Actor }
          - name: Mortgage Brokerage
            note: Mortgage advice and intermediation are regulated; brokers must be authorised and give suitable advice.
            operating_domains:
              - "Client fact-find and sourcing"
              - Lender product comparison
              - "Decision-in-principle requests"
              - Case packaging and submission
              - Affordability and protection advice
              - Pipeline and offer chasing
              - "Procuration-fee reconciliation"
            vocabulary:
              - { term: Case, runtime_type: Object }
              - { term: Mortgage broker, runtime_type: Actor }
              - { term: Applicant, runtime_type: Actor }
              - { term: Decision in principle, runtime_type: Event }
              - { term: Recommend a product, runtime_type: Decision }
              - { term: Package the case, runtime_type: Workflow }
              - { term: Submitted to lender, runtime_type: State }
              - { term: Suitability letter, runtime_type: Artefact }
              - { term: Offer issued, runtime_type: Event }
              - { term: Sourcing result, runtime_type: Object }
              - { term: Completed, runtime_type: State }
              - { term: Procuration fee earned, runtime_type: Outcome }
              - { term: Conversion rate, runtime_type: Learning }
              - { term: Lender, runtime_type: Actor }
          - name: "Capital Markets & Securitisation"
            note: "Securitisation and MSR sales are regulated under securities and risk-retention rules."
            operating_domains:
              - Loan pooling and eligibility
              - "Best-efforts and mandatory commitments"
              - Pipeline hedging (TBA)
              - Pool delivery and certification
              - MSR valuation and sale
              - "Whole-loan trading"
              - Investor reporting and surveillance
            vocabulary:
              - { term: Loan pool, runtime_type: Object }
              - { term: Capital markets desk, runtime_type: Actor }
              - { term: Investor, runtime_type: Actor }
              - { term: Commitment taken, runtime_type: Event }
              - { term: Hedge placed, runtime_type: Event }
              - { term: Allocate to pool, runtime_type: Decision }
              - { term: Deliver the pool, runtime_type: Workflow }
              - { term: Pool certification, runtime_type: Artefact }
              - { term: Delivered, runtime_type: State }
              - { term: MSR, runtime_type: Object }
              - { term: Gain on sale, runtime_type: Outcome }
              - { term: Hedged, runtime_type: State }
              - { term: Hedge effectiveness, runtime_type: Learning }
              - { term: Trade confirmation, runtime_type: Artefact }
      - name: "n-tradeOS"
        buyer: "Broker-dealers, hedge funds, prop desks and exchanges — the Head of Trading or COO of the desk pays for the order, execution and post-trade operating system."
        os_test: "Distinct buyer (trading desks/venues), real-time state model (order → routed → partially filled → filled → cleared → settled), markets vocabulary (RFQ, slippage, margin call, novation) and many repeatable desks/venues — wholly separate from deposits, advice or lending."
        sectors:
          - name: "Order & Execution Management"
            note: "Order handling and best execution are regulated (MiFID II / Reg NMS) for broker-dealers."
            operating_domains:
              - Order entry and staging
              - Smart order routing
              - Algo strategy selection
              - Fill management and allocation
              - "Best-execution monitoring"
              - Slippage and TCA analysis
              - "Cancel-replace and amends"
            vocabulary:
              - { term: Order, runtime_type: Object }
              - { term: Trader, runtime_type: Actor }
              - { term: Order routed, runtime_type: Event }
              - { term: Partially filled, runtime_type: State }
              - { term: Choose algo strategy, runtime_type: Decision }
              - { term: Work the order, runtime_type: Workflow }
              - { term: Fill received, runtime_type: Event }
              - { term: Filled, runtime_type: State }
              - { term: Execution report, runtime_type: Artefact }
              - { term: Slippage, runtime_type: Outcome }
              - { term: Cancelled, runtime_type: State }
              - { term: Venue, runtime_type: Actor }
              - { term: Implementation shortfall, runtime_type: Learning }
              - { term: Allocation, runtime_type: Object }
          - name: "Clearing & Settlement"
            note: "Clearing and settlement are regulated (EMIR / Dodd-Frank); CCPs and margining rules are statutory."
            operating_domains:
              - Trade matching and affirmation
              - Novation to clearing house
              - Margin calculation and calls
              - Settlement instruction and netting
              - "Fail management and buy-ins"
              - Collateral substitution
              - Position and exposure reporting
            vocabulary:
              - { term: Trade, runtime_type: Object }
              - { term: Clearing member, runtime_type: Actor }
              - { term: Central counterparty, runtime_type: Actor }
              - { term: Trade matched, runtime_type: Event }
              - { term: Novated, runtime_type: State }
              - { term: Meet the margin call, runtime_type: Decision }
              - { term: Run settlement cycle, runtime_type: Workflow }
              - { term: Margin call issued, runtime_type: Event }
              - { term: Settled, runtime_type: State }
              - { term: Settlement fail, runtime_type: State }
              - { term: Variation margin, runtime_type: Outcome }
              - { term: Margin statement, runtime_type: Artefact }
              - { term: Fail rate, runtime_type: Learning }
              - { term: Collateral, runtime_type: Object }
          - name: "Market Making & Liquidity"
            note: "Market making is a regulated activity with quoting obligations and position-limit oversight."
            operating_domains:
              - Quote generation and spread setting
              - Inventory and skew management
              - Hedging and delta neutrality
              - "RFQ response and auto-quoting"
              - "Adverse-selection monitoring"
              - Position limit control
              - "P&L attribution by book"
            vocabulary:
              - { term: Quote, runtime_type: Object }
              - { term: Market maker, runtime_type: Actor }
              - { term: Counterparty, runtime_type: Actor }
              - { term: RFQ received, runtime_type: Event }
              - { term: Quoted, runtime_type: State }
              - { term: Set the spread, runtime_type: Decision }
              - { term: "Auto-quote stream", runtime_type: Workflow }
              - { term: Inventory skewed, runtime_type: State }
              - { term: Hedge executed, runtime_type: Event }
              - { term: Realised spread, runtime_type: Outcome }
              - { term: Position, runtime_type: Object }
              - { term: Tear sheet, runtime_type: Artefact }
              - { term: Fill ratio, runtime_type: Learning }
              - { term: Flat, runtime_type: State }
          - name: "Derivatives & Structured Products"
            note: "OTC derivatives are regulated (EMIR/Dodd-Frank); trade reporting and margining are mandatory."
            operating_domains:
              - Trade structuring and pricing
              - Confirmation and ISDA documentation
              - "Lifecycle events (resets, fixings)"
              - Collateral and CSA management
              - Valuation and XVA
              - Exercise and expiry handling
              - Regulatory trade reporting
            vocabulary:
              - { term: Contract, runtime_type: Object }
              - { term: Structurer, runtime_type: Actor }
              - { term: Counterparty, runtime_type: Actor }
              - { term: Trade booked, runtime_type: Event }
              - { term: Live, runtime_type: State }
              - { term: Exercise decision, runtime_type: Decision }
              - { term: Process lifecycle event, runtime_type: Workflow }
              - { term: Confirmation, runtime_type: Artefact }
              - { term: Fixing applied, runtime_type: Event }
              - { term: Expired, runtime_type: State }
              - { term: "Mark-to-market", runtime_type: Outcome }
              - { term: CSA collateral, runtime_type: Object }
              - { term: XVA charge, runtime_type: Learning }
              - { term: Termsheet, runtime_type: Artefact }
          - name: "Trade Surveillance & Risk"
            note: "Market-abuse surveillance is a statutory obligation (MAR / SEC); STOR filing is mandatory."
            operating_domains:
              - "Pre-trade limit checks"
              - "Real-time position and VaR monitoring"
              - "Market-abuse alerting"
              - "Best-execution surveillance"
              - Communications surveillance
              - Stress testing and scenario runs
              - Breach escalation and case management
            vocabulary:
              - { term: Alert, runtime_type: Object }
              - { term: Surveillance analyst, runtime_type: Actor }
              - { term: Trader, runtime_type: Actor }
              - { term: Limit breach, runtime_type: Event }
              - { term: Under review, runtime_type: State }
              - { term: Escalate the alert, runtime_type: Decision }
              - { term: Run surveillance sweep, runtime_type: Workflow }
              - { term: STOR report, runtime_type: Artefact }
              - { term: Cleared, runtime_type: State }
              - { term: "Value-at-risk", runtime_type: Outcome }
              - { term: Spoofing flagged, runtime_type: Event }
              - { term: Stress scenario, runtime_type: Object }
              - { term: Alert precision, runtime_type: Learning }
              - { term: Risk limit, runtime_type: Object }
      - name: "n-paymentsOS"
        buyer: "Payment processors, PSPs, acquirers and fintech wallets — the Head of Payments or COO pays for the money-movement and settlement operating system."
        os_test: "Distinct buyer (payment operators), unique state model (initiated → authorised → captured → cleared → settled → reconciled, with reversal paths), money-rails vocabulary (acquirer, scheme fee, chargeback, ledger entry) and a vast repeatable processor/PSP population — separate from cards-as-deposit-product and from trading."
        sectors:
          - name: "Card Acquiring & Processing"
            note: "Acquiring is regulated under PSD2/card-scheme rules and PCI-DSS; merchant underwriting AML applies."
            operating_domains:
              - Merchant onboarding and underwriting
              - Authorisation and capture
              - Clearing and scheme submission
              - Settlement and funding to merchant
              - Chargeback and representment
              - "Interchange and scheme-fee accounting"
              - Terminal and gateway management
            vocabulary:
              - { term: Transaction, runtime_type: Object }
              - { term: Merchant, runtime_type: Actor }
              - { term: Acquirer, runtime_type: Actor }
              - { term: Authorisation, runtime_type: Event }
              - { term: Captured, runtime_type: State }
              - { term: Approve merchant, runtime_type: Decision }
              - { term: Run settlement batch, runtime_type: Workflow }
              - { term: Chargeback received, runtime_type: Event }
              - { term: Settled to merchant, runtime_type: State }
              - { term: Settlement report, runtime_type: Artefact }
              - { term: Net settlement amount, runtime_type: Outcome }
              - { term: Reversed, runtime_type: State }
              - { term: Authorisation rate, runtime_type: Learning }
              - { term: Card scheme, runtime_type: Actor }
          - name: "Account-to-Account & Bank Transfers"
            note: "Payment initiation is regulated (PSD2, NACHA, Pay.UK); sanctions screening is mandatory."
            operating_domains:
              - Payment initiation and validation
              - Rail selection (ACH/SEPA/Faster Payments)
              - Sanctions and limit screening
              - Submission and acknowledgement
              - Return and recall handling
              - Reconciliation against bank statements
              - "Mandate and direct-debit management"
            vocabulary:
              - { term: Payment, runtime_type: Object }
              - { term: Payer, runtime_type: Actor }
              - { term: Payee, runtime_type: Actor }
              - { term: Payment initiated, runtime_type: Event }
              - { term: Pending submission, runtime_type: State }
              - { term: Select the rail, runtime_type: Decision }
              - { term: Submit to rail, runtime_type: Workflow }
              - { term: Payment returned, runtime_type: Event }
              - { term: Settled, runtime_type: State }
              - { term: Remittance advice, runtime_type: Artefact }
              - { term: Funds delivered, runtime_type: Outcome }
              - { term: Recalled, runtime_type: State }
              - { term: "Straight-through rate", runtime_type: Learning }
              - { term: "Direct-debit mandate", runtime_type: Object }
          - name: "Cross-Border & FX Payments"
            note: "Cross-border payments are regulated; travel-rule, sanctions and money-transmission licences apply."
            operating_domains:
              - Beneficiary and corridor setup
              - FX rate quoting and locking
              - Correspondent routing
              - "Compliance and travel-rule screening"
              - "Funding and pre-positioning"
              - Tracking and SWIFT GPI status
              - Reconciliation and nostro management
            vocabulary:
              - { term: "Cross-border payment", runtime_type: Object }
              - { term: Sender, runtime_type: Actor }
              - { term: Beneficiary, runtime_type: Actor }
              - { term: Rate locked, runtime_type: Event }
              - { term: In transit, runtime_type: State }
              - { term: Choose routing path, runtime_type: Decision }
              - { term: Route via correspondent, runtime_type: Workflow }
              - { term: Payment credited, runtime_type: Event }
              - { term: Delivered, runtime_type: State }
              - { term: MT103, runtime_type: Artefact }
              - { term: FX margin earned, runtime_type: Outcome }
              - { term: Returned for repair, runtime_type: State }
              - { term: Corridor delivery time, runtime_type: Learning }
              - { term: Nostro account, runtime_type: Object }
          - name: "Wallets & Stored Value"
            note: "Stored value / e-money is regulated; an e-money licence and safeguarding of funds are required."
            operating_domains:
              - Wallet creation and KYC tiering
              - "Top-up and load handling"
              - "Peer-to-peer transfers"
              - Spend and merchant payment
              - Balance and ledger management
              - "Withdrawal and cash-out"
              - Dormancy and balance sweep
            vocabulary:
              - { term: Wallet, runtime_type: Object }
              - { term: Wallet holder, runtime_type: Actor }
              - { term: "Top-up received", runtime_type: Event }
              - { term: Active, runtime_type: State }
              - { term: "Approve cash-out", runtime_type: Decision }
              - { term: Process P2P transfer, runtime_type: Workflow }
              - { term: Transfer sent, runtime_type: Event }
              - { term: Available balance, runtime_type: State }
              - { term: Ledger entry, runtime_type: Artefact }
              - { term: Frozen, runtime_type: State }
              - { term: Float held, runtime_type: Outcome }
              - { term: Withdrawal completed, runtime_type: Event }
              - { term: "Active-wallet rate", runtime_type: Learning }
              - { term: Recipient, runtime_type: Actor }
          - name: "Reconciliation & Settlement Ops"
            note: "Settlement and safeguarding reconciliation are regulated under PSD2/e-money client-money rules."
            operating_domains:
              - "Incoming-file ingestion and parsing"
              - Matching across ledgers and rails
              - Exception and break investigation
              - Fee and interchange verification
              - Funding and payout scheduling
              - Nostro/vostro reconciliation
              - "Settlement-cycle close and reporting"
            vocabulary:
              - { term: Settlement file, runtime_type: Object }
              - { term: Operations analyst, runtime_type: Actor }
              - { term: Partner bank, runtime_type: Actor }
              - { term: File ingested, runtime_type: Event }
              - { term: Matched, runtime_type: State }
              - { term: Resolve the break, runtime_type: Decision }
              - { term: Run reconciliation, runtime_type: Workflow }
              - { term: Break raised, runtime_type: Event }
              - { term: Unmatched, runtime_type: State }
              - { term: Reconciliation report, runtime_type: Artefact }
              - { term: Match rate achieved, runtime_type: Outcome }
              - { term: Funded, runtime_type: State }
              - { term: Break ageing, runtime_type: Learning }
              - { term: Ledger, runtime_type: Object }
          - name: "Payments Fraud & Risk"
            note: Strong Customer Authentication (SCA/3DS) and fraud reporting are regulated under PSD2.
            operating_domains:
              - "Real-time transaction scoring"
              - Rules and velocity checks
              - "Step-up authentication (3DS/SCA)"
              - Manual review queue
              - "Chargeback-fraud disputing"
              - Device and behavioural signals
              - Model monitoring and feedback
            vocabulary:
              - { term: Transaction risk case, runtime_type: Object }
              - { term: Fraud analyst, runtime_type: Actor }
              - { term: Cardholder, runtime_type: Actor }
              - { term: Risk score computed, runtime_type: Event }
              - { term: Flagged for review, runtime_type: State }
              - { term: "Approve, decline or step-up", runtime_type: Decision }
              - { term: Run fraud screening, runtime_type: Workflow }
              - { term: Challenge issued, runtime_type: Event }
              - { term: Confirmed fraud, runtime_type: State }
              - { term: Case file, runtime_type: Artefact }
              - { term: Fraud loss avoided, runtime_type: Outcome }
              - { term: Cleared as genuine, runtime_type: State }
              - { term: "Fraud-detection rate", runtime_type: Learning }
              - { term: Device fingerprint, runtime_type: Object }
      - name: "n-lendingOS"
        buyer: "Consumer/SME lenders, BNPL providers and credit unions — the Head of Credit or Chief Lending Officer pays for the non-mortgage credit decision-and-collections operating system."
        os_test: "Distinct buyer (credit lenders), its own state model (application → decisioned → drawn → performing → arrears → charged-off/recovered), unsecured-credit vocabulary (decision engine, affordability, DPD bucket, write-off) and many repeatable lenders — distinct from mortgage (secured/property/escrow) and from card-as-deposit-product."
        sectors:
          - name: Consumer Lending
            note: Consumer credit is regulated (CONC / Reg Z); affordability checks and licensing are mandatory.
            operating_domains:
              - Application and identity verification
              - "Credit-bureau pull and scoring"
              - Affordability and income assessment
              - Decisioning and pricing for risk
              - Offer and acceptance
              - Disbursement and account setup
              - "Early-arrears monitoring"
            vocabulary:
              - { term: Loan application, runtime_type: Object }
              - { term: Applicant, runtime_type: Actor }
              - { term: Underwriter, runtime_type: Actor }
              - { term: Application submitted, runtime_type: Event }
              - { term: Approved, runtime_type: State }
              - { term: Credit decision, runtime_type: Decision }
              - { term: Run decision engine, runtime_type: Workflow }
              - { term: Credit agreement, runtime_type: Artefact }
              - { term: Funds disbursed, runtime_type: Event }
              - { term: Performing, runtime_type: State }
              - { term: "Risk-based price", runtime_type: Outcome }
              - { term: Declined, runtime_type: State }
              - { term: Approval rate, runtime_type: Learning }
              - { term: Bureau report, runtime_type: Artefact }
          - name: "SME & Business Lending"
            note: Business lending may be regulated depending on size; security and guarantee taking carry legal duties.
            operating_domains:
              - Business application and entity checks
              - "Financials and bank-statement analysis"
              - "Cash-flow and affordability modelling"
              - Guarantor and security assessment
              - Credit committee approval
              - Facility drawdown and covenants
              - Annual review and renewal
            vocabulary:
              - { term: Facility, runtime_type: Object }
              - { term: Business borrower, runtime_type: Actor }
              - { term: Credit analyst, runtime_type: Actor }
              - { term: Application received, runtime_type: Event }
              - { term: Sanctioned, runtime_type: State }
              - { term: Credit committee approval, runtime_type: Decision }
              - { term: Run credit assessment, runtime_type: Workflow }
              - { term: Facility letter, runtime_type: Artefact }
              - { term: Drawdown, runtime_type: Event }
              - { term: Covenant breach, runtime_type: State }
              - { term: Exposure at default, runtime_type: Outcome }
              - { term: Personal guarantee, runtime_type: Object }
              - { term: Default rate by cohort, runtime_type: Learning }
              - { term: Guarantor, runtime_type: Actor }
          - name: "Buy-Now-Pay-Later & POS Finance"
            note: BNPL is increasingly regulated consumer credit; affordability and disclosure rules are expanding (FCA/CFPB).
            operating_domains:
              - "Checkout eligibility and soft-check"
              - Instant split/instalment decisioning
              - Merchant settlement and discount
              - Repayment scheduling and reminders
              - "Late-fee and missed-payment handling"
              - Refund and return reconciliation
              - "Limit and re-use management"
            vocabulary:
              - { term: Order, runtime_type: Object }
              - { term: Shopper, runtime_type: Actor }
              - { term: Merchant, runtime_type: Actor }
              - { term: Checkout requested, runtime_type: Event }
              - { term: Approved at checkout, runtime_type: State }
              - { term: Instant credit decision, runtime_type: Decision }
              - { term: Schedule instalments, runtime_type: Workflow }
              - { term: Instalment due, runtime_type: Event }
              - { term: Repayment plan, runtime_type: Artefact }
              - { term: Paid in full, runtime_type: State }
              - { term: Missed instalment, runtime_type: State }
              - { term: Merchant discount earned, runtime_type: Outcome }
              - { term: "Repeat-use rate", runtime_type: Learning }
              - { term: Available limit, runtime_type: Object }
          - name: "Collections & Recoveries"
            note: "Debt collection is regulated (FDCPA / FCA CONC); vulnerable-customer and fair-treatment rules apply."
            operating_domains:
              - Arrears segmentation and strategy
              - Contact and treatment paths
              - "Promise-to-pay and payment plans"
              - "Forbearance and vulnerable-customer handling"
              - "Charge-off and provisioning"
              - Debt sale and agency placement
              - Litigation and recovery tracking
            vocabulary:
              - { term: Arrears case, runtime_type: Object }
              - { term: Collections agent, runtime_type: Actor }
              - { term: Customer in arrears, runtime_type: Actor }
              - { term: Payment missed, runtime_type: Event }
              - { term: In arrears, runtime_type: State }
              - { term: Choose treatment path, runtime_type: Decision }
              - { term: Run collections strategy, runtime_type: Workflow }
              - { term: Promise to pay, runtime_type: Artefact }
              - { term: Charged off, runtime_type: State }
              - { term: Cured, runtime_type: State }
              - { term: Amount recovered, runtime_type: Outcome }
              - { term: Debt sold, runtime_type: Event }
              - { term: "Roll-rate", runtime_type: Learning }
              - { term: DPD bucket, runtime_type: Object }
          - name: "Credit Risk & Portfolio Management"
            note: "Provisioning and capital are regulated (IFRS 9 / CECL, Basel); model governance rules apply."
            operating_domains:
              - Scorecard development and monitoring
              - Limit and exposure setting
              - Provisioning and IFRS 9/CECL staging
              - Vintage and cohort analysis
              - Stress testing and scenarios
              - Policy rule management
              - "Early-warning indicator tracking"
            vocabulary:
              - { term: Portfolio, runtime_type: Object }
              - { term: Credit risk manager, runtime_type: Actor }
              - { term: Borrower cohort, runtime_type: Actor }
              - { term: Scorecard deployed, runtime_type: Event }
              - { term: Stage 2 watch, runtime_type: State }
              - { term: Set credit policy, runtime_type: Decision }
              - { term: Run provisioning model, runtime_type: Workflow }
              - { term: "Loss-forecast report", runtime_type: Artefact }
              - { term: Limit breach, runtime_type: Event }
              - { term: Within appetite, runtime_type: State }
              - { term: Expected credit loss, runtime_type: Outcome }
              - { term: Provision raised, runtime_type: Event }
              - { term: Gini / KS score, runtime_type: Learning }
              - { term: Scorecard, runtime_type: Object }
  - name: "Property & Built Environment"
    os:
      - name: "n-propOS"
        buyer: "Estate agency / lettings principals and property investment firms who pay per branch or per managed unit to run sales, lettings and asset management."
        os_test: "Owns the deal-and-tenancy lifecycle (instruction → offer → exchange/let → managed unit) with its own pipeline state model, agency-specific vocabulary (vendor, applicant, asking price, AST), its own buyer (agency principal) and budget — distinct from conveyancing's legal file or construction's project."
        sectors:
          - name: Residential Sales Agency
            note: Property descriptions and fees are regulated under the Consumer Protection from Unfair Trading Regs and require a registered redress scheme.
            operating_domains:
              - Instruction and listing book
              - Applicant register and viewing diary
              - Offer negotiation and chain progression
              - Vendor reporting and feedback
              - "Portal and window-card marketing"
              - Valuation and market appraisal pipeline
              - Branch performance and fee pipeline
            vocabulary:
              - { term: Vendor, runtime_type: Actor }
              - { term: Applicant, runtime_type: Actor }
              - { term: Instruction, runtime_type: Object }
              - { term: Property listing, runtime_type: Object }
              - { term: Asking price, runtime_type: State }
              - { term: Viewing booked, runtime_type: Event }
              - { term: Offer received, runtime_type: Event }
              - { term: Accept or reject offer, runtime_type: Decision }
              - { term: Under offer, runtime_type: State }
              - { term: Chain progression, runtime_type: Workflow }
              - { term: Market appraisal report, runtime_type: Artefact }
              - { term: Sole agency agreement, runtime_type: Artefact }
              - { term: Sale agreed (sold STC), runtime_type: Outcome }
              - { term: Days on market, runtime_type: Learning }
              - { term: "Listing-to-instruction conversion", runtime_type: Learning }
          - name: "Residential Lettings & Tenancy"
            note: "Tenant deposits must be protected in a government-approved scheme within 30 days; right-to-rent and tenant-fee bans are statutory."
            operating_domains:
              - Rental listing and applicant matching
              - "Tenant referencing and right-to-rent checks"
              - "Tenancy agreement and move-in pack"
              - Rent collection and arrears ledger
              - Deposit registration and protection
              - "Inventory and check-in/check-out"
              - Renewals and notice management
            vocabulary:
              - { term: Landlord, runtime_type: Actor }
              - { term: Prospective tenant, runtime_type: Actor }
              - { term: Rental property, runtime_type: Object }
              - { term: Tenancy agreement (AST), runtime_type: Artefact }
              - { term: Holding deposit taken, runtime_type: Event }
              - { term: Referencing in progress, runtime_type: State }
              - { term: "Right-to-rent check", runtime_type: Decision }
              - { term: Deposit protection, runtime_type: Workflow }
              - { term: "Move-in completed", runtime_type: Event }
              - { term: Let agreed, runtime_type: State }
              - { term: Rent arrears, runtime_type: State }
              - { term: Section 21 / Section 8 notice, runtime_type: Artefact }
              - { term: Inventory report, runtime_type: Artefact }
              - { term: Tenancy completed, runtime_type: Outcome }
              - { term: Void period, runtime_type: Learning }
              - { term: Rent collection rate, runtime_type: Learning }
          - name: "Block & Leasehold Property Management"
            note: "Service charges and Section 20 consultations are governed by the Landlord and Tenant Act 1985; building-safety duties under the Building Safety Act 2022."
            operating_domains:
              - "Service-charge budgeting and demands"
              - Communal repairs and planned maintenance
              - "Section 20 major-works consultation"
              - Ground rent and lease compliance
              - Resident and RTM company liaison
              - "Building safety and fire-risk register"
              - Reserve fund and accounts
            vocabulary:
              - { term: Leaseholder, runtime_type: Actor }
              - { term: Managing agent, runtime_type: Actor }
              - { term: Managed block, runtime_type: Object }
              - { term: "Service-charge budget", runtime_type: Artefact }
              - { term: "Service-charge demand issued", runtime_type: Event }
              - { term: Arrears balance, runtime_type: State }
              - { term: Section 20 consultation, runtime_type: Workflow }
              - { term: Approve major works contractor, runtime_type: Decision }
              - { term: Planned maintenance schedule, runtime_type: Artefact }
              - { term: "Fire-risk assessment", runtime_type: Artefact }
              - { term: Lease breach, runtime_type: State }
              - { term: "Reserve fund top-up", runtime_type: Event }
              - { term: "Year-end service-charge accounts", runtime_type: Outcome }
              - { term: "Reserve-fund adequacy", runtime_type: Learning }
              - { term: Arrears recovery rate, runtime_type: Learning }
          - name: Commercial Property Agency
            operating_domains:
              - Office/retail/industrial space marketing
              - Tenant requirement and acquisition briefs
              - Heads of terms negotiation
              - Rent reviews and lease events
              - Investment sale and yield analysis
              - "Occupier fit-out and dilapidations"
              - Agency fee and disposal pipeline
            vocabulary:
              - { term: Occupier (tenant), runtime_type: Actor }
              - { term: Landlord / investor, runtime_type: Actor }
              - { term: Commercial unit, runtime_type: Object }
              - { term: Requirement brief, runtime_type: Artefact }
              - { term: Space marketed, runtime_type: State }
              - { term: Inspection arranged, runtime_type: Event }
              - { term: Heads of terms agreed, runtime_type: Event }
              - { term: Recommend lease terms, runtime_type: Decision }
              - { term: Rent review, runtime_type: Workflow }
              - { term: Heads of terms, runtime_type: Artefact }
              - { term: Under offer, runtime_type: State }
              - { term: Deal completed (let/sold), runtime_type: Outcome }
              - { term: Net initial yield, runtime_type: Learning }
              - { term: Void and incentive cost, runtime_type: Learning }
          - name: "Property Asset & Portfolio Management"
            operating_domains:
              - Portfolio holdings and unit register
              - Acquisition and disposal appraisal
              - Net operating income and yield tracking
              - Capital expenditure and refurbishment planning
              - "Lease event and rent-roll calendar"
              - Valuation and revaluation cycle
              - Investor and lender reporting
            vocabulary:
              - { term: Asset manager, runtime_type: Actor }
              - { term: Investor, runtime_type: Actor }
              - { term: Held asset, runtime_type: Object }
              - { term: Rent roll, runtime_type: Object }
              - { term: Acquisition approved, runtime_type: Event }
              - { term: Under management, runtime_type: State }
              - { term: Hold or sell decision, runtime_type: Decision }
              - { term: Business plan, runtime_type: Artefact }
              - { term: Capex programme, runtime_type: Workflow }
              - { term: Revaluation, runtime_type: Event }
              - { term: Lease event calendar, runtime_type: Object }
              - { term: Investor report, runtime_type: Artefact }
              - { term: Disposal completed, runtime_type: Outcome }
              - { term: Total return / IRR, runtime_type: Learning }
              - { term: Occupancy rate, runtime_type: Learning }
          - name: "Mortgage & Property Finance Broking"
            note: "Mortgage advice is FCA-regulated; advisers must hold CeMAP-equivalent qualification and produce suitability documentation."
            operating_domains:
              - "Client fact-find and affordability"
              - Lender product sourcing and comparison
              - "Decision-in-principle and application"
              - Case packaging and underwriting liaison
              - Protection and insurance attachment
              - "Offer-to-completion pipeline"
              - Commission and compliance file
            vocabulary:
              - { term: Borrower client, runtime_type: Actor }
              - { term: Mortgage adviser, runtime_type: Actor }
              - { term: Mortgage case, runtime_type: Object }
              - { term: "Fact-find", runtime_type: Artefact }
              - { term: Decision in principle issued, runtime_type: Event }
              - { term: Recommend product, runtime_type: Decision }
              - { term: Application submitted, runtime_type: Event }
              - { term: In underwriting, runtime_type: State }
              - { term: Case packaging, runtime_type: Workflow }
              - { term: Suitability report, runtime_type: Artefact }
              - { term: Mortgage offer received, runtime_type: Event }
              - { term: Completed / drawn down, runtime_type: Outcome }
              - { term: "Offer-to-completion time", runtime_type: Learning }
              - { term: "Application-to-offer conversion", runtime_type: Learning }
      - name: "n-conveyOS"
        buyer: "Conveyancing solicitors, licensed conveyancers and property-law firms who pay per matter or per fee-earner seat to run the legal transfer of property."
        os_test: "Runs the legal matter file (searches, enquiries, contract, completion, registration) under SRA/CLC regulation with strictly ordered legal milestones, client-account ledgers and a vocabulary (requisitions, completion statement, TR1) no agency or construction system carries — its own buyer (firm partner) and compliance budget."
        sectors:
          - name: Residential Conveyancing
            note: "Regulated by the SRA or CLC; client money held in a regulated client account; AML and source-of-funds checks mandatory."
            operating_domains:
              - Matter opening and client onboarding
              - Property searches ordering and review
              - Contract pack and enquiries
              - Mortgage offer and lender requirements
              - Exchange and completion scheduling
              - Land Registry submission
              - "Client-account ledger and completion funds"
            vocabulary:
              - { term: Buyer client, runtime_type: Actor }
              - { term: Conveyancer, runtime_type: Actor }
              - { term: Matter file, runtime_type: Object }
              - { term: Local authority search, runtime_type: Artefact }
              - { term: Enquiries raised, runtime_type: Event }
              - { term: Awaiting replies to enquiries, runtime_type: State }
              - { term: Report on title, runtime_type: Artefact }
              - { term: Ready to exchange decision, runtime_type: Decision }
              - { term: Exchange of contracts, runtime_type: Event }
              - { term: Completion, runtime_type: Workflow }
              - { term: Completion statement, runtime_type: Artefact }
              - { term: Registered at Land Registry, runtime_type: Outcome }
              - { term: Matter completed, runtime_type: Outcome }
              - { term: Days to exchange, runtime_type: Learning }
              - { term: "Fall-through rate", runtime_type: Learning }
          - name: "Commercial Conveyancing & Real Estate Law"
            note: "SRA-regulated legal practice; SDLT/LTT returns are statutory tax filings."
            operating_domains:
              - Due diligence and title investigation
              - Lease drafting and negotiation
              - Certificate of title for lenders
              - Heads of terms to completion
              - SDLT and corporate structuring
              - Property finance and security
              - "Post-completion registration"
            vocabulary:
              - { term: Corporate client, runtime_type: Actor }
              - { term: Real estate solicitor, runtime_type: Actor }
              - { term: Transaction file, runtime_type: Object }
              - { term: Title investigation, runtime_type: Workflow }
              - { term: Due diligence report, runtime_type: Artefact }
              - { term: Enquiries outstanding, runtime_type: State }
              - { term: Lease engrossment, runtime_type: Artefact }
              - { term: Approve certificate of title, runtime_type: Decision }
              - { term: Completion of acquisition, runtime_type: Event }
              - { term: Security registered, runtime_type: State }
              - { term: Charge created (debenture), runtime_type: Artefact }
              - { term: Deal completed, runtime_type: Outcome }
              - { term: Diligence cycle time, runtime_type: Learning }
              - { term: Enquiry turnaround, runtime_type: Learning }
          - name: "Remortgage & Transfer of Equity"
            note: "Lender panel membership and CQS accreditation typically required; client-account and AML rules apply."
            operating_domains:
              - "New-lender requirements and redemption"
              - Existing charge redemption statement
              - Transfer of equity drafting
              - "ID/AML and source-of-funds checks"
              - Completion and new charge registration
              - Lender CHAPS funds reconciliation
            vocabulary:
              - { term: Remortgaging owner, runtime_type: Actor }
              - { term: Outgoing lender, runtime_type: Actor }
              - { term: Remortgage matter, runtime_type: Object }
              - { term: Redemption statement requested, runtime_type: Event }
              - { term: Awaiting mortgage offer, runtime_type: State }
              - { term: Transfer of equity deed (TR1), runtime_type: Artefact }
              - { term: Approve completion date, runtime_type: Decision }
              - { term: Completion, runtime_type: Workflow }
              - { term: Funds released, runtime_type: Event }
              - { term: New charge registered, runtime_type: State }
              - { term: Matter completed, runtime_type: Outcome }
              - { term: SDLT return, runtime_type: Artefact }
              - { term: Completion accuracy, runtime_type: Learning }
              - { term: Remortgage turnaround, runtime_type: Learning }
          - name: "New-Build & Plot Conveyancing"
            note: "Structural warranty (NHBC/equivalent) and Consumer Code for Home Builders apply; SRA-regulated."
            operating_domains:
              - Developer contract pack and plot allocation
              - Reservation and exchange deadlines
              - Plan and lease/transfer review
              - "Help-to-Buy and incentive handling"
              - "Build-stage and snagging linkage"
              - Notice to complete on practical completion
            vocabulary:
              - { term: Plot buyer, runtime_type: Actor }
              - { term: "Developer's solicitor", runtime_type: Actor }
              - { term: Plot matter, runtime_type: Object }
              - { term: Reservation agreement, runtime_type: Artefact }
              - { term: Exchange deadline (28 days), runtime_type: State }
              - { term: Exchange on plot, runtime_type: Event }
              - { term: Notice to complete served, runtime_type: Event }
              - { term: Confirm build warranty present, runtime_type: Decision }
              - { term: Plot transfer (lease/TP1), runtime_type: Artefact }
              - { term: Completion on legal completion, runtime_type: Workflow }
              - { term: Awaiting practical completion, runtime_type: State }
              - { term: Plot completed and registered, runtime_type: Outcome }
              - { term: "Exchange-deadline hit rate", runtime_type: Learning }
              - { term: "Reservation-to-exchange time", runtime_type: Learning }
          - name: "Property Disputes & Land Registration"
            note: "Litigation conducted under SRA regulation and First-tier Tribunal (Property Chamber) rules."
            operating_domains:
              - Boundary and easement disputes
              - Adverse possession applications
              - Title rectification and first registration
              - Restrictive covenant issues
              - Lease extension and enfranchisement
              - Tribunal and court filings
            vocabulary:
              - { term: Disputing party, runtime_type: Actor }
              - { term: Property litigator, runtime_type: Actor }
              - { term: Dispute matter, runtime_type: Object }
              - { term: Official copy of register, runtime_type: Artefact }
              - { term: Application lodged, runtime_type: Event }
              - { term: Awaiting Land Registry decision, runtime_type: State }
              - { term: Pursue or settle decision, runtime_type: Decision }
              - { term: Tribunal referral, runtime_type: Workflow }
              - { term: Statement of case, runtime_type: Artefact }
              - { term: Title amended / restriction entered, runtime_type: Event }
              - { term: Dispute resolved, runtime_type: Outcome }
              - { term: Lease extension granted, runtime_type: Outcome }
              - { term: Time to resolution, runtime_type: Learning }
              - { term: Settlement vs trial rate, runtime_type: Learning }
      - name: "n-constructionOS"
        buyer: "Main contractors, specialist trades and developers who pay per project or per active site to run the build from tender to handover."
        os_test: "Runs the construction project lifecycle (tender → programme → site → snagging → handover) with a programme/critical-path state model, on-site and CDM-specific vocabulary (RFI, variation, retention, practical completion) and its own buyer (contracts director) and budget — none of which fit a legal matter or a managed tenancy."
        sectors:
          - name: "Main Contracting & Site Delivery"
            note: "CDM 2015 health-and-safety duties and the Construction Act payment regime (notices, pay-less) apply."
            operating_domains:
              - "Programme and critical-path management"
              - Subcontractor packages and procurement
              - Site daily diary and labour allocation
              - RFIs and technical queries
              - Variations and instructions
              - "Valuations, retention and payment applications"
              - Snagging and practical completion
            vocabulary:
              - { term: Site manager, runtime_type: Actor }
              - { term: Subcontractor, runtime_type: Actor }
              - { term: Construction project, runtime_type: Object }
              - { term: Programme (Gantt), runtime_type: Artefact }
              - { term: RFI raised, runtime_type: Event }
              - { term: On programme / behind, runtime_type: State }
              - { term: Approve variation, runtime_type: Decision }
              - { term: Variation order, runtime_type: Artefact }
              - { term: Valuation submitted, runtime_type: Event }
              - { term: Snagging, runtime_type: Workflow }
              - { term: Retention held, runtime_type: State }
              - { term: Practical completion certified, runtime_type: Outcome }
              - { term: Handover completed, runtime_type: Outcome }
              - { term: Programme slippage, runtime_type: Learning }
              - { term: "Cost-to-complete variance", runtime_type: Learning }
          - name: "Quantity Surveying & Cost Management"
            note: "RICS-regulated practice where the QS is a chartered surveyor; valuation certificates carry contractual weight."
            operating_domains:
              - "Bill of quantities and take-off"
              - Cost plan and budget tracking
              - Subcontractor valuations and certificates
              - Variation pricing and change control
              - Cash flow and cost reporting
              - Final account negotiation
              - Retention release schedule
            vocabulary:
              - { term: Quantity surveyor, runtime_type: Actor }
              - { term: Client QS, runtime_type: Actor }
              - { term: Bill of quantities, runtime_type: Object }
              - { term: Cost plan, runtime_type: Artefact }
              - { term: "Take-off measured", runtime_type: Event }
              - { term: Budget on track / overspent, runtime_type: State }
              - { term: Certify valuation, runtime_type: Decision }
              - { term: Interim certificate, runtime_type: Artefact }
              - { term: Variation priced, runtime_type: Event }
              - { term: Final account negotiation, runtime_type: Workflow }
              - { term: Retention release, runtime_type: State }
              - { term: Final account agreed, runtime_type: Outcome }
              - { term: Cost variance vs budget, runtime_type: Learning }
              - { term: Margin erosion, runtime_type: Learning }
          - name: "Architecture & Design Coordination"
            note: "ARB-registered architects; building-regs and planning submissions are statutory; Building Safety Act gateways for higher-risk buildings."
            operating_domains:
              - Design stages (RIBA work stages)
              - Drawing register and revisions
              - Model coordination and clash detection
              - "Planning and building-regs submissions"
              - Specification and schedules
              - Design RFIs and approvals
              - Information release schedule
            vocabulary:
              - { term: Architect, runtime_type: Actor }
              - { term: Design client, runtime_type: Actor }
              - { term: Drawing, runtime_type: Object }
              - { term: Drawing register, runtime_type: Object }
              - { term: Design issued, runtime_type: Event }
              - { term: "Awaiting client sign-off", runtime_type: State }
              - { term: Approve design revision, runtime_type: Decision }
              - { term: Clash detection, runtime_type: Workflow }
              - { term: Planning application submitted, runtime_type: Event }
              - { term: Specification, runtime_type: Artefact }
              - { term: Planning permission granted, runtime_type: Outcome }
              - { term: "Stage sign-off complete", runtime_type: Outcome }
              - { term: Revisions per drawing, runtime_type: Learning }
              - { term: Information release adherence, runtime_type: Learning }
          - name: "Specialist Trades & Subcontracting"
            note: Gas Safe registration and electrical (Part P / NICEIC) competence are legally required for those trades.
            operating_domains:
              - Job booking and dispatch
              - Quotes and pricing
              - Materials ordering and stock
              - Labour and van scheduling
              - "On-site works and sign-off sheets"
              - Certification (electrical/gas)
              - Invoicing and retention chasing
            vocabulary:
              - { term: Tradesperson / engineer, runtime_type: Actor }
              - { term: Site client / main contractor, runtime_type: Actor }
              - { term: Job, runtime_type: Object }
              - { term: Quote, runtime_type: Artefact }
              - { term: Job dispatched, runtime_type: Event }
              - { term: Awaiting materials, runtime_type: State }
              - { term: Accept or decline job, runtime_type: Decision }
              - { term: Works in progress, runtime_type: State }
              - { term: Job completion workflow, runtime_type: Workflow }
              - { term: Compliance certificate (EICR/Gas Safe), runtime_type: Artefact }
              - { term: "Sign-off sheet signed", runtime_type: Event }
              - { term: Job completed and invoiced, runtime_type: Outcome }
              - { term: "First-time fix rate", runtime_type: Learning }
              - { term: Average job margin, runtime_type: Learning }
          - name: "Property Development & Land"
            note: "Planning consents, S106 agreements, CIL and structural warranties are statutory/regulated obligations."
            operating_domains:
              - Site appraisal and land acquisition
              - Development viability and GDV modelling
              - Planning and S106/CIL obligations
              - Funding and drawdown schedule
              - Build programme oversight
              - Sales/marketing release of units
              - "Scheme close-out and profit reconciliation"
            vocabulary:
              - { term: Developer, runtime_type: Actor }
              - { term: Landowner, runtime_type: Actor }
              - { term: Development site, runtime_type: Object }
              - { term: Appraisal (GDV model), runtime_type: Artefact }
              - { term: Land acquired, runtime_type: Event }
              - { term: In planning, runtime_type: State }
              - { term: "Go / no-go on acquisition", runtime_type: Decision }
              - { term: Drawdown schedule, runtime_type: Workflow }
              - { term: Planning granted, runtime_type: Event }
              - { term: Unit released for sale, runtime_type: Event }
              - { term: Build complete, runtime_type: State }
              - { term: Scheme delivered at profit, runtime_type: Outcome }
              - { term: Profit on cost, runtime_type: Learning }
              - { term: Sales rate (units/month), runtime_type: Learning }
          - name: "Building Control & Compliance"
            note: "Statutory function under the Building Act / Building Safety Act; BSR oversight for higher-risk buildings; registered building inspectors only."
            operating_domains:
              - "Building-regs application intake"
              - Plans assessment and approval
              - Site inspections at stages
              - "Higher-risk building gateways"
              - Completion certificate issue
              - "Enforcement and non-compliance"
              - "Competent-person scheme records"
            vocabulary:
              - { term: Building control surveyor, runtime_type: Actor }
              - { term: Duty holder / principal contractor, runtime_type: Actor }
              - { term: "Building-regs application", runtime_type: Object }
              - { term: Approved plans, runtime_type: Artefact }
              - { term: Stage inspection booked, runtime_type: Event }
              - { term: Awaiting inspection, runtime_type: State }
              - { term: Pass or fail inspection, runtime_type: Decision }
              - { term: Gateway review, runtime_type: Workflow }
              - { term: "Non-conformance raised", runtime_type: Event }
              - { term: Conditional approval, runtime_type: State }
              - { term: Completion certificate, runtime_type: Artefact }
              - { term: Building signed off, runtime_type: Outcome }
              - { term: "First-pass inspection rate", runtime_type: Learning }
              - { term: Time to certificate, runtime_type: Learning }
      - name: "n-facilitiesOS"
        buyer: "Facilities managers, FM service providers and building operators who pay per building or per portfolio to keep occupied buildings running, safe and compliant."
        os_test: "Runs the live-building operation (assets, PPM, reactive jobs, compliance, space) with an asset-and-SLA state model and an operational vocabulary (work order, PPM, SLA breach, statutory inspection) — distinct from constructing the building or transacting it; its own buyer (head of FM) and recurring service budget."
        sectors:
          - name: "Hard FM & Building Maintenance"
            note: "LOLER, PUWER, gas and electrical statutory inspections are legally mandated for building plant."
            operating_domains:
              - Asset register and criticality
              - Planned preventive maintenance (PPM)
              - Reactive work orders and dispatch
              - Engineer scheduling and mobile working
              - Spare parts and stores
              - Plant performance and uptime
              - Statutory inspections (LOLER/PUWER)
            vocabulary:
              - { term: FM engineer, runtime_type: Actor }
              - { term: Building occupier, runtime_type: Actor }
              - { term: Asset (plant item), runtime_type: Object }
              - { term: Work order, runtime_type: Object }
              - { term: Fault reported, runtime_type: Event }
              - { term: Work order open, runtime_type: State }
              - { term: Prioritise reactive job, runtime_type: Decision }
              - { term: PPM schedule, runtime_type: Workflow }
              - { term: Statutory inspection certificate, runtime_type: Artefact }
              - { term: Awaiting parts, runtime_type: State }
              - { term: Job completed, runtime_type: Event }
              - { term: Asset back in service, runtime_type: Outcome }
              - { term: Asset uptime, runtime_type: Learning }
              - { term: "PPM compliance %", runtime_type: Learning }
          - name: "Soft FM & Workplace Services"
            operating_domains:
              - Cleaning schedules and audits
              - Security and access control
              - "Reception and front-of-house"
              - Waste and recycling streams
              - Catering and vending
              - Helpdesk and occupant requests
              - "Service-level monitoring"
            vocabulary:
              - { term: Workplace operative, runtime_type: Actor }
              - { term: Building user, runtime_type: Actor }
              - { term: Service area, runtime_type: Object }
              - { term: Cleaning schedule, runtime_type: Artefact }
              - { term: Request logged, runtime_type: Event }
              - { term: Request open, runtime_type: State }
              - { term: Assign to team, runtime_type: Decision }
              - { term: Service round, runtime_type: Workflow }
              - { term: Audit failed, runtime_type: Event }
              - { term: SLA breached, runtime_type: State }
              - { term: Audit report, runtime_type: Artefact }
              - { term: Request resolved, runtime_type: Outcome }
              - { term: Occupant satisfaction, runtime_type: Learning }
              - { term: SLA attainment, runtime_type: Learning }
          - name: "Health, Safety & Compliance"
            note: "Fire Safety Order, L8 (Legionella), RIDDOR reporting and Building Safety Act golden-thread duties are statutory."
            operating_domains:
              - Compliance asset register (the golden thread)
              - Risk assessments and method statements
              - Fire safety and evacuation
              - Water hygiene (Legionella)
              - "Permit-to-work control"
              - Incident and accident reporting
              - Audit and certification tracking
            vocabulary:
              - { term: Compliance manager, runtime_type: Actor }
              - { term: Responsible person, runtime_type: Actor }
              - { term: Compliance item, runtime_type: Object }
              - { term: Risk assessment (RAMS), runtime_type: Artefact }
              - { term: Inspection due, runtime_type: Event }
              - { term: Compliant / overdue, runtime_type: State }
              - { term: Issue permit to work, runtime_type: Decision }
              - { term: "Permit-to-work flow", runtime_type: Workflow }
              - { term: Incident reported, runtime_type: Event }
              - { term: "Non-compliance flagged", runtime_type: State }
              - { term: Certificate of compliance, runtime_type: Artefact }
              - { term: Building fully compliant, runtime_type: Outcome }
              - { term: Compliance score, runtime_type: Learning }
              - { term: RIDDOR incident rate, runtime_type: Learning }
          - name: "Energy & Sustainability Management"
            note: MEES sets a minimum EPC rating for let property; SECR/ESOS carbon reporting is mandatory for larger organisations.
            operating_domains:
              - "Meter and sub-meter data"
              - Energy consumption and tariffs
              - Carbon footprint and reporting
              - EPC and MEES compliance
              - Retrofit and efficiency projects
              - Renewable generation tracking
              - BMS optimisation
            vocabulary:
              - { term: Energy manager, runtime_type: Actor }
              - { term: Building owner, runtime_type: Actor }
              - { term: Meter, runtime_type: Object }
              - { term: Consumption reading, runtime_type: Event }
              - { term: Above / below target, runtime_type: State }
              - { term: Approve retrofit measure, runtime_type: Decision }
              - { term: Energy audit, runtime_type: Workflow }
              - { term: EPC certificate, runtime_type: Artefact }
              - { term: Carbon report, runtime_type: Artefact }
              - { term: Retrofit installed, runtime_type: Event }
              - { term: "Net-zero target met", runtime_type: Outcome }
              - { term: Energy intensity (kWh/m²), runtime_type: Learning }
              - { term: Carbon reduction achieved, runtime_type: Learning }
          - name: "Space & Workplace Management"
            operating_domains:
              - Floor plans and space register
              - Desk and room booking
              - Occupancy and utilisation sensing
              - "Moves, adds and changes (MAC)"
              - Lease and occupancy cost allocation
              - Stacking and scenario planning
              - Wayfinding and signage
            vocabulary:
              - { term: Workplace manager, runtime_type: Actor }
              - { term: Employee occupant, runtime_type: Actor }
              - { term: Space (desk/room/floor), runtime_type: Object }
              - { term: Floor plan, runtime_type: Artefact }
              - { term: Desk booked, runtime_type: Event }
              - { term: Occupied / vacant, runtime_type: State }
              - { term: Approve move request, runtime_type: Decision }
              - { term: "Move, add, change (MAC)", runtime_type: Workflow }
              - { term: Occupancy snapshot captured, runtime_type: Event }
              - { term: "Over-capacity", runtime_type: State }
              - { term: Space plan, runtime_type: Artefact }
              - { term: Reconfiguration completed, runtime_type: Outcome }
              - { term: Space utilisation rate, runtime_type: Learning }
              - { term: Cost per occupied desk, runtime_type: Learning }
      - name: "n-housingOS"
        buyer: "Social landlords, housing associations and local-authority housing teams who pay per home or per tenancy to manage social and affordable housing."
        os_test: "Runs the social-tenancy and home lifecycle under regulator-of-social-housing rules (allocations, repairs, ASB, damp & mould, rent arrears) with a tenancy-and-property state model and a regulated-housing vocabulary distinct from market lettings or commercial FM; its own buyer (housing director) and grant/rent-funded budget."
        sectors:
          - name: "Tenancy & Housing Management"
            note: Regulated by the Regulator of Social Housing consumer standards; allocations governed by the Housing Act and local lettings policy.
            operating_domains:
              - "Allocations and lettings (choice-based)"
              - "Tenancy sign-up and terms"
              - Estate and neighbourhood management
              - "Anti-social behaviour (ASB) cases"
              - "Tenancy changes (succession, mutual exchange)"
              - Vulnerability and tenancy support
              - Possession and notice management
            vocabulary:
              - { term: Tenant / resident, runtime_type: Actor }
              - { term: Housing officer, runtime_type: Actor }
              - { term: Tenancy, runtime_type: Object }
              - { term: Property allocated, runtime_type: Event }
              - { term: Tenancy live, runtime_type: State }
              - { term: Decide allocation / shortlist, runtime_type: Decision }
              - { term: ASB case workflow, runtime_type: Workflow }
              - { term: Tenancy agreement, runtime_type: Artefact }
              - { term: Notice of seeking possession served, runtime_type: Event }
              - { term: "At-risk tenancy", runtime_type: State }
              - { term: Sustainable tenancy maintained, runtime_type: Outcome }
              - { term: Mutual exchange completed, runtime_type: Outcome }
              - { term: Tenancy sustainment rate, runtime_type: Learning }
              - { term: ASB case resolution time, runtime_type: Learning }
          - name: "Repairs & Asset Maintenance"
            note: "Awaab's Law / Decent Homes and disrepair (Homes Fitness for Human Habitation Act) impose statutory repair timescales for damp and hazards."
            operating_domains:
              - Repair reporting and diagnosis
              - Appointment booking and trade dispatch
              - Responsive vs planned repairs
              - "Damp, mould and disrepair cases"
              - "Void turnaround and re-let"
              - Stock condition surveys
              - Component replacement programmes
            vocabulary:
              - { term: Resident reporter, runtime_type: Actor }
              - { term: Repairs operative, runtime_type: Actor }
              - { term: Repair job, runtime_type: Object }
              - { term: Home (stock unit), runtime_type: Object }
              - { term: Repair reported, runtime_type: Event }
              - { term: Awaiting appointment, runtime_type: State }
              - { term: Triage priority (emergency/routine), runtime_type: Decision }
              - { term: "Damp & mould case workflow", runtime_type: Workflow }
              - { term: Job order, runtime_type: Artefact }
              - { term: Void property, runtime_type: State }
              - { term: Repair completed, runtime_type: Outcome }
              - { term: "Property re-let", runtime_type: Outcome }
              - { term: Repairs completed in target, runtime_type: Learning }
              - { term: Average void turnaround, runtime_type: Learning }
          - name: "Rents, Income & Arrears"
            note: "Pre-action protocol for rent-arrears possession must be followed before court action; welfare-benefit interactions are regulated."
            operating_domains:
              - Rent account and charges
              - "Universal Credit and housing-benefit interface"
              - Arrears escalation and recovery
              - Payment plans and forbearance
              - "Service-charge setting"
              - Income collection performance
              - "Former-tenant arrears"
            vocabulary:
              - { term: Account holder (tenant), runtime_type: Actor }
              - { term: Income officer, runtime_type: Actor }
              - { term: Rent account, runtime_type: Object }
              - { term: Charge raised, runtime_type: Event }
              - { term: In arrears, runtime_type: State }
              - { term: Escalate to recovery, runtime_type: Decision }
              - { term: Arrears escalation pathway, runtime_type: Workflow }
              - { term: Payment plan agreed, runtime_type: Artefact }
              - { term: Notice issued, runtime_type: Event }
              - { term: Account in credit, runtime_type: State }
              - { term: Arrears cleared, runtime_type: Outcome }
              - { term: "Current tenant arrears %", runtime_type: Learning }
              - { term: Collection rate, runtime_type: Learning }
              - { term: "Write-off level", runtime_type: Learning }
          - name: "Complaints, Resident Voice & Compliance"
            note: Housing Ombudsman Complaint Handling Code is statutory; Tenant Satisfaction Measures reporting is mandated by the Regulator of Social Housing.
            operating_domains:
              - Complaint logging and stages
              - Housing Ombudsman correspondence
              - Resident engagement and surveys
              - Tenant Satisfaction Measures (TSMs)
              - Compliance (gas/electric/fire/asbestos/water/lifts)
              - "Self-referral and learning from complaints"
              - Equality and vulnerability records
            vocabulary:
              - { term: Complainant resident, runtime_type: Actor }
              - { term: Complaints officer, runtime_type: Actor }
              - { term: Complaint case, runtime_type: Object }
              - { term: Complaint logged, runtime_type: Event }
              - { term: Stage 1 / Stage 2, runtime_type: State }
              - { term: Uphold or not uphold, runtime_type: Decision }
              - { term: "Complaint-handling workflow", runtime_type: Workflow }
              - { term: Compliance certificate (the big six), runtime_type: Artefact }
              - { term: Ombudsman determination received, runtime_type: Event }
              - { term: Overdue response, runtime_type: State }
              - { term: Complaint resolved, runtime_type: Outcome }
              - { term: Tenant Satisfaction Measures, runtime_type: Learning }
              - { term: Complaints upheld rate, runtime_type: Learning }
          - name: "Development & Affordable Housing Supply"
            note: "Affordable Homes Programme grant conditions, S106 affordable obligations and shared-ownership leases are regulated."
            operating_domains:
              - Land and scheme pipeline
              - Grant funding (Affordable Homes Programme)
              - S106 and nomination agreements
              - Tenure mix and shared ownership
              - Handover from contractor to housing
              - "First-let and allocations readiness"
              - Defects and aftercare period
            vocabulary:
              - { term: Development manager, runtime_type: Actor }
              - { term: Funder / Homes England, runtime_type: Actor }
              - { term: "New-build scheme", runtime_type: Object }
              - { term: Grant funding agreement, runtime_type: Artefact }
              - { term: Scheme approved, runtime_type: Event }
              - { term: In development, runtime_type: State }
              - { term: Approve tenure mix, runtime_type: Decision }
              - { term: Handover to housing workflow, runtime_type: Workflow }
              - { term: Homes handed over, runtime_type: Event }
              - { term: In defects period, runtime_type: State }
              - { term: Homes delivered and let, runtime_type: Outcome }
              - { term: Grant drawn per unit, runtime_type: Learning }
              - { term: Programme delivery vs target, runtime_type: Learning }
  - name: "Healthcare & Care"
    os:
      - name: "n-healthOS"
        buyer: "NHS trusts, GP partnerships and private hospital groups (the medical director / practice manager signs, the ICB or insurer funds the contract)."
        os_test: "Distinct buyer (provider boards), distinct state model (the patient clinical record and care pathway), distinct vocabulary (consultations, referrals, episodes) and thousands of repeatable provider organisations — a real OS, not a wording skin of care."
        sectors:
          - name: General Practice (Primary Care)
            note: "Regulated: CQC-registered primary medical service; prescribing under GMC/GPhC and controlled-drugs rules."
            operating_domains:
              - The patient list and registration
              - Daily appointment book and triage
              - Repeat prescription requests
              - Referrals to secondary care
              - "Long-term condition reviews (QOF)"
              - Childhood and seasonal immunisations
              - Incoming clinical correspondence and results
            vocabulary:
              - { term: Registered patient, runtime_type: Actor }
              - { term: GP / practice nurse, runtime_type: Actor }
              - { term: Appointment slot, runtime_type: Object }
              - { term: Patient record, runtime_type: Object }
              - { term: Consultation booked, runtime_type: Event }
              - { term: "Did-not-attend", runtime_type: Event }
              - { term: On the waiting list, runtime_type: State }
              - { term: Triage decision, runtime_type: Decision }
              - { term: "Refer or treat in-house", runtime_type: Decision }
              - { term: Repeat prescription run, runtime_type: Workflow }
              - { term: Referral letter, runtime_type: Artefact }
              - { term: Sick note (fit note), runtime_type: Artefact }
              - { term: Condition under control, runtime_type: Outcome }
              - { term: QOF achievement points, runtime_type: Learning }
          - name: "Acute Hospital & Outpatients"
            note: "Regulated: CQC-registered acute provider; RTT 18-week and emergency-access standards are statutory."
            operating_domains:
              - Outpatient clinic templates and slots
              - Inpatient bed board and ward rounds
              - Theatre lists and surgical scheduling
              - "Referral-to-treatment (RTT) pathways"
              - "Diagnostic ordering (imaging, pathology)"
              - Discharge planning and summaries
              - Multidisciplinary team (MDT) meetings
            vocabulary:
              - { term: Inpatient, runtime_type: Actor }
              - { term: Consultant / registrar, runtime_type: Actor }
              - { term: Hospital bed, runtime_type: Object }
              - { term: Care episode, runtime_type: Object }
              - { term: Admission, runtime_type: Event }
              - { term: Discharge, runtime_type: Event }
              - { term: Awaiting theatre, runtime_type: State }
              - { term: Breaching RTT clock, runtime_type: State }
              - { term: Treatment plan decision, runtime_type: Decision }
              - { term: Discharge planning, runtime_type: Workflow }
              - { term: Discharge summary, runtime_type: Artefact }
              - { term: Operation note, runtime_type: Artefact }
              - { term: Length of stay, runtime_type: Learning }
              - { term: Patient recovered / clinical outcome, runtime_type: Outcome }
          - name: "Community & District Nursing"
            note: "Regulated: NMC-registered nursing; CQC-registered community provider."
            operating_domains:
              - The caseload of housebound patients
              - "Daily home-visit rounds and routing"
              - "Wound and pressure-ulcer management"
              - Catheter and continence care
              - Insulin and medicines administration in the home
              - "Palliative and end-of-life visits"
              - Caseload handover between teams
            vocabulary:
              - { term: Housebound patient, runtime_type: Actor }
              - { term: Community nurse, runtime_type: Actor }
              - { term: Visit on the round, runtime_type: Object }
              - { term: Wound assessment, runtime_type: Object }
              - { term: Visit completed, runtime_type: Event }
              - { term: Referral received, runtime_type: Event }
              - { term: Wound healing / deteriorating, runtime_type: State }
              - { term: Visit frequency decision, runtime_type: Decision }
              - { term: Daily round planning, runtime_type: Workflow }
              - { term: Care plan, runtime_type: Artefact }
              - { term: Wound photo record, runtime_type: Artefact }
              - { term: Avoided hospital admission, runtime_type: Outcome }
              - { term: Healing rate, runtime_type: Learning }
              - { term: Discharged from caseload, runtime_type: Outcome }
          - name: "Diagnostics & Imaging"
            note: "Regulated: IR(ME)R ionising-radiation rules; UKAS-accredited pathology; CQC diagnostic registration."
            operating_domains:
              - The imaging request queue
              - "Modality scheduling (MRI, CT, X-ray, ultrasound)"
              - Reporting worklist for radiologists
              - "Critical-finding alerts"
              - Pathology specimen tracking
              - "Result turnaround and sign-off"
              - Equipment QA and dose monitoring
            vocabulary:
              - { term: Referring clinician, runtime_type: Actor }
              - { term: Reporting radiologist, runtime_type: Actor }
              - { term: Imaging study, runtime_type: Object }
              - { term: Specimen, runtime_type: Object }
              - { term: Scan acquired, runtime_type: Event }
              - { term: Critical finding flagged, runtime_type: Event }
              - { term: Awaiting report, runtime_type: State }
              - { term: Protocol selection, runtime_type: Decision }
              - { term: Reporting workflow, runtime_type: Workflow }
              - { term: Radiology report, runtime_type: Artefact }
              - { term: Result released to referrer, runtime_type: Outcome }
              - { term: Report turnaround time, runtime_type: Learning }
              - { term: Radiation dose record, runtime_type: Artefact }
          - name: "Urgent & Emergency Care"
            note: "Regulated: CQC urgent-care registration; statutory 4-hour and ambulance-handover standards."
            operating_domains:
              - "The A&E tracking board"
              - Triage and streaming on arrival
              - Ambulance handover queue
              - Resus and majors flow
              - "4-hour decision-to-admit clock"
              - "Same-day emergency care (SDEC) pathway"
              - "Mental-health crisis presentations"
            vocabulary:
              - { term: Arriving patient, runtime_type: Actor }
              - { term: Triage nurse, runtime_type: Actor }
              - { term: "Tracking-board entry", runtime_type: Object }
              - { term: Acuity category, runtime_type: Object }
              - { term: Patient arrival, runtime_type: Event }
              - { term: Ambulance handover, runtime_type: Event }
              - { term: "Breaching 4-hour target", runtime_type: State }
              - { term: "Admit-or-discharge decision", runtime_type: Decision }
              - { term: Streaming workflow, runtime_type: Workflow }
              - { term: Triage assessment, runtime_type: Artefact }
              - { term: Patient stabilised, runtime_type: Outcome }
              - { term: "Time-to-treatment", runtime_type: Learning }
              - { term: Left without being seen, runtime_type: State }
          - name: "Private & Insured Care"
            note: "Regulated: CQC-registered independent provider; PHIN outcome publication; FCA rules on regulated insurance activity."
            operating_domains:
              - "Self-pay and insured patient enquiries"
              - "Pre-authorisation with insurers"
              - Consultant clinic and theatre booking
              - Itemised billing and CCSD coding
              - Insurer claims submission and settlement
              - Patient pathway concierge
              - Outcome and PROMs reporting to insurers
            vocabulary:
              - { term: "Self-pay patient", runtime_type: Actor }
              - { term: Insurer, runtime_type: Actor }
              - { term: Treatment package, runtime_type: Object }
              - { term: "Pre-authorisation code", runtime_type: Object }
              - { term: Quote accepted, runtime_type: Event }
              - { term: Claim submitted, runtime_type: Event }
              - { term: Awaiting authorisation, runtime_type: State }
              - { term: Approve or query claim, runtime_type: Decision }
              - { term: Claims settlement workflow, runtime_type: Workflow }
              - { term: Itemised invoice, runtime_type: Artefact }
              - { term: Claim paid, runtime_type: Outcome }
              - { term: Claim acceptance rate, runtime_type: Learning }
              - { term: "Patient-reported outcome (PROM)", runtime_type: Learning }
      - name: "n-careOS"
        buyer: "Care-home operators and domiciliary-care agency owners (registered manager / director signs; local-authority commissioners and self-funders pay the fees)."
        os_test: "Different buyer (social-care providers, not the NHS), different state model (the resident/service-user's care plan and visit log, not a clinical record), different vocabulary (rotas, fees, safeguarding) and tens of thousands of repeatable agencies and homes — a genuine OS."
        sectors:
          - name: "Residential & Nursing Homes"
            note: "Regulated: CQC-registered care home; medicines under NICE SC1; safeguarding under Care Act 2014."
            operating_domains:
              - The resident roster and room board
              - Daily care notes and observations
              - Medication administration rounds (MAR)
              - Staff rota and shift cover
              - Falls and incident logging
              - "Care-plan reviews and reassessment"
              - Family communication and visits
            vocabulary:
              - { term: Resident, runtime_type: Actor }
              - { term: Carer / nurse on shift, runtime_type: Actor }
              - { term: Care plan, runtime_type: Object }
              - { term: MAR chart, runtime_type: Object }
              - { term: Medication given, runtime_type: Event }
              - { term: Fall recorded, runtime_type: Event }
              - { term: Care needs increasing, runtime_type: State }
              - { term: Escalate to GP or 999, runtime_type: Decision }
              - { term: Medication round, runtime_type: Workflow }
              - { term: Daily care note, runtime_type: Artefact }
              - { term: Body map, runtime_type: Artefact }
              - { term: Resident settled and well, runtime_type: Outcome }
              - { term: Occupancy rate, runtime_type: Learning }
              - { term: Safeguarding concern raised, runtime_type: State }
          - name: Domiciliary (Home) Care
            note: "Regulated: CQC-registered domiciliary provider; electronic call monitoring evidences commissioned hours."
            operating_domains:
              - The visit schedule and rounds
              - "Carer-to-client matching"
              - "Electronic call monitoring (check-in/out)"
              - Care tasks per visit
              - Travel time and route planning
              - Missed and late call alerts
              - Timesheet and invoice reconciliation
            vocabulary:
              - { term: Service user, runtime_type: Actor }
              - { term: Care worker, runtime_type: Actor }
              - { term: Visit, runtime_type: Object }
              - { term: Care package, runtime_type: Object }
              - { term: "Check-in at door", runtime_type: Event }
              - { term: Late or missed call, runtime_type: Event }
              - { term: Visit in progress, runtime_type: State }
              - { term: Reassign cover for sickness, runtime_type: Decision }
              - { term: Rota scheduling, runtime_type: Workflow }
              - { term: Visit task log, runtime_type: Artefact }
              - { term: Care worker timesheet, runtime_type: Artefact }
              - { term: Client able to stay at home, runtime_type: Outcome }
              - { term: "On-time visit rate", runtime_type: Learning }
              - { term: Care package reviewed, runtime_type: Outcome }
          - name: "Supported Living & Learning Disability"
            note: "Regulated: CQC-registered; Mental Capacity Act 2005 and DoLS/LPS for capacity and deprivation of liberty."
            operating_domains:
              - Tenant support plans and goals
              - Daily living and independence tasks
              - Positive behaviour support records
              - Activity and community access planning
              - Staff support ratios per tenant
              - "Capacity and best-interest decisions"
              - Money and tenancy management
            vocabulary:
              - { term: Tenant, runtime_type: Actor }
              - { term: Support worker, runtime_type: Actor }
              - { term: Support plan, runtime_type: Object }
              - { term: Personal goal, runtime_type: Object }
              - { term: Goal milestone reached, runtime_type: Event }
              - { term: Incident of distress, runtime_type: Event }
              - { term: Settled in own tenancy, runtime_type: State }
              - { term: "Best-interest decision", runtime_type: Decision }
              - { term: Positive behaviour support, runtime_type: Workflow }
              - { term: Outcome tracker, runtime_type: Artefact }
              - { term: Capacity assessment, runtime_type: Artefact }
              - { term: Increased independence, runtime_type: Outcome }
              - { term: Progress against goals, runtime_type: Learning }
          - name: "Children's Residential & Fostering"
            note: "Regulated: Ofsted-registered (Children's Homes Regs 2015 / fostering); statutory IRO reviews."
            operating_domains:
              - The placement matching and roster
              - "Daily care and key-work sessions"
              - Education and PEP tracking
              - "Looked-after-child reviews"
              - "Risk and missing-from-home logging"
              - Contact arrangements with family
              - "Foster-carer recruitment and approval"
            vocabulary:
              - { term: "Looked-after child", runtime_type: Actor }
              - { term: Key worker / foster carer, runtime_type: Actor }
              - { term: Placement, runtime_type: Object }
              - { term: Placement plan, runtime_type: Object }
              - { term: Placement started, runtime_type: Event }
              - { term: "Missing-from-home episode", runtime_type: Event }
              - { term: Placement at risk of breakdown, runtime_type: State }
              - { term: Matching decision, runtime_type: Decision }
              - { term: Statutory review cycle, runtime_type: Workflow }
              - { term: Daily log, runtime_type: Artefact }
              - { term: Personal education plan, runtime_type: Artefact }
              - { term: "Stable, lasting placement", runtime_type: Outcome }
              - { term: Placement stability rate, runtime_type: Learning }
          - name: "Reablement & Intermediate Care"
            note: "Regulated: Care Act 2014 reablement duty; CQC where personal care is provided."
            operating_domains:
              - "The short-term reablement caseload"
              - "Goal-based recovery plans"
              - "Step-down beds from hospital"
              - Equipment and adaptation provision
              - "Therapy-led independence tasks"
              - "6-week outcome reviews"
              - Onward referral at discharge
            vocabulary:
              - { term: Reablement client, runtime_type: Actor }
              - { term: Reablement worker / OT, runtime_type: Actor }
              - { term: Recovery goal, runtime_type: Object }
              - { term: "Step-down bed", runtime_type: Object }
              - { term: Reablement started, runtime_type: Event }
              - { term: Goal achieved, runtime_type: Event }
              - { term: Progressing toward independence, runtime_type: State }
              - { term: Continue or step down support, runtime_type: Decision }
              - { term: "6-week reablement cycle", runtime_type: Workflow }
              - { term: Outcome review, runtime_type: Artefact }
              - { term: No ongoing care needed, runtime_type: Outcome }
              - { term: Reduction in care hours, runtime_type: Learning }
              - { term: Equipment installed, runtime_type: Event }
          - name: "Care Commissioning & Brokerage"
            note: "Regulated: Public Contracts Regulations / Provider Selection Regime; Care Act sufficiency duty."
            operating_domains:
              - The provider framework and approved list
              - Care package brokerage and placement
              - Fee negotiation and rate cards
              - Quality and contract monitoring
              - Spot vs block purchasing
              - Provider failure contingency
              - Invoice validation against delivered hours
            vocabulary:
              - { term: Commissioner / broker, runtime_type: Actor }
              - { term: Approved provider, runtime_type: Actor }
              - { term: Care package request, runtime_type: Object }
              - { term: Rate card, runtime_type: Object }
              - { term: Package placed, runtime_type: Event }
              - { term: Provider concern raised, runtime_type: Event }
              - { term: Awaiting placement, runtime_type: State }
              - { term: Provider selection decision, runtime_type: Decision }
              - { term: Brokerage workflow, runtime_type: Workflow }
              - { term: Service specification, runtime_type: Artefact }
              - { term: Need met within budget, runtime_type: Outcome }
              - { term: Cost per package, runtime_type: Learning }
              - { term: Contract under review, runtime_type: State }
      - name: "n-dentalOS"
        buyer: Dental practice owners and DSO/corporate groups (principal dentist / practice manager signs; NHS contract value and private patients fund it).
        os_test: "Own buyer (practice principals), own state model (the tooth chart and treatment plan, not a medical record), own vocabulary (UDAs, charting, recalls) and a large repeatable population of practices — clearly a separate OS from general health."
        sectors:
          - name: NHS Mixed Practice
            note: "Regulated: CQC and GDC registration; NHS dental contract (UDA/FP17) under NHS BSA."
            operating_domains:
              - The recall and appointment book
              - Tooth charting and treatment planning
              - Banded NHS courses of treatment
              - UDA target tracking and claims (FP17)
              - Patient exemption and charge checks
              - Lab work tracking
              - Recall scheduling
            vocabulary:
              - { term: NHS patient, runtime_type: Actor }
              - { term: Dentist / hygienist, runtime_type: Actor }
              - { term: Tooth chart, runtime_type: Object }
              - { term: Course of treatment, runtime_type: Object }
              - { term: Course completed, runtime_type: Event }
              - { term: "Failed-to-attend", runtime_type: Event }
              - { term: Open course of treatment, runtime_type: State }
              - { term: Banding decision, runtime_type: Decision }
              - { term: FP17 claim submission, runtime_type: Workflow }
              - { term: Treatment plan, runtime_type: Artefact }
              - { term: FP17 claim form, runtime_type: Artefact }
              - { term: UDA target delivered, runtime_type: Outcome }
              - { term: UDA delivery rate, runtime_type: Learning }
          - name: "Private & Cosmetic Dentistry"
            note: "Regulated: GDC; finance plans may be FCA-regulated consumer credit."
            operating_domains:
              - "Smile-design consultations and case acceptance"
              - Itemised private treatment plans
              - "Clear-aligner and whitening cases"
              - Implant case staging
              - Finance and payment plans
              - Before/after photo records
              - Membership plan management
            vocabulary:
              - { term: Private patient, runtime_type: Actor }
              - { term: Treatment coordinator, runtime_type: Actor }
              - { term: Cosmetic case, runtime_type: Object }
              - { term: Itemised quote, runtime_type: Object }
              - { term: Case accepted, runtime_type: Event }
              - { term: Deposit taken, runtime_type: Event }
              - { term: Case in treatment, runtime_type: State }
              - { term: "Treatment-option recommendation", runtime_type: Decision }
              - { term: "Case-acceptance workflow", runtime_type: Workflow }
              - { term: Clinical photo set, runtime_type: Artefact }
              - { term: Consent form, runtime_type: Artefact }
              - { term: Smile transformed, runtime_type: Outcome }
              - { term: "Case-acceptance rate", runtime_type: Learning }
          - name: Orthodontics
            note: "Regulated: GDC; NHS orthodontic contract eligibility via IOTN."
            operating_domains:
              - The active patient bracket/aligner caseload
              - "Treatment-stage scheduling"
              - Wire and aligner change visits
              - IOTN scoring and case eligibility
              - Retention and review phase
              - "Lab and aligner-order tracking"
              - "Long contract-length monitoring"
            vocabulary:
              - { term: Orthodontic patient, runtime_type: Actor }
              - { term: Orthodontist / therapist, runtime_type: Actor }
              - { term: Active appliance, runtime_type: Object }
              - { term: Treatment stage, runtime_type: Object }
              - { term: Aligner change, runtime_type: Event }
              - { term: Debond appointment, runtime_type: Event }
              - { term: In active treatment, runtime_type: State }
              - { term: IOTN eligibility decision, runtime_type: Decision }
              - { term: "Treatment-progression workflow", runtime_type: Workflow }
              - { term: Treatment record, runtime_type: Artefact }
              - { term: Retainer fitted, runtime_type: Event }
              - { term: "Aligned, stable bite", runtime_type: Outcome }
              - { term: Average treatment duration, runtime_type: Learning }
          - name: Dental Laboratory
            note: "Regulated: MHRA custom-made medical device regulations; GDC-registered technicians."
            operating_domains:
              - The lab case queue and bench tracking
              - "Digital impression intake (intra-oral scans)"
              - CAD design and milling jobs
              - Shade and prescription matching
              - Despatch and delivery dates
              - Remake and adjustment handling
              - Practice account management
            vocabulary:
              - { term: Referring practice, runtime_type: Actor }
              - { term: Dental technician, runtime_type: Actor }
              - { term: Lab case, runtime_type: Object }
              - { term: Prescription (lab ticket), runtime_type: Object }
              - { term: Impression received, runtime_type: Event }
              - { term: Case despatched, runtime_type: Event }
              - { term: On the bench, runtime_type: State }
              - { term: Remake or adjust decision, runtime_type: Decision }
              - { term: "Case-fabrication workflow", runtime_type: Workflow }
              - { term: CAD design file, runtime_type: Artefact }
              - { term: Finished restoration, runtime_type: Artefact }
              - { term: Case delivered on time, runtime_type: Outcome }
              - { term: Remake rate, runtime_type: Learning }
          - name: "Community & Domiciliary Dental"
            note: "Regulated: GDC and CQC; Mental Capacity Act for best-interest treatment; sedation governance."
            operating_domains:
              - "The special-care patient caseload"
              - Domiciliary visit scheduling
              - Sedation and GA referral pathway
              - "Care-home oral-health rounds"
              - "Capacity and best-interest assessment"
              - Mobile equipment management
              - Referral triage from GDPs
            vocabulary:
              - { term: "Special-care patient", runtime_type: Actor }
              - { term: Community dentist, runtime_type: Actor }
              - { term: Domiciliary visit, runtime_type: Object }
              - { term: Referral, runtime_type: Object }
              - { term: Visit completed, runtime_type: Event }
              - { term: Referral received, runtime_type: Event }
              - { term: Awaiting GA slot, runtime_type: State }
              - { term: "Sedation-or-GA decision", runtime_type: Decision }
              - { term: "Best-interest assessment", runtime_type: Workflow }
              - { term: Mobile treatment record, runtime_type: Artefact }
              - { term: Pain resolved / mouth healthy, runtime_type: Outcome }
              - { term: "Access-to-care rate", runtime_type: Learning }
              - { term: Care plan, runtime_type: Artefact }
      - name: "n-vetOS"
        buyer: Veterinary practice owners and corporate vet groups (clinical director / practice manager signs; pet owners and pet insurers pay).
        os_test: "Own buyer (vet practices), own state model (the animal patient record with species/weight-dosing and owner-as-payer), own vocabulary (consults, ops, vaccinations, insurance claims) and a huge repeatable practice population — a real, distinct OS."
        sectors:
          - name: "Companion-Animal Practice"
            note: "Regulated: RCVS practice standards; VMD prescribing cascade and POM-V controls."
            operating_domains:
              - The consult diary and ops list
              - Animal clinical records (species/breed/weight)
              - Vaccination and parasite recall schedule
              - "Dispensary and POM-V dispensing"
              - Insurance claim processing
              - "Health-plan subscriptions"
              - Owner reminders and recalls
            vocabulary:
              - { term: Pet owner (client), runtime_type: Actor }
              - { term: Animal patient, runtime_type: Actor }
              - { term: Clinical record, runtime_type: Object }
              - { term: Consult slot, runtime_type: Object }
              - { term: Consultation, runtime_type: Event }
              - { term: Vaccination due, runtime_type: Event }
              - { term: Under treatment, runtime_type: State }
              - { term: "Treat, refer or operate", runtime_type: Decision }
              - { term: Insurance claim workflow, runtime_type: Workflow }
              - { term: "Prescription (POM-V)", runtime_type: Artefact }
              - { term: Insurance claim form, runtime_type: Artefact }
              - { term: Animal recovered, runtime_type: Outcome }
              - { term: Recall compliance rate, runtime_type: Learning }
              - { term: "Health-plan member", runtime_type: State }
          - name: Equine Practice
            note: "Regulated: RCVS; VMD cascade; performance-horse medication rules under BHA/FEI where relevant."
            operating_domains:
              - "The yard-visit ambulatory rounds"
              - "Per-horse clinical and lameness records"
              - "Pre-purchase vetting exams"
              - Routine dentistry and worming visits
              - "Emergency colic call-outs"
              - Stud and reproduction work
              - Mileage and visit billing
            vocabulary:
              - { term: Horse owner / yard, runtime_type: Actor }
              - { term: Equine vet, runtime_type: Actor }
              - { term: Horse record, runtime_type: Object }
              - { term: Yard visit, runtime_type: Object }
              - { term: Visit attended, runtime_type: Event }
              - { term: Colic emergency call, runtime_type: Event }
              - { term: Lame / sound, runtime_type: State }
              - { term: Pass or fail vetting, runtime_type: Decision }
              - { term: Ambulatory round planning, runtime_type: Workflow }
              - { term: Vetting certificate, runtime_type: Artefact }
              - { term: "Lameness work-up record", runtime_type: Artefact }
              - { term: Horse fit to work, runtime_type: Outcome }
              - { term: "Call-out response time", runtime_type: Learning }
          - name: "Farm & Production Animal"
            note: "Regulated: APHA notifiable-disease reporting; VMD responsible-use; farm assurance schemes."
            operating_domains:
              - The herd/flock health records
              - "Routine fertility and TB-testing visits"
              - "Herd health-plan management"
              - Antibiotic stewardship and recording
              - Statutory disease reporting
              - "Movement and medicine-book compliance"
              - "Production-data monitoring"
            vocabulary:
              - { term: Farmer, runtime_type: Actor }
              - { term: Farm vet, runtime_type: Actor }
              - { term: Herd / flock, runtime_type: Object }
              - { term: Medicine book, runtime_type: Object }
              - { term: TB test performed, runtime_type: Event }
              - { term: Notifiable disease suspected, runtime_type: Event }
              - { term: Herd under restriction, runtime_type: State }
              - { term: Treat or cull decision, runtime_type: Decision }
              - { term: "Herd health-plan workflow", runtime_type: Workflow }
              - { term: Health plan, runtime_type: Artefact }
              - { term: Disease report, runtime_type: Artefact }
              - { term: Herd health improved, runtime_type: Outcome }
              - { term: Antibiotic use rate, runtime_type: Learning }
          - name: "Referral & Specialist Hospitals"
            note: "Regulated: RCVS-accredited veterinary hospital standards; specialist registration."
            operating_domains:
              - The referral intake from primary vets
              - Specialist case workups
              - Advanced imaging (CT/MRI) scheduling
              - Surgical theatre lists
              - ICU and inpatient monitoring
              - "Referring-vet communication"
              - Estimate and deposit handling
            vocabulary:
              - { term: Referring vet, runtime_type: Actor }
              - { term: Specialist, runtime_type: Actor }
              - { term: Referral case, runtime_type: Object }
              - { term: Inpatient stay, runtime_type: Object }
              - { term: Referral accepted, runtime_type: Event }
              - { term: Surgery performed, runtime_type: Event }
              - { term: In intensive care, runtime_type: State }
              - { term: "Surgical-approach decision", runtime_type: Decision }
              - { term: Referral workflow, runtime_type: Workflow }
              - { term: Discharge report to rDVM, runtime_type: Artefact }
              - { term: Treatment estimate, runtime_type: Artefact }
              - { term: Successful outcome, runtime_type: Outcome }
              - { term: Case survival rate, runtime_type: Learning }
          - name: "Out-of-Hours & Emergency"
            note: "Regulated: RCVS 24-hour emergency cover obligation; controlled-drug handling out of hours."
            operating_domains:
              - The overnight triage line
              - Emergency case prioritisation
              - "On-call rota across practices"
              - "Critical-care stabilisation"
              - Handover back to day practice
              - Emergency estimate and consent
              - Euthanasia and bereavement support
            vocabulary:
              - { term: Distressed owner, runtime_type: Actor }
              - { term: Emergency vet on call, runtime_type: Actor }
              - { term: Emergency case, runtime_type: Object }
              - { term: Triage call, runtime_type: Object }
              - { term: Emergency presentation, runtime_type: Event }
              - { term: Handover to day practice, runtime_type: Event }
              - { term: Critical / stable, runtime_type: State }
              - { term: Treat or euthanise decision, runtime_type: Decision }
              - { term: "Triage-and-stabilise workflow", runtime_type: Workflow }
              - { term: "Consent-to-treat form", runtime_type: Artefact }
              - { term: Patient stabilised overnight, runtime_type: Outcome }
              - { term: "Triage-to-treatment time", runtime_type: Learning }
              - { term: Handover note, runtime_type: Artefact }
      - name: "n-pharmaOS"
        buyer: "Community pharmacy owners/multiples, dispensing-appliance and online-pharmacy operators (superintendent pharmacist / owner signs; NHS dispensing reimbursement and retail pay)."
        os_test: "Own buyer (pharmacy contractors), own state model (the prescription/dispensing record and stock, not a clinical record), own vocabulary (scripts, MDS, reimbursement, services) and a huge repeatable contractor population — a distinct OS from clinical health."
        sectors:
          - name: Community Pharmacy Dispensing
            note: "Regulated: GPhC-registered pharmacy; controlled drugs under Misuse of Drugs Regs; NHS terms of service."
            operating_domains:
              - The prescription queue (EPS)
              - Dispensing and labelling bench
              - Stock and ordering management
              - "Controlled-drug register"
              - NHS reimbursement claims (FP34)
              - "Owings and out-of-stock handling"
              - Patient collection and delivery
            vocabulary:
              - { term: Patient, runtime_type: Actor }
              - { term: Pharmacist / dispenser, runtime_type: Actor }
              - { term: Prescription (script), runtime_type: Object }
              - { term: Stock item, runtime_type: Object }
              - { term: Script received (EPS), runtime_type: Event }
              - { term: Item dispensed, runtime_type: Event }
              - { term: Awaiting collection, runtime_type: State }
              - { term: "Clinical-check decision", runtime_type: Decision }
              - { term: Dispensing workflow, runtime_type: Workflow }
              - { term: Dispensing label, runtime_type: Artefact }
              - { term: "Controlled-drug register entry", runtime_type: Artefact }
              - { term: Medicine supplied safely, runtime_type: Outcome }
              - { term: Dispensing accuracy rate, runtime_type: Learning }
          - name: Pharmacy Clinical Services
            note: "Regulated: GPhC; supply under PGDs; NHS advanced/clinical service specifications."
            operating_domains:
              - The Pharmacy First consultation pathway
              - Flu and travel vaccination clinics
              - "New Medicine Service follow-ups"
              - "Blood-pressure check service"
              - "Contraception and minor-ailment supply"
              - Service claim submission (MYS)
              - Patient consent and booking
            vocabulary:
              - { term: Service patient, runtime_type: Actor }
              - { term: Clinical pharmacist, runtime_type: Actor }
              - { term: Service consultation, runtime_type: Object }
              - { term: Patient group direction (PGD), runtime_type: Object }
              - { term: Consultation completed, runtime_type: Event }
              - { term: Vaccine administered, runtime_type: Event }
              - { term: Eligible for service, runtime_type: State }
              - { term: "Treat, supply or refer", runtime_type: Decision }
              - { term: Pharmacy First workflow, runtime_type: Workflow }
              - { term: Consultation record, runtime_type: Artefact }
              - { term: Service claim, runtime_type: Artefact }
              - { term: Patient managed in pharmacy, runtime_type: Outcome }
              - { term: Service uptake rate, runtime_type: Learning }
          - name: "Dispensing Appliance & MDS / Care-Home Supply"
            note: "Regulated: GPhC; DAC contract for appliances; CD handling in monitored-dosage systems."
            operating_domains:
              - "The monitored-dosage-system production line"
              - "Care-home cycle scheduling"
              - Appliance and stoma supply
              - "Bulk repeat-order management"
              - Bespoke compliance packaging
              - Delivery rounds to homes
              - Reconciliation against MAR charts
            vocabulary:
              - { term: Care home / housebound patient, runtime_type: Actor }
              - { term: MDS technician, runtime_type: Actor }
              - { term: Blister pack (MDS), runtime_type: Object }
              - { term: Repeat cycle, runtime_type: Object }
              - { term: Pack assembled, runtime_type: Event }
              - { term: Cycle dispatched, runtime_type: Event }
              - { term: In production cycle, runtime_type: State }
              - { term: "Pack-or-bottle decision", runtime_type: Decision }
              - { term: MDS production workflow, runtime_type: Workflow }
              - { term: MAR chart, runtime_type: Artefact }
              - { term: Compliance pack delivered, runtime_type: Outcome }
              - { term: "On-time cycle rate", runtime_type: Learning }
              - { term: Appliance prescription, runtime_type: Artefact }
          - name: "Online & Distance-Selling Pharmacy"
            note: "Regulated: GPhC distance-selling registration; MHRA POM rules; prescriber regulation."
            operating_domains:
              - The online order pipeline
              - Remote prescriber questionnaire review
              - "Hub-and-spoke dispensing"
              - "Courier and tracked-delivery logistics"
              - Age and identity verification
              - "Repeat-order subscriptions"
              - "Adverse-event and recall handling"
            vocabulary:
              - { term: Online patient, runtime_type: Actor }
              - { term: Remote prescriber, runtime_type: Actor }
              - { term: Online order, runtime_type: Object }
              - { term: Digital questionnaire, runtime_type: Object }
              - { term: Order placed, runtime_type: Event }
              - { term: Parcel dispatched, runtime_type: Event }
              - { term: "Awaiting prescriber sign-off", runtime_type: State }
              - { term: Approve or decline supply, runtime_type: Decision }
              - { term: Hub dispensing workflow, runtime_type: Workflow }
              - { term: Electronic prescription, runtime_type: Artefact }
              - { term: Medicine delivered safely, runtime_type: Outcome }
              - { term: "Order-to-doorstep time", runtime_type: Learning }
              - { term: Flagged for clinical review, runtime_type: State }
          - name: "Hospital & Aseptic Pharmacy"
            note: "Regulated: MHRA aseptic/manufacturing (Specials) licensing; GPhC; chemo handling under COSHH."
            operating_domains:
              - The inpatient medicines supply
              - Aseptic / chemotherapy compounding
              - Ward stock and automated cabinets
              - Clinical pharmacist medicines review
              - TTO (discharge medicines) preparation
              - Drug expenditure and formulary control
              - Batch and QA release
            vocabulary:
              - { term: Inpatient, runtime_type: Actor }
              - { term: Hospital pharmacist, runtime_type: Actor }
              - { term: Drug chart, runtime_type: Object }
              - { term: Aseptic batch, runtime_type: Object }
              - { term: Medicines reconciliation done, runtime_type: Event }
              - { term: Batch released, runtime_type: Event }
              - { term: Awaiting QA release, runtime_type: State }
              - { term: "Formulary-approval decision", runtime_type: Decision }
              - { term: Aseptic compounding workflow, runtime_type: Workflow }
              - { term: Discharge medicines (TTO), runtime_type: Artefact }
              - { term: Worksheet / batch record, runtime_type: Artefact }
              - { term: Patient safely medicated, runtime_type: Outcome }
              - { term: Medicines optimisation savings, runtime_type: Learning }
      - name: "n-mentalhealthOS"
        buyer: "Mental-health and therapy providers — IAPT/NHS Talking Therapies services, private clinics, EAPs and rehab units (clinical/service director signs; NHS, insurers and employers pay)."
        os_test: "Distinct buyer (mental-health providers), distinct state model (the episode-of-care with risk and outcome measures, not a physical clinical record), distinct vocabulary (sessions, risk, CPA, outcome measures) and a repeatable provider population — a genuine OS, not a sector of n-healthOS."
        sectors:
          - name: NHS Talking Therapies (IAPT)
            note: "Regulated: NHS Talking Therapies standards; clinicians under HCPC/BABCP/BACP; data under NHS IG."
            operating_domains:
              - "The self-referral and assessment intake"
              - "Stepped-care allocation"
              - Session booking across the caseload
              - "Routine outcome measurement (PHQ-9/GAD-7)"
              - "Waiting-list and recovery tracking"
              - Risk and safeguarding escalation
              - "Discharge and relapse-prevention"
            vocabulary:
              - { term: Client (service user), runtime_type: Actor }
              - { term: Psychological wellbeing practitioner, runtime_type: Actor }
              - { term: Episode of care, runtime_type: Object }
              - { term: Outcome questionnaire, runtime_type: Object }
              - { term: Assessment booked, runtime_type: Event }
              - { term: Session attended, runtime_type: Event }
              - { term: On the waiting list, runtime_type: State }
              - { term: "Step-up / step-down decision", runtime_type: Decision }
              - { term: "Stepped-care workflow", runtime_type: Workflow }
              - { term: Treatment plan, runtime_type: Artefact }
              - { term: Moved to recovery, runtime_type: Outcome }
              - { term: Recovery rate, runtime_type: Learning }
              - { term: Risk flag raised, runtime_type: State }
          - name: Community Mental Health (CMHT/CPA)
            note: "Regulated: CQC; Mental Health Act 1983 for detained patients; HCPC/NMC registration."
            operating_domains:
              - The team caseload and care coordination
              - "Care-programme-approach plans"
              - Depot and clozapine clinics
              - "Crisis and home-treatment handover"
              - Risk assessment and formulation
              - Care plan and recovery reviews
              - "Care-coordinator allocation"
            vocabulary:
              - { term: Service user, runtime_type: Actor }
              - { term: Care coordinator, runtime_type: Actor }
              - { term: Care plan (CPA), runtime_type: Object }
              - { term: Risk assessment, runtime_type: Object }
              - { term: Review meeting held, runtime_type: Event }
              - { term: Relapse / crisis, runtime_type: Event }
              - { term: Stable in the community, runtime_type: State }
              - { term: Admit or treat at home, runtime_type: Decision }
              - { term: "Care-coordination workflow", runtime_type: Workflow }
              - { term: Crisis plan, runtime_type: Artefact }
              - { term: Recovery sustained, runtime_type: Outcome }
              - { term: Caseload acuity, runtime_type: Learning }
              - { term: Under home treatment, runtime_type: State }
          - name: "Inpatient & Crisis Care"
            note: "Regulated: Mental Health Act 1983 / MHA Code of Practice; CQC; restraint reporting duties."
            operating_domains:
              - The ward bed state and admissions
              - MHA detention and section tracking
              - "Observation-level management"
              - "Leave and section-17 authorisation"
              - Seclusion and restraint recording
              - Tribunal and discharge planning
              - "Bed-finding across the network"
            vocabulary:
              - { term: Detained patient, runtime_type: Actor }
              - { term: Responsible clinician, runtime_type: Actor }
              - { term: Ward bed, runtime_type: Object }
              - { term: Section paperwork, runtime_type: Object }
              - { term: Admission under section, runtime_type: Event }
              - { term: Restraint incident, runtime_type: Event }
              - { term: On enhanced observations, runtime_type: State }
              - { term: Grant or refuse leave, runtime_type: Decision }
              - { term: "Section-17 leave workflow", runtime_type: Workflow }
              - { term: Seclusion record, runtime_type: Artefact }
              - { term: Tribunal report, runtime_type: Artefact }
              - { term: Safely discharged, runtime_type: Outcome }
              - { term: Average length of admission, runtime_type: Learning }
          - name: "Private Therapy & Counselling"
            note: "Regulated: BACP/UKCP/HCPC professional standards; insurer-funded work needs registration."
            operating_domains:
              - The private client book and waitlist
              - Session scheduling and reminders
              - Contracting and consent
              - "Outcome-measure tracking (CORE-10)"
              - "Self-pay and insurer billing"
              - Supervision and case notes
              - "Therapy-modality matching"
            vocabulary:
              - { term: Private client, runtime_type: Actor }
              - { term: Therapist / counsellor, runtime_type: Actor }
              - { term: Therapy session, runtime_type: Object }
              - { term: Therapeutic contract, runtime_type: Object }
              - { term: Session held, runtime_type: Event }
              - { term: Cancellation, runtime_type: Event }
              - { term: In active therapy, runtime_type: State }
              - { term: Modality and frequency choice, runtime_type: Decision }
              - { term: "Session-billing workflow", runtime_type: Workflow }
              - { term: Session note, runtime_type: Artefact }
              - { term: Insurer invoice, runtime_type: Artefact }
              - { term: Client goals met, runtime_type: Outcome }
              - { term: "Outcome-measure improvement", runtime_type: Learning }
          - name: "Addiction & Substance Misuse"
            note: "Regulated: CQC; controlled-drug prescribing under Misuse of Drugs Regs; NDTMS reporting."
            operating_domains:
              - The treatment caseload and keyworking
              - "Opioid-substitution prescribing and titration"
              - Supervised consumption arrangements
              - "Drug-test result tracking"
              - Recovery and abstinence goal plans
              - Detox and rehab referral
              - Outcome (TOP) recording
            vocabulary:
              - { term: Client in treatment, runtime_type: Actor }
              - { term: Recovery keyworker, runtime_type: Actor }
              - { term: Recovery plan, runtime_type: Object }
              - { term: Prescription / titration, runtime_type: Object }
              - { term: Drug test taken, runtime_type: Event }
              - { term: Missed pickup, runtime_type: Event }
              - { term: Stable on script, runtime_type: State }
              - { term: "Titrate, hold or detox decision", runtime_type: Decision }
              - { term: "Treatment-journey workflow", runtime_type: Workflow }
              - { term: Care and recovery plan, runtime_type: Artefact }
              - { term: Treatment outcome profile (TOP), runtime_type: Artefact }
              - { term: Sustained recovery, runtime_type: Outcome }
              - { term: Successful completion rate, runtime_type: Learning }
          - name: "Children & Young People (CAMHS)"
            note: "Regulated: CQC; safeguarding under Children Act; clinicians under HCPC/NMC/GMC."
            operating_domains:
              - The CYP referral and triage queue
              - "Tier-based caseload management"
              - Neurodevelopmental (ADHD/autism) assessment pathway
              - School and family liaison
              - "Risk and self-harm monitoring"
              - "Goal-based outcome tracking"
              - Transition to adult services
            vocabulary:
              - { term: Young person, runtime_type: Actor }
              - { term: CAMHS clinician, runtime_type: Actor }
              - { term: Referral, runtime_type: Object }
              - { term: Assessment pathway, runtime_type: Object }
              - { term: Referral triaged, runtime_type: Event }
              - { term: Crisis presentation, runtime_type: Event }
              - { term: Awaiting assessment, runtime_type: State }
              - { term: "Accept, signpost or escalate", runtime_type: Decision }
              - { term: Neurodevelopmental assessment workflow, runtime_type: Workflow }
              - { term: "Goal-based outcome record", runtime_type: Artefact }
              - { term: Diagnosis / formulation report, runtime_type: Artefact }
              - { term: Young person better supported, runtime_type: Outcome }
              - { term: "Waiting-time to assessment", runtime_type: Learning }
  - name: "People & Workforce"
    os:
      - name: "n-recOS"
        buyer: "Recruitment agency owners and in-house talent acquisition leaders who pay per seat/placement to fill roles faster."
        os_test: "Distinct buyer (agency/TA director, not HR), candidate-pipeline state model, placement-fee economics, and a vocabulary (req, shortlist, placement, rebate) no other OS shares — a repeatable industry of recruiters."
        sectors:
          - name: "Contingency & permanent agency recruitment"
            operating_domains:
              - Live vacancies / open requisitions taken from clients
              - "Candidate pipeline per role (long-list to offer)"
              - Client account and PSL (preferred supplier list) relationships
              - "Candidate sourcing channels (job boards, referrals, headhunt)"
              - Interview scheduling between client and candidate
              - Placement and invoicing / fee tracking
              - "Rebate and fall-off risk window"
              - Consultant desk performance and commission
            vocabulary:
              - { term: Vacancy (job order), runtime_type: Object }
              - { term: Candidate, runtime_type: Actor }
              - { term: Hiring client, runtime_type: Actor }
              - { term: Recruitment consultant, runtime_type: Actor }
              - { term: CV / résumé, runtime_type: Artefact }
              - { term: Shortlist submission, runtime_type: Event }
              - { term: Candidate stage (sourced → placed), runtime_type: State }
              - { term: Send CV to client decision, runtime_type: Decision }
              - { term: Interview booked, runtime_type: Event }
              - { term: Offer extended, runtime_type: Event }
              - { term: Placement, runtime_type: Outcome }
              - { term: Terms of business, runtime_type: Artefact }
              - { term: "Rebate / fall-off", runtime_type: State }
              - { term: Fill the role workflow, runtime_type: Workflow }
              - { term: "Time-to-fill", runtime_type: Learning }
              - { term: Placement fee invoice, runtime_type: Artefact }
          - name: Executive search (retained headhunting)
            operating_domains:
              - Retained search assignments / mandates
              - Target company mapping and longlists
              - Confidential candidate approaches
              - Client stakeholder / board engagement
              - "Competency-based assessment and referencing"
              - Search progress reporting to client
              - "Off-limits and conflict tracking"
              - Retainer billing milestones
            vocabulary:
              - { term: Search mandate, runtime_type: Object }
              - { term: Target executive, runtime_type: Actor }
              - { term: Research analyst, runtime_type: Actor }
              - { term: Company map / longlist, runtime_type: Artefact }
              - { term: Approach call, runtime_type: Event }
              - { term: Candidate status (approached → engaged), runtime_type: State }
              - { term: Present to client decision, runtime_type: Decision }
              - { term: Candidate report / profile pack, runtime_type: Artefact }
              - { term: Reference check, runtime_type: Event }
              - { term: "Off-limits restriction", runtime_type: State }
              - { term: Appointed hire, runtime_type: Outcome }
              - { term: Retainer milestone invoice, runtime_type: Artefact }
              - { term: Run the search workflow, runtime_type: Workflow }
              - { term: Shortlist quality score, runtime_type: Learning }
              - { term: Client (hiring board), runtime_type: Actor }
          - name: "Temporary & contract staffing desk"
            note: "Temp work agencies are regulated (e.g. UK Conduct Regulations / EAA; right-to-work and worker classification checks are mandatory)."
            operating_domains:
              - Worker availability pool
              - Open shifts and bookings from clients
              - Timesheet capture and approval
              - Pay and bill rate management
              - "Compliance docs (right-to-work, certs)"
              - "Worker no-show / backfill handling"
              - Margin per booking
              - Recurring rota / framework fulfilment
            vocabulary:
              - { term: Temp worker, runtime_type: Actor }
              - { term: Booking client, runtime_type: Actor }
              - { term: Shift / assignment, runtime_type: Object }
              - { term: Availability status, runtime_type: State }
              - { term: Shift filled, runtime_type: Event }
              - { term: Assign worker decision, runtime_type: Decision }
              - { term: Timesheet, runtime_type: Artefact }
              - { term: Timesheet approved, runtime_type: Event }
              - { term: Pay rate / bill rate, runtime_type: Object }
              - { term: "No-show", runtime_type: Event }
              - { term: "Right-to-work check", runtime_type: Artefact }
              - { term: Booking margin, runtime_type: Outcome }
              - { term: Fill the shift workflow, runtime_type: Workflow }
              - { term: "Fill rate / fulfilment %", runtime_type: Learning }
          - name: "RPO & talent sourcing services"
            operating_domains:
              - Embedded client hiring programmes
              - Sourcing campaigns and talent pools
              - "Employer-brand and outreach sequences"
              - "SLA and hiring-velocity dashboards"
              - Diversity slate tracking
              - Hiring manager intake and calibration
              - Candidate experience / NPS
              - "Cost-per-hire reporting"
            vocabulary:
              - { term: Hiring programme, runtime_type: Object }
              - { term: Sourcer, runtime_type: Actor }
              - { term: Hiring manager, runtime_type: Actor }
              - { term: Talent pool, runtime_type: Object }
              - { term: Outreach sequence, runtime_type: Workflow }
              - { term: Candidate replied, runtime_type: Event }
              - { term: Intake / calibration, runtime_type: Decision }
              - { term: Pipeline health status, runtime_type: State }
              - { term: Diversity slate, runtime_type: Artefact }
              - { term: Hire delivered, runtime_type: Outcome }
              - { term: SLA breach, runtime_type: Event }
              - { term: Intake brief, runtime_type: Artefact }
              - { term: "Cost-per-hire", runtime_type: Learning }
              - { term: Candidate NPS, runtime_type: Learning }
          - name: "Healthcare & locum recruitment"
            note: "Clinical recruitment is regulated (GMC/NMC registration, DBS, framework agency tiers, mandatory revalidation)."
            operating_domains:
              - Clinician credential and revalidation registry
              - Locum and bank shift fulfilment
              - Compliance pack expiry tracking
              - Framework / agency tier rates
              - Rota gaps across wards/practices
              - DBS and indemnity verification
              - Placement into NHS/private settings
              - Revalidation and appraisal dates
            vocabulary:
              - { term: Locum clinician, runtime_type: Actor }
              - { term: Trust / practice client, runtime_type: Actor }
              - { term: Locum shift, runtime_type: Object }
              - { term: Compliance pack, runtime_type: Artefact }
              - { term: Credential expiry status, runtime_type: State }
              - { term: DBS / indemnity check, runtime_type: Event }
              - { term: Clear to work decision, runtime_type: Decision }
              - { term: Shift confirmed, runtime_type: Event }
              - { term: Framework rate card, runtime_type: Object }
              - { term: Revalidation reminder, runtime_type: Event }
              - { term: Filled locum placement, runtime_type: Outcome }
              - { term: Compliance audit pass, runtime_type: Artefact }
              - { term: Vet and place workflow, runtime_type: Workflow }
              - { term: "Compliance currency %", runtime_type: Learning }
      - name: "n-hrOS"
        buyer: "HR directors / people-ops leaders and SMB owners who pay per employee/month to run the workforce lifecycle."
        os_test: "Buyer is the employer's HR function (not an agency), state model is the employee lifecycle and case management, vocabulary is contracts/leave/grievance/payroll — a repeatable industry of in-house people teams."
        sectors:
          - name: "Core HR & employee lifecycle"
            operating_domains:
              - Employee record / single source of truth
              - Org chart and reporting lines
              - Onboarding and offboarding journeys
              - "Job and pay-grade structure"
              - Position management / headcount plan
              - Document and contract storage
              - "Lifecycle change requests (promotion, transfer)"
              - Workforce reporting and analytics
            vocabulary:
              - { term: Employee record, runtime_type: Object }
              - { term: Employee, runtime_type: Actor }
              - { term: Line manager, runtime_type: Actor }
              - { term: Employment contract, runtime_type: Artefact }
              - { term: "Employment status (active/on-leave/leaver)", runtime_type: State }
              - { term: Onboarding task completed, runtime_type: Event }
              - { term: Approve change decision, runtime_type: Decision }
              - { term: Org chart, runtime_type: Object }
              - { term: Position / vacancy slot, runtime_type: Object }
              - { term: Promotion effective, runtime_type: Event }
              - { term: Leaver / exit, runtime_type: Outcome }
              - { term: Onboarding journey, runtime_type: Workflow }
              - { term: Headcount report, runtime_type: Artefact }
              - { term: Attrition rate, runtime_type: Learning }
          - name: "Payroll & benefits administration"
            note: "Payroll is regulated (HMRC RTI/PAYE reporting, statutory pension auto-enrolment, data-protection of pay data)."
            operating_domains:
              - Pay runs and cycles
              - "Gross-to-net calculation and deductions"
              - "Statutory filings (PAYE/RTI, tax)"
              - "Pension auto-enrolment"
              - Benefits enrolment and elections
              - Expense and reimbursement processing
              - Payslip distribution
              - "Year-end / P60 reporting"
            vocabulary:
              - { term: Pay run, runtime_type: Object }
              - { term: Payroll administrator, runtime_type: Actor }
              - { term: "Gross-to-net calculation", runtime_type: Workflow }
              - { term: Payslip, runtime_type: Artefact }
              - { term: Pay run status (draft/approved/paid), runtime_type: State }
              - { term: Approve pay run decision, runtime_type: Decision }
              - { term: RTI / statutory submission, runtime_type: Event }
              - { term: "Pension auto-enrolment", runtime_type: Event }
              - { term: Benefit election, runtime_type: Object }
              - { term: Deduction / earning line, runtime_type: Object }
              - { term: Payment disbursed, runtime_type: Outcome }
              - { term: "P60 / year-end document", runtime_type: Artefact }
              - { term: Payroll accuracy rate, runtime_type: Learning }
              - { term: Employee (payee), runtime_type: Actor }
          - name: "Time, attendance & leave"
            note: "Bound by working-time regulations and statutory leave entitlements (e.g. EU/UK Working Time Directive, statutory sick/holiday pay)."
            operating_domains:
              - "Working-time and shift schedules"
              - "Clock-in / clock-out capture"
              - Absence and leave balances
              - "Holiday and time-off requests"
              - Overtime and TOIL accrual
              - Sickness and statutory leave tracking
              - Rota coverage and gaps
              - "Working-time compliance limits"
            vocabulary:
              - { term: Timesheet, runtime_type: Artefact }
              - { term: Schedule / rota, runtime_type: Object }
              - { term: Employee, runtime_type: Actor }
              - { term: "Clock-in event", runtime_type: Event }
              - { term: Leave balance, runtime_type: Object }
              - { term: Leave request status (pending/approved), runtime_type: State }
              - { term: Approve leave decision, runtime_type: Decision }
              - { term: Absence recorded, runtime_type: Event }
              - { term: Overtime / TOIL accrual, runtime_type: Object }
              - { term: "Working-time breach", runtime_type: State }
              - { term: "Approved time-off", runtime_type: Outcome }
              - { term: "Request time-off workflow", runtime_type: Workflow }
              - { term: Absence (Bradford) factor, runtime_type: Learning }
              - { term: Coverage report, runtime_type: Artefact }
          - name: "Employee relations & case management"
            note: Disciplinary/grievance handling is governed by employment law (e.g. ACAS Code in the UK); mishandling creates tribunal liability.
            operating_domains:
              - Grievance and disciplinary cases
              - Investigation files and evidence
              - Hearing and outcome tracking
              - Performance improvement plans
              - Sickness/absence management cases
              - Tribunal and dispute risk
              - Policy and acknowledgement records
              - Case SLA and escalation
            vocabulary:
              - { term: ER case, runtime_type: Object }
              - { term: Employee (subject), runtime_type: Actor }
              - { term: Case manager / HRBP, runtime_type: Actor }
              - { term: Grievance raised, runtime_type: Event }
              - { term: Case stage (open/investigation/hearing), runtime_type: State }
              - { term: Investigation report, runtime_type: Artefact }
              - { term: Disciplinary outcome decision, runtime_type: Decision }
              - { term: Hearing scheduled, runtime_type: Event }
              - { term: PIP / improvement plan, runtime_type: Object }
              - { term: Sanction / outcome letter, runtime_type: Artefact }
              - { term: Case resolved, runtime_type: Outcome }
              - { term: Run the case workflow, runtime_type: Workflow }
              - { term: Tribunal risk flag, runtime_type: State }
              - { term: "Time-to-resolution", runtime_type: Learning }
          - name: "Performance & reviews"
            operating_domains:
              - Goal / OKR setting and cascade
              - Review cycles and calibration
              - "Continuous feedback and check-ins"
              - "360 / multi-rater feedback"
              - Rating and distribution curves
              - "Succession and talent grids (9-box)"
              - Compensation review linkage
              - Manager and team analytics
            vocabulary:
              - { term: Goal / OKR, runtime_type: Object }
              - { term: Reviewee, runtime_type: Actor }
              - { term: Reviewer / manager, runtime_type: Actor }
              - { term: Review cycle, runtime_type: Workflow }
              - { term: "Check-in submitted", runtime_type: Event }
              - { term: Review status (not started/in review/closed), runtime_type: State }
              - { term: Calibration decision, runtime_type: Decision }
              - { term: 360 feedback form, runtime_type: Artefact }
              - { term: Performance rating, runtime_type: Outcome }
              - { term: "9-box / talent grid", runtime_type: Object }
              - { term: Review signed off, runtime_type: Event }
              - { term: Engagement / eNPS score, runtime_type: Learning }
              - { term: "Goal-attainment rate", runtime_type: Learning }
              - { term: Calibration summary, runtime_type: Artefact }
      - name: "n-staffingOS"
        buyer: "Workforce / VMS managers and shift-based employers (retail, hospitality, logistics, gig platforms) who pay to fill and manage deployed labour at scale."
        os_test: "Buyer manages deployed/contingent labour at scale (not lifecycle HR, not placement fees); state model is shift supply-and-demand and deployment; vocabulary is requisition/VMS/deployment/utilisation — distinct repeatable industry of workforce ops."
        sectors:
          - name: "Shift scheduling & deployment"
            operating_domains:
              - "Demand forecast per site/day-part"
              - Shift templates and patterns
              - "Open-shift marketplace and bidding"
              - Worker eligibility and skills matching
              - "Swap, drop and cover requests"
              - "Real-time roster and call-offs"
              - "Labour-budget vs actual hours"
              - "Site-level coverage compliance"
            vocabulary:
              - { term: Shift, runtime_type: Object }
              - { term: Shift worker, runtime_type: Actor }
              - { term: Scheduling manager, runtime_type: Actor }
              - { term: Demand forecast, runtime_type: Object }
              - { term: Open shift published, runtime_type: Event }
              - { term: Shift state (open/claimed/covered), runtime_type: State }
              - { term: Assign / publish decision, runtime_type: Decision }
              - { term: Swap request, runtime_type: Event }
              - { term: Roster / schedule, runtime_type: Artefact }
              - { term: Build the rota workflow, runtime_type: Workflow }
              - { term: Coverage achieved, runtime_type: Outcome }
              - { term: Understaffing alert, runtime_type: State }
              - { term: "Schedule-adherence %", runtime_type: Learning }
              - { term: Labour cost vs budget, runtime_type: Learning }
          - name: Contingent workforce / VMS
            note: "Contingent labour carries co-employment and worker-classification risk (e.g. IR35/AB5-style rules); tenure limits are compliance-driven."
            operating_domains:
              - Worker requisitions to suppliers
              - Supplier / agency tiers and distribution
              - Candidate submittal and selection
              - "Rate cards and rate-card compliance"
              - "Statement-of-work engagements"
              - "Tenure and co-employment limits"
              - Spend and savings tracking
              - Onboarding/offboarding of contingent staff
            vocabulary:
              - { term: Worker requisition, runtime_type: Object }
              - { term: Contingent worker, runtime_type: Actor }
              - { term: Supplier / staffing agency, runtime_type: Actor }
              - { term: Submittal received, runtime_type: Event }
              - { term: Requisition state (open/filled/closed), runtime_type: State }
              - { term: Select candidate decision, runtime_type: Decision }
              - { term: Rate card, runtime_type: Object }
              - { term: Statement of work (SOW), runtime_type: Artefact }
              - { term: Worker engaged / started, runtime_type: Event }
              - { term: "Tenure / co-employment limit", runtime_type: State }
              - { term: Filled engagement, runtime_type: Outcome }
              - { term: Distribute requisition workflow, runtime_type: Workflow }
              - { term: Realised savings, runtime_type: Learning }
              - { term: "Time-to-submit", runtime_type: Learning }
          - name: "Gig & on-demand workforce"
            note: "Gig models face worker-classification and minimum-wage regulation (e.g. platform-work directives, AB5/IR35-style tests)."
            operating_domains:
              - Job / task offers to the pool
              - "Worker availability and geo-matching"
              - Accept / claim flow and surge pricing
              - "In-task tracking and proof-of-completion"
              - Ratings and reliability scores
              - "Instant / earned-wage payouts"
              - Worker tier and access gating
              - Dispute and reassignment handling
            vocabulary:
              - { term: Gig / task offer, runtime_type: Object }
              - { term: Gig worker, runtime_type: Actor }
              - { term: Requester / platform, runtime_type: Actor }
              - { term: Offer accepted, runtime_type: Event }
              - { term: Task state (offered/active/done), runtime_type: State }
              - { term: Accept gig decision, runtime_type: Decision }
              - { term: Proof of completion, runtime_type: Artefact }
              - { term: Task completed, runtime_type: Event }
              - { term: Reliability / rating score, runtime_type: Learning }
              - { term: Worker tier, runtime_type: State }
              - { term: Instant payout, runtime_type: Outcome }
              - { term: "Claim-and-complete workflow", runtime_type: Workflow }
              - { term: Dispute raised, runtime_type: Event }
              - { term: Earnings statement, runtime_type: Artefact }
          - name: "Field & frontline workforce management"
            note: "Field work is bound by lone-worker safety duties and sector certification (e.g. Gas Safe, electrical, working-at-height)."
            operating_domains:
              - Job dispatch to mobile workers
              - Route and territory optimisation
              - "Skills, certs and asset matching"
              - "On-site check-in / geofencing"
              - "Work-order completion and signoff"
              - Parts/asset consumption
              - "SLA and response-time tracking"
              - "Lone-worker safety monitoring"
            vocabulary:
              - { term: Work order / job, runtime_type: Object }
              - { term: Field worker / technician, runtime_type: Actor }
              - { term: Dispatcher, runtime_type: Actor }
              - { term: Job dispatched, runtime_type: Event }
              - { term: "Job state (assigned/en-route/onsite/done)", runtime_type: State }
              - { term: Dispatch / route decision, runtime_type: Decision }
              - { term: "On-site check-in", runtime_type: Event }
              - { term: Completion certificate, runtime_type: Artefact }
              - { term: Job completed, runtime_type: Outcome }
              - { term: "Dispatch-and-complete workflow", runtime_type: Workflow }
              - { term: SLA breach, runtime_type: State }
              - { term: "First-time-fix rate", runtime_type: Learning }
              - { term: "Lone-worker check", runtime_type: Object }
              - { term: Mobile technician (asset), runtime_type: Object }
          - name: "Workforce compliance & credentialing"
            note: "Credentialing enforces statutory checks (right-to-work, DBS/background screening, sector licensing) with audit obligations."
            operating_domains:
              - "Worker eligibility and right-to-work"
              - Certification and licence registry
              - Expiry and renewal tracking
              - Background and screening checks
              - Training currency requirements
              - Audit packs and evidence
              - "Block / suspend on non-compliance"
              - Regulator reporting
            vocabulary:
              - { term: Worker credential profile, runtime_type: Object }
              - { term: Worker, runtime_type: Actor }
              - { term: Compliance officer, runtime_type: Actor }
              - { term: Certificate / licence, runtime_type: Artefact }
              - { term: Compliance state (clear/expiring/blocked), runtime_type: State }
              - { term: Check submitted, runtime_type: Event }
              - { term: "Clear-to-deploy decision", runtime_type: Decision }
              - { term: Renewal due reminder, runtime_type: Event }
              - { term: Background screen result, runtime_type: Artefact }
              - { term: Verified compliant worker, runtime_type: Outcome }
              - { term: "Vet-and-clear workflow", runtime_type: Workflow }
              - { term: Suspension applied, runtime_type: Event }
              - { term: Compliance currency rate, runtime_type: Learning }
              - { term: Audit pack, runtime_type: Artefact }
      - name: "n-learningOS"
        buyer: "L&D / talent-development leaders, training providers and compliance managers who pay per learner to build skills and prove training."
        os_test: "Buyer is L&D/training (not HR ops or recruiting); state model is enrolment-to-mastery and competency; vocabulary is course/SCORM/credential/competency — a repeatable industry of learning teams and training businesses."
        sectors:
          - name: "Corporate L&D / LMS"
            operating_domains:
              - Course catalogue and learning paths
              - Enrolment and assignment rules
              - Content (SCORM/xAPI) delivery
              - Progress and completion tracking
              - Assessments and pass marks
              - "Manager-assigned training"
              - "Skills-gap mapping"
              - Learning analytics and reporting
            vocabulary:
              - { term: Course, runtime_type: Object }
              - { term: Learner, runtime_type: Actor }
              - { term: "L&D administrator", runtime_type: Actor }
              - { term: Learning path, runtime_type: Object }
              - { term: Enrolment created, runtime_type: Event }
              - { term: Progress state (not started/in progress/complete), runtime_type: State }
              - { term: Assign training decision, runtime_type: Decision }
              - { term: Assessment / quiz, runtime_type: Artefact }
              - { term: Module completed, runtime_type: Event }
              - { term: Course completion, runtime_type: Outcome }
              - { term: "Complete-the-path workflow", runtime_type: Workflow }
              - { term: Certificate of completion, runtime_type: Artefact }
              - { term: Completion rate, runtime_type: Learning }
              - { term: "Skills-gap insight", runtime_type: Learning }
          - name: "Compliance & mandatory training"
            note: "Mandatory training satisfies legal/sector duties (e.g. health & safety, safeguarding, AML/financial-services CPD) with audit requirements."
            operating_domains:
              - Mandatory course matrix by role
              - Recurring renewal cycles
              - Due / overdue tracking
              - "Attestations and sign-offs"
              - Policy acknowledgements
              - "Audit-ready evidence trails"
              - "Escalation on non-completion"
              - Regulator / inspection reporting
            vocabulary:
              - { term: Mandatory course, runtime_type: Object }
              - { term: Employee (learner), runtime_type: Actor }
              - { term: Compliance lead, runtime_type: Actor }
              - { term: Training matrix, runtime_type: Object }
              - { term: Training assigned, runtime_type: Event }
              - { term: Compliance state (current/due/overdue), runtime_type: State }
              - { term: "Sign-off / attestation decision", runtime_type: Decision }
              - { term: Completion record, runtime_type: Artefact }
              - { term: Renewal due, runtime_type: Event }
              - { term: Verified compliant, runtime_type: Outcome }
              - { term: "Renew-and-attest workflow", runtime_type: Workflow }
              - { term: Escalation raised, runtime_type: Event }
              - { term: "Compliance completion %", runtime_type: Learning }
              - { term: Audit evidence pack, runtime_type: Artefact }
          - name: "Apprenticeships & vocational training"
            note: "Apprenticeships are regulated and funded (e.g. ESFA/IfATE standards, levy rules, Ofsted inspection, mandatory EPA)."
            operating_domains:
              - Apprenticeship standards and frameworks
              - Learner cohorts and start dates
              - "On-/off-the-job training hours log"
              - Portfolio of evidence
              - Progress reviews (tripartite)
              - "End-point assessment gateway"
              - Funding and levy drawdown
              - Achievement and dropout tracking
            vocabulary:
              - { term: Apprenticeship standard, runtime_type: Object }
              - { term: Apprentice, runtime_type: Actor }
              - { term: Training provider / coach, runtime_type: Actor }
              - { term: "Off-the-job hours log", runtime_type: Object }
              - { term: Progress review held, runtime_type: Event }
              - { term: "Learner state (on-programme/gateway/EPA)", runtime_type: State }
              - { term: "Gateway-ready decision", runtime_type: Decision }
              - { term: Portfolio of evidence, runtime_type: Artefact }
              - { term: "End-point assessment", runtime_type: Event }
              - { term: Achievement / completion, runtime_type: Outcome }
              - { term: "Deliver-the-standard workflow", runtime_type: Workflow }
              - { term: Funding / levy claim, runtime_type: Artefact }
              - { term: Achievement rate, runtime_type: Learning }
              - { term: "Funding-rules client / employer", runtime_type: Actor }
          - name: "Certification & continuing professional development (CPD)"
            note: "Certification bodies operate under accreditation and awarding-body rules (e.g. Ofqual, ISO/IEC 17024) governing exam integrity and revocation."
            operating_domains:
              - Credential and qualification catalogue
              - CPD point / credit accrual
              - Exam booking and proctoring
              - Digital badge / credential issuance
              - Recertification cycles
              - Member / candidate registry
              - Revocation and verification
              - "Awarding-body reporting"
            vocabulary:
              - { term: Credential / qualification, runtime_type: Object }
              - { term: Candidate / member, runtime_type: Actor }
              - { term: Awarding body / assessor, runtime_type: Actor }
              - { term: CPD record, runtime_type: Object }
              - { term: Exam sat, runtime_type: Event }
              - { term: Credential state (active/lapsed/revoked), runtime_type: State }
              - { term: Award credential decision, runtime_type: Decision }
              - { term: Digital badge / certificate, runtime_type: Artefact }
              - { term: Recertification due, runtime_type: Event }
              - { term: Certified professional, runtime_type: Outcome }
              - { term: "Certify-and-renew workflow", runtime_type: Workflow }
              - { term: Verification request, runtime_type: Event }
              - { term: Pass rate, runtime_type: Learning }
              - { term: CPD credits earned, runtime_type: Learning }
          - name: "Skills & talent development"
            operating_domains:
              - Skills taxonomy and inventory
              - Self / manager skill assessments
              - Personal development plans
              - Mentoring and coaching matches
              - Internal mobility / gig marketplace
              - "Career-path and role mapping"
              - "Capability-gap analytics"
              - Reskilling programme tracking
            vocabulary:
              - { term: Skill, runtime_type: Object }
              - { term: Employee (talent), runtime_type: Actor }
              - { term: Mentor / coach, runtime_type: Actor }
              - { term: Skills inventory, runtime_type: Object }
              - { term: Skill assessed, runtime_type: Event }
              - { term: Proficiency state (novice→expert), runtime_type: State }
              - { term: Recommend development decision, runtime_type: Decision }
              - { term: Development plan (PDP), runtime_type: Artefact }
              - { term: Mentoring match made, runtime_type: Event }
              - { term: Capability uplift, runtime_type: Outcome }
              - { term: "Grow-the-skill workflow", runtime_type: Workflow }
              - { term: Internal mobility move, runtime_type: Event }
              - { term: "Skills-coverage index", runtime_type: Learning }
              - { term: "Time-to-proficiency", runtime_type: Learning }
  - name: Education
    os:
      - name: "n-eduOS"
        buyer: "K-12 schools, multi-academy trusts and districts — paid for by the school/district administration budget."
        os_test: "Distinct buyer (head/principal/district), statutory compliance state model (attendance, safeguarding, special-needs plans) and a daily-operations vocabulary no other OS shares — repeatable across tens of thousands of schools."
        sectors:
          - name: "Primary & Secondary School Operations"
            note: "Statutory attendance returns and safeguarding/child-protection duties are legally mandated (e.g. KCSIE in England)."
            operating_domains:
              - Daily attendance and absence registers
              - Timetable and room/teacher allocation
              - Pupil records and pastoral notes
              - Parent communications and consent
              - Behaviour and rewards tracking
              - Internal assessment and report cards
              - "Safeguarding referrals and child-protection logs"
            vocabulary:
              - { term: Pupil, runtime_type: Actor }
              - { term: Teacher, runtime_type: Actor }
              - { term: Class group / form, runtime_type: Object }
              - { term: Timetable, runtime_type: Object }
              - { term: Lesson period, runtime_type: Event }
              - { term: Register taken, runtime_type: Event }
              - { term: Marked present / absent, runtime_type: State }
              - { term: Detention issued, runtime_type: Decision }
              - { term: Safeguarding referral, runtime_type: Workflow }
              - { term: Report card, runtime_type: Artefact }
              - { term: Parental consent form, runtime_type: Artefact }
              - { term: "End-of-year promotion", runtime_type: Outcome }
              - { term: Attendance rate, runtime_type: Learning }
              - { term: Behaviour point, runtime_type: Object }
              - { term: Pastoral note, runtime_type: Artefact }
          - name: "Special Educational Needs & Inclusion"
            note: EHCP / IEP processes and statutory annual reviews are legally regulated provision for disabled learners.
            operating_domains:
              - Individual education / support plans
              - EHCP / IEP statutory reviews
              - Specialist intervention scheduling
              - "Teaching-assistant deployment"
              - "Accessibility and exam-access arrangements"
              - Annual review meetings with parents
              - Funding and provision mapping
            vocabulary:
              - { term: Learner with SEND, runtime_type: Actor }
              - { term: SENCo (coordinator), runtime_type: Actor }
              - { term: "Education, Health & Care Plan", runtime_type: Artefact }
              - { term: Provision map, runtime_type: Object }
              - { term: Intervention session, runtime_type: Event }
              - { term: On the SEN register, runtime_type: State }
              - { term: "Plan-do-review cycle", runtime_type: Workflow }
              - { term: Annual review held, runtime_type: Event }
              - { term: "Exam-access arrangement granted", runtime_type: Decision }
              - { term: Funding band assigned, runtime_type: Decision }
              - { term: Target met, runtime_type: Outcome }
              - { term: Progress against target, runtime_type: Learning }
              - { term: Support plan, runtime_type: Artefact }
              - { term: Specialist referral, runtime_type: Workflow }
          - name: "School Admissions & Enrolment"
            note: School admissions follow a statutory admissions code with a legal appeals process.
            operating_domains:
              - "Open-day and prospectus enquiries"
              - Application intake and waitlists
              - Catchment and oversubscription criteria
              - Offer and acceptance management
              - Appeals handling
              - "In-year and mid-term transfers"
              - "Roll-forward / census reconciliation"
            vocabulary:
              - { term: Applicant family, runtime_type: Actor }
              - { term: Admissions officer, runtime_type: Actor }
              - { term: Application, runtime_type: Object }
              - { term: Waitlist, runtime_type: Object }
              - { term: Offer made, runtime_type: Event }
              - { term: Place accepted, runtime_type: State }
              - { term: Oversubscription criteria applied, runtime_type: Decision }
              - { term: Appeal lodged, runtime_type: Workflow }
              - { term: Offer letter, runtime_type: Artefact }
              - { term: Enrolled on roll, runtime_type: Outcome }
              - { term: Fill rate, runtime_type: Learning }
              - { term: Catchment boundary, runtime_type: Object }
              - { term: "In-year transfer", runtime_type: Event }
              - { term: Census record, runtime_type: Artefact }
          - name: "Curriculum & Lesson Planning"
            operating_domains:
              - "Scheme-of-work design"
              - Lesson plan authoring and sharing
              - "Learning-objective and standards mapping"
              - Resource and worksheet libraries
              - Differentiation for ability groups
              - "Cross-class moderation"
              - Curriculum coverage tracking
            vocabulary:
              - { term: Subject lead, runtime_type: Actor }
              - { term: Scheme of work, runtime_type: Object }
              - { term: Lesson plan, runtime_type: Artefact }
              - { term: Learning objective, runtime_type: Object }
              - { term: Curriculum standard, runtime_type: Object }
              - { term: Lesson delivered, runtime_type: Event }
              - { term: Plan published, runtime_type: State }
              - { term: Differentiation choice, runtime_type: Decision }
              - { term: Moderation review, runtime_type: Workflow }
              - { term: Resource pack, runtime_type: Artefact }
              - { term: Coverage complete, runtime_type: Outcome }
              - { term: Coverage gap, runtime_type: Learning }
              - { term: Knowledge organiser, runtime_type: Artefact }
              - { term: Pacing guide, runtime_type: Object }
          - name: "Parent Engagement & Communications"
            operating_domains:
              - Announcements and newsletters
              - "Parents' evening / conference booking"
              - Permission slips and trip consent
              - "Fee, lunch and club payments"
              - Absence reporting by parents
              - "Two-way messaging and translation"
              - "Home-school agreement tracking"
            vocabulary:
              - { term: Parent / carer, runtime_type: Actor }
              - { term: School office, runtime_type: Actor }
              - { term: Message thread, runtime_type: Object }
              - { term: Newsletter, runtime_type: Artefact }
              - { term: Message sent, runtime_type: Event }
              - { term: Read receipt, runtime_type: State }
              - { term: "Parents' evening slot booked", runtime_type: Event }
              - { term: Consent given, runtime_type: Decision }
              - { term: Permission slip, runtime_type: Artefact }
              - { term: Trip payment workflow, runtime_type: Workflow }
              - { term: Payment collected, runtime_type: Outcome }
              - { term: Engagement rate, runtime_type: Learning }
              - { term: Absence report, runtime_type: Event }
              - { term: "Home-school agreement", runtime_type: Artefact }
          - name: "School Finance & Operations"
            note: "Publicly-funded schools must file statutory financial returns and grant-spend declarations."
            operating_domains:
              - Budget setting and forecasting
              - "Pupil-premium / grant tracking"
              - Procurement and purchase orders
              - "Catering and free-school-meal eligibility"
              - Facilities and maintenance requests
              - Staff cover and supply booking
              - Statutory financial returns
            vocabulary:
              - { term: Business manager, runtime_type: Actor }
              - { term: Budget line, runtime_type: Object }
              - { term: Purchase order, runtime_type: Artefact }
              - { term: Grant fund, runtime_type: Object }
              - { term: Order approved, runtime_type: Decision }
              - { term: Invoice received, runtime_type: Event }
              - { term: Within budget, runtime_type: State }
              - { term: "Cover-booking workflow", runtime_type: Workflow }
              - { term: Supply teacher booked, runtime_type: Event }
              - { term: Maintenance ticket, runtime_type: Object }
              - { term: "Year-end accounts", runtime_type: Artefact }
              - { term: Balanced budget, runtime_type: Outcome }
              - { term: Spend per pupil, runtime_type: Learning }
              - { term: "Free-school-meal eligibility", runtime_type: State }
      - name: "n-universityOS"
        buyer: "Universities and higher-education colleges — paid for by the registrar's / provost's institutional systems budget."
        os_test: "Own buyer (registrar, provost, dean), a credit-and-degree-progression state model unique to HE, research-grant and student-lifecycle workflows, and vocabulary (modules, credits, awards, tenure) absent elsewhere — repeatable across thousands of institutions."
        sectors:
          - name: "Student Lifecycle & Registry"
            note: "Awarding degrees is a regulated activity tied to degree-awarding-powers and statutory data returns (HESA / IPEDS)."
            operating_domains:
              - Course and module enrolment
              - Credit accumulation and progression
              - "Programme-of-study management"
              - "Withdrawal, suspension and reinstatement"
              - Transcript and award production
              - Graduation and conferral
              - "Statutory student-data returns"
            vocabulary:
              - { term: Student, runtime_type: Actor }
              - { term: Registrar, runtime_type: Actor }
              - { term: Module, runtime_type: Object }
              - { term: Programme of study, runtime_type: Object }
              - { term: Credit, runtime_type: Object }
              - { term: Enrolment confirmed, runtime_type: Event }
              - { term: Good standing, runtime_type: State }
              - { term: Progression decision, runtime_type: Decision }
              - { term: "Suspend-and-reinstate workflow", runtime_type: Workflow }
              - { term: Transcript, runtime_type: Artefact }
              - { term: Degree conferred, runtime_type: Outcome }
              - { term: Continuation rate, runtime_type: Learning }
              - { term: Award classification, runtime_type: Decision }
              - { term: Diploma certificate, runtime_type: Artefact }
          - name: "Admissions & Recruitment"
            note: "International recruitment requires licensed visa sponsorship and immigration-compliance reporting."
            operating_domains:
              - Applicant funnel and CRM
              - "Entry-requirement and offer rules"
              - Clearing / waitlist management
              - International student visa sponsorship
              - Scholarship and bursary allocation
              - Deposit and acceptance tracking
              - Yield and conversion analytics
            vocabulary:
              - { term: Applicant, runtime_type: Actor }
              - { term: Admissions tutor, runtime_type: Actor }
              - { term: Application, runtime_type: Object }
              - { term: Offer made, runtime_type: Event }
              - { term: Conditional offer, runtime_type: State }
              - { term: "Offer-decision workflow", runtime_type: Workflow }
              - { term: Scholarship awarded, runtime_type: Decision }
              - { term: Visa sponsorship (CAS), runtime_type: Artefact }
              - { term: Deposit paid, runtime_type: Event }
              - { term: Place confirmed, runtime_type: Outcome }
              - { term: Conversion rate, runtime_type: Learning }
              - { term: Entry tariff, runtime_type: Object }
              - { term: Clearing place, runtime_type: Object }
              - { term: Bursary letter, runtime_type: Artefact }
          - name: "Research Administration & Grants"
            note: "Human-subjects research requires ethics/IRB approval and funder-mandated integrity compliance."
            operating_domains:
              - "Funding-call discovery"
              - Grant proposal and costing
              - Award setup and budget management
              - Ethics and integrity approval
              - Research outputs and publications
              - Ethics / IRB review
              - Impact and assessment submissions
            vocabulary:
              - { term: Principal investigator, runtime_type: Actor }
              - { term: Research office, runtime_type: Actor }
              - { term: Funding call, runtime_type: Object }
              - { term: Grant proposal, runtime_type: Artefact }
              - { term: Proposal submitted, runtime_type: Event }
              - { term: Award active, runtime_type: State }
              - { term: "Ethics-approval workflow", runtime_type: Workflow }
              - { term: Ethics approval granted, runtime_type: Decision }
              - { term: Grant budget, runtime_type: Object }
              - { term: Publication, runtime_type: Artefact }
              - { term: Grant awarded, runtime_type: Outcome }
              - { term: Citation / impact score, runtime_type: Learning }
              - { term: Milestone report, runtime_type: Artefact }
              - { term: "Spend-down decision", runtime_type: Decision }
          - name: "Academic Quality & Assessment"
            note: "Assessment and award standards are governed by quality-assurance regulators (e.g. QAA / OfS, accreditation bodies)."
            operating_domains:
              - Exam scheduling and venues
              - Coursework submission and marking
              - "Plagiarism / academic-integrity checks"
              - "Exam-board moderation"
              - "External examiner sign-off"
              - "Mitigating-circumstances handling"
              - Programme review and validation
            vocabulary:
              - { term: Examiner, runtime_type: Actor }
              - { term: External examiner, runtime_type: Actor }
              - { term: Assessment, runtime_type: Object }
              - { term: Submission, runtime_type: Artefact }
              - { term: Work submitted, runtime_type: Event }
              - { term: Under moderation, runtime_type: State }
              - { term: "Exam-board workflow", runtime_type: Workflow }
              - { term: Mark ratified, runtime_type: Decision }
              - { term: "Academic-integrity flag", runtime_type: Event }
              - { term: Mitigating circumstances granted, runtime_type: Decision }
              - { term: Final grade, runtime_type: Outcome }
              - { term: Pass rate, runtime_type: Learning }
              - { term: "Exam-board minutes", runtime_type: Artefact }
              - { term: Module rubric, runtime_type: Object }
          - name: "Faculty & Academic HR"
            operating_domains:
              - Workload and teaching allocation
              - Tenure / promotion cases
              - Sabbatical and leave planning
              - Probation and review
              - Appointment and contract management
              - Peer teaching observation
              - Academic performance review
            vocabulary:
              - { term: Academic staff member, runtime_type: Actor }
              - { term: Dean / head of department, runtime_type: Actor }
              - { term: Workload model, runtime_type: Object }
              - { term: Teaching allocation, runtime_type: Object }
              - { term: Promotion case submitted, runtime_type: Event }
              - { term: On probation, runtime_type: State }
              - { term: "Tenure-review workflow", runtime_type: Workflow }
              - { term: Promotion decision, runtime_type: Decision }
              - { term: Sabbatical approved, runtime_type: Decision }
              - { term: Appointment contract, runtime_type: Artefact }
              - { term: Tenure granted, runtime_type: Outcome }
              - { term: Teaching evaluation score, runtime_type: Learning }
              - { term: Observation report, runtime_type: Artefact }
              - { term: Workload balance, runtime_type: State }
          - name: "Student Support & Wellbeing"
            note: "Disability support and student conduct processes carry statutory duty-of-care and equality obligations."
            operating_domains:
              - Counselling and wellbeing appointments
              - Disability and accessibility support
              - Academic advising / tutoring
              - "At-risk early-warning monitoring"
              - Hardship and welfare funds
              - Conduct and disciplinary cases
              - Retention interventions
            vocabulary:
              - { term: Student, runtime_type: Actor }
              - { term: Wellbeing adviser, runtime_type: Actor }
              - { term: Support case, runtime_type: Object }
              - { term: Appointment, runtime_type: Object }
              - { term: Appointment booked, runtime_type: Event }
              - { term: "Flagged at-risk", runtime_type: State }
              - { term: Disability support plan, runtime_type: Artefact }
              - { term: Referral workflow, runtime_type: Workflow }
              - { term: Intervention decision, runtime_type: Decision }
              - { term: Hardship fund granted, runtime_type: Decision }
              - { term: Student retained, runtime_type: Outcome }
              - { term: Engagement / risk score, runtime_type: Learning }
              - { term: Case note, runtime_type: Artefact }
              - { term: Conduct hearing, runtime_type: Event }
      - name: "n-trainingOS"
        buyer: "Corporate L&D teams, vocational training providers and bootcamps — paid for by the learning-and-development or commercial-training budget."
        os_test: "Distinct buyer (CLO / training-provider owner), a competency-and-completion state model rather than degrees, cohort/booking commerce workflows, and vocabulary (course, cohort, seat, completion) unlike school or degree systems — repeatable across the corporate-learning and vocational market."
        sectors:
          - name: "Corporate Learning & Development"
            operating_domains:
              - Course catalogue and assignment
              - Mandatory training campaigns
              - Skill / competency frameworks
              - Learning paths and curricula
              - "Manager-team learning dashboards"
              - Content authoring and updates
              - Completion and compliance reporting
            vocabulary:
              - { term: Learner / employee, runtime_type: Actor }
              - { term: "L&D administrator", runtime_type: Actor }
              - { term: Course, runtime_type: Object }
              - { term: Learning path, runtime_type: Object }
              - { term: Course assigned, runtime_type: Event }
              - { term: In progress, runtime_type: State }
              - { term: Enrolment workflow, runtime_type: Workflow }
              - { term: Skill gap flagged, runtime_type: Decision }
              - { term: Competency, runtime_type: Object }
              - { term: Course completed, runtime_type: Outcome }
              - { term: Completion rate, runtime_type: Learning }
              - { term: Completion certificate, runtime_type: Artefact }
              - { term: Course content / module, runtime_type: Artefact }
              - { term: "Due-date breached", runtime_type: State }
          - name: "Compliance & Mandatory Training"
            note: "Tracks legally-mandated training (health-and-safety, AML, data-protection) where non-compliance carries regulatory penalty."
            operating_domains:
              - Regulatory training requirements
              - Renewal and expiry tracking
              - "Role-based training matrices"
              - "Audit-evidence collection"
              - "Attestation and sign-off"
              - Escalation for overdue training
              - Regulator reporting packs
            vocabulary:
              - { term: Regulated worker, runtime_type: Actor }
              - { term: Compliance officer, runtime_type: Actor }
              - { term: Training requirement, runtime_type: Object }
              - { term: Training matrix, runtime_type: Object }
              - { term: Training assigned, runtime_type: Event }
              - { term: Compliant, runtime_type: State }
              - { term: Expired / lapsed, runtime_type: State }
              - { term: Renewal workflow, runtime_type: Workflow }
              - { term: Attestation signed, runtime_type: Decision }
              - { term: Audit evidence pack, runtime_type: Artefact }
              - { term: Certificate of completion, runtime_type: Artefact }
              - { term: Fully compliant workforce, runtime_type: Outcome }
              - { term: Compliance rate, runtime_type: Learning }
              - { term: Overdue escalation, runtime_type: Event }
          - name: "Vocational & Apprenticeship Training"
            note: "Apprenticeships are government-funded and regulated (e.g. ESFA / Ofsted), with mandated end-point assessment and funding rules."
            operating_domains:
              - Apprenticeship standards and frameworks
              - "On-the-job / off-the-job hours logging"
              - Portfolio of evidence building
              - Workplace assessor visits
              - "Functional-skills delivery"
              - "Gateway and end-point assessment"
              - Funding and levy claims
            vocabulary:
              - { term: Apprentice, runtime_type: Actor }
              - { term: Assessor / coach, runtime_type: Actor }
              - { term: Apprenticeship standard, runtime_type: Object }
              - { term: Evidence portfolio, runtime_type: Object }
              - { term: Assessor visit, runtime_type: Event }
              - { term: "Off-the-job hours", runtime_type: Object }
              - { term: On programme, runtime_type: State }
              - { term: Gateway workflow, runtime_type: Workflow }
              - { term: Gateway decision, runtime_type: Decision }
              - { term: "End-point assessment", runtime_type: Event }
              - { term: Apprenticeship achieved, runtime_type: Outcome }
              - { term: Achievement rate, runtime_type: Learning }
              - { term: Learning agreement, runtime_type: Artefact }
              - { term: Levy claim, runtime_type: Artefact }
          - name: "Coding Bootcamps & Cohort Programmes"
            note: "Income-share / deferred-tuition financing is a regulated consumer-credit product in many jurisdictions."
            operating_domains:
              - Cohort scheduling and capacity
              - Project and assignment grading
              - Mentor and instructor allocation
              - "Career-services and placement"
              - "Income-share / financing agreements"
              - "Capstone and demo-day delivery"
              - "Outcomes / job-placement reporting"
            vocabulary:
              - { term: Bootcamp student, runtime_type: Actor }
              - { term: Instructor / mentor, runtime_type: Actor }
              - { term: Cohort, runtime_type: Object }
              - { term: Sprint / project, runtime_type: Object }
              - { term: Project submitted, runtime_type: Event }
              - { term: Active in cohort, runtime_type: State }
              - { term: "Capstone-review workflow", runtime_type: Workflow }
              - { term: Graduation decision, runtime_type: Decision }
              - { term: "Income-share agreement", runtime_type: Artefact }
              - { term: Capstone project, runtime_type: Artefact }
              - { term: Job placement, runtime_type: Outcome }
              - { term: Placement rate, runtime_type: Learning }
              - { term: Demo day, runtime_type: Event }
              - { term: Graduated, runtime_type: State }
          - name: Online Course Marketplace (Creator)
            operating_domains:
              - Course publishing and pricing
              - Lesson and module authoring
              - Student enrolment and access
              - Reviews and ratings
              - Promotions and coupons
              - Payouts and revenue share
              - "Engagement and drop-off analytics"
            vocabulary:
              - { term: Course creator, runtime_type: Actor }
              - { term: Enrolled learner, runtime_type: Actor }
              - { term: Course listing, runtime_type: Object }
              - { term: Lesson / video, runtime_type: Artefact }
              - { term: Purchase / enrolment, runtime_type: Event }
              - { term: Published, runtime_type: State }
              - { term: Coupon issued, runtime_type: Decision }
              - { term: Payout workflow, runtime_type: Workflow }
              - { term: Review left, runtime_type: Event }
              - { term: Certificate of completion, runtime_type: Artefact }
              - { term: Revenue earned, runtime_type: Outcome }
              - { term: Completion / watch rate, runtime_type: Learning }
              - { term: Coupon code, runtime_type: Object }
              - { term: Refund requested, runtime_type: Event }
          - name: "Instructor-Led & Classroom Training Operations"
            operating_domains:
              - Scheduled class and session booking
              - Seat and waitlist management
              - Trainer and venue allocation
              - Joining instructions and logistics
              - Materials and kit distribution
              - "Attendance and sign-in sheets"
              - "Post-course evaluation"
            vocabulary:
              - { term: Delegate, runtime_type: Actor }
              - { term: Trainer, runtime_type: Actor }
              - { term: Scheduled session, runtime_type: Object }
              - { term: Seat, runtime_type: Object }
              - { term: Booking placed, runtime_type: Event }
              - { term: Confirmed / waitlisted, runtime_type: State }
              - { term: "Booking-and-allocation workflow", runtime_type: Workflow }
              - { term: Venue assigned, runtime_type: Decision }
              - { term: Joining instructions, runtime_type: Artefact }
              - { term: Attended, runtime_type: Outcome }
              - { term: Attendance / fill rate, runtime_type: Learning }
              - { term: "Sign-in sheet", runtime_type: Artefact }
              - { term: Course materials, runtime_type: Artefact }
              - { term: Evaluation submitted, runtime_type: Event }
      - name: "n-certificationOS"
        buyer: "Awarding bodies, professional institutes and exam boards — paid for by the certification/credentialing-programme budget."
        os_test: "Own buyer (certification-body owner / chief examiner), a credential-issuance-and-validity state model (issued, expired, revoked) distinct from learning delivery, secure exam-integrity workflows, and vocabulary (candidate, credential, recertification, verification) unique to credentialing — repeatable across professional bodies worldwide."
        sectors:
          - name: Professional Certification Programmes
            note: Professional certification is frequently accredited (e.g. ISO 17024) and may be a legal requirement to practise.
            operating_domains:
              - Eligibility and prerequisite checks
              - Exam registration and scheduling
              - Candidate identity verification
              - Result determination and grading
              - Credential issuance
              - Recertification and CPD tracking
              - Public credential verification
            vocabulary:
              - { term: Candidate, runtime_type: Actor }
              - { term: Certification body, runtime_type: Actor }
              - { term: Credential, runtime_type: Object }
              - { term: Eligibility application, runtime_type: Object }
              - { term: Exam booked, runtime_type: Event }
              - { term: Certified / active, runtime_type: State }
              - { term: Recertification workflow, runtime_type: Workflow }
              - { term: Pass/fail determination, runtime_type: Decision }
              - { term: Credential issued, runtime_type: Outcome }
              - { term: Digital badge / certificate, runtime_type: Artefact }
              - { term: Pass rate, runtime_type: Learning }
              - { term: Expired credential, runtime_type: State }
              - { term: CPD points logged, runtime_type: Event }
              - { term: Verification record, runtime_type: Artefact }
          - name: "Exam Delivery & Proctoring"
            note: "High-stakes exam delivery is governed by test-security and data-protection standards; biometric proctoring is regulated."
            operating_domains:
              - "Test-centre and slot allocation"
              - Online / remote proctoring
              - Item bank and form assembly
              - Live invigilation and incident handling
              - Candidate authentication
              - Response capture and scoring
              - "Security-breach investigation"
            vocabulary:
              - { term: "Test-taker", runtime_type: Actor }
              - { term: Proctor / invigilator, runtime_type: Actor }
              - { term: Exam form, runtime_type: Object }
              - { term: Test slot, runtime_type: Object }
              - { term: Exam started, runtime_type: Event }
              - { term: In session, runtime_type: State }
              - { term: Proctoring workflow, runtime_type: Workflow }
              - { term: Flag / intervene decision, runtime_type: Decision }
              - { term: Integrity incident logged, runtime_type: Event }
              - { term: Score report, runtime_type: Artefact }
              - { term: Result delivered, runtime_type: Outcome }
              - { term: Flag rate, runtime_type: Learning }
              - { term: Voided / invalidated, runtime_type: State }
              - { term: Incident report, runtime_type: Artefact }
          - name: "Licensure & Regulatory Examinations"
            note: "Licensure to practise (medicine, law, engineering, finance) is a statutory regulated activity with legal enforcement."
            operating_domains:
              - Statutory eligibility screening
              - "Fitness-to-practise checks"
              - Licence issuance and renewal
              - "Mandatory continuing-education tracking"
              - Register / roster maintenance
              - Complaints and disciplinary action
              - Regulator data reporting
            vocabulary:
              - { term: Licensee / practitioner, runtime_type: Actor }
              - { term: Licensing board, runtime_type: Actor }
              - { term: Licence, runtime_type: Object }
              - { term: Public register, runtime_type: Object }
              - { term: Application submitted, runtime_type: Event }
              - { term: Licensed / in good standing, runtime_type: State }
              - { term: Renewal workflow, runtime_type: Workflow }
              - { term: "Fitness-to-practise decision", runtime_type: Decision }
              - { term: Licence granted, runtime_type: Outcome }
              - { term: Licence certificate, runtime_type: Artefact }
              - { term: Suspended / revoked, runtime_type: State }
              - { term: Disciplinary case opened, runtime_type: Event }
              - { term: "Continuing-education compliance", runtime_type: Learning }
              - { term: Register entry, runtime_type: Artefact }
          - name: "Digital Credentials & Verification"
            operating_domains:
              - Verifiable credential issuance
              - "Open-badge design and criteria"
              - Wallet and sharing
              - "Employer / third-party verification"
              - Credential revocation
              - Stacking and pathways
              - Issuance analytics
            vocabulary:
              - { term: Credential holder, runtime_type: Actor }
              - { term: Issuer, runtime_type: Actor }
              - { term: Verifiable credential, runtime_type: Object }
              - { term: Badge criteria, runtime_type: Object }
              - { term: Credential issued, runtime_type: Event }
              - { term: Valid, runtime_type: State }
              - { term: Verification request workflow, runtime_type: Workflow }
              - { term: Revocation decision, runtime_type: Decision }
              - { term: Open badge, runtime_type: Artefact }
              - { term: Verified by employer, runtime_type: Outcome }
              - { term: Verification volume, runtime_type: Learning }
              - { term: Revoked, runtime_type: State }
              - { term: Shared to wallet, runtime_type: Event }
              - { term: Credential record, runtime_type: Artefact }
          - name: "Awarding Body Standards & Accreditation"
            note: "Awarding bodies and their qualifications are regulated (e.g. Ofqual, accreditation councils) with formal appeals and malpractice rules."
            operating_domains:
              - Qualification / standard design
              - Centre approval and quality assurance
              - External moderation and verification
              - Standardisation of markers
              - Appeals and enquiries about results
              - Malpractice investigation
              - Awarding and certification cycle
            vocabulary:
              - { term: Approved centre, runtime_type: Actor }
              - { term: External verifier, runtime_type: Actor }
              - { term: Qualification standard, runtime_type: Object }
              - { term: Assessment specification, runtime_type: Object }
              - { term: Centre approved, runtime_type: Event }
              - { term: Under verification, runtime_type: State }
              - { term: Standardisation workflow, runtime_type: Workflow }
              - { term: Award decision, runtime_type: Decision }
              - { term: Enquiry about results lodged, runtime_type: Event }
              - { term: Certificate issued, runtime_type: Artefact }
              - { term: Qualification awarded, runtime_type: Outcome }
              - { term: Centre conformance rate, runtime_type: Learning }
              - { term: Malpractice case, runtime_type: Object }
              - { term: Verification report, runtime_type: Artefact }
  - name: "Government & Public Sector"
    os:
      - name: "n-govOS"
        buyer: "Permanent secretaries, central-government CIOs and digital service heads who own departmental delivery budgets."
        os_test: "Central government runs policy, programmes and citizen identity at national scale with its own appropriations budget, Cabinet/Treasury controls, GDS-style frontends, a programme/policy state model, and Whitehall vocabulary that no council or court shares."
        sectors:
          - name: "Policy & Legislation"
            note: Legislative process is governed by Parliamentary standing orders and statutory consultation duties.
            operating_domains:
              - Green and white papers in drafting
              - Bills passing through Parliamentary stages
              - Statutory instruments and secondary legislation
              - Impact assessments and consultation responses
              - Ministerial submissions and decision boxes
              - "Cross-Whitehall policy clearances"
              - Commencement dates and transition schedules
            vocabulary:
              - { term: Policy lead, runtime_type: Actor }
              - { term: Bill, runtime_type: Object }
              - { term: Consultation, runtime_type: Workflow }
              - { term: Royal Assent, runtime_type: Event }
              - { term: In committee stage, runtime_type: State }
              - { term: Ministerial submission, runtime_type: Artefact }
              - { term: Clearance decision, runtime_type: Decision }
              - { term: Impact assessment, runtime_type: Artefact }
              - { term: Statutory instrument, runtime_type: Object }
              - { term: Commencement, runtime_type: Event }
              - { term: Policy outcome delivered, runtime_type: Outcome }
              - { term: Consultation insight, runtime_type: Learning }
              - { term: Drafting amendment, runtime_type: Event }
              - { term: Cleared for introduction, runtime_type: State }
          - name: "Major Programmes & Delivery (GMPP)"
            note: Major projects are subject to mandatory IPA assurance and HM Treasury spending controls.
            operating_domains:
              - Programmes on the Government Major Projects Portfolio
              - Business cases at OBC/FBC stages
              - Spending Review settlements and reprofiling
              - Gateway reviews and IPA assurance
              - Benefits realisation plans
              - Risk and issue registers
              - Senior Responsible Owner appointments
            vocabulary:
              - { term: Senior Responsible Owner, runtime_type: Actor }
              - { term: Programme, runtime_type: Object }
              - { term: Business case, runtime_type: Artefact }
              - { term: Gateway review, runtime_type: Workflow }
              - { term: Delivery confidence assessment, runtime_type: Decision }
              - { term: Amber/Red rating, runtime_type: State }
              - { term: Reset point reached, runtime_type: Event }
              - { term: Benefit realised, runtime_type: Outcome }
              - { term: Risk register, runtime_type: Artefact }
              - { term: Milestone slip, runtime_type: Event }
              - { term: Funding approval, runtime_type: Decision }
              - { term: Lessons learned log, runtime_type: Learning }
              - { term: In implementation, runtime_type: State }
              - { term: Reprofiled budget, runtime_type: Object }
          - name: "Citizen Identity & Digital Services"
            note: Digital identity must meet the UK digital identity and attributes trust framework and UK GDPR.
            operating_domains:
              - "Verified citizen accounts and sign-in journeys"
              - Identity proofing and document checks
              - Service transactions across the gov estate
              - "Single sign-on and trust framework integrations"
              - "Accessibility and assisted-digital routes"
              - Service performance dashboards
              - Notification and message preferences
            vocabulary:
              - { term: Citizen, runtime_type: Actor }
              - { term: Verified account, runtime_type: Object }
              - { term: Identity proofing, runtime_type: Workflow }
              - { term: "Sign-in", runtime_type: Event }
              - { term: Identity verified, runtime_type: State }
              - { term: Proofing decision, runtime_type: Decision }
              - { term: Credential, runtime_type: Artefact }
              - { term: Service transaction completed, runtime_type: Outcome }
              - { term: Document check, runtime_type: Workflow }
              - { term: Account locked, runtime_type: State }
              - { term: Notification sent, runtime_type: Event }
              - { term: Completion rate, runtime_type: Learning }
              - { term: Trust framework scheme, runtime_type: Object }
              - { term: "Assisted-digital handoff", runtime_type: Event }
          - name: "Public Procurement & Commercial"
            note: Procurement is regulated by the Procurement Act 2023 and transparency/standstill rules.
            operating_domains:
              - Tenders and competitive procedures
              - Framework agreements and dynamic markets
              - Supplier bids and evaluation panels
              - Contract awards and standstill periods
              - Spend controls and approvals
              - Supplier performance and KPIs
              - Social value and SME targets
            vocabulary:
              - { term: Contracting authority, runtime_type: Actor }
              - { term: Tender, runtime_type: Object }
              - { term: Bid evaluation, runtime_type: Workflow }
              - { term: Contract award, runtime_type: Event }
              - { term: Under standstill, runtime_type: State }
              - { term: Award decision, runtime_type: Decision }
              - { term: Framework agreement, runtime_type: Artefact }
              - { term: Supplier, runtime_type: Actor }
              - { term: Contract signed, runtime_type: Outcome }
              - { term: Spend approval, runtime_type: Decision }
              - { term: Tender published, runtime_type: Event }
              - { term: Social value score, runtime_type: Learning }
              - { term: Contract notice, runtime_type: Artefact }
              - { term: In competition, runtime_type: State }
          - name: "Public Finance & Spending Control"
            note: "Governed by HM Treasury's Managing Public Money and the Government Financial Reporting Manual."
            operating_domains:
              - Departmental budgets (DEL/AME) and allocations
              - Estimates and Supplementary Estimates
              - Spend approvals against delegations
              - Accruals accounting and outturn
              - Fiscal events and forecasts
              - Managing public money compliance
              - "Audit and value-for-money reviews"
            vocabulary:
              - { term: Finance business partner, runtime_type: Actor }
              - { term: Budget line, runtime_type: Object }
              - { term: Estimate, runtime_type: Artefact }
              - { term: Approval to spend, runtime_type: Decision }
              - { term: Within delegation, runtime_type: State }
              - { term: Outturn reported, runtime_type: Event }
              - { term: Reconciliation, runtime_type: Workflow }
              - { term: Overspend, runtime_type: State }
              - { term: Forecast, runtime_type: Artefact }
              - { term: "Value-for-money achieved", runtime_type: Outcome }
              - { term: Audit finding, runtime_type: Learning }
              - { term: Virement, runtime_type: Event }
              - { term: Accounting officer, runtime_type: Actor }
              - { term: Funds released, runtime_type: Event }
          - name: "Freedom of Information & Casework Correspondence"
            note: "Bound by the Freedom of Information Act 2000 (20-working-day duty) and UK GDPR for SARs."
            operating_domains:
              - FOI and subject access requests
              - "Ministerial correspondence (PQs, treat-officials)"
              - Public enquiries and complaint cases
              - Exemption assessments and redaction
              - Statutory response clocks
              - Disclosure logs and publication
              - Internal reviews and appeals
            vocabulary:
              - { term: Requester, runtime_type: Actor }
              - { term: FOI request, runtime_type: Object }
              - { term: Exemption assessment, runtime_type: Workflow }
              - { term: Statutory clock started, runtime_type: Event }
              - { term: Awaiting clearance, runtime_type: State }
              - { term: Disclosure decision, runtime_type: Decision }
              - { term: Response letter, runtime_type: Artefact }
              - { term: Redacted document, runtime_type: Artefact }
              - { term: Request closed, runtime_type: Outcome }
              - { term: Internal review requested, runtime_type: Event }
              - { term: Overdue, runtime_type: State }
              - { term: "Response-time performance", runtime_type: Learning }
              - { term: Caseworker, runtime_type: Actor }
              - { term: Published to disclosure log, runtime_type: Event }
      - name: "n-justiceOS"
        buyer: "Court service chief executives, prosecution-service heads and prison/probation directors who own justice-system operating budgets."
        os_test: "The justice system has its own ring-fenced budget, judiciary-controlled frontends, a case-lifecycle state model (charge→trial→sentence→supervision) and legal vocabulary (defendant, listing, custody) that exists nowhere in benefits or planning — a distinct OS, not a re-skin."
        sectors:
          - name: "Criminal Courts & Case Management"
            note: Operates under the Criminal Procedure Rules and judicial listing independence.
            operating_domains:
              - Charges and indictments before the court
              - Hearing listings and court diaries
              - Pleas and case progression stages
              - Evidence bundles and disclosure
              - Custody and bail status
              - Verdicts and sentencing
              - Warrants and enforcement orders
            vocabulary:
              - { term: Defendant, runtime_type: Actor }
              - { term: Case file, runtime_type: Object }
              - { term: Listing, runtime_type: Workflow }
              - { term: Hearing, runtime_type: Event }
              - { term: Awaiting trial, runtime_type: State }
              - { term: Plea, runtime_type: Decision }
              - { term: Indictment, runtime_type: Artefact }
              - { term: Verdict returned, runtime_type: Event }
              - { term: Sentence passed, runtime_type: Outcome }
              - { term: Remanded in custody, runtime_type: State }
              - { term: Evidence bundle, runtime_type: Artefact }
              - { term: Adjournment, runtime_type: Event }
              - { term: Magistrate, runtime_type: Actor }
              - { term: "Conviction-rate trend", runtime_type: Learning }
          - name: "Civil & Family Courts"
            note: Governed by the Civil Procedure Rules and Family Procedure Rules.
            operating_domains:
              - Claims and money judgments
              - "Family applications (care, contact, divorce)"
              - Case management directions
              - Mediation and dispute resolution
              - Orders and undertakings
              - Fee remissions and hardship
              - Enforcement of judgments
            vocabulary:
              - { term: Claimant, runtime_type: Actor }
              - { term: Claim, runtime_type: Object }
              - { term: Directions hearing, runtime_type: Workflow }
              - { term: Application filed, runtime_type: Event }
              - { term: Stayed, runtime_type: State }
              - { term: Court order, runtime_type: Decision }
              - { term: Consent order, runtime_type: Artefact }
              - { term: Judgment, runtime_type: Artefact }
              - { term: Dispute resolved, runtime_type: Outcome }
              - { term: Mediation, runtime_type: Workflow }
              - { term: Default judgment entered, runtime_type: Event }
              - { term: Awaiting allocation, runtime_type: State }
              - { term: Respondent, runtime_type: Actor }
              - { term: "Settlement-rate insight", runtime_type: Learning }
          - name: "Prosecution & Charging"
            note: "Charging follows the Code for Crown Prosecutors (evidential and public-interest tests)."
            operating_domains:
              - Police case files referred for charge
              - Charging decisions and threshold tests
              - Evidence review and disclosure schedules
              - Witness and victim management
              - "Pre-charge bail and diversions"
              - Trial readiness and counsel briefing
              - Appeals and reviews of decisions
            vocabulary:
              - { term: Prosecutor, runtime_type: Actor }
              - { term: Case file, runtime_type: Object }
              - { term: Charging review, runtime_type: Workflow }
              - { term: Referral received, runtime_type: Event }
              - { term: Under review, runtime_type: State }
              - { term: Charging decision, runtime_type: Decision }
              - { term: Disclosure schedule, runtime_type: Artefact }
              - { term: Charge authorised, runtime_type: Event }
              - { term: Case discontinued, runtime_type: Outcome }
              - { term: Witness, runtime_type: Actor }
              - { term: Counsel brief, runtime_type: Artefact }
              - { term: No further action, runtime_type: State }
              - { term: "Trial-readiness rate", runtime_type: Learning }
              - { term: Charge conviction secured, runtime_type: Outcome }
          - name: "Prisons & Custody"
            note: "Custody operates under the Prison Rules and sentence-calculation legislation."
            operating_domains:
              - Prisoner reception and induction
              - Cell allocation and population management
              - Categorisation and risk assessment
              - Sentence calculation and release dates
              - Adjudications and incidents
              - "Regime, work and education"
              - Transfers and escorts
            vocabulary:
              - { term: Prisoner, runtime_type: Actor }
              - { term: Prison record, runtime_type: Object }
              - { term: Categorisation review, runtime_type: Workflow }
              - { term: Reception, runtime_type: Event }
              - { term: On remand, runtime_type: State }
              - { term: Categorisation decision, runtime_type: Decision }
              - { term: Sentence calculation, runtime_type: Artefact }
              - { term: Released on licence, runtime_type: Outcome }
              - { term: Adjudication, runtime_type: Event }
              - { term: Segregated, runtime_type: State }
              - { term: Cell allocation, runtime_type: Decision }
              - { term: Incident report, runtime_type: Artefact }
              - { term: Transfer authorised, runtime_type: Event }
              - { term: Reoffending rate, runtime_type: Learning }
          - name: "Probation & Community Supervision"
            note: Supervision is delivered under sentencing legislation and probation national standards.
            operating_domains:
              - Offenders on licence or community orders
              - Sentence plans and interventions
              - "Risk-of-harm assessments"
              - Appointments and reporting compliance
              - Recall and breach proceedings
              - Accredited programmes and unpaid work
              - "Resettlement and through-the-gate"
            vocabulary:
              - { term: Service user, runtime_type: Actor }
              - { term: Supervision case, runtime_type: Object }
              - { term: Risk assessment, runtime_type: Workflow }
              - { term: Appointment attended, runtime_type: Event }
              - { term: On licence, runtime_type: State }
              - { term: Recall decision, runtime_type: Decision }
              - { term: Sentence plan, runtime_type: Artefact }
              - { term: Breach raised, runtime_type: Event }
              - { term: Order completed, runtime_type: Outcome }
              - { term: High risk of harm, runtime_type: State }
              - { term: Probation officer, runtime_type: Actor }
              - { term: "Unpaid-work hours", runtime_type: Artefact }
              - { term: Compliance rate, runtime_type: Learning }
              - { term: Recalled to custody, runtime_type: Outcome }
          - name: "Tribunals & Administrative Justice"
            note: "Tribunals operate under the Tribunal Procedure Rules and chamber-specific legislation."
            operating_domains:
              - "Appeals across benefit, tax, immigration chambers"
              - Listings and panel composition
              - Bundles and respondent responses
              - Paper and oral hearings
              - Decisions and statements of reasons
              - Onward appeals to upper tribunal
              - "Set-aside and review applications"
            vocabulary:
              - { term: Appellant, runtime_type: Actor }
              - { term: Appeal, runtime_type: Object }
              - { term: Listing, runtime_type: Workflow }
              - { term: Appeal lodged, runtime_type: Event }
              - { term: Awaiting hearing, runtime_type: State }
              - { term: Tribunal decision, runtime_type: Decision }
              - { term: Statement of reasons, runtime_type: Artefact }
              - { term: Appeal allowed, runtime_type: Outcome }
              - { term: Respondent bundle, runtime_type: Artefact }
              - { term: Struck out, runtime_type: State }
              - { term: Tribunal judge, runtime_type: Actor }
              - { term: Onward appeal, runtime_type: Event }
              - { term: Hearing held, runtime_type: Event }
              - { term: Overturn rate, runtime_type: Learning }
      - name: "n-benefitOS"
        buyer: "Welfare/social-security agency directors and DWP-equivalent operations chiefs who own the benefits delivery budget."
        os_test: "Welfare delivery has its own multi-billion budget, eligibility-engine frontends, a claim-lifecycle state model (apply→assess→award→review→sanction) and entitlement vocabulary distinct from courts or councils — a standalone OS by buyer, money and model."
        sectors:
          - name: "Working-Age Benefits & Universal Credit"
            note: "Entitlement governed by social-security legislation and conditionality regulations."
            operating_domains:
              - New claims and verification
              - Earnings and means assessment
              - Award calculation and payment cycles
              - Claimant commitments and conditionality
              - Sanctions and disputes
              - "Change-of-circumstance reporting"
              - Advances and deductions
            vocabulary:
              - { term: Claimant, runtime_type: Actor }
              - { term: Claim, runtime_type: Object }
              - { term: Means assessment, runtime_type: Workflow }
              - { term: Claim submitted, runtime_type: Event }
              - { term: In payment, runtime_type: State }
              - { term: Award decision, runtime_type: Decision }
              - { term: Claimant commitment, runtime_type: Artefact }
              - { term: Payment issued, runtime_type: Event }
              - { term: Entitlement awarded, runtime_type: Outcome }
              - { term: Sanctioned, runtime_type: State }
              - { term: Work coach, runtime_type: Actor }
              - { term: Change of circumstances, runtime_type: Event }
              - { term: Award notice, runtime_type: Artefact }
              - { term: "Off-flow rate", runtime_type: Learning }
          - name: "Disability & Health Assessment"
            note: Assessments follow statutory descriptor criteria and equality duties for disabled applicants.
            operating_domains:
              - "PIP/DLA-style applications"
              - Functional health assessments
              - Evidence gathering from clinicians
              - Points scoring against descriptors
              - Award periods and review dates
              - Mandatory reconsiderations
              - Appeals to tribunal
            vocabulary:
              - { term: Applicant, runtime_type: Actor }
              - { term: Health assessment, runtime_type: Workflow }
              - { term: Application, runtime_type: Object }
              - { term: Assessment booked, runtime_type: Event }
              - { term: Awaiting assessment, runtime_type: State }
              - { term: Entitlement decision, runtime_type: Decision }
              - { term: Assessment report, runtime_type: Artefact }
              - { term: Descriptor points, runtime_type: Object }
              - { term: Award granted, runtime_type: Outcome }
              - { term: Mandatory reconsideration, runtime_type: Event }
              - { term: Disallowed, runtime_type: State }
              - { term: Healthcare assessor, runtime_type: Actor }
              - { term: "Decision-overturn rate", runtime_type: Learning }
              - { term: Reconsidered award, runtime_type: Outcome }
          - name: "Pensions & Retirement"
            note: "Governed by the Pensions Act and national-insurance contribution rules."
            operating_domains:
              - State pension entitlement and forecasts
              - "National-insurance qualifying years"
              - Deferral and uprating
              - "Pension credit means-test"
              - Payment scheduling abroad and at home
              - Bereavement and inherited entitlement
              - Overpayment recovery
            vocabulary:
              - { term: Pensioner, runtime_type: Actor }
              - { term: Pension record, runtime_type: Object }
              - { term: Entitlement calculation, runtime_type: Workflow }
              - { term: State pension age reached, runtime_type: Event }
              - { term: In payment, runtime_type: State }
              - { term: Award decision, runtime_type: Decision }
              - { term: Pension forecast, runtime_type: Artefact }
              - { term: Qualifying year, runtime_type: Object }
              - { term: Pension awarded, runtime_type: Outcome }
              - { term: Deferred, runtime_type: State }
              - { term: Uprating applied, runtime_type: Event }
              - { term: Bereavement notified, runtime_type: Event }
              - { term: Award letter, runtime_type: Artefact }
              - { term: "Take-up rate", runtime_type: Learning }
          - name: "Child & Family Support"
            note: "Maintenance is statutory under child-support legislation with enforcement powers."
            operating_domains:
              - Child benefit and maintenance
              - Childcare cost support
              - Family means assessment
              - Maintenance liability and arrears
              - Payment arrangements and enforcement
              - Parentage and household checks
              - "High-income charge reconciliation"
            vocabulary:
              - { term: Receiving parent, runtime_type: Actor }
              - { term: Maintenance case, runtime_type: Object }
              - { term: Liability assessment, runtime_type: Workflow }
              - { term: Application opened, runtime_type: Event }
              - { term: "Collect & pay", runtime_type: State }
              - { term: Maintenance calculation, runtime_type: Decision }
              - { term: Payment schedule, runtime_type: Artefact }
              - { term: Arrears accrued, runtime_type: Event }
              - { term: Maintenance paid, runtime_type: Outcome }
              - { term: Paying parent, runtime_type: Actor }
              - { term: In arrears, runtime_type: State }
              - { term: Enforcement action, runtime_type: Decision }
              - { term: Liability order, runtime_type: Artefact }
              - { term: Compliance rate, runtime_type: Learning }
          - name: "Employment Support & Back-to-Work"
            note: Employment programmes operate under DWP commissioning and provider contracts.
            operating_domains:
              - Jobseeker caseloads and segmentation
              - Employment programmes and referrals
              - Skills and training plans
              - "Job-search activity tracking"
              - Employer vacancy matching
              - Outcome payments to providers
              - Health and work conversations
            vocabulary:
              - { term: Jobseeker, runtime_type: Actor }
              - { term: Caseload, runtime_type: Object }
              - { term: Programme referral, runtime_type: Workflow }
              - { term: Referral made, runtime_type: Event }
              - { term: Actively seeking work, runtime_type: State }
              - { term: Referral decision, runtime_type: Decision }
              - { term: Action plan, runtime_type: Artefact }
              - { term: Job start, runtime_type: Event }
              - { term: Sustained employment, runtime_type: Outcome }
              - { term: Provider, runtime_type: Actor }
              - { term: Disengaged, runtime_type: State }
              - { term: Vacancy match, runtime_type: Workflow }
              - { term: Outcome payment, runtime_type: Artefact }
              - { term: "Job-outcome rate", runtime_type: Learning }
          - name: "Fraud, Error & Debt"
            note: "Investigations operate under social-security fraud legislation and PACE caution rules."
            operating_domains:
              - "Risk-scored claims for review"
              - Investigations and interviews under caution
              - Overpayment identification and classification
              - Recovery plans and deductions
              - Penalties and prosecutions
              - "Debt portfolio and write-offs"
              - "Data-matching and surveillance referrals"
            vocabulary:
              - { term: Subject, runtime_type: Actor }
              - { term: Overpayment, runtime_type: Object }
              - { term: Investigation, runtime_type: Workflow }
              - { term: Risk flag raised, runtime_type: Event }
              - { term: Under investigation, runtime_type: State }
              - { term: Recovery decision, runtime_type: Decision }
              - { term: Penalty notice, runtime_type: Artefact }
              - { term: Debt referred, runtime_type: Event }
              - { term: Overpayment recovered, runtime_type: Outcome }
              - { term: Investigator, runtime_type: Actor }
              - { term: Written off, runtime_type: State }
              - { term: Interview under caution, runtime_type: Event }
              - { term: Recovery rate, runtime_type: Learning }
              - { term: Fraud confirmed, runtime_type: Outcome }
      - name: "n-councilOS"
        buyer: "Local-authority chief executives and directors of place/people services who own the council's general fund."
        os_test: "Local councils have their own precept/grant budget, member-governed frontends, a service-request and statutory-duty state model, and ward/place vocabulary (member, precept, statutory care duty) that central government and courts don't use — clearly its own OS."
        sectors:
          - name: Adult Social Care
            note: Statutory duty under the Care Act 2014 and safeguarding/charging regulations.
            operating_domains:
              - Care assessments and reviews
              - Care and support plans
              - Personal budgets and direct payments
              - Provider placements and brokerage
              - Safeguarding concerns
              - Financial assessment and charging
              - Reablement and hospital discharge
            vocabulary:
              - { term: Service user, runtime_type: Actor }
              - { term: Care package, runtime_type: Object }
              - { term: Needs assessment, runtime_type: Workflow }
              - { term: Assessment requested, runtime_type: Event }
              - { term: Eligible for support, runtime_type: State }
              - { term: Eligibility decision, runtime_type: Decision }
              - { term: Support plan, runtime_type: Artefact }
              - { term: Personal budget, runtime_type: Object }
              - { term: Needs met, runtime_type: Outcome }
              - { term: Safeguarding alert, runtime_type: Event }
              - { term: Social worker, runtime_type: Actor }
              - { term: Awaiting placement, runtime_type: State }
              - { term: Financial assessment, runtime_type: Workflow }
              - { term: "Delayed-discharge rate", runtime_type: Learning }
          - name: "Children's Services & Safeguarding"
            note: Statutory under the Children Act 1989/2004 and Working Together safeguarding guidance.
            operating_domains:
              - Referrals and contacts to the front door
              - "Child-in-need and child-protection plans"
              - "Looked-after children and placements"
              - Statutory visits and reviews
              - Court proceedings and care orders
              - Fostering and adoption
              - Early help and family support
            vocabulary:
              - { term: Child, runtime_type: Actor }
              - { term: "Child's case", runtime_type: Object }
              - { term: Assessment, runtime_type: Workflow }
              - { term: Referral received, runtime_type: Event }
              - { term: On a protection plan, runtime_type: State }
              - { term: Threshold decision, runtime_type: Decision }
              - { term: "Child-protection plan", runtime_type: Artefact }
              - { term: Statutory visit, runtime_type: Event }
              - { term: Permanence achieved, runtime_type: Outcome }
              - { term: Social worker, runtime_type: Actor }
              - { term: "Looked-after", runtime_type: State }
              - { term: Placement, runtime_type: Object }
              - { term: Care order made, runtime_type: Event }
              - { term: "Re-referral rate", runtime_type: Learning }
          - name: "Housing & Homelessness"
            note: Statutory duties under the Housing Act 1996 and Homelessness Reduction Act 2017.
            operating_domains:
              - Homelessness applications and triage
              - Housing register and allocations
              - Temporary accommodation placements
              - Tenancy and rent accounts
              - Repairs and disrepair cases
              - Prevention and relief duties
              - Bidding and lettings
            vocabulary:
              - { term: Applicant, runtime_type: Actor }
              - { term: Housing application, runtime_type: Object }
              - { term: Homelessness assessment, runtime_type: Workflow }
              - { term: Application made, runtime_type: Event }
              - { term: In temporary accommodation, runtime_type: State }
              - { term: Duty decision, runtime_type: Decision }
              - { term: Personal housing plan, runtime_type: Artefact }
              - { term: Property offered, runtime_type: Event }
              - { term: Settled accommodation secured, runtime_type: Outcome }
              - { term: Tenant, runtime_type: Actor }
              - { term: Threatened with homelessness, runtime_type: State }
              - { term: Allocation, runtime_type: Decision }
              - { term: Repair order, runtime_type: Artefact }
              - { term: Prevention rate, runtime_type: Learning }
          - name: "Council Tax & Local Revenues"
            note: "Billing and recovery governed by the Local Government Finance Act and council-tax regulations."
            operating_domains:
              - "Council-tax accounts and bands"
              - "Business-rates (NNDR) accounts"
              - "Discounts, exemptions and reliefs"
              - Billing and instalment plans
              - Recovery and enforcement
              - "Council-tax support claims"
              - "Refunds and write-offs"
            vocabulary:
              - { term: Taxpayer, runtime_type: Actor }
              - { term: "Council-tax account", runtime_type: Object }
              - { term: Recovery, runtime_type: Workflow }
              - { term: Bill issued, runtime_type: Event }
              - { term: In arrears, runtime_type: State }
              - { term: Discount decision, runtime_type: Decision }
              - { term: Liability order, runtime_type: Artefact }
              - { term: Reminder sent, runtime_type: Event }
              - { term: Account settled, runtime_type: Outcome }
              - { term: Exemption, runtime_type: Object }
              - { term: Summoned, runtime_type: State }
              - { term: Enforcement agent referral, runtime_type: Decision }
              - { term: Bill, runtime_type: Artefact }
              - { term: Collection rate, runtime_type: Learning }
          - name: "Waste, Highways & Environment"
            note: Highways duties under the Highways Act and waste duties under environmental protection legislation.
            operating_domains:
              - Bin collection rounds and schedules
              - "Missed-collection and fly-tipping reports"
              - "Pothole and street-defect repairs"
              - Street cleansing and grounds
              - Permits and road closures
              - Recycling and disposal contracts
              - Environmental enforcement
            vocabulary:
              - { term: Resident, runtime_type: Actor }
              - { term: Service request, runtime_type: Object }
              - { term: Repair job, runtime_type: Workflow }
              - { term: Report logged, runtime_type: Event }
              - { term: Awaiting works, runtime_type: State }
              - { term: Prioritisation decision, runtime_type: Decision }
              - { term: Work order, runtime_type: Artefact }
              - { term: Crew dispatched, runtime_type: Event }
              - { term: Defect fixed, runtime_type: Outcome }
              - { term: Operative, runtime_type: Actor }
              - { term: Overdue, runtime_type: State }
              - { term: Collection round, runtime_type: Object }
              - { term: "Fixed-penalty notice", runtime_type: Artefact }
              - { term: "First-time-fix rate", runtime_type: Learning }
          - name: "Democratic Services & Governance"
            note: "Governed by the Local Government Act and access-to-information/standards regulations."
            operating_domains:
              - Committee meetings and agendas
              - Member casework and ward enquiries
              - "Decisions and call-ins"
              - Registers of interest and declarations
              - Public consultations and petitions
              - Scrutiny and audit
              - Constitution and delegations
            vocabulary:
              - { term: Councillor, runtime_type: Actor }
              - { term: Committee meeting, runtime_type: Object }
              - { term: "Decision-making", runtime_type: Workflow }
              - { term: Meeting convened, runtime_type: Event }
              - { term: "Open for call-in", runtime_type: State }
              - { term: Resolution, runtime_type: Decision }
              - { term: Agenda pack, runtime_type: Artefact }
              - { term: Decision published, runtime_type: Event }
              - { term: Decision implemented, runtime_type: Outcome }
              - { term: Resident petitioner, runtime_type: Actor }
              - { term: Called in, runtime_type: State }
              - { term: Member casework, runtime_type: Object }
              - { term: Minutes, runtime_type: Artefact }
              - { term: "Decision-response time", runtime_type: Learning }
      - name: "n-licensingOS"
        buyer: "Regulatory-services and licensing managers in councils and national regulators who own permit/registration income and compliance budgets."
        os_test: "Licensing is a distinct OS: its buyer owns fee income, its frontend is built around application→grant→condition→renewal→enforcement, its state model is permission-status, and its vocabulary (licensee, conditions, suspension) differs from benefits, planning or courts."
        sectors:
          - name: "Alcohol, Entertainment & Late-Night"
            note: Regulated under the Licensing Act 2003 with statutory licensing objectives.
            operating_domains:
              - Premises and personal licence applications
              - Licensable activities and conditions
              - Hearings and representations
              - Temporary event notices
              - Reviews and suspensions
              - Designated premises supervisors
              - Enforcement and test purchases
            vocabulary:
              - { term: Licensee, runtime_type: Actor }
              - { term: Premises licence, runtime_type: Object }
              - { term: Application processing, runtime_type: Workflow }
              - { term: Application received, runtime_type: Event }
              - { term: Pending hearing, runtime_type: State }
              - { term: Grant decision, runtime_type: Decision }
              - { term: Licence conditions, runtime_type: Artefact }
              - { term: Licence granted, runtime_type: Event }
              - { term: Premises licensed, runtime_type: Outcome }
              - { term: Responsible authority, runtime_type: Actor }
              - { term: Suspended, runtime_type: State }
              - { term: Review triggered, runtime_type: Event }
              - { term: Licence certificate, runtime_type: Artefact }
              - { term: Compliance rate, runtime_type: Learning }
          - name: "Taxi & Private Hire"
            note: "Licensed under the Town Police Clauses Act and Local Government (Misc. Provisions) Act with statutory fit-and-proper tests."
            operating_domains:
              - Driver and vehicle licence applications
              - DBS and medical checks
              - Vehicle inspections and plates
              - Operator licensing
              - Knowledge and safeguarding tests
              - Complaints and revocations
              - Renewals and condition checks
            vocabulary:
              - { term: Driver applicant, runtime_type: Actor }
              - { term: Driver licence, runtime_type: Object }
              - { term: "Fit-and-proper check", runtime_type: Workflow }
              - { term: Application submitted, runtime_type: Event }
              - { term: Awaiting checks, runtime_type: State }
              - { term: Grant decision, runtime_type: Decision }
              - { term: Vehicle plate, runtime_type: Artefact }
              - { term: Inspection passed, runtime_type: Event }
              - { term: Licensed to operate, runtime_type: Outcome }
              - { term: Operator, runtime_type: Actor }
              - { term: Revoked, runtime_type: State }
              - { term: Complaint logged, runtime_type: Event }
              - { term: Badge, runtime_type: Artefact }
              - { term: "Renewal-on-time rate", runtime_type: Learning }
          - name: "Food, Health & Safety Registration"
            note: "Regulated under the Food Safety Act, Food Hygiene Rating Scheme and Health and Safety at Work Act."
            operating_domains:
              - Food business registrations
              - Hygiene inspections and ratings
              - "Health-and-safety inspections"
              - Improvement and prohibition notices
              - Sampling and complaints
              - "Infectious-disease investigations"
              - "Re-rating and appeals"
            vocabulary:
              - { term: Food business operator, runtime_type: Actor }
              - { term: Registered premises, runtime_type: Object }
              - { term: Inspection, runtime_type: Workflow }
              - { term: Registration received, runtime_type: Event }
              - { term: Awaiting inspection, runtime_type: State }
              - { term: Rating decision, runtime_type: Decision }
              - { term: Hygiene rating, runtime_type: Artefact }
              - { term: Improvement notice served, runtime_type: Event }
              - { term: Compliant, runtime_type: Outcome }
              - { term: Environmental health officer, runtime_type: Actor }
              - { term: Prohibited, runtime_type: State }
              - { term: Inspection report, runtime_type: Artefact }
              - { term: "Re-rating requested", runtime_type: Event }
              - { term: "Broadly-compliant rate", runtime_type: Learning }
          - name: "Gambling & Adult Entertainment"
            note: "Regulated under the Gambling Act 2005 and local-authority adult-entertainment licensing powers."
            operating_domains:
              - Premises and operating licences
              - Personal management licences
              - Local risk assessments
              - "Sexual-entertainment venue licensing"
              - Conditions and exclusions
              - Reviews and revocations
              - Compliance assessments
            vocabulary:
              - { term: Operator, runtime_type: Actor }
              - { term: Operating licence, runtime_type: Object }
              - { term: Licensing assessment, runtime_type: Workflow }
              - { term: Application lodged, runtime_type: Event }
              - { term: Under consideration, runtime_type: State }
              - { term: Grant decision, runtime_type: Decision }
              - { term: Licence conditions, runtime_type: Artefact }
              - { term: Licence issued, runtime_type: Event }
              - { term: Authorised to operate, runtime_type: Outcome }
              - { term: Licensing authority, runtime_type: Actor }
              - { term: Revoked, runtime_type: State }
              - { term: Review hearing, runtime_type: Event }
              - { term: Risk assessment, runtime_type: Artefact }
              - { term: "Compliance-finding rate", runtime_type: Learning }
          - name: "Environmental & Trade Permits"
            note: "Regulated under the Environmental Permitting Regulations and animal-welfare/scrap-metal licensing law."
            operating_domains:
              - Environmental permits for installations
              - "Waste-carrier and scrap-metal licences"
              - "Animal-activity and pet-shop licences"
              - "Street-trading consents"
              - Skip and scaffold permits
              - Discharge and emissions conditions
              - Variations and surrenders
            vocabulary:
              - { term: Permit holder, runtime_type: Actor }
              - { term: Permit, runtime_type: Object }
              - { term: Permitting, runtime_type: Workflow }
              - { term: Application duly made, runtime_type: Event }
              - { term: In determination, runtime_type: State }
              - { term: Permit decision, runtime_type: Decision }
              - { term: Permit conditions, runtime_type: Artefact }
              - { term: Permit issued, runtime_type: Event }
              - { term: Authorised activity, runtime_type: Outcome }
              - { term: Regulator, runtime_type: Actor }
              - { term: Surrendered, runtime_type: State }
              - { term: Variation requested, runtime_type: Event }
              - { term: Permit document, runtime_type: Artefact }
              - { term: "Permit-compliance rate", runtime_type: Learning }
          - name: "Trading Standards & Consumer Protection"
            note: "Enforced under the Consumer Protection from Unfair Trading Regulations and weights-and-measures law."
            operating_domains:
              - Trader registrations and approvals
              - "Product-safety and labelling checks"
              - "Underage-sales test purchases"
              - "Weights-and-measures verification"
              - "Scams and rogue-trader cases"
              - Enforcement notices and prosecutions
              - "Primary-authority partnerships"
            vocabulary:
              - { term: Trader, runtime_type: Actor }
              - { term: Approval, runtime_type: Object }
              - { term: Market surveillance, runtime_type: Workflow }
              - { term: Complaint received, runtime_type: Event }
              - { term: Under enforcement, runtime_type: State }
              - { term: Enforcement decision, runtime_type: Decision }
              - { term: Enforcement notice, runtime_type: Artefact }
              - { term: Test purchase made, runtime_type: Event }
              - { term: Consumer harm prevented, runtime_type: Outcome }
              - { term: "Trading-standards officer", runtime_type: Actor }
              - { term: Prohibited from trading, runtime_type: State }
              - { term: Prosecution, runtime_type: Decision }
              - { term: Evidence file, runtime_type: Artefact }
              - { term: "Detriment-prevented value", runtime_type: Learning }
      - name: "n-planningOS"
        buyer: "Heads of planning, development management and building-control who own planning fee income and local-plan delivery."
        os_test: "Planning is its own OS: a distinct buyer owning fee income, a spatial/map-centric frontend, an application→consultation→determination→appeal→enforcement state model, and land-use vocabulary (application, consent, conditions, allocation) found in no other government OS."
        sectors:
          - name: Development Management
            note: Regulated under the Town and Country Planning Act and Development Management Procedure Order.
            operating_domains:
              - Planning applications and validation
              - Statutory and neighbour consultations
              - Site visits and case assessment
              - Officer reports and recommendations
              - Committee determinations
              - Conditions and obligations
              - Decision notices and timescales
            vocabulary:
              - { term: Applicant, runtime_type: Actor }
              - { term: Planning application, runtime_type: Object }
              - { term: Consultation, runtime_type: Workflow }
              - { term: Application validated, runtime_type: Event }
              - { term: Pending consideration, runtime_type: State }
              - { term: Determination, runtime_type: Decision }
              - { term: Officer report, runtime_type: Artefact }
              - { term: Decision issued, runtime_type: Event }
              - { term: Planning permission granted, runtime_type: Outcome }
              - { term: Case officer, runtime_type: Actor }
              - { term: Refused, runtime_type: State }
              - { term: Planning condition, runtime_type: Artefact }
              - { term: Decision notice, runtime_type: Artefact }
              - { term: "Determination-in-time rate", runtime_type: Learning }
          - name: "Local Plans & Policy"
            note: "Plan-making follows the NPPF and Town and Country Planning (Local Planning) Regulations."
            operating_domains:
              - "Local-plan preparation and stages"
              - Site allocations and the call for sites
              - Evidence base and viability
              - Public examination by inspector
              - "Housing-need and land-supply targets"
              - Consultation responses (Reg 18/19)
              - Adoption and monitoring
            vocabulary:
              - { term: "Planning-policy officer", runtime_type: Actor }
              - { term: Local plan, runtime_type: Object }
              - { term: "Plan-making", runtime_type: Workflow }
              - { term: Consultation opened, runtime_type: Event }
              - { term: At examination, runtime_type: State }
              - { term: Allocation decision, runtime_type: Decision }
              - { term: Site allocation, runtime_type: Artefact }
              - { term: Plan adopted, runtime_type: Event }
              - { term: Sound plan in place, runtime_type: Outcome }
              - { term: Inspector, runtime_type: Actor }
              - { term: Found unsound, runtime_type: State }
              - { term: Evidence base, runtime_type: Artefact }
              - { term: "Five-year land supply", runtime_type: Learning }
              - { term: "Main-modification proposed", runtime_type: Event }
          - name: Building Control
            note: "Regulated under the Building Regulations and the Building Safety Act for higher-risk buildings."
            operating_domains:
              - "Building-regulations applications"
              - Plans checking and approvals
              - Site inspections at key stages
              - Completion certificates
              - "Dangerous-structure and demolition notices"
              - "Higher-risk building gateways"
              - "Competent-person scheme records"
            vocabulary:
              - { term: Building owner, runtime_type: Actor }
              - { term: "Building-control application", runtime_type: Object }
              - { term: Plans check, runtime_type: Workflow }
              - { term: Application deposited, runtime_type: Event }
              - { term: Awaiting inspection, runtime_type: State }
              - { term: Approval decision, runtime_type: Decision }
              - { term: Approved plans, runtime_type: Artefact }
              - { term: Inspection passed, runtime_type: Event }
              - { term: Completion certificate issued, runtime_type: Outcome }
              - { term: "Building-control surveyor", runtime_type: Actor }
              - { term: "Non-compliant", runtime_type: State }
              - { term: "Dangerous-structure notice", runtime_type: Artefact }
              - { term: Gateway submitted, runtime_type: Event }
              - { term: "First-inspection-pass rate", runtime_type: Learning }
          - name: Planning Enforcement
            note: Enforcement powers under the Town and Country Planning Act with statutory immunity periods.
            operating_domains:
              - Alleged breaches and complaints
              - Site investigations and evidence
              - "Breach-of-condition cases"
              - Enforcement and stop notices
              - Retrospective applications
              - Appeals against notices
              - Prosecutions and injunctions
            vocabulary:
              - { term: Landowner, runtime_type: Actor }
              - { term: Enforcement case, runtime_type: Object }
              - { term: Investigation, runtime_type: Workflow }
              - { term: Breach reported, runtime_type: Event }
              - { term: Under investigation, runtime_type: State }
              - { term: Expediency decision, runtime_type: Decision }
              - { term: Enforcement notice, runtime_type: Artefact }
              - { term: Notice served, runtime_type: Event }
              - { term: Breach remedied, runtime_type: Outcome }
              - { term: Enforcement officer, runtime_type: Actor }
              - { term: "Non-compliant", runtime_type: State }
              - { term: Site visit, runtime_type: Workflow }
              - { term: Stop notice, runtime_type: Artefact }
              - { term: "Compliance-on-notice rate", runtime_type: Learning }
          - name: "Land Charges & Property Searches"
            note: Maintained under the Local Land Charges Act with statutory accuracy and compensation duties.
            operating_domains:
              - "Local land-charge registrations"
              - Official search requests
              - CON29 enquiries of the local authority
              - "Conditions, agreements and notices on land"
              - Highways and planning history data
              - Search turnaround and accuracy
              - Updates to the charges register
            vocabulary:
              - { term: Search applicant, runtime_type: Actor }
              - { term: Land charge, runtime_type: Object }
              - { term: Search processing, runtime_type: Workflow }
              - { term: Search requested, runtime_type: Event }
              - { term: Awaiting data, runtime_type: State }
              - { term: Registration decision, runtime_type: Decision }
              - { term: Search result, runtime_type: Artefact }
              - { term: Charge registered, runtime_type: Event }
              - { term: Search returned, runtime_type: Outcome }
              - { term: Conveyancer, runtime_type: Actor }
              - { term: On the register, runtime_type: State }
              - { term: Charges register, runtime_type: Object }
              - { term: Official certificate, runtime_type: Artefact }
              - { term: Search turnaround time, runtime_type: Learning }
          - name: "Infrastructure & Developer Contributions"
            note: Governed by Section 106 of the Town and Country Planning Act and the CIL Regulations.
            operating_domains:
              - Section 106 agreements and obligations
              - Community Infrastructure Levy charges
              - Contribution triggers and milestones
              - Monitoring and compliance
              - Spend allocation to projects
              - "Affordable-housing delivery"
              - "Reliefs, exemptions and appeals"
            vocabulary:
              - { term: Developer, runtime_type: Actor }
              - { term: Section 106 obligation, runtime_type: Object }
              - { term: Contribution monitoring, runtime_type: Workflow }
              - { term: Trigger reached, runtime_type: Event }
              - { term: Outstanding, runtime_type: State }
              - { term: Levy decision, runtime_type: Decision }
              - { term: CIL liability notice, runtime_type: Artefact }
              - { term: Payment received, runtime_type: Event }
              - { term: Infrastructure funded, runtime_type: Outcome }
              - { term: Monitoring officer, runtime_type: Actor }
              - { term: In breach, runtime_type: State }
              - { term: Spend allocation, runtime_type: Decision }
              - { term: Deed of agreement, runtime_type: Artefact }
              - { term: "Contributions-collected rate", runtime_type: Learning }
  - name: Commerce
    os:
      - name: "n-commerceOS"
        buyer: "Head of Ecommerce / DTC founder who owns the online store P&L and conversion rate"
        os_test: "Distinct buyer (ecommerce lead, not the warehouse or buyer), own SaaS budget (Shopify/commerce platform stack), frontend built around storefront + cart + checkout state, a state model of carts/orders/sessions found nowhere else, and thousands of repeatable DTC/online-merchant companies."
        sectors:
          - name: "Direct-to-Consumer Brand Store"
            operating_domains:
              - "Product catalogue & variants"
              - "Storefront theme & landing pages"
              - "Cart & checkout funnel"
              - "Promotions & discount codes"
              - Email/SMS lifecycle flows
              - "Reviews & user-generated content"
              - "Conversion-rate experiments"
            vocabulary:
              - { term: Shopper, runtime_type: Actor }
              - { term: Product listing, runtime_type: Object }
              - { term: Variant (size/colour), runtime_type: Object }
              - { term: Cart, runtime_type: Object }
              - { term: Add to cart, runtime_type: Event }
              - { term: Abandoned checkout, runtime_type: State }
              - { term: Discount code, runtime_type: Artefact }
              - { term: Apply best discount, runtime_type: Decision }
              - { term: Checkout flow, runtime_type: Workflow }
              - { term: Order confirmation, runtime_type: Artefact }
              - { term: Order placed, runtime_type: Event }
              - { term: Paid order, runtime_type: Outcome }
              - { term: A/B test on PDP, runtime_type: Decision }
              - { term: Conversion rate, runtime_type: Learning }
              - { term: Average order value, runtime_type: Learning }
          - name: "Subscription & Recurring Commerce"
            note: "Recurring-card billing falls under card-network rules (PCI-DSS, mandates) and UK/EU subscription auto-renewal consumer-protection law."
            operating_domains:
              - "Subscription plans & tiers"
              - "Billing cycles & renewals"
              - "Box curation / build-a-box"
              - Pause / skip / swap controls
              - "Dunning & failed-payment recovery"
              - "Churn-prevention offers"
              - Member portal
            vocabulary:
              - { term: Subscriber, runtime_type: Actor }
              - { term: Subscription plan, runtime_type: Object }
              - { term: Billing cycle, runtime_type: Object }
              - { term: Renewal charge, runtime_type: Event }
              - { term: Active subscription, runtime_type: State }
              - { term: Paused subscription, runtime_type: State }
              - { term: Failed payment, runtime_type: Event }
              - { term: Retry payment / dunning, runtime_type: Workflow }
              - { term: "Keep-or-cancel offer", runtime_type: Decision }
              - { term: Invoice, runtime_type: Artefact }
              - { term: Cancellation, runtime_type: Event }
              - { term: Churned member, runtime_type: Outcome }
              - { term: Retained member, runtime_type: Outcome }
              - { term: Monthly recurring revenue, runtime_type: Learning }
              - { term: Churn rate, runtime_type: Learning }
          - name: Headless / Composable Commerce
            operating_domains:
              - "Commerce API & GraphQL layer"
              - Content management (CMS) for storefront
              - "Pricing & promotion engine"
              - "Search & merchandising service"
              - "Payment & tax microservices"
              - "Front-end framework (Next/Remix)"
              - "Webhooks & event bus"
            vocabulary:
              - { term: Developer, runtime_type: Actor }
              - { term: Commerce API, runtime_type: Object }
              - { term: Product feed, runtime_type: Object }
              - { term: Storefront token, runtime_type: Artefact }
              - { term: Webhook fired, runtime_type: Event }
              - { term: Cache invalidation, runtime_type: Event }
              - { term: Stale catalogue, runtime_type: State }
              - { term: Routing logic, runtime_type: Decision }
              - { term: Deploy storefront, runtime_type: Workflow }
              - { term: Build artefact, runtime_type: Artefact }
              - { term: Live storefront, runtime_type: State }
              - { term: Successful deploy, runtime_type: Outcome }
              - { term: API latency, runtime_type: Learning }
              - { term: Core Web Vitals, runtime_type: Learning }
              - { term: Customer (end shopper), runtime_type: Actor }
          - name: "Cross-Border & International Commerce"
            note: "Cross-border sales trigger customs/import VAT obligations (UK GVMS, EU IOSS) and restricted/dual-use export controls per destination."
            operating_domains:
              - "Local currency & FX pricing"
              - "Duty & tax calculation (DDP/DDU)"
              - "Multi-language storefronts"
              - "Geo-routed catalogue"
              - Local payment methods
              - Customs documentation
              - "Restricted-product compliance"
            vocabulary:
              - { term: International shopper, runtime_type: Actor }
              - { term: Market / region, runtime_type: Object }
              - { term: Price book, runtime_type: Object }
              - { term: "Landed-cost quote", runtime_type: Artefact }
              - { term: Currency conversion, runtime_type: Event }
              - { term: Duties prepaid (DDP), runtime_type: State }
              - { term: Held at customs, runtime_type: State }
              - { term: Choose DDP vs DDU, runtime_type: Decision }
              - { term: Commercial invoice, runtime_type: Artefact }
              - { term: Customs clearance, runtime_type: Workflow }
              - { term: Cleared shipment, runtime_type: Event }
              - { term: Delivered order, runtime_type: Outcome }
              - { term: "Cross-border conversion", runtime_type: Learning }
              - { term: Duty leakage, runtime_type: Learning }
          - name: "Social & Live-Stream Commerce"
            operating_domains:
              - "Shoppable posts & product tags"
              - "Live-stream shopping events"
              - Creator / affiliate links
              - "In-app checkout"
              - "Drop & flash-sale scheduling"
              - "Comment-to-buy automation"
              - "Engagement & attribution analytics"
            vocabulary:
              - { term: Creator, runtime_type: Actor }
              - { term: Viewer, runtime_type: Actor }
              - { term: Shoppable post, runtime_type: Object }
              - { term: Live shopping event, runtime_type: Object }
              - { term: Product tag tapped, runtime_type: Event }
              - { term: "Live & selling", runtime_type: State }
              - { term: Affiliate link, runtime_type: Artefact }
              - { term: Schedule the drop, runtime_type: Decision }
              - { term: Run the live sale, runtime_type: Workflow }
              - { term: "Comment-to-buy", runtime_type: Event }
              - { term: "Sold-out drop", runtime_type: State }
              - { term: Attributed sale, runtime_type: Outcome }
              - { term: Live conversion rate, runtime_type: Learning }
              - { term: Creator commission earned, runtime_type: Outcome }
          - name: "Storefront Merchandising & CRO"
            operating_domains:
              - "Collection & category curation"
              - "On-site search & autocomplete"
              - Personalised recommendations
              - "Banner & hero scheduling"
              - "Bundle & upsell offers"
              - "Inventory-aware ranking"
              - "Funnel analytics & heatmaps"
            vocabulary:
              - { term: Merchandiser, runtime_type: Actor }
              - { term: Collection, runtime_type: Object }
              - { term: Search query, runtime_type: Object }
              - { term: Recommendation slot, runtime_type: Object }
              - { term: Pin product to top, runtime_type: Decision }
              - { term: "Out-of-stock", runtime_type: State }
              - { term: Boost rule, runtime_type: Artefact }
              - { term: Product viewed, runtime_type: Event }
              - { term: "Re-rank collection", runtime_type: Workflow }
              - { term: Upsell bundle, runtime_type: Object }
              - { term: "Click-through", runtime_type: Event }
              - { term: "Add-to-cart rate", runtime_type: Learning }
              - { term: Search exit rate, runtime_type: Learning }
              - { term: Incremental revenue, runtime_type: Outcome }
      - name: "n-marketplaceOS"
        buyer: "Marketplace operator / GM who owns take-rate, liquidity and the balance between buyers and sellers"
        os_test: "A multi-sided buyer (the platform operator, not a single merchant), revenue via take-rate/commission budgets, a frontend built around seller onboarding + listings + matching + payouts, a two-sided state model (supply liquidity, order matching, split payouts) absent from single-merchant commerce, and many repeatable marketplace companies."
        sectors:
          - name: "Product Marketplace (multi-vendor)"
            note: "Operators acting as payment facilitators must meet KYC/AML obligations and money-transmission/e-money rules for holding and splitting funds."
            operating_domains:
              - "Seller onboarding & verification"
              - "Listing creation & moderation"
              - Catalogue mapping / deduplication
              - "Buyer search & discovery"
              - Order routing to sellers
              - "Split payouts & commission"
              - "Dispute & refund resolution"
            vocabulary:
              - { term: Seller, runtime_type: Actor }
              - { term: Buyer, runtime_type: Actor }
              - { term: Listing, runtime_type: Object }
              - { term: Seller verification, runtime_type: Workflow }
              - { term: Listing under review, runtime_type: State }
              - { term: Listing approved, runtime_type: Event }
              - { term: Commission rate, runtime_type: Object }
              - { term: Payout, runtime_type: Artefact }
              - { term: Hold seller payout, runtime_type: Decision }
              - { term: Dispute raised, runtime_type: Event }
              - { term: Refund issued, runtime_type: Outcome }
              - { term: Completed transaction, runtime_type: Outcome }
              - { term: Gross merchandise value, runtime_type: Learning }
              - { term: Take rate, runtime_type: Learning }
          - name: Services Marketplace
            operating_domains:
              - "Provider profiles & credentials"
              - "Service catalogue & packages"
              - "Availability & booking calendar"
              - Quote / proposal exchange
              - "Escrow & milestone release"
              - "Two-sided reviews"
              - "Trust & safety moderation"
            vocabulary:
              - { term: Service provider, runtime_type: Actor }
              - { term: Client, runtime_type: Actor }
              - { term: Service package, runtime_type: Object }
              - { term: Booking request, runtime_type: Event }
              - { term: Quote, runtime_type: Artefact }
              - { term: Accept the quote, runtime_type: Decision }
              - { term: Booking confirmed, runtime_type: State }
              - { term: Funds in escrow, runtime_type: State }
              - { term: Milestone delivered, runtime_type: Event }
              - { term: Release payment, runtime_type: Workflow }
              - { term: Completed job, runtime_type: Outcome }
              - { term: Provider rating, runtime_type: Artefact }
              - { term: "Repeat-booking rate", runtime_type: Learning }
              - { term: "Match-to-book conversion", runtime_type: Learning }
          - name: "Rental & Access Marketplace"
            note: Protection/insurance plans bundled with rentals may constitute regulated insurance distribution depending on jurisdiction.
            operating_domains:
              - Rentable inventory listings
              - "Availability calendar & blackout dates"
              - "Booking & reservation flow"
              - "Security deposit & damage claims"
              - Handover / return condition checks
              - Dynamic rental pricing
              - "Insurance & protection plans"
            vocabulary:
              - { term: Owner / lister, runtime_type: Actor }
              - { term: Renter, runtime_type: Actor }
              - { term: Rentable item, runtime_type: Object }
              - { term: Reservation, runtime_type: Object }
              - { term: Date blocked, runtime_type: State }
              - { term: "Check-out handover", runtime_type: Event }
              - { term: Return inspection, runtime_type: Workflow }
              - { term: Security deposit, runtime_type: Artefact }
              - { term: Damage claim, runtime_type: Decision }
              - { term: Item returned, runtime_type: Event }
              - { term: Deposit refunded, runtime_type: Outcome }
              - { term: Utilisation rate, runtime_type: Learning }
              - { term: Damage incidence, runtime_type: Learning }
              - { term: Protection plan, runtime_type: Artefact }
          - name: "Resale & Recommerce Marketplace"
            note: "Authentication claims and resale of branded goods touch trademark/counterfeit law and consumer-protection rules on condition disclosure."
            operating_domains:
              - "Item intake & authentication"
              - Condition grading
              - "Consignment vs buy-outright pricing"
              - "Photography & listing pipeline"
              - Buyer purchase flow
              - Seller payout / store credit
              - "Returns & re-listing"
            vocabulary:
              - { term: Consignor, runtime_type: Actor }
              - { term: Buyer, runtime_type: Actor }
              - { term: "Pre-owned item", runtime_type: Object }
              - { term: Item intake, runtime_type: Workflow }
              - { term: Authentication check, runtime_type: Decision }
              - { term: Authenticated, runtime_type: State }
              - { term: Condition grade, runtime_type: Artefact }
              - { term: Listed for sale, runtime_type: State }
              - { term: Item sold, runtime_type: Event }
              - { term: Consignor payout, runtime_type: Outcome }
              - { term: Store credit, runtime_type: Artefact }
              - { term: "Re-list", runtime_type: Workflow }
              - { term: "Sell-through rate", runtime_type: Learning }
              - { term: Authentication accuracy, runtime_type: Learning }
          - name: B2B / Wholesale Marketplace
            note: Offering net terms / trade credit can constitute regulated lending and requires affordability/credit checks in some jurisdictions.
            operating_domains:
              - Verified business buyer onboarding
              - "Tiered & negotiated pricing"
              - Minimum order quantities (MOQ)
              - "RFQ & bulk quoting"
              - Trade credit / net terms
              - Supplier compliance documents
              - Bulk order fulfilment routing
            vocabulary:
              - { term: Wholesale buyer, runtime_type: Actor }
              - { term: Supplier, runtime_type: Actor }
              - { term: Catalogue SKU, runtime_type: Object }
              - { term: Price tier, runtime_type: Object }
              - { term: RFQ submitted, runtime_type: Event }
              - { term: Quote issued, runtime_type: Artefact }
              - { term: Approve net terms, runtime_type: Decision }
              - { term: Pending verification, runtime_type: State }
              - { term: Bulk order, runtime_type: Object }
              - { term: "Negotiate-and-order", runtime_type: Workflow }
              - { term: Trade credit line, runtime_type: Artefact }
              - { term: Won account, runtime_type: Outcome }
              - { term: Reorder frequency, runtime_type: Learning }
              - { term: Credit default rate, runtime_type: Learning }
      - name: "n-retailOS"
        buyer: "Head of Retail / store operations director who owns store P&L, staff and physical inventory"
        os_test: "Buyer is store operations (not the online ecommerce lead), budget for POS/store systems, a frontend built around the physical store, registers, floor staff and shelves, a state model of registers/tills/store stock/foot traffic unique to physical retail, and many repeatable retail chains and independents."
        sectors:
          - name: "Point of Sale & Checkout"
            note: "Card acceptance is bound by PCI-DSS; receipts and tax handling must meet local fiscal/VAT requirements (some jurisdictions mandate fiscalised tills)."
            operating_domains:
              - Register / till configuration
              - "Barcode scanning & lookup"
              - "Tender & split payments"
              - Receipts (print/digital)
              - "Returns & exchanges at till"
              - Cash drawer reconciliation
              - "Offline-mode transaction queue"
            vocabulary:
              - { term: Cashier, runtime_type: Actor }
              - { term: Customer, runtime_type: Actor }
              - { term: Register / till, runtime_type: Object }
              - { term: Basket, runtime_type: Object }
              - { term: Scan item, runtime_type: Event }
              - { term: Tender payment, runtime_type: Event }
              - { term: Drawer open, runtime_type: State }
              - { term: Apply return policy, runtime_type: Decision }
              - { term: Receipt, runtime_type: Artefact }
              - { term: Sale completed, runtime_type: Outcome }
              - { term: "End-of-day cash-up", runtime_type: Workflow }
              - { term: Cash variance, runtime_type: State }
              - { term: Sales per hour, runtime_type: Learning }
              - { term: Items per basket, runtime_type: Learning }
          - name: "Store Inventory & Replenishment"
            operating_domains:
              - "On-shelf stock counts"
              - "Backroom & stockroom locations"
              - "Replenishment & shelf gap detection"
              - "Stock receiving & put-away"
              - "Cycle counts & shrinkage"
              - "Inter-store transfers"
              - Planogram compliance
            vocabulary:
              - { term: Stock associate, runtime_type: Actor }
              - { term: Stock unit (SKU), runtime_type: Object }
              - { term: Shelf location, runtime_type: Object }
              - { term: Delivery received, runtime_type: Event }
              - { term: "Put-away", runtime_type: Workflow }
              - { term: Shelf gap, runtime_type: State }
              - { term: Trigger replenishment, runtime_type: Decision }
              - { term: Cycle count, runtime_type: Workflow }
              - { term: "Stock-out", runtime_type: State }
              - { term: Transfer note, runtime_type: Artefact }
              - { term: Counted stock, runtime_type: Outcome }
              - { term: Shrinkage, runtime_type: Learning }
              - { term: "On-shelf availability", runtime_type: Learning }
              - { term: Stock adjustment, runtime_type: Event }
          - name: "Workforce & Store Operations"
            note: "Rostering and time/attendance must comply with working-time, minimum-wage and rest-break employment regulation."
            operating_domains:
              - "Shift scheduling & rotas"
              - "Clock-in / time & attendance"
              - "Task lists & store walks"
              - Labour budgeting vs traffic
              - "Training & certifications"
              - Opening / closing checklists
              - "Compliance & incident logging"
            vocabulary:
              - { term: Store associate, runtime_type: Actor }
              - { term: Store manager, runtime_type: Actor }
              - { term: Shift, runtime_type: Object }
              - { term: Rota, runtime_type: Artefact }
              - { term: Clock in, runtime_type: Event }
              - { term: On shift, runtime_type: State }
              - { term: Assign task, runtime_type: Decision }
              - { term: Opening checklist, runtime_type: Workflow }
              - { term: Task completed, runtime_type: Event }
              - { term: Incident report, runtime_type: Artefact }
              - { term: Covered shift, runtime_type: Outcome }
              - { term: Understaffed, runtime_type: State }
              - { term: "Labour cost %", runtime_type: Learning }
              - { term: Sales per labour hour, runtime_type: Learning }
          - name: "Pricing & Promotions (in-store)"
            note: "Promotional pricing must comply with unit-pricing and reference-price ('was/now') consumer-protection rules to avoid misleading offers."
            operating_domains:
              - "Shelf-edge & electronic labels"
              - "Markdown & clearance pricing"
              - "Multi-buy & promotion setup"
              - Price overrides at till
              - Competitor price monitoring
              - Loyalty discount rules
              - Margin guardrails
            vocabulary:
              - { term: Pricing manager, runtime_type: Actor }
              - { term: Price label, runtime_type: Object }
              - { term: Markdown, runtime_type: Object }
              - { term: Promotion, runtime_type: Object }
              - { term: Price change pushed, runtime_type: Event }
              - { term: On promotion, runtime_type: State }
              - { term: Approve markdown, runtime_type: Decision }
              - { term: Schedule promotion, runtime_type: Workflow }
              - { term: Promotion live, runtime_type: State }
              - { term: Price audit report, runtime_type: Artefact }
              - { term: Margin protected, runtime_type: Outcome }
              - { term: Promo uplift, runtime_type: Learning }
              - { term: Markdown loss, runtime_type: Learning }
              - { term: Override logged, runtime_type: Event }
          - name: "Customer Loyalty & CRM (retail)"
            note: "Holding customer profiles and marketing consent is subject to data-protection law (UK GDPR / PECR for electronic marketing)."
            operating_domains:
              - "Loyalty enrolment & cards"
              - "Points & rewards ledger"
              - "Tiers & member benefits"
              - "Targeted offers & coupons"
              - "Customer profile & purchase history"
              - "Consent & marketing preferences"
              - "Member analytics & segments"
            vocabulary:
              - { term: Member, runtime_type: Actor }
              - { term: Loyalty account, runtime_type: Object }
              - { term: Points balance, runtime_type: Object }
              - { term: Points earned, runtime_type: Event }
              - { term: Reward redeemed, runtime_type: Event }
              - { term: Gold tier, runtime_type: State }
              - { term: Send targeted offer, runtime_type: Decision }
              - { term: Coupon, runtime_type: Artefact }
              - { term: Enrol member, runtime_type: Workflow }
              - { term: Marketing consent, runtime_type: State }
              - { term: Retained customer, runtime_type: Outcome }
              - { term: Repeat purchase rate, runtime_type: Learning }
              - { term: Redemption rate, runtime_type: Learning }
              - { term: Customer lifetime value, runtime_type: Learning }
          - name: "Omnichannel & Click-and-Collect"
            operating_domains:
              - "Buy-online-pickup-in-store (BOPIS)"
              - "Ship-from-store fulfilment"
              - Unified inventory view
              - "Endless aisle / order-in-store"
              - Returns across channels
              - "Locker & collection point ops"
              - Single customer order history
            vocabulary:
              - { term: Omnichannel shopper, runtime_type: Actor }
              - { term: Pickup associate, runtime_type: Actor }
              - { term: Online order, runtime_type: Object }
              - { term: Collection point, runtime_type: Object }
              - { term: Order ready for pickup, runtime_type: State }
              - { term: Customer collected, runtime_type: Event }
              - { term: Pick from store shelf, runtime_type: Workflow }
              - { term: Route to nearest store, runtime_type: Decision }
              - { term: "Ship-from-store label", runtime_type: Artefact }
              - { term: "Cross-channel return", runtime_type: Event }
              - { term: Fulfilled order, runtime_type: Outcome }
              - { term: Awaiting collection, runtime_type: State }
              - { term: "Click-collect rate", runtime_type: Learning }
              - { term: Pick accuracy, runtime_type: Learning }
      - name: "n-logisticsOS"
        buyer: "Head of Transport / logistics director who owns freight spend, fleet and on-time delivery"
        os_test: "Buyer is transport/logistics (not warehouse or procurement), budget for TMS/fleet systems, a frontend built around shipments, routes, vehicles and carriers, a state model of in-transit/loads/legs/exceptions distinct from inventory or order systems, and many repeatable carriers, 3PLs and shippers."
        sectors:
          - name: "Freight & Transport Management (TMS)"
            note: "Carriage is governed by carrier liability conventions (CMR for road, Hague-Visby for sea) and licensing of freight operators."
            operating_domains:
              - "Load planning & consolidation"
              - "Carrier selection & rating"
              - "Freight booking & tendering"
              - "Shipment tracking & ETA"
              - "Freight audit & invoice match"
              - "Exception & claims handling"
              - Multimodal leg planning
            vocabulary:
              - { term: Shipper, runtime_type: Actor }
              - { term: Carrier, runtime_type: Actor }
              - { term: Shipment, runtime_type: Object }
              - { term: Load, runtime_type: Object }
              - { term: Tender to carrier, runtime_type: Decision }
              - { term: In transit, runtime_type: State }
              - { term: Pickup completed, runtime_type: Event }
              - { term: Bill of lading, runtime_type: Artefact }
              - { term: Plan and dispatch, runtime_type: Workflow }
              - { term: Delivery exception, runtime_type: Event }
              - { term: Delivered on time, runtime_type: Outcome }
              - { term: Freight invoice, runtime_type: Artefact }
              - { term: "On-time delivery %", runtime_type: Learning }
              - { term: Cost per mile, runtime_type: Learning }
          - name: "Last-Mile Delivery"
            note: "Driver classification (employee vs gig) and tachograph/driver-hours rules apply where relevant."
            operating_domains:
              - Route optimisation
              - "Driver dispatch & app"
              - Delivery time windows
              - Proof of delivery capture
              - "Failed-delivery & re-attempt"
              - Customer delivery notifications
              - "Driver settlement & pay"
            vocabulary:
              - { term: Driver, runtime_type: Actor }
              - { term: Recipient, runtime_type: Actor }
              - { term: Delivery stop, runtime_type: Object }
              - { term: Route, runtime_type: Object }
              - { term: Optimise route, runtime_type: Decision }
              - { term: Out for delivery, runtime_type: State }
              - { term: Parcel scanned, runtime_type: Event }
              - { term: Proof of delivery, runtime_type: Artefact }
              - { term: Run the route, runtime_type: Workflow }
              - { term: Failed attempt, runtime_type: Event }
              - { term: Delivered parcel, runtime_type: Outcome }
              - { term: Missed delivery, runtime_type: State }
              - { term: "First-attempt success rate", runtime_type: Learning }
              - { term: Stops per hour, runtime_type: Learning }
          - name: Fleet Management
            note: "Commercial fleets require operator licences, periodic roadworthiness inspections and driver-hours/tachograph compliance."
            operating_domains:
              - "Vehicle register & assets"
              - "Maintenance & service schedule"
              - "Fuel & energy tracking"
              - "Telematics & driver behaviour"
              - Compliance (MOT/inspections)
              - "Fleet utilisation & assignment"
              - "Incident & accident records"
            vocabulary:
              - { term: Fleet manager, runtime_type: Actor }
              - { term: Vehicle, runtime_type: Object }
              - { term: Maintenance schedule, runtime_type: Object }
              - { term: Service due, runtime_type: State }
              - { term: Inspection logged, runtime_type: Event }
              - { term: Off the road (VOR), runtime_type: State }
              - { term: Schedule the service, runtime_type: Decision }
              - { term: Maintenance workflow, runtime_type: Workflow }
              - { term: Service record, runtime_type: Artefact }
              - { term: Vehicle returned to service, runtime_type: Outcome }
              - { term: "Harsh-braking event", runtime_type: Event }
              - { term: Roadworthy, runtime_type: State }
              - { term: Fleet utilisation, runtime_type: Learning }
              - { term: Cost per vehicle, runtime_type: Learning }
          - name: International Freight Forwarding
            note: "Forwarding and customs brokerage are licensed/regulated activities; filings touch import VAT, duty and dual-use export controls."
            operating_domains:
              - "Booking & space allocation"
              - "Container & consolidation planning"
              - "Customs brokerage & filing"
              - "Documentation (B/L, certificates)"
              - "Port & terminal coordination"
              - "Demurrage & detention tracking"
              - "Track-and-trace across legs"
            vocabulary:
              - { term: Freight forwarder, runtime_type: Actor }
              - { term: Consignee, runtime_type: Actor }
              - { term: Container, runtime_type: Object }
              - { term: Booking, runtime_type: Object }
              - { term: Vessel departed, runtime_type: Event }
              - { term: At port / on water, runtime_type: State }
              - { term: File customs entry, runtime_type: Decision }
              - { term: Customs clearance, runtime_type: Workflow }
              - { term: Certificate of origin, runtime_type: Artefact }
              - { term: Held for inspection, runtime_type: State }
              - { term: Cleared and released, runtime_type: Event }
              - { term: Delivered to consignee, runtime_type: Outcome }
              - { term: Demurrage cost, runtime_type: Learning }
              - { term: Transit time, runtime_type: Learning }
          - name: "Parcel & Carrier Management"
            operating_domains:
              - "Multi-carrier rate shopping"
              - "Label generation & manifesting"
              - "Service-level selection"
              - Tracking aggregation
              - "Returns label & RMA"
              - Carrier performance scorecards
              - "Surcharge & billing reconciliation"
            vocabulary:
              - { term: Shipping operator, runtime_type: Actor }
              - { term: Carrier account, runtime_type: Object }
              - { term: Parcel, runtime_type: Object }
              - { term: "Rate-shop carriers", runtime_type: Decision }
              - { term: Shipping label, runtime_type: Artefact }
              - { term: Manifest closed, runtime_type: Event }
              - { term: Label printed, runtime_type: State }
              - { term: Buy and print labels, runtime_type: Workflow }
              - { term: Tracking update, runtime_type: Event }
              - { term: Return label, runtime_type: Artefact }
              - { term: Shipped parcel, runtime_type: Outcome }
              - { term: Awaiting collection, runtime_type: State }
              - { term: Average shipping cost, runtime_type: Learning }
              - { term: "Carrier on-time score", runtime_type: Learning }
      - name: "n-procurementOS"
        buyer: Chief Procurement Officer / Head of Purchasing who owns indirect/direct spend and supplier contracts
        os_test: "Buyer is procurement/purchasing (not the warehouse or sales), budget for source-to-pay suites, a frontend built around requisitions, suppliers, sourcing events and POs, a state model of approvals/sourcing/spend distinct from selling or shipping, and many repeatable enterprises with procurement functions."
        sectors:
          - name: "Procure-to-Pay (P2P)"
            operating_domains:
              - Purchase requisitions
              - "Approval workflows & limits"
              - Purchase order issuance
              - Goods/service receipt
              - "Invoice matching (3-way)"
              - "Spend categories & budgets"
              - "Catalogue & punch-out buying"
            vocabulary:
              - { term: Requester, runtime_type: Actor }
              - { term: Approver, runtime_type: Actor }
              - { term: Requisition, runtime_type: Object }
              - { term: Purchase order, runtime_type: Object }
              - { term: Submit for approval, runtime_type: Event }
              - { term: Pending approval, runtime_type: State }
              - { term: Approve the spend, runtime_type: Decision }
              - { term: "Three-way match", runtime_type: Workflow }
              - { term: Goods receipt note, runtime_type: Artefact }
              - { term: Invoice matched, runtime_type: Event }
              - { term: PO closed, runtime_type: Outcome }
              - { term: "Off-contract spend", runtime_type: State }
              - { term: "Maverick spend %", runtime_type: Learning }
              - { term: PO cycle time, runtime_type: Learning }
          - name: "Strategic Sourcing & Tendering"
            note: "Public-sector tendering must follow procurement regulation (e.g. UK Procurement Act / EU directives) on fairness, transparency and timelines."
            operating_domains:
              - Sourcing event setup (RFx)
              - "Supplier invitation & registration"
              - "Bid collection & comparison"
              - "Scoring & evaluation criteria"
              - "Award decision & justification"
              - Savings tracking
              - Reverse auctions
            vocabulary:
              - { term: Sourcing lead, runtime_type: Actor }
              - { term: Bidding supplier, runtime_type: Actor }
              - { term: Sourcing event (RFP/RFQ), runtime_type: Object }
              - { term: Bid, runtime_type: Object }
              - { term: Bid submitted, runtime_type: Event }
              - { term: Under evaluation, runtime_type: State }
              - { term: Award the contract, runtime_type: Decision }
              - { term: Run the tender, runtime_type: Workflow }
              - { term: Scorecard, runtime_type: Artefact }
              - { term: Award notice, runtime_type: Artefact }
              - { term: Awarded supplier, runtime_type: Outcome }
              - { term: Realised savings, runtime_type: Outcome }
              - { term: "Sourcing savings %", runtime_type: Learning }
              - { term: Bid coverage, runtime_type: Learning }
          - name: "Supplier Management & Onboarding"
            note: "Supplier screening must satisfy sanctions/AML and (increasingly) modern-slavery and ESG due-diligence obligations."
            operating_domains:
              - "Supplier registration & vetting"
              - "Bank & tax detail validation"
              - "Document & certification collection"
              - "Risk & sanctions screening"
              - Performance scorecards
              - Supplier segmentation
              - "Periodic re-qualification"
            vocabulary:
              - { term: Supplier, runtime_type: Actor }
              - { term: Procurement officer, runtime_type: Actor }
              - { term: Supplier record, runtime_type: Object }
              - { term: Onboarding form, runtime_type: Object }
              - { term: Documents submitted, runtime_type: Event }
              - { term: Pending verification, runtime_type: State }
              - { term: Approve supplier, runtime_type: Decision }
              - { term: Vet and onboard, runtime_type: Workflow }
              - { term: Compliance certificate, runtime_type: Artefact }
              - { term: Sanctions flag, runtime_type: State }
              - { term: Approved supplier, runtime_type: Outcome }
              - { term: Supplier scorecard, runtime_type: Artefact }
              - { term: Supplier risk score, runtime_type: Learning }
              - { term: Onboarding cycle time, runtime_type: Learning }
          - name: Contract Lifecycle Management
            note: "E-signature and contract execution must meet electronic-signature law (eIDAS / UK eIDAS) for enforceability."
            operating_domains:
              - "Contract authoring & templates"
              - "Clause library & playbooks"
              - "Negotiation & redlining"
              - "Approval & e-signature"
              - "Obligation & milestone tracking"
              - "Renewal & expiry alerts"
              - "Contract repository & search"
            vocabulary:
              - { term: Contract owner, runtime_type: Actor }
              - { term: Counterparty, runtime_type: Actor }
              - { term: Contract, runtime_type: Object }
              - { term: Clause, runtime_type: Object }
              - { term: Redline sent, runtime_type: Event }
              - { term: In negotiation, runtime_type: State }
              - { term: Approve final terms, runtime_type: Decision }
              - { term: Route for signature, runtime_type: Workflow }
              - { term: Signed contract, runtime_type: Artefact }
              - { term: Active / executed, runtime_type: State }
              - { term: Renewal due, runtime_type: Event }
              - { term: Executed agreement, runtime_type: Outcome }
              - { term: "Auto-renewal rate", runtime_type: Learning }
              - { term: "Time-to-signature", runtime_type: Learning }
          - name: "Spend Analytics & Category Management"
            operating_domains:
              - Spend data classification
              - Category taxonomy
              - Supplier consolidation analysis
              - "Tail-spend identification"
              - "Savings pipeline & opportunities"
              - Budget vs actual tracking
              - "Compliance & leakage reporting"
            vocabulary:
              - { term: Category manager, runtime_type: Actor }
              - { term: Spend record, runtime_type: Object }
              - { term: Category, runtime_type: Object }
              - { term: Spend classified, runtime_type: Event }
              - { term: Unclassified spend, runtime_type: State }
              - { term: Target a category, runtime_type: Decision }
              - { term: Build the savings plan, runtime_type: Workflow }
              - { term: Opportunity assessment, runtime_type: Artefact }
              - { term: Savings opportunity, runtime_type: Object }
              - { term: Savings realised, runtime_type: Outcome }
              - { term: Addressable spend, runtime_type: State }
              - { term: "Tail-spend ratio", runtime_type: Learning }
              - { term: Spend under management, runtime_type: Learning }
              - { term: Supplier concentration, runtime_type: Learning }
      - name: "n-supplychainOS"
        buyer: "VP Supply Chain / S&OP director who owns demand-supply balance, inventory targets and resilience"
        os_test: "Buyer is supply-chain planning (not transport or purchasing execution), budget for planning/IBP suites, a frontend built around forecasts, plans, inventory positions and the bullwhip across the network, a planning state model (forecast/plan/allocation/disruption) distinct from execution systems, and many repeatable manufacturers/distributors."
        sectors:
          - name: "Demand Planning & Forecasting"
            operating_domains:
              - Demand forecast generation
              - "Forecast overrides & consensus"
              - "New-product introduction curves"
              - "Seasonality & promotion lift"
              - Forecast accuracy review
              - Demand sensing signals
              - Statistical model selection
            vocabulary:
              - { term: Demand planner, runtime_type: Actor }
              - { term: Forecast, runtime_type: Object }
              - { term: Demand signal, runtime_type: Object }
              - { term: Forecast published, runtime_type: Event }
              - { term: Awaiting consensus, runtime_type: State }
              - { term: Override the forecast, runtime_type: Decision }
              - { term: Run the forecast cycle, runtime_type: Workflow }
              - { term: Consensus forecast, runtime_type: Artefact }
              - { term: Forecast locked, runtime_type: State }
              - { term: Plan approved, runtime_type: Outcome }
              - { term: Bias detected, runtime_type: Event }
              - { term: Forecast accuracy (MAPE), runtime_type: Learning }
              - { term: Forecast bias, runtime_type: Learning }
          - name: "Inventory & Replenishment Planning"
            operating_domains:
              - "Safety-stock & reorder points"
              - Replenishment proposals
              - "Multi-echelon optimisation"
              - "Excess & obsolete review"
              - ABC/XYZ segmentation
              - Inventory targets by node
              - Allocation under shortage
            vocabulary:
              - { term: Inventory planner, runtime_type: Actor }
              - { term: "Stock-keeping unit", runtime_type: Object }
              - { term: Reorder point, runtime_type: Object }
              - { term: Below safety stock, runtime_type: State }
              - { term: Replenishment proposed, runtime_type: Event }
              - { term: Approve replenishment, runtime_type: Decision }
              - { term: Rebalance inventory, runtime_type: Workflow }
              - { term: Replenishment order, runtime_type: Artefact }
              - { term: Excess / obsolete, runtime_type: State }
              - { term: "Stock-out avoided", runtime_type: Outcome }
              - { term: Stockout event, runtime_type: Event }
              - { term: Inventory turns, runtime_type: Learning }
              - { term: Days of supply, runtime_type: Learning }
              - { term: Fill rate, runtime_type: Learning }
          - name: "Sales & Operations Planning (S&OP / IBP)"
            operating_domains:
              - "Demand-supply reconciliation"
              - "Capacity & constraint balancing"
              - "Scenario / what-if modelling"
              - "Executive review & sign-off"
              - Financial reconciliation to plan
              - Gap closure actions
              - Rolling planning horizon
            vocabulary:
              - { term: "S&OP planner", runtime_type: Actor }
              - { term: Executive sponsor, runtime_type: Actor }
              - { term: Supply plan, runtime_type: Object }
              - { term: Scenario, runtime_type: Object }
              - { term: Imbalance flagged, runtime_type: State }
              - { term: "Run a what-if", runtime_type: Decision }
              - { term: "Reconcile demand & supply", runtime_type: Workflow }
              - { term: Plan presented, runtime_type: Event }
              - { term: Consensus plan, runtime_type: Artefact }
              - { term: Plan signed off, runtime_type: Outcome }
              - { term: Constrained plan, runtime_type: State }
              - { term: Gap closed, runtime_type: Event }
              - { term: Plan attainment, runtime_type: Learning }
              - { term: "Demand-supply gap", runtime_type: Learning }
          - name: "Supply Chain Visibility & Control Tower"
            operating_domains:
              - "End-to-end shipment visibility"
              - "Disruption & risk alerts"
              - "Supplier & node monitoring"
              - "Exception triage & resolution"
              - "ETA prediction & delay impact"
              - Network event timeline
              - Resolution playbooks
            vocabulary:
              - { term: "Control-tower analyst", runtime_type: Actor }
              - { term: Supply node, runtime_type: Object }
              - { term: Inbound shipment, runtime_type: Object }
              - { term: Disruption alert, runtime_type: Event }
              - { term: At risk, runtime_type: State }
              - { term: Escalate the exception, runtime_type: Decision }
              - { term: Resolve the disruption, runtime_type: Workflow }
              - { term: Mitigation plan, runtime_type: Artefact }
              - { term: Delayed, runtime_type: State }
              - { term: Exception resolved, runtime_type: Outcome }
              - { term: ETA revised, runtime_type: Event }
              - { term: "On-time-in-full (OTIF)", runtime_type: Learning }
              - { term: Disruption response time, runtime_type: Learning }
          - name: "Production & Manufacturing Planning"
            note: "Production of regulated goods (food, pharma, chemicals) must follow GMP and batch-traceability requirements."
            operating_domains:
              - Master production schedule
              - Material requirements (MRP)
              - "Capacity & line scheduling"
              - "Work-order release"
              - Bill of materials management
              - "Constraint & bottleneck planning"
              - Schedule adherence tracking
            vocabulary:
              - { term: Production planner, runtime_type: Actor }
              - { term: Work order, runtime_type: Object }
              - { term: Bill of materials, runtime_type: Object }
              - { term: Material shortage, runtime_type: State }
              - { term: Run MRP, runtime_type: Workflow }
              - { term: Release the work order, runtime_type: Decision }
              - { term: Work order released, runtime_type: Event }
              - { term: Production schedule, runtime_type: Artefact }
              - { term: On the line, runtime_type: State }
              - { term: Production completed, runtime_type: Outcome }
              - { term: Line stoppage, runtime_type: Event }
              - { term: Schedule adherence, runtime_type: Learning }
              - { term: Capacity utilisation, runtime_type: Learning }
      - name: "n-fulfilmentOS"
        buyer: "Head of Warehouse / Fulfilment operations who owns pick-pack-ship throughput and order accuracy"
        os_test: "Buyer is warehouse/fulfilment operations (not transport or planning), budget for WMS/OMS systems, a frontend built around bins, totes, pickers, waves and packing stations, a state model of pick/pack/dock/inventory-location distinct from selling, planning or shipping, and many repeatable 3PLs, fulfilment centres and DTC warehouses."
        sectors:
          - name: Warehouse Management (WMS)
            operating_domains:
              - "Receiving & dock scheduling"
              - "Put-away & slotting"
              - "Bin & location management"
              - "Cycle counting & accuracy"
              - "Wave & task management"
              - Replenishment to pick faces
              - "Labour & equipment tracking"
            vocabulary:
              - { term: Warehouse operative, runtime_type: Actor }
              - { term: Bin location, runtime_type: Object }
              - { term: Tote / pallet, runtime_type: Object }
              - { term: Goods received, runtime_type: Event }
              - { term: Put away stock, runtime_type: Workflow }
              - { term: Location empty, runtime_type: State }
              - { term: Slot the item, runtime_type: Decision }
              - { term: Cycle count, runtime_type: Workflow }
              - { term: Count variance, runtime_type: State }
              - { term: Stock put away, runtime_type: Outcome }
              - { term: Inventory adjustment, runtime_type: Event }
              - { term: Inventory accuracy, runtime_type: Learning }
              - { term: "Dock-to-stock time", runtime_type: Learning }
          - name: "Order Fulfilment & Pick-Pack-Ship"
            operating_domains:
              - "Order release & batching"
              - "Pick path & assignment"
              - "Pick confirmation & scan"
              - "Packing & cartonisation"
              - "Carton weigh & verify"
              - "Label & manifest at pack"
              - "Short-pick & substitution handling"
            vocabulary:
              - { term: Picker, runtime_type: Actor }
              - { term: Packer, runtime_type: Actor }
              - { term: Pick list, runtime_type: Object }
              - { term: Order, runtime_type: Object }
              - { term: Wave released, runtime_type: Event }
              - { term: Picked item, runtime_type: Event }
              - { term: Short pick, runtime_type: State }
              - { term: Substitute the item, runtime_type: Decision }
              - { term: "Pick-pack-ship", runtime_type: Workflow }
              - { term: Packing slip, runtime_type: Artefact }
              - { term: Ready to ship, runtime_type: State }
              - { term: Order shipped, runtime_type: Outcome }
              - { term: Units picked per hour, runtime_type: Learning }
              - { term: Order accuracy, runtime_type: Learning }
          - name: "Returns & Reverse Logistics"
            note: "Returns and refunds are bound by consumer-rights/distance-selling law; recalled or hazardous returns follow safety-disposal rules."
            operating_domains:
              - Return authorisation (RMA)
              - Inbound return receiving
              - "Inspection & disposition grading"
              - Restock / refurbish / scrap routing
              - "Refund & credit trigger"
              - Return reason capture
              - "Warranty & recall handling"
            vocabulary:
              - { term: Returns operative, runtime_type: Actor }
              - { term: Returning customer, runtime_type: Actor }
              - { term: Return (RMA), runtime_type: Object }
              - { term: Returned item, runtime_type: Object }
              - { term: Return received, runtime_type: Event }
              - { term: Awaiting inspection, runtime_type: State }
              - { term: Disposition decision, runtime_type: Decision }
              - { term: Grade and route, runtime_type: Workflow }
              - { term: Disposition note, runtime_type: Artefact }
              - { term: Restocked, runtime_type: State }
              - { term: Refund triggered, runtime_type: Outcome }
              - { term: Return rate, runtime_type: Learning }
              - { term: Recovery value, runtime_type: Learning }
          - name: "Inventory Control & Accuracy"
            note: "Lot/expiry tracking is mandatory for food, pharma and other regulated goods to support recall and FEFO compliance."
            operating_domains:
              - "Real-time stock ledger"
              - Lot / batch / serial tracking
              - "Expiry & FEFO management"
              - "Stock holds & quarantine"
              - Inventory reconciliation
              - "Damage & write-off processing"
              - "Multi-location stock view"
            vocabulary:
              - { term: Inventory controller, runtime_type: Actor }
              - { term: Stock item, runtime_type: Object }
              - { term: Lot / batch, runtime_type: Object }
              - { term: Quarantine hold, runtime_type: State }
              - { term: Stock counted, runtime_type: Event }
              - { term: Release the hold, runtime_type: Decision }
              - { term: Reconcile inventory, runtime_type: Workflow }
              - { term: "Write-off record", runtime_type: Artefact }
              - { term: Expired, runtime_type: State }
              - { term: Reconciled stock, runtime_type: Outcome }
              - { term: Discrepancy logged, runtime_type: Event }
              - { term: "Stock accuracy %", runtime_type: Learning }
              - { term: Shrinkage rate, runtime_type: Learning }
          - name: "Cold-Chain & Specialised Fulfilment"
            note: "Cold-chain and dangerous-goods handling are governed by GDP (pharma), food-safety (HACCP) and ADR/IATA dangerous-goods regulation."
            operating_domains:
              - "Temperature-zone storage"
              - "Cold-chain monitoring & alerts"
              - "Hazmat & dangerous-goods handling"
              - "Time-critical / perishable picking"
              - "Insulated packing & gel-pack rules"
              - "Excursion & breach logging"
              - Compliance documentation
            vocabulary:
              - { term: "Cold-chain operative", runtime_type: Actor }
              - { term: Temperature zone, runtime_type: Object }
              - { term: Perishable item, runtime_type: Object }
              - { term: Temperature reading, runtime_type: Event }
              - { term: Within range, runtime_type: State }
              - { term: Temperature excursion, runtime_type: Event }
              - { term: Quarantine the batch, runtime_type: Decision }
              - { term: "Cold-chain pack-out", runtime_type: Workflow }
              - { term: Excursion report, runtime_type: Artefact }
              - { term: Breached / spoiled, runtime_type: State }
              - { term: Compliant shipment, runtime_type: Outcome }
              - { term: "Cold-chain compliance rate", runtime_type: Learning }
              - { term: Spoilage rate, runtime_type: Learning }
  - name: "Industry & Manufacturing"
    os:
      - name: "n-manufactureOS"
        buyer: "VP of Manufacturing / Plant Manager who owns throughput, yield and on-time delivery for a production site."
        os_test: "Has its own buyer (operations leadership), its own budget (MES/production line of credit), a distinctive shop-floor frontend (work orders, routings, takt boards), a distinctive state model (order released → in-process → complete → shipped), and repeatable across every factory — a genuine OS, not a re-skin."
        sectors:
          - name: "Discrete Assembly & Final Assembly"
            operating_domains:
              - "Assembly line / takt-paced station"
              - Work order on a routing
              - "Bill of materials & kitting"
              - "Operator workstation & andon call"
              - "Line-side material flow (kanban)"
              - "First-pass-yield station check"
              - "Shift handover & line balancing"
            vocabulary:
              - { term: Line Operator, runtime_type: Actor }
              - { term: Work Order, runtime_type: Object }
              - { term: Bill of Materials, runtime_type: Artefact }
              - { term: Routing, runtime_type: Workflow }
              - { term: Andon Pull, runtime_type: Event }
              - { term: Station Cycle Complete, runtime_type: Event }
              - { term: "In-Process", runtime_type: State }
              - { term: Line Stopped, runtime_type: State }
              - { term: Rework or Scrap Call, runtime_type: Decision }
              - { term: Kit, runtime_type: Object }
              - { term: Build Record, runtime_type: Artefact }
              - { term: Units Shipped to Plan, runtime_type: Outcome }
              - { term: "First-Pass Yield", runtime_type: Learning }
              - { term: Takt Adherence, runtime_type: Learning }
          - name: "Process & Batch Manufacturing (chemicals, food, pharma)"
            note: "Pharma and food batch records are regulated (FDA 21 CFR Part 11, EU GMP); electronic batch records and lot traceability are mandated."
            operating_domains:
              - "Batch recipe & phase steps"
              - Reactor / vessel / mixer
              - "Charge & dispense of raw materials"
              - "In-line CIP (clean-in-place) cycle"
              - "Batch genealogy & lot tracing"
              - "Set-point control & deviation watch"
              - Yield reconciliation per batch
            vocabulary:
              - { term: Process Operator, runtime_type: Actor }
              - { term: Batch, runtime_type: Object }
              - { term: Master Recipe, runtime_type: Artefact }
              - { term: Phase Sequence, runtime_type: Workflow }
              - { term: Material Charge, runtime_type: Event }
              - { term: "Set-Point Deviation", runtime_type: Event }
              - { term: Cooking / Reacting, runtime_type: State }
              - { term: On Hold (QA), runtime_type: State }
              - { term: Release or Reprocess, runtime_type: Decision }
              - { term: Lot Number, runtime_type: Object }
              - { term: Batch Record, runtime_type: Artefact }
              - { term: Released Batch Quantity, runtime_type: Outcome }
              - { term: Batch Yield, runtime_type: Learning }
              - { term: "Right-First-Time Rate", runtime_type: Learning }
          - name: "Production Planning & Scheduling"
            operating_domains:
              - Master production schedule
              - Finite capacity scheduling board
              - Material requirements (MRP) run
              - "Changeover & sequence optimisation"
              - Demand vs. capacity load view
              - "Expedite & de-expedite queue"
              - Schedule attainment tracking
            vocabulary:
              - { term: Production Planner, runtime_type: Actor }
              - { term: Planned Order, runtime_type: Object }
              - { term: Master Schedule, runtime_type: Artefact }
              - { term: MRP Run, runtime_type: Workflow }
              - { term: Schedule Published, runtime_type: Event }
              - { term: Material Shortage Flagged, runtime_type: Event }
              - { term: Firm Planned, runtime_type: State }
              - { term: Capacity Overloaded, runtime_type: State }
              - { term: Resequence the Line, runtime_type: Decision }
              - { term: Changeover Slot, runtime_type: Object }
              - { term: Capacity Plan, runtime_type: Artefact }
              - { term: "On-Time-In-Full Delivery", runtime_type: Outcome }
              - { term: Schedule Attainment, runtime_type: Learning }
              - { term: Changeover Loss, runtime_type: Learning }
          - name: "Machining & Fabrication (CNC, metalworking)"
            operating_domains:
              - "CNC machine cell & tool magazine"
              - "Job setup & first-article inspection"
              - "Tool life & offset management"
              - "Spindle / cutting program (G-code)"
              - "Coolant & chip management"
              - "In-cycle dimensional check"
              - Machine utilisation tracking
            vocabulary:
              - { term: Machinist, runtime_type: Actor }
              - { term: Job, runtime_type: Object }
              - { term: NC Program, runtime_type: Artefact }
              - { term: Setup Sheet, runtime_type: Workflow }
              - { term: Tool Change, runtime_type: Event }
              - { term: Cycle Start, runtime_type: Event }
              - { term: Running, runtime_type: State }
              - { term: Idle / Waiting Setup, runtime_type: State }
              - { term: Scrap or Save Part, runtime_type: Decision }
              - { term: Cutting Tool, runtime_type: Object }
              - { term: "First-Article Report", runtime_type: Artefact }
              - { term: Good Parts Produced, runtime_type: Outcome }
              - { term: Spindle Utilisation, runtime_type: Learning }
              - { term: Tool Life per Edge, runtime_type: Learning }
          - name: "Contract Manufacturing & EMS"
            note: Aerospace/medical EMS work is governed by AS9100 / ISO 13485; traceability and certificates of conformance are contractually and legally required.
            operating_domains:
              - "Customer build package & spec"
              - New product introduction (NPI) ramp
              - "Approved vendor list & part sourcing"
              - Production traveller per serial
              - Customer quality reporting
              - Engineering change order handling
              - "Yield & cost per customer program"
            vocabulary:
              - { term: Program Manager, runtime_type: Actor }
              - { term: Customer Build Package, runtime_type: Object }
              - { term: Production Traveller, runtime_type: Artefact }
              - { term: NPI Ramp, runtime_type: Workflow }
              - { term: Engineering Change Released, runtime_type: Event }
              - { term: Build Authorised, runtime_type: Event }
              - { term: In Qualification, runtime_type: State }
              - { term: On Customer Hold, runtime_type: State }
              - { term: Accept Deviation Request, runtime_type: Decision }
              - { term: Serialised Unit, runtime_type: Object }
              - { term: Certificate of Conformance, runtime_type: Artefact }
              - { term: Program Margin, runtime_type: Outcome }
              - { term: Program Yield, runtime_type: Learning }
              - { term: "Ramp-to-Volume Time", runtime_type: Learning }
          - name: "Warehouse & Material Logistics (internal)"
            operating_domains:
              - "Receiving & inbound inspection dock"
              - "Storage bin & put-away location"
              - "Pick-pack-ship for finished goods"
              - "Cycle count & inventory accuracy"
              - "Line replenishment & milk run"
              - "Goods-in transit & WIP staging"
              - Inventory turns tracking
            vocabulary:
              - { term: Warehouse Operator, runtime_type: Actor }
              - { term: Pallet / Handling Unit, runtime_type: Object }
              - { term: Pick List, runtime_type: Artefact }
              - { term: "Put-Away Flow", runtime_type: Workflow }
              - { term: Goods Received, runtime_type: Event }
              - { term: Replenishment Triggered, runtime_type: Event }
              - { term: Available to Promise, runtime_type: State }
              - { term: Quarantined Stock, runtime_type: State }
              - { term: Allocate or Backorder, runtime_type: Decision }
              - { term: Storage Bin, runtime_type: Object }
              - { term: Goods Receipt Note, runtime_type: Artefact }
              - { term: Orders Shipped Complete, runtime_type: Outcome }
              - { term: Inventory Accuracy, runtime_type: Learning }
              - { term: Inventory Turns, runtime_type: Learning }
      - name: "n-qualityOS"
        buyer: "Quality Director / Head of QA who owns conformance, audit-readiness and the cost of poor quality."
        os_test: "Distinct buyer (quality function with its own budget), a distinctive frontend (inspection plans, NCRs, CAPA, audit findings), a distinctive state model (open → investigated → contained → closed/effective), and a distinctive vocabulary that production tooling does not own — a real OS, not a tab inside MES."
        sectors:
          - name: "Incoming & In-Process Inspection"
            operating_domains:
              - "Inspection plan & sampling rule"
              - Gauge / measurement instrument
              - "Characteristic & tolerance check"
              - "Non-conformance capture at source"
              - "Quarantine & disposition queue"
              - Supplier defect feedback loop
              - "Defect-rate trending"
            vocabulary:
              - { term: Quality Inspector, runtime_type: Actor }
              - { term: Inspection Lot, runtime_type: Object }
              - { term: Inspection Plan, runtime_type: Artefact }
              - { term: Sampling Workflow, runtime_type: Workflow }
              - { term: Measurement Recorded, runtime_type: Event }
              - { term: "Out-of-Tolerance Found", runtime_type: Event }
              - { term: Accepted, runtime_type: State }
              - { term: Quarantined, runtime_type: State }
              - { term: "Accept, Reject or Use-As-Is", runtime_type: Decision }
              - { term: Gauge, runtime_type: Object }
              - { term: Inspection Report, runtime_type: Artefact }
              - { term: Lots Released to Production, runtime_type: Outcome }
              - { term: Defect Parts Per Million, runtime_type: Learning }
              - { term: Supplier Defect Rate, runtime_type: Learning }
          - name: "Non-Conformance & CAPA"
            note: "In medical-device and pharma settings CAPA is a regulated record (FDA QSR 21 CFR 820 / ISO 13485) and must be auditable."
            operating_domains:
              - "Non-conformance report (NCR) intake"
              - "Containment & quarantine action"
              - "Root-cause investigation (8D / 5-Why)"
              - "Corrective & preventive action plan"
              - Effectiveness verification
              - Recurrence tracking by part/process
              - "Cost-of-poor-quality ledger"
            vocabulary:
              - { term: Quality Engineer, runtime_type: Actor }
              - { term: "Non-Conformance Report", runtime_type: Object }
              - { term: 8D Report, runtime_type: Artefact }
              - { term: CAPA Process, runtime_type: Workflow }
              - { term: NCR Raised, runtime_type: Event }
              - { term: Containment Applied, runtime_type: Event }
              - { term: Under Investigation, runtime_type: State }
              - { term: "Closed-Effective", runtime_type: State }
              - { term: Assign Root Cause, runtime_type: Decision }
              - { term: Corrective Action, runtime_type: Object }
              - { term: Verification Record, runtime_type: Artefact }
              - { term: Recurrence Eliminated, runtime_type: Outcome }
              - { term: CAPA Closure Time, runtime_type: Learning }
              - { term: Cost of Poor Quality, runtime_type: Learning }
          - name: "Calibration & Metrology"
            note: Calibration must be traceable to national standards (ISO/IEC 17025); accredited labs are formally regulated.
            operating_domains:
              - "Instrument register & cal schedule"
              - "Calibration certificate & standard"
              - "Out-of-tolerance impact assessment"
              - Reference standard traceability
              - Recall of suspect measurements
              - Cal due / overdue dashboard
              - Measurement system analysis (MSA)
            vocabulary:
              - { term: Calibration Technician, runtime_type: Actor }
              - { term: Measuring Instrument, runtime_type: Object }
              - { term: Calibration Certificate, runtime_type: Artefact }
              - { term: Calibration Cycle, runtime_type: Workflow }
              - { term: Calibration Due, runtime_type: Event }
              - { term: "Found Out-of-Tolerance", runtime_type: Event }
              - { term: In Calibration, runtime_type: State }
              - { term: Overdue / Out of Service, runtime_type: State }
              - { term: Quarantine Affected Measurements, runtime_type: Decision }
              - { term: Reference Standard, runtime_type: Object }
              - { term: Traceability Chain, runtime_type: Artefact }
              - { term: "Instruments Fit-for-Use", runtime_type: Outcome }
              - { term: Calibration Compliance Rate, runtime_type: Learning }
              - { term: "Gauge R&R", runtime_type: Learning }
          - name: Supplier Quality Management
            operating_domains:
              - "Supplier scorecard & rating"
              - "PPAP / first-article approval"
              - "Supplier audit & finding tracking"
              - "Incoming reject & charge-back"
              - Containment at supplier (controlled shipping)
              - Approved supplier list governance
              - Supplier performance trending
            vocabulary:
              - { term: Supplier Quality Engineer, runtime_type: Actor }
              - { term: Supplier, runtime_type: Actor }
              - { term: PPAP Submission, runtime_type: Object }
              - { term: Supplier Approval Workflow, runtime_type: Workflow }
              - { term: PPAP Approved, runtime_type: Event }
              - { term: "Charge-Back Issued", runtime_type: Event }
              - { term: Approved Source, runtime_type: State }
              - { term: On Controlled Shipping, runtime_type: State }
              - { term: Approve or Reject Submission, runtime_type: Decision }
              - { term: Supplier Scorecard, runtime_type: Artefact }
              - { term: Audit Finding Log, runtime_type: Artefact }
              - { term: Qualified Supply Base, runtime_type: Outcome }
              - { term: Supplier PPM, runtime_type: Learning }
              - { term: "On-Time Quality Delivery", runtime_type: Learning }
          - name: "Quality Management System & Audit"
            note: ISO 9001 / IATF 16949 / AS9100 certification audits are formal regulated assessments; document control and records retention are mandated.
            operating_domains:
              - "Controlled document & SOP library"
              - "Internal & external audit programme"
              - "Finding & observation tracking"
              - Management review cadence
              - "Training & competency records"
              - Change control governance
              - "Audit-readiness scorecard"
            vocabulary:
              - { term: Quality Manager, runtime_type: Actor }
              - { term: Auditor, runtime_type: Actor }
              - { term: Controlled Document, runtime_type: Object }
              - { term: Audit Programme, runtime_type: Workflow }
              - { term: Finding Raised, runtime_type: Event }
              - { term: Document Revised, runtime_type: Event }
              - { term: Effective / Released, runtime_type: State }
              - { term: "Non-Conformity Open", runtime_type: State }
              - { term: Accept or Escalate Finding, runtime_type: Decision }
              - { term: Standard Operating Procedure, runtime_type: Artefact }
              - { term: Audit Report, runtime_type: Artefact }
              - { term: Certification Maintained, runtime_type: Outcome }
              - { term: Audit Finding Closure Rate, runtime_type: Learning }
              - { term: Document Control Compliance, runtime_type: Learning }
      - name: "n-maintenanceOS"
        buyer: "Maintenance & Reliability Manager who owns asset uptime, maintenance cost and spare-parts inventory."
        os_test: "Own buyer (maintenance/reliability), own budget (CMMS + MRO spares), a distinctive frontend (asset register, work orders, PM schedules, condition alerts), a distinctive state model (failure → notified → planned → executed → returned to service), and a distinctive vocabulary — a real OS separate from production."
        sectors:
          - name: "Preventive & Planned Maintenance"
            operating_domains:
              - "Asset register & equipment hierarchy"
              - "PM schedule & task list"
              - Maintenance work order
              - "Backlog & planning board"
              - "Permit-to-work coordination"
              - "Spare-parts reservation per job"
              - PM compliance tracking
            vocabulary:
              - { term: Maintenance Technician, runtime_type: Actor }
              - { term: Asset, runtime_type: Object }
              - { term: PM Work Order, runtime_type: Object }
              - { term: PM Schedule, runtime_type: Workflow }
              - { term: Work Order Raised, runtime_type: Event }
              - { term: Job Completed, runtime_type: Event }
              - { term: In Service, runtime_type: State }
              - { term: Awaiting Parts, runtime_type: State }
              - { term: Defer or Execute Now, runtime_type: Decision }
              - { term: Task List, runtime_type: Artefact }
              - { term: Maintenance History Log, runtime_type: Artefact }
              - { term: Asset Uptime, runtime_type: Outcome }
              - { term: PM Compliance, runtime_type: Learning }
              - { term: Schedule Compliance Rate, runtime_type: Learning }
          - name: "Reactive Maintenance & Breakdowns"
            operating_domains:
              - Breakdown / fault notification
              - "Triage & priority assignment"
              - "Diagnosis & fault isolation"
              - Emergency spare sourcing
              - "Return-to-service sign-off"
              - "Repeat-failure flagging"
              - "Mean-time-to-repair tracking"
            vocabulary:
              - { term: Shift Maintainer, runtime_type: Actor }
              - { term: Breakdown Notification, runtime_type: Object }
              - { term: Fault Report, runtime_type: Artefact }
              - { term: Triage Flow, runtime_type: Workflow }
              - { term: Equipment Tripped, runtime_type: Event }
              - { term: Restored to Service, runtime_type: Event }
              - { term: Down, runtime_type: State }
              - { term: Limp Mode / Degraded, runtime_type: State }
              - { term: "Repair or Run-to-Failure", runtime_type: Decision }
              - { term: Replacement Part, runtime_type: Object }
              - { term: Repair Record, runtime_type: Artefact }
              - { term: Restored Availability, runtime_type: Outcome }
              - { term: Mean Time To Repair, runtime_type: Learning }
              - { term: Repeat Failure Rate, runtime_type: Learning }
          - name: "Predictive & Condition Monitoring"
            operating_domains:
              - "Sensor & condition data stream"
              - Vibration / thermal / oil analysis
              - "Alarm threshold & alert rule"
              - "Anomaly & failure-mode detection"
              - "Remaining-useful-life estimate"
              - "Inspection route & rounds"
              - "Avoided-failure tracking"
            vocabulary:
              - { term: Reliability Engineer, runtime_type: Actor }
              - { term: Monitored Asset, runtime_type: Object }
              - { term: Condition Reading, runtime_type: Artefact }
              - { term: Monitoring Route, runtime_type: Workflow }
              - { term: Threshold Crossed, runtime_type: Event }
              - { term: Anomaly Detected, runtime_type: Event }
              - { term: Healthy, runtime_type: State }
              - { term: Alarm / Degrading, runtime_type: State }
              - { term: Intervene or Keep Monitoring, runtime_type: Decision }
              - { term: Sensor, runtime_type: Object }
              - { term: Health Assessment Report, runtime_type: Artefact }
              - { term: Failures Avoided, runtime_type: Outcome }
              - { term: Remaining Useful Life, runtime_type: Learning }
              - { term: Prediction Accuracy, runtime_type: Learning }
          - name: "MRO Spare Parts & Storeroom"
            operating_domains:
              - "Spare-parts catalogue & criticality"
              - "Storeroom bin & stock level"
              - "Reorder point & min/max policy"
              - "Parts issue & return to job"
              - "Obsolescence & dead-stock review"
              - "Vendor lead-time tracking"
              - "Stockout-avoidance metric"
            vocabulary:
              - { term: Storeroom Keeper, runtime_type: Actor }
              - { term: Spare Part, runtime_type: Object }
              - { term: Parts Catalogue, runtime_type: Artefact }
              - { term: Replenishment Flow, runtime_type: Workflow }
              - { term: Part Issued to Job, runtime_type: Event }
              - { term: Reorder Point Hit, runtime_type: Event }
              - { term: In Stock, runtime_type: State }
              - { term: Stocked Out, runtime_type: State }
              - { term: "Stock or Source-on-Demand", runtime_type: Decision }
              - { term: Storeroom Bin, runtime_type: Object }
              - { term: Stock Issue Note, runtime_type: Artefact }
              - { term: Parts Availability, runtime_type: Outcome }
              - { term: Stockout Rate, runtime_type: Learning }
              - { term: Spares Carrying Cost, runtime_type: Learning }
          - name: "Asset Lifecycle & Capital Planning"
            operating_domains:
              - "Asset master & nameplate data"
              - "Lifecycle & replacement forecast"
              - "Capital project & retrofit request"
              - Total cost of ownership view
              - "Decommission & disposal record"
              - "Warranty & service contract tracking"
              - Asset health index scoring
            vocabulary:
              - { term: Asset Manager, runtime_type: Actor }
              - { term: Capital Asset, runtime_type: Object }
              - { term: Lifecycle Forecast, runtime_type: Artefact }
              - { term: Capital Planning Cycle, runtime_type: Workflow }
              - { term: Asset Commissioned, runtime_type: Event }
              - { term: Asset Decommissioned, runtime_type: Event }
              - { term: Operational, runtime_type: State }
              - { term: "End-of-Life", runtime_type: State }
              - { term: "Repair, Replace or Retire", runtime_type: Decision }
              - { term: Service Contract, runtime_type: Object }
              - { term: Disposal Record, runtime_type: Artefact }
              - { term: Extended Asset Life, runtime_type: Outcome }
              - { term: Total Cost of Ownership, runtime_type: Learning }
              - { term: Asset Health Index, runtime_type: Learning }
      - name: "n-energyOS"
        buyer: "Energy Manager / Plant Sustainability Lead who owns energy spend, carbon reporting and demand charges."
        os_test: "Distinct buyer (energy/sustainability with a separate cost centre), distinctive frontend (meter trees, load curves, tariff models, carbon ledger), distinctive state model (metered → reconciled → optimised → reported), and a vocabulary (kWh, demand charge, scope emissions) that no other OS owns — a real OS."
        sectors:
          - name: Industrial Energy Management
            note: Energy reporting may be subject to ISO 50001 and statutory schemes (e.g. UK ESOS / SECR); audited energy disclosures are regulated.
            operating_domains:
              - "Sub-meter tree & energy hierarchy"
              - "Load profile & demand curve"
              - "Tariff & demand-charge model"
              - "Energy baseline & target"
              - "Power factor & quality monitoring"
              - Energy KPI per unit of output
              - Energy reduction project tracking
            vocabulary:
              - { term: Energy Manager, runtime_type: Actor }
              - { term: Energy Meter, runtime_type: Object }
              - { term: Load Profile, runtime_type: Artefact }
              - { term: "Metering & Reconciliation", runtime_type: Workflow }
              - { term: Demand Peak Recorded, runtime_type: Event }
              - { term: Tariff Window Changed, runtime_type: Event }
              - { term: Within Baseline, runtime_type: State }
              - { term: Over Target, runtime_type: State }
              - { term: Shed or Hold Load, runtime_type: Decision }
              - { term: Energy Account, runtime_type: Object }
              - { term: Energy Report, runtime_type: Artefact }
              - { term: Energy Cost Saved, runtime_type: Outcome }
              - { term: Energy Intensity (kWh/unit), runtime_type: Learning }
              - { term: Power Factor, runtime_type: Learning }
          - name: "On-Site Generation & Renewables"
            note: "Grid export, settlement and generation licensing are regulated (e.g. Ofgem in the UK); PPAs and embedded benefits are contractually governed."
            operating_domains:
              - Generation asset (PV / CHP / wind)
              - Generation forecast vs. actual
              - "Grid export & import balance"
              - Power purchase agreement terms
              - "Curtailment & dispatch decision"
              - Maintenance window for generators
              - Renewable yield tracking
            vocabulary:
              - { term: Generation Operator, runtime_type: Actor }
              - { term: Generation Asset, runtime_type: Object }
              - { term: Generation Forecast, runtime_type: Artefact }
              - { term: Dispatch Schedule, runtime_type: Workflow }
              - { term: Export to Grid, runtime_type: Event }
              - { term: Curtailment Signal, runtime_type: Event }
              - { term: Generating, runtime_type: State }
              - { term: Curtailed, runtime_type: State }
              - { term: "Self-Consume or Export", runtime_type: Decision }
              - { term: Power Purchase Agreement, runtime_type: Object }
              - { term: Generation Settlement Statement, runtime_type: Artefact }
              - { term: Renewable Energy Delivered, runtime_type: Outcome }
              - { term: Capacity Factor, runtime_type: Learning }
              - { term: "Self-Consumption Ratio", runtime_type: Learning }
          - name: "Carbon & Emissions Accounting"
            note: "Carbon disclosure is increasingly mandatory (e.g. CSRD, SEC climate rules, EU ETS); reported figures require third-party assurance."
            operating_domains:
              - Emissions source inventory
              - Scope 1/2/3 ledger
              - Emission factor library
              - "Carbon target & glide path"
              - Reduction initiative pipeline
              - "Disclosure & verification pack"
              - Carbon intensity per product
            vocabulary:
              - { term: Sustainability Lead, runtime_type: Actor }
              - { term: Emissions Source, runtime_type: Object }
              - { term: Emission Factor, runtime_type: Artefact }
              - { term: Carbon Accounting Cycle, runtime_type: Workflow }
              - { term: Activity Data Captured, runtime_type: Event }
              - { term: Reduction Milestone Hit, runtime_type: Event }
              - { term: On Track to Target, runtime_type: State }
              - { term: "Off Glide-Path", runtime_type: State }
              - { term: "Reduce, Offset or Defer", runtime_type: Decision }
              - { term: Carbon Ledger Entry, runtime_type: Object }
              - { term: Disclosure Report, runtime_type: Artefact }
              - { term: Emissions Reduced, runtime_type: Outcome }
              - { term: Carbon Intensity per Product, runtime_type: Learning }
              - { term: Scope 3 Coverage, runtime_type: Learning }
          - name: "Demand Response & Flexibility"
            note: "Demand-response and capacity-market participation are governed by grid operator rules and settlement codes (e.g. National Grid ESO / balancing services)."
            operating_domains:
              - Flexible load register
              - "Demand-response event signal"
              - "Curtailment plan & playbook"
              - Capacity market commitment
              - Battery / storage dispatch
              - "Settlement & payment reconciliation"
              - Flexibility revenue tracking
            vocabulary:
              - { term: Flexibility Operator, runtime_type: Actor }
              - { term: Flexible Load, runtime_type: Object }
              - { term: Response Playbook, runtime_type: Artefact }
              - { term: Dispatch Response Flow, runtime_type: Workflow }
              - { term: DR Event Called, runtime_type: Event }
              - { term: Load Shed Confirmed, runtime_type: Event }
              - { term: Available to Respond, runtime_type: State }
              - { term: Responding / Dispatched, runtime_type: State }
              - { term: Participate or Opt Out, runtime_type: Decision }
              - { term: Storage Battery, runtime_type: Object }
              - { term: Settlement Statement, runtime_type: Artefact }
              - { term: Flexibility Revenue Earned, runtime_type: Outcome }
              - { term: Response Delivery Accuracy, runtime_type: Learning }
              - { term: Availability Factor, runtime_type: Learning }
          - name: "Compressed Air, Steam & Utilities-Within-Plant"
            operating_domains:
              - Compressor / boiler house assets
              - "Steam & air distribution network"
              - "Leak detection & loss survey"
              - "Set-point & pressure optimisation"
              - "Trap & condensate management"
              - Utility cost allocation to lines
              - Specific energy consumption tracking
            vocabulary:
              - { term: Utilities Engineer, runtime_type: Actor }
              - { term: Compressor / Boiler, runtime_type: Object }
              - { term: Distribution Network, runtime_type: Object }
              - { term: Leak Survey, runtime_type: Workflow }
              - { term: Pressure Drop Detected, runtime_type: Event }
              - { term: Leak Logged, runtime_type: Event }
              - { term: Optimised, runtime_type: State }
              - { term: Leaking / Inefficient, runtime_type: State }
              - { term: Repair or Tolerate Loss, runtime_type: Decision }
              - { term: Survey Report, runtime_type: Artefact }
              - { term: Cost Allocation Sheet, runtime_type: Artefact }
              - { term: Utility Losses Eliminated, runtime_type: Outcome }
              - { term: Specific Energy Consumption, runtime_type: Learning }
              - { term: Compressed Air Leak Rate, runtime_type: Learning }
      - name: "n-utilitiesOS"
        buyer: "Network / Utility Operations Director who owns service continuity, regulatory performance and network capital."
        os_test: "Distinct buyer (regulated utility operations), a distinctive frontend (network topology, outages, meter-to-cash, regulatory KPIs), a distinctive state model (energised → fault → isolated → restored), and a vocabulary tied to grid/water networks that plant-level OSs never use — clearly its own OS."
        sectors:
          - name: Electricity Distribution Network Operations
            note: "Distribution operators are licensed and performance-regulated (e.g. Ofgem RIIO in the UK); reliability indices carry financial incentives/penalties."
            operating_domains:
              - "Network topology & feeder map"
              - "Switching & isolation plan"
              - "Outage & fault management"
              - Load forecasting per substation
              - "Connection & new-supply request"
              - "Voltage & power-quality monitoring"
              - Network reliability (SAIDI/SAIFI) tracking
            vocabulary:
              - { term: Control Room Operator, runtime_type: Actor }
              - { term: Feeder / Substation, runtime_type: Object }
              - { term: Switching Programme, runtime_type: Artefact }
              - { term: Outage Restoration Flow, runtime_type: Workflow }
              - { term: Fault Detected, runtime_type: Event }
              - { term: Supply Restored, runtime_type: Event }
              - { term: Energised, runtime_type: State }
              - { term: Isolated, runtime_type: State }
              - { term: Reroute or Wait for Repair, runtime_type: Decision }
              - { term: Connection Request, runtime_type: Object }
              - { term: Outage Report, runtime_type: Artefact }
              - { term: Customer Minutes Restored, runtime_type: Outcome }
              - { term: SAIDI / SAIFI, runtime_type: Learning }
              - { term: Network Availability, runtime_type: Learning }
          - name: "Water & Wastewater Operations"
            note: "Water quality and discharge are statutorily regulated (e.g. DWI, Environment Agency, EU Water Framework Directive); consents and sampling are legally enforced."
            operating_domains:
              - "Treatment works & process stages"
              - "Pumping station & pressure zone"
              - "Water quality sampling & compliance"
              - "Leakage & burst-main management"
              - Discharge consent monitoring
              - "Network pressure & flow balancing"
              - "Compliance & quality KPI tracking"
            vocabulary:
              - { term: Treatment Operator, runtime_type: Actor }
              - { term: Treatment Works, runtime_type: Object }
              - { term: Quality Sample, runtime_type: Object }
              - { term: Treatment Process Flow, runtime_type: Workflow }
              - { term: Sample Taken, runtime_type: Event }
              - { term: Consent Breach Detected, runtime_type: Event }
              - { term: Within Consent, runtime_type: State }
              - { term: Out of Compliance, runtime_type: State }
              - { term: "Divert or Treat-On", runtime_type: Decision }
              - { term: Discharge Consent, runtime_type: Artefact }
              - { term: Compliance Sample Report, runtime_type: Artefact }
              - { term: Compliant Water Supplied, runtime_type: Outcome }
              - { term: Leakage Rate, runtime_type: Learning }
              - { term: Quality Compliance Rate, runtime_type: Learning }
          - name: "Gas Network & Pipeline Operations"
            note: "Gas transportation is safety-licensed (e.g. HSE Gas Safety Management Regulations); emergency-response times are legally mandated."
            operating_domains:
              - "Pipeline & main asset register"
              - "Pressure tier & regulator station"
              - Leak / escape report management
              - "Emergency isolation & make-safe"
              - Mains replacement programme
              - "Odour & gas-detection survey"
              - Network safety performance tracking
            vocabulary:
              - { term: Gas Network Engineer, runtime_type: Actor }
              - { term: Pipeline / Main, runtime_type: Object }
              - { term: Escape Report, runtime_type: Object }
              - { term: "Make-Safe Procedure", runtime_type: Workflow }
              - { term: Gas Escape Reported, runtime_type: Event }
              - { term: Supply Isolated, runtime_type: Event }
              - { term: Live, runtime_type: State }
              - { term: Capped / Made Safe, runtime_type: State }
              - { term: Repair or Replace Main, runtime_type: Decision }
              - { term: Regulator Station, runtime_type: Object }
              - { term: Survey Record, runtime_type: Artefact }
              - { term: Escapes Made Safe On Time, runtime_type: Outcome }
              - { term: Escape Response Time, runtime_type: Learning }
              - { term: Mains Replacement Rate, runtime_type: Learning }
          - name: "Metering, Billing & Meter-to-Cash"
            note: "Metering and billing follow regulated codes (e.g. supply licence conditions, smart-meter data privacy rules); estimates and back-billing are constrained by regulation."
            operating_domains:
              - "Meter register & reading schedule"
              - "Consumption & estimate management"
              - "Tariff & rate application"
              - "Billing run & exception queue"
              - "Smart-meter data validation"
              - "Dispute & adjustment handling"
              - Billing accuracy tracking
            vocabulary:
              - { term: Metering Operator, runtime_type: Actor }
              - { term: Meter, runtime_type: Object }
              - { term: Meter Reading, runtime_type: Object }
              - { term: "Meter-to-Cash Flow", runtime_type: Workflow }
              - { term: Reading Received, runtime_type: Event }
              - { term: Billing Exception Raised, runtime_type: Event }
              - { term: Billed, runtime_type: State }
              - { term: On Dispute, runtime_type: State }
              - { term: "Estimate or Re-Read", runtime_type: Decision }
              - { term: Tariff, runtime_type: Artefact }
              - { term: Customer Bill, runtime_type: Artefact }
              - { term: Revenue Collected, runtime_type: Outcome }
              - { term: Billing Accuracy, runtime_type: Learning }
              - { term: "Estimated-Read Ratio", runtime_type: Learning }
          - name: "Field Service & Network Workforce"
            note: Field work on live networks requires regulated safe systems of work and permits (e.g. electrical safety rules / CDM); competency authorisation is mandated.
            operating_domains:
              - "Field job dispatch & scheduling"
              - "Crew & vehicle resource pool"
              - "Permit & safe-system-of-work issue"
              - "Job pack & site instruction"
              - "First-time-fix on site"
              - "Mobile job completion & evidence"
              - Field productivity tracking
            vocabulary:
              - { term: Field Engineer, runtime_type: Actor }
              - { term: Dispatcher, runtime_type: Actor }
              - { term: Field Job, runtime_type: Object }
              - { term: "Dispatch & Scheduling Flow", runtime_type: Workflow }
              - { term: Job Dispatched, runtime_type: Event }
              - { term: Job Completed On Site, runtime_type: Event }
              - { term: En Route, runtime_type: State }
              - { term: On Site, runtime_type: State }
              - { term: "Complete or Return-Visit", runtime_type: Decision }
              - { term: Permit to Work, runtime_type: Artefact }
              - { term: Completion Evidence Pack, runtime_type: Artefact }
              - { term: Jobs Completed to SLA, runtime_type: Outcome }
              - { term: "First-Time-Fix Rate", runtime_type: Learning }
              - { term: Jobs per Crew per Day, runtime_type: Learning }
      - name: "n-industrialOS"
        buyer: "Director of Digital Manufacturing / OT Operations who owns the industrial control, data and automation backbone."
        os_test: "Distinct buyer (OT/automation/digital), distinctive frontend (control loops, OT asset inventory, recipe/parameter management, edge/data pipelines), a distinctive state model (commissioned → controlling → drifting → re-tuned), and a vocabulary (PLC, set-point, OT/IT, digital twin) that the operations OSs treat only as black boxes — a genuine OS."
        sectors:
          - name: "Industrial Control & Automation (PLC/SCADA/DCS)"
            note: "Safety-instrumented systems and interlocks are governed by functional-safety standards (IEC 61508 / 61511); SIL verification is required."
            operating_domains:
              - "Control loop & PID parameter"
              - "PLC / DCS program & logic"
              - "SCADA tag & HMI screen"
              - "Alarm rationalisation & flood control"
              - "Set-point & recipe download"
              - "Control-narrative & interlock map"
              - Loop performance tracking
            vocabulary:
              - { term: Control Engineer, runtime_type: Actor }
              - { term: Control Loop, runtime_type: Object }
              - { term: PLC Program, runtime_type: Artefact }
              - { term: "Set-Point Download Flow", runtime_type: Workflow }
              - { term: Alarm Triggered, runtime_type: Event }
              - { term: "Set-Point Changed", runtime_type: Event }
              - { term: In Automatic, runtime_type: State }
              - { term: In Manual / Bypassed, runtime_type: State }
              - { term: Auto or Manual Override, runtime_type: Decision }
              - { term: SCADA Tag, runtime_type: Object }
              - { term: Control Narrative, runtime_type: Artefact }
              - { term: Process Held in Control, runtime_type: Outcome }
              - { term: Loop Variability, runtime_type: Learning }
              - { term: Alarm Flood Rate, runtime_type: Learning }
          - name: "OT Cybersecurity & Network"
            note: "Critical industrial infrastructure is regulated for cyber resilience (e.g. NIS Regulations, IEC 62443); incident reporting can be legally mandated."
            operating_domains:
              - "OT asset inventory & zones"
              - "Network segmentation & conduits"
              - "Vulnerability & patch backlog"
              - "Anomalous-traffic detection"
              - "Remote-access governance"
              - Incident response playbook
              - "OT risk-exposure tracking"
            vocabulary:
              - { term: OT Security Engineer, runtime_type: Actor }
              - { term: OT Asset, runtime_type: Object }
              - { term: Asset Inventory, runtime_type: Artefact }
              - { term: Incident Response Flow, runtime_type: Workflow }
              - { term: Intrusion Detected, runtime_type: Event }
              - { term: Patch Applied, runtime_type: Event }
              - { term: Secure / Segmented, runtime_type: State }
              - { term: Exposed / At Risk, runtime_type: State }
              - { term: Isolate or Monitor, runtime_type: Decision }
              - { term: Security Zone, runtime_type: Object }
              - { term: Incident Report, runtime_type: Artefact }
              - { term: Threats Contained, runtime_type: Outcome }
              - { term: Mean Time To Detect, runtime_type: Learning }
              - { term: Patch Coverage, runtime_type: Learning }
          - name: "Industrial Data & Historian / Analytics"
            operating_domains:
              - "Time-series historian & tags"
              - "Data pipeline & contextualisation"
              - "KPI & dashboard authoring"
              - "Data-quality & gap monitoring"
              - Model / analytic deployment
              - "Self-serve analytics access"
              - "Data-availability tracking"
            vocabulary:
              - { term: Manufacturing Data Engineer, runtime_type: Actor }
              - { term: Historian Tag, runtime_type: Object }
              - { term: Data Pipeline, runtime_type: Workflow }
              - { term: Contextualisation Model, runtime_type: Artefact }
              - { term: Data Gap Detected, runtime_type: Event }
              - { term: Analytic Deployed, runtime_type: Event }
              - { term: Streaming / Live, runtime_type: State }
              - { term: Stale / Disconnected, runtime_type: State }
              - { term: Backfill or Discard, runtime_type: Decision }
              - { term: Dataset, runtime_type: Object }
              - { term: KPI Dashboard, runtime_type: Artefact }
              - { term: Decisions Informed by Data, runtime_type: Outcome }
              - { term: Data Availability, runtime_type: Learning }
              - { term: Tag Coverage, runtime_type: Learning }
          - name: "Robotics & Cobots"
            note: "Robot cell safety is regulated by machinery and functional-safety standards (ISO 10218 / ISO/TS 15066 for collaborative robots)."
            operating_domains:
              - "Robot cell & end-effector"
              - "Path / program teach & deploy"
              - "Cell safety & light-curtain zones"
              - "Cycle-time & throughput tuning"
              - "Gripper & tooling changeover"
              - "Fault recovery & re-home"
              - Robot utilisation tracking
            vocabulary:
              - { term: Robotics Technician, runtime_type: Actor }
              - { term: Robot Cell, runtime_type: Object }
              - { term: Robot Program / Path, runtime_type: Artefact }
              - { term: "Teach & Deploy Flow", runtime_type: Workflow }
              - { term: Cycle Triggered, runtime_type: Event }
              - { term: Safety Stop Hit, runtime_type: Event }
              - { term: Running Auto, runtime_type: State }
              - { term: Faulted / Estop, runtime_type: State }
              - { term: "Reset or Re-Teach", runtime_type: Decision }
              - { term: "End-Effector", runtime_type: Object }
              - { term: Cell Layout Spec, runtime_type: Artefact }
              - { term: Cells Running to Cycle, runtime_type: Outcome }
              - { term: Robot Utilisation, runtime_type: Learning }
              - { term: Mean Time Between Stops, runtime_type: Learning }
          - name: "Digital Twin & Simulation"
            operating_domains:
              - Plant / line digital model
              - "Simulation scenario & run"
              - "Model-to-reality calibration"
              - "What-if & bottleneck analysis"
              - "Commissioning & virtual test"
              - Parameter optimisation experiment
              - Model fidelity tracking
            vocabulary:
              - { term: Simulation Engineer, runtime_type: Actor }
              - { term: Digital Twin Model, runtime_type: Object }
              - { term: Scenario Definition, runtime_type: Artefact }
              - { term: Simulation Run Flow, runtime_type: Workflow }
              - { term: Run Completed, runtime_type: Event }
              - { term: Model Recalibrated, runtime_type: Event }
              - { term: Calibrated, runtime_type: State }
              - { term: Drifting from Reality, runtime_type: State }
              - { term: Adopt or Reject Scenario, runtime_type: Decision }
              - { term: Simulation Run, runtime_type: Object }
              - { term: Optimisation Result Pack, runtime_type: Artefact }
              - { term: Validated Design Change, runtime_type: Outcome }
              - { term: Model Fidelity, runtime_type: Learning }
              - { term: Prediction Error, runtime_type: Learning }
      - name: "n-safetyOS"
        buyer: "Head of HSE (Health, Safety & Environment) who owns incident rate, regulatory compliance and the licence to operate."
        os_test: "Distinct buyer (HSE function with its own statutory accountability and budget), a distinctive frontend (incidents, permits, risk assessments, observations, environmental consents), a distinctive state model (hazard → assessed → controlled → incident → investigated → closed), and a vocabulary that no operations OS owns — unmistakably its own OS."
        sectors:
          - name: "Incident & Investigation Management"
            note: "Serious incidents are legally reportable (e.g. RIDDOR in the UK, OSHA recordkeeping in the US); investigation records can be evidential."
            operating_domains:
              - "Incident & near-miss report"
              - "Severity triage & classification"
              - "Investigation (root-cause) workflow"
              - Corrective action tracking
              - Regulatory reportability check
              - "Lessons-learned distribution"
              - "Incident-rate trending"
            vocabulary:
              - { term: Safety Officer, runtime_type: Actor }
              - { term: Incident Report, runtime_type: Object }
              - { term: Investigation Pack, runtime_type: Artefact }
              - { term: Investigation Workflow, runtime_type: Workflow }
              - { term: Incident Reported, runtime_type: Event }
              - { term: Investigation Closed, runtime_type: Event }
              - { term: Under Investigation, runtime_type: State }
              - { term: "Closed-Verified", runtime_type: State }
              - { term: "Reportable or Internal-Only", runtime_type: Decision }
              - { term: Corrective Action, runtime_type: Object }
              - { term: "Lessons-Learned Bulletin", runtime_type: Artefact }
              - { term: Recurrence Prevented, runtime_type: Outcome }
              - { term: Total Recordable Incident Rate, runtime_type: Learning }
              - { term: "Lost-Time Injury Frequency", runtime_type: Learning }
          - name: "Permit to Work & Safe Systems"
            note: "Permit-to-work, LOTO and confined-space entry are legally mandated controls (e.g. HSE / OSHA 1910.147); breaches carry enforcement liability."
            operating_domains:
              - "Permit issue & authorisation"
              - "Isolation & lockout/tagout (LOTO)"
              - "Hot-work / confined-space control"
              - "Permit conflict & SIMOPS check"
              - "Gas test & atmosphere monitoring"
              - "Permit handback & close-out"
              - Permit compliance tracking
            vocabulary:
              - { term: Permit Authoriser, runtime_type: Actor }
              - { term: Work Permit, runtime_type: Object }
              - { term: Isolation Certificate, runtime_type: Artefact }
              - { term: Permit Issue Flow, runtime_type: Workflow }
              - { term: Permit Issued, runtime_type: Event }
              - { term: Permit Handed Back, runtime_type: Event }
              - { term: Active Permit, runtime_type: State }
              - { term: Suspended, runtime_type: State }
              - { term: Authorise or Reject Permit, runtime_type: Decision }
              - { term: Lockout Point, runtime_type: Object }
              - { term: Method Statement, runtime_type: Artefact }
              - { term: Work Done Without Harm, runtime_type: Outcome }
              - { term: Permit Compliance Rate, runtime_type: Learning }
              - { term: Isolation Error Rate, runtime_type: Learning }
          - name: "Risk Assessment & Hazard Control"
            note: "Risk assessments are a legal duty (e.g. Management of Health & Safety at Work Regulations); records must be suitable, sufficient and current."
            operating_domains:
              - "Hazard register & risk matrix"
              - Task / area risk assessment
              - "Control measure & hierarchy"
              - "Residual-risk acceptance sign-off"
              - "Review cadence & re-assessment"
              - Method statement library
              - "Risk-exposure tracking"
            vocabulary:
              - { term: Risk Assessor, runtime_type: Actor }
              - { term: Hazard, runtime_type: Object }
              - { term: Risk Assessment, runtime_type: Artefact }
              - { term: Assessment Review Cycle, runtime_type: Workflow }
              - { term: Hazard Identified, runtime_type: Event }
              - { term: Control Implemented, runtime_type: Event }
              - { term: Controlled / Tolerable, runtime_type: State }
              - { term: Unacceptable Risk, runtime_type: State }
              - { term: "Accept, Reduce or Eliminate", runtime_type: Decision }
              - { term: Control Measure, runtime_type: Object }
              - { term: Safe System of Work, runtime_type: Artefact }
              - { term: Risk Reduced to Tolerable, runtime_type: Outcome }
              - { term: Open High Risks, runtime_type: Learning }
              - { term: Assessment Currency, runtime_type: Learning }
          - name: "Environmental Compliance & Permits"
            note: "Environmental permits, emissions limits and waste consignment are statutorily regulated (e.g. Environment Agency / EPA); breaches are enforceable offences."
            operating_domains:
              - "Environmental permit & consent"
              - Emissions / discharge monitoring
              - "Waste classification & disposal"
              - "Spill & exceedance event log"
              - "Regulatory return & reporting"
              - "Audit & inspection readiness"
              - "Compliance-exceedance tracking"
            vocabulary:
              - { term: Environmental Manager, runtime_type: Actor }
              - { term: Environmental Permit, runtime_type: Object }
              - { term: Monitoring Return, runtime_type: Artefact }
              - { term: Compliance Reporting Flow, runtime_type: Workflow }
              - { term: Exceedance Recorded, runtime_type: Event }
              - { term: Spill Reported, runtime_type: Event }
              - { term: Within Permit Limits, runtime_type: State }
              - { term: In Breach, runtime_type: State }
              - { term: "Self-Report or Remediate First", runtime_type: Decision }
              - { term: Waste Consignment, runtime_type: Object }
              - { term: Compliance Certificate, runtime_type: Artefact }
              - { term: Permit Compliance Maintained, runtime_type: Outcome }
              - { term: Exceedance Count, runtime_type: Learning }
              - { term: Waste Diversion Rate, runtime_type: Learning }
          - name: "Occupational Health & Workforce Safety"
            note: "Health surveillance and exposure limits are legally mandated (e.g. COSHH, Control of Noise/Vibration Regulations); confidential health records carry data-protection duties."
            operating_domains:
              - Health surveillance schedule
              - Exposure monitoring (noise/dust/chem)
              - "Fitness-for-work & return-to-work"
              - "PPE issue & competency record"
              - Behavioural safety observation
              - "Toolbox talk & briefing log"
              - "Health-exposure trend tracking"
            vocabulary:
              - { term: Occupational Health Advisor, runtime_type: Actor }
              - { term: Worker Health Record, runtime_type: Object }
              - { term: Exposure Survey, runtime_type: Artefact }
              - { term: Health Surveillance Flow, runtime_type: Workflow }
              - { term: Exposure Recorded, runtime_type: Event }
              - { term: Safety Observation Logged, runtime_type: Event }
              - { term: Fit for Work, runtime_type: State }
              - { term: Restricted Duties, runtime_type: State }
              - { term: Clear or Refer Worker, runtime_type: Decision }
              - { term: PPE Issue Record, runtime_type: Object }
              - { term: Toolbox Talk Record, runtime_type: Artefact }
              - { term: Workforce Kept Healthy, runtime_type: Outcome }
              - { term: Exposure Exceedance Rate, runtime_type: Learning }
              - { term: Safe Behaviour Index, runtime_type: Learning }
  - name: "Media & Digital"
    os:
      - name: "n-mediaOS"
        buyer: "Head of digital / managing editor at a newsroom, broadcaster, or media company who owns the editorial production budget."
        os_test: "Distinct buyer (editor-in-chief vs ad ops vs platform), its own state model around the editorial lifecycle (pitch → fact-check → published → corrected), a newsroom-native vocabulary, and a repeatable population of newsrooms, wires, and broadcasters."
        sectors:
          - name: "Newsroom & Editorial Production"
            note: "Editorial standards, right-of-reply, and defamation/libel exposure are regulated; embargo and press-council codes apply."
            operating_domains:
              - Story pitches and the assignment desk
              - "The editorial calendar and run-of-show"
              - "Draft articles moving through copy and sub-editing"
              - "Fact-checking and source verification"
              - "Embargoed releases and breaking-news alerts"
              - "Corrections, updates and takedowns"
              - Photo desk and asset selection
              - Homepage and section curation
            vocabulary:
              - { term: Reporter, runtime_type: Actor }
              - { term: Assignment desk, runtime_type: Actor }
              - { term: Story, runtime_type: Object }
              - { term: Pitch, runtime_type: Object }
              - { term: Source, runtime_type: Object }
              - { term: Embargo lifted, runtime_type: Event }
              - { term: "Breaking-news alert", runtime_type: Event }
              - { term: "In sub-editing", runtime_type: State }
              - { term: Spike or run, runtime_type: Decision }
              - { term: Send to copy desk, runtime_type: Workflow }
              - { term: Published article, runtime_type: Artefact }
              - { term: Correction notice, runtime_type: Artefact }
              - { term: Story went live, runtime_type: Outcome }
              - { term: Pickup and citation count, runtime_type: Learning }
          - name: "Broadcast & Live Television"
            note: "Broadcast licence conditions, watershed/timing rules, captioning mandates and compliance logging are regulated."
            operating_domains:
              - The rundown and segment timing
              - Master control and playout schedule
              - Live studio gallery and camera cuts
              - "Lower-thirds and on-air graphics"
              - Satellite feeds and live remotes
              - "Ad-break insertion and station IDs"
              - Captioning and compliance logging
              - "Programme as-runs and reconciliation"
            vocabulary:
              - { term: Producer, runtime_type: Actor }
              - { term: Anchor, runtime_type: Actor }
              - { term: Segment, runtime_type: Object }
              - { term: Rundown, runtime_type: Object }
              - { term: "Lower-third", runtime_type: Artefact }
              - { term: Cut to live, runtime_type: Event }
              - { term: Ad break started, runtime_type: Event }
              - { term: On air, runtime_type: State }
              - { term: Take the next item, runtime_type: Decision }
              - { term: Roll the package, runtime_type: Workflow }
              - { term: "As-run log", runtime_type: Artefact }
              - { term: Programme aired clean, runtime_type: Outcome }
              - { term: Overrun in seconds, runtime_type: Learning }
          - name: "Investigative & Long-form Desk"
            note: "Source protection, defamation, and pre-publication legal clearance are regulated/privileged activities."
            operating_domains:
              - Document caches and leaked datasets
              - Source protection and secure dropboxes
              - "Legal review and pre-publication clearance"
              - Reporting timelines spanning months
              - Evidence boards linking people and entities
              - "Right-of-reply correspondence"
              - "Multi-part series planning"
              - Data analysis and reconciliation
            vocabulary:
              - { term: Investigative reporter, runtime_type: Actor }
              - { term: Whistleblower, runtime_type: Actor }
              - { term: Document cache, runtime_type: Object }
              - { term: Lead, runtime_type: Object }
              - { term: Evidence board, runtime_type: Object }
              - { term: Legal cleared it, runtime_type: Event }
              - { term: Under legal review, runtime_type: State }
              - { term: Publish or hold, runtime_type: Decision }
              - { term: "Send for pre-publication review", runtime_type: Workflow }
              - { term: Series exposé, runtime_type: Artefact }
              - { term: "Right-of-reply letter", runtime_type: Artefact }
              - { term: Story stood up, runtime_type: Outcome }
              - { term: "Impact and follow-on coverage", runtime_type: Learning }
          - name: "Wire Service & Syndication"
            note: "Content licensing, syndication rights and copyright terms govern redistribution."
            operating_domains:
              - Wire feed slugging and priority levels
              - "Multi-language transmission"
              - Subscriber distribution lists
              - Photo and video wire packages
              - Rate cards and licensing terms
              - "Take-downs and kill notices"
              - Story slugs and topic codes
              - Subscriber usage reporting
            vocabulary:
              - { term: Wire editor, runtime_type: Actor }
              - { term: Subscriber outlet, runtime_type: Actor }
              - { term: Wire item, runtime_type: Object }
              - { term: Slug, runtime_type: Object }
              - { term: Priority flash, runtime_type: Event }
              - { term: Kill notice issued, runtime_type: Event }
              - { term: On the wire, runtime_type: State }
              - { term: Set transmission priority, runtime_type: Decision }
              - { term: Transmit to subscribers, runtime_type: Workflow }
              - { term: Syndication package, runtime_type: Artefact }
              - { term: Licensing agreement, runtime_type: Artefact }
              - { term: Story carried by outlets, runtime_type: Outcome }
              - { term: Pickup rate by subscriber, runtime_type: Learning }
          - name: "Audience & Distribution"
            operating_domains:
              - "Homepage and app-feed curation"
              - Push notifications and alerts
              - Newsletter editions and sends
              - Paywall and metering rules
              - SEO headlines and tagging
              - Social distribution scheduling
              - Traffic and engagement dashboards
              - A/B headline testing
            vocabulary:
              - { term: Audience editor, runtime_type: Actor }
              - { term: Subscriber, runtime_type: Actor }
              - { term: Headline variant, runtime_type: Object }
              - { term: Newsletter edition, runtime_type: Object }
              - { term: Push sent, runtime_type: Event }
              - { term: Paywall hit, runtime_type: Event }
              - { term: Behind the paywall, runtime_type: State }
              - { term: Promote to homepage, runtime_type: Decision }
              - { term: Schedule the send, runtime_type: Workflow }
              - { term: Curated front page, runtime_type: Artefact }
              - { term: Subscription conversion, runtime_type: Outcome }
              - { term: "Click-through and dwell time", runtime_type: Learning }
      - name: "n-socialOS"
        buyer: "Head of social / community manager at a brand, agency, or platform team who owns the social presence and moderation budget."
        os_test: "Buyer is the social/community lead (not the editor or the ad buyer), with a distinct state model around posts, conversations, and moderation queues, a platform-native vocabulary (feeds, threads, mentions, bans), and thousands of repeatable social teams and platforms."
        sectors:
          - name: Social Media Management
            operating_domains:
              - The content calendar across channels
              - Drafts and scheduled posts
              - "Cross-network publishing"
              - "Approval workflows and sign-off"
              - Hashtag and asset libraries
              - Reply and mention monitoring
              - Campaign tagging and link tracking
              - Performance reporting per channel
            vocabulary:
              - { term: Social manager, runtime_type: Actor }
              - { term: Follower, runtime_type: Actor }
              - { term: Post, runtime_type: Object }
              - { term: Content calendar, runtime_type: Object }
              - { term: Post published, runtime_type: Event }
              - { term: Mention received, runtime_type: Event }
              - { term: Scheduled, runtime_type: State }
              - { term: Approve or reject post, runtime_type: Decision }
              - { term: "Route for sign-off", runtime_type: Workflow }
              - { term: Carousel asset, runtime_type: Artefact }
              - { term: Campaign report, runtime_type: Artefact }
              - { term: Post went viral, runtime_type: Outcome }
              - { term: Engagement rate, runtime_type: Learning }
          - name: Community Management
            operating_domains:
              - Member onboarding and roles
              - Discussion threads and channels
              - Reputation and trust levels
              - Events and AMAs
              - "Rules, pinned posts and onboarding flows"
              - Reports and escalations
              - Sentiment and health tracking
              - Ambassador and mod programmes
            vocabulary:
              - { term: Community member, runtime_type: Actor }
              - { term: Moderator, runtime_type: Actor }
              - { term: Thread, runtime_type: Object }
              - { term: Channel, runtime_type: Object }
              - { term: Member joined, runtime_type: Event }
              - { term: Report filed, runtime_type: Event }
              - { term: Pending approval, runtime_type: State }
              - { term: Grant or revoke role, runtime_type: Decision }
              - { term: Onboard new member, runtime_type: Workflow }
              - { term: Pinned guidelines, runtime_type: Artefact }
              - { term: Community grew, runtime_type: Outcome }
              - { term: Community health score, runtime_type: Learning }
          - name: "Trust & Safety / Content Moderation"
            note: "Subject to platform-liability and online-safety regimes (e.g. DSA, Online Safety Act); illegal-content removal is legally mandated."
            operating_domains:
              - The moderation queue and severity tiers
              - Policy rules and decision trees
              - User reports and appeals
              - "Account actions (warn, suspend, ban)"
              - "Known-harm hash databases"
              - "Reviewer workflows and double-checks"
              - Audit trails for enforcement
              - Transparency reporting
            vocabulary:
              - { term: Reviewer, runtime_type: Actor }
              - { term: Reported user, runtime_type: Actor }
              - { term: Flagged item, runtime_type: Object }
              - { term: Policy rule, runtime_type: Object }
              - { term: Report escalated, runtime_type: Event }
              - { term: Appeal submitted, runtime_type: Event }
              - { term: Awaiting review, runtime_type: State }
              - { term: "Remove, suspend or allow", runtime_type: Decision }
              - { term: Run through escalation tier, runtime_type: Workflow }
              - { term: Enforcement record, runtime_type: Artefact }
              - { term: Account actioned, runtime_type: Outcome }
              - { term: "Time-to-action and accuracy", runtime_type: Learning }
          - name: "Influencer & Creator Partnerships"
            note: "Advertising-disclosure rules (e.g. FTC, ASA) require clear sponsorship labelling."
            operating_domains:
              - Creator discovery and shortlists
              - Briefs and deliverable schedules
              - Contracts and usage rights
              - Content approval and revisions
              - "Disclosure and #ad compliance"
              - Payment milestones
              - Campaign performance tracking
              - Whitelisting and boosting
            vocabulary:
              - { term: Brand manager, runtime_type: Actor }
              - { term: Influencer, runtime_type: Actor }
              - { term: Brief, runtime_type: Object }
              - { term: Deliverable, runtime_type: Object }
              - { term: Content submitted, runtime_type: Event }
              - { term: Approved for posting, runtime_type: State }
              - { term: Approve or request revision, runtime_type: Decision }
              - { term: Send brief and collect drafts, runtime_type: Workflow }
              - { term: Partnership agreement, runtime_type: Artefact }
              - { term: Sponsored post, runtime_type: Artefact }
              - { term: Campaign delivered, runtime_type: Outcome }
              - { term: Cost per engagement, runtime_type: Learning }
          - name: "Social Listening & Reputation"
            operating_domains:
              - "Keyword and brand-mention tracking"
              - Sentiment streams and spikes
              - Crisis detection and alerting
              - "Share-of-voice benchmarking"
              - Topic and trend clustering
              - Influencer/critic identification
              - Response playbooks
              - Executive reputation dashboards
            vocabulary:
              - { term: Analyst, runtime_type: Actor }
              - { term: Brand advocate, runtime_type: Actor }
              - { term: Mention, runtime_type: Object }
              - { term: Tracked keyword, runtime_type: Object }
              - { term: Sentiment spike, runtime_type: Event }
              - { term: Crisis flagged, runtime_type: Event }
              - { term: Trending negative, runtime_type: State }
              - { term: Respond or monitor, runtime_type: Decision }
              - { term: Trigger crisis playbook, runtime_type: Workflow }
              - { term: Listening report, runtime_type: Artefact }
              - { term: Reputation recovered, runtime_type: Outcome }
              - { term: Share of voice, runtime_type: Learning }
      - name: "n-creatorOS"
        buyer: "The independent creator or their small management team who owns their channels, monetisation, and production budget."
        os_test: "Buyer is the creator/talent themselves (not a newsroom or platform), with a state model around content pipelines and revenue streams, creator-economy vocabulary (uploads, drops, tiers, payouts), and a large repeatable population of professional creators and MCNs."
        sectors:
          - name: Content Production Pipeline
            operating_domains:
              - Idea backlog and content buckets
              - Scripting and storyboards
              - Filming and shoot days
              - Editing and revisions
              - Thumbnails and titles
              - Upload and scheduling
              - Series and playlist planning
              - Repurposing into clips
            vocabulary:
              - { term: Creator, runtime_type: Actor }
              - { term: Editor, runtime_type: Actor }
              - { term: Video, runtime_type: Object }
              - { term: Script, runtime_type: Object }
              - { term: Upload published, runtime_type: Event }
              - { term: In editing, runtime_type: State }
              - { term: Publish or hold for batch, runtime_type: Decision }
              - { term: Move idea to production, runtime_type: Workflow }
              - { term: Final cut, runtime_type: Artefact }
              - { term: Thumbnail, runtime_type: Artefact }
              - { term: Video went live, runtime_type: Outcome }
              - { term: Average view duration, runtime_type: Learning }
          - name: "Monetisation & Revenue"
            note: "Sponsored-content disclosure and tax-reporting obligations apply to creator earnings."
            operating_domains:
              - "Ad-revenue and RPM tracking"
              - "Brand-deal pipeline"
              - Membership and subscription tiers
              - Merch drops and inventory
              - Affiliate links and codes
              - "Tips, super-chats and donations"
              - Payout schedules across platforms
              - "Rate-card and negotiation"
            vocabulary:
              - { term: Creator, runtime_type: Actor }
              - { term: Sponsor, runtime_type: Actor }
              - { term: Brand deal, runtime_type: Object }
              - { term: Membership tier, runtime_type: Object }
              - { term: Payout cleared, runtime_type: Event }
              - { term: Deal signed, runtime_type: Event }
              - { term: Awaiting payout, runtime_type: State }
              - { term: Accept or counter the offer, runtime_type: Decision }
              - { term: Invoice and collect payment, runtime_type: Workflow }
              - { term: Sponsorship contract, runtime_type: Artefact }
              - { term: Monthly revenue hit target, runtime_type: Outcome }
              - { term: Revenue per thousand views, runtime_type: Learning }
          - name: "Audience Growth & Channel Analytics"
            operating_domains:
              - Subscriber and follower funnels
              - "Retention and drop-off curves"
              - "Traffic-source breakdowns"
              - Algorithm signals and CTR
              - "Cross-platform growth"
              - Community posts and polls
              - "Trend-jacking opportunities"
              - Competitor benchmarking
            vocabulary:
              - { term: Subscriber, runtime_type: Actor }
              - { term: Channel, runtime_type: Object }
              - { term: Retention curve, runtime_type: Object }
              - { term: Subscriber milestone hit, runtime_type: Event }
              - { term: Trending, runtime_type: State }
              - { term: Double down or pivot content, runtime_type: Decision }
              - { term: Analyse and adjust strategy, runtime_type: Workflow }
              - { term: Analytics snapshot, runtime_type: Artefact }
              - { term: Channel hit a growth tier, runtime_type: Outcome }
              - { term: "Click-through rate", runtime_type: Learning }
              - { term: Audience analyst, runtime_type: Actor }
              - { term: Watch hours, runtime_type: Object }
          - name: Live Streaming
            operating_domains:
              - "Stream schedule and go-live"
              - Scene switching and overlays
              - Chat moderation and bots
              - Alerts and donation goals
              - Raids and host coordination
              - Clip capture and highlights
              - Subscriber perks and emotes
              - Stream health and bitrate
            vocabulary:
              - { term: Streamer, runtime_type: Actor }
              - { term: Chat moderator, runtime_type: Actor }
              - { term: Stream, runtime_type: Object }
              - { term: Overlay scene, runtime_type: Object }
              - { term: Went live, runtime_type: Event }
              - { term: Raid incoming, runtime_type: Event }
              - { term: Live now, runtime_type: State }
              - { term: Switch scene or end stream, runtime_type: Decision }
              - { term: Start the broadcast, runtime_type: Workflow }
              - { term: Highlight clip, runtime_type: Artefact }
              - { term: Stream hit concurrent peak, runtime_type: Outcome }
              - { term: Average concurrent viewers, runtime_type: Learning }
          - name: "Talent Management & Brand"
            note: "Talent representation, likeness/IP rights and exclusivity clauses are contractually regulated."
            operating_domains:
              - Roster of represented creators
              - Inbound deal inbox
              - Calendar and availability
              - "Rights, likeness and IP"
              - "Personal-brand assets and kits"
              - PR and press opportunities
              - Career and content roadmap
              - Conflict and exclusivity tracking
            vocabulary:
              - { term: Manager, runtime_type: Actor }
              - { term: Represented creator, runtime_type: Actor }
              - { term: Deal inquiry, runtime_type: Object }
              - { term: Roster slot, runtime_type: Object }
              - { term: Offer came in, runtime_type: Event }
              - { term: Under negotiation, runtime_type: State }
              - { term: Take or pass on opportunity, runtime_type: Decision }
              - { term: Vet and route the deal, runtime_type: Workflow }
              - { term: Media kit, runtime_type: Artefact }
              - { term: Management agreement, runtime_type: Artefact }
              - { term: Creator signed a major deal, runtime_type: Outcome }
              - { term: Deal close rate, runtime_type: Learning }
      - name: "n-gameOS"
        buyer: "Studio head / live-ops director / publisher who owns the game's development and live-service budget."
        os_test: "Buyer is the game studio/publisher (distinct from media or streaming), with a state model around builds, live services, and player economies, deeply game-native vocabulary (sprints, patches, seasons, ban waves), and a repeatable population of studios and publishers."
        sectors:
          - name: Game Development Production
            note: "Platform certification and age-rating (PEGI/ESRB) approvals are required before release."
            operating_domains:
              - Feature backlog and sprints
              - Builds and version branches
              - Bug tracking and triage
              - Milestone and vertical slices
              - Asset pipeline and reviews
              - Playtests and feedback loops
              - Certification submissions
              - Release candidates
            vocabulary:
              - { term: Game designer, runtime_type: Actor }
              - { term: QA tester, runtime_type: Actor }
              - { term: Build, runtime_type: Object }
              - { term: Bug ticket, runtime_type: Object }
              - { term: Build broke, runtime_type: Event }
              - { term: Milestone reached, runtime_type: Event }
              - { term: In QA, runtime_type: State }
              - { term: Ship or slip the milestone, runtime_type: Decision }
              - { term: Submit for certification, runtime_type: Workflow }
              - { term: Release candidate, runtime_type: Artefact }
              - { term: Gold master shipped, runtime_type: Outcome }
              - { term: Crash rate, runtime_type: Learning }
          - name: "Live Ops & Game Economy"
            note: "Loot-box and paid-currency mechanics face gambling-adjacent regulation and spend-disclosure rules in several jurisdictions."
            operating_domains:
              - Seasons and battle passes
              - "Live events and limited-time modes"
              - "In-game economy and sinks/sources"
              - Patch and hotfix cadence
              - Store rotation and offers
              - Player segmentation and targeting
              - A/B tested tuning
              - Currency and item catalogue
            vocabulary:
              - { term: "Live-ops manager", runtime_type: Actor }
              - { term: Player, runtime_type: Actor }
              - { term: Season, runtime_type: Object }
              - { term: "In-game item", runtime_type: Object }
              - { term: Event went live, runtime_type: Event }
              - { term: Hotfix deployed, runtime_type: Event }
              - { term: Live event running, runtime_type: State }
              - { term: Buff or nerf the economy, runtime_type: Decision }
              - { term: Roll out the patch, runtime_type: Workflow }
              - { term: Patch notes, runtime_type: Artefact }
              - { term: Engagement spiked this season, runtime_type: Outcome }
              - { term: Daily active users, runtime_type: Learning }
          - name: "Player Community & Support"
            operating_domains:
              - Support tickets and refunds
              - Player reports and ban waves
              - Forums and feedback channels
              - Patch communication
              - Account recovery
              - "Anti-cheat enforcement"
              - Sentiment and review monitoring
              - Player surveys
            vocabulary:
              - { term: Support agent, runtime_type: Actor }
              - { term: Player account, runtime_type: Actor }
              - { term: Support ticket, runtime_type: Object }
              - { term: Player report, runtime_type: Object }
              - { term: Cheat detected, runtime_type: Event }
              - { term: Refund requested, runtime_type: Event }
              - { term: Account suspended, runtime_type: State }
              - { term: Ban or warn the account, runtime_type: Decision }
              - { term: Run the ban wave, runtime_type: Workflow }
              - { term: Resolution note, runtime_type: Artefact }
              - { term: Player retained after issue, runtime_type: Outcome }
              - { term: Ticket resolution time, runtime_type: Learning }
          - name: "Esports & Competitive"
            note: "Prize distribution, player contracts, and integrity/anti-match-fixing rules carry regulatory and contractual obligations."
            operating_domains:
              - Tournament brackets and seeding
              - Match scheduling and casting
              - Team and roster registration
              - Rulebooks and referee decisions
              - "Prize-pool distribution"
              - "Anti-cheat and integrity"
              - Broadcast production
              - Ranking and leaderboards
            vocabulary:
              - { term: Tournament organiser, runtime_type: Actor }
              - { term: Pro player, runtime_type: Actor }
              - { term: Match, runtime_type: Object }
              - { term: Bracket, runtime_type: Object }
              - { term: Match started, runtime_type: Event }
              - { term: Roster locked, runtime_type: State }
              - { term: Uphold or overturn the call, runtime_type: Decision }
              - { term: Run the tournament, runtime_type: Workflow }
              - { term: Final standings, runtime_type: Artefact }
              - { term: "Prize-pool payout", runtime_type: Artefact }
              - { term: Championship decided, runtime_type: Outcome }
              - { term: Viewership peak, runtime_type: Learning }
          - name: "Game Publishing & Storefront"
            operating_domains:
              - "Store-page and listing assets"
              - Pricing and regional tiers
              - "Wishlists and pre-orders"
              - Launch and release windows
              - Discount campaigns and sales
              - "Revenue-share and payouts"
              - Localisation and ratings
              - DLC and bundle catalogue
            vocabulary:
              - { term: Publisher, runtime_type: Actor }
              - { term: Customer, runtime_type: Actor }
              - { term: Store listing, runtime_type: Object }
              - { term: Price tier, runtime_type: Object }
              - { term: Game launched, runtime_type: Event }
              - { term: Wishlist hit threshold, runtime_type: Event }
              - { term: "Pre-order live", runtime_type: State }
              - { term: Set the launch discount, runtime_type: Decision }
              - { term: Publish to the storefront, runtime_type: Workflow }
              - { term: Store page, runtime_type: Artefact }
              - { term: Launch sales target met, runtime_type: Outcome }
              - { term: Wishlist conversion rate, runtime_type: Learning }
      - name: "n-streamOS"
        buyer: "VP of content / programming or product lead at a streaming service who owns the catalogue, encoding, and subscriber budget."
        os_test: "Buyer runs a streaming platform (distinct from broadcast newsroom or creator), with a state model around content licensing, encoding pipelines, and subscriber lifecycles, OTT-native vocabulary (windows, transcodes, CDN, churn), and a repeatable population of SVOD/AVOD services."
        sectors:
          - name: "Content Acquisition & Licensing"
            note: "Content licensing, territory rights and music-clearance are legally governed."
            operating_domains:
              - Title pipeline and pitches
              - Licensing windows and territories
              - Rights and exclusivity
              - Deal terms and minimum guarantees
              - Catalogue gaps and slate planning
              - Renewal and expiry tracking
              - Content cost amortisation
              - Originals commissioning
            vocabulary:
              - { term: Content acquisition lead, runtime_type: Actor }
              - { term: Rights holder, runtime_type: Actor }
              - { term: Title, runtime_type: Object }
              - { term: Licensing window, runtime_type: Object }
              - { term: Rights expired, runtime_type: Event }
              - { term: Deal closed, runtime_type: Event }
              - { term: Under negotiation, runtime_type: State }
              - { term: License or pass on the title, runtime_type: Decision }
              - { term: Clear rights and onboard title, runtime_type: Workflow }
              - { term: Licensing agreement, runtime_type: Artefact }
              - { term: Title acquired for catalogue, runtime_type: Outcome }
              - { term: Cost per viewing hour, runtime_type: Learning }
          - name: "Encoding & Media Supply Chain"
            note: "DRM, accessibility/captioning mandates and content-protection terms apply."
            operating_domains:
              - Ingest and source masters
              - Transcode profiles and renditions
              - Subtitle and caption files
              - QC and compliance checks
              - Packaging and DRM
              - CDN distribution and caching
              - Metadata and artwork
              - "Failed-asset reprocessing"
            vocabulary:
              - { term: Media operations engineer, runtime_type: Actor }
              - { term: Source master, runtime_type: Object }
              - { term: Transcode profile, runtime_type: Object }
              - { term: Encode finished, runtime_type: Event }
              - { term: QC failed, runtime_type: Event }
              - { term: In transcoding, runtime_type: State }
              - { term: Approve or reject the asset, runtime_type: Decision }
              - { term: Run the encoding pipeline, runtime_type: Workflow }
              - { term: Packaged stream, runtime_type: Artefact }
              - { term: Caption file, runtime_type: Artefact }
              - { term: Title ready to stream, runtime_type: Outcome }
              - { term: Encode success rate, runtime_type: Learning }
          - name: "Programming & Merchandising"
            operating_domains:
              - "Home-page rows and rails"
              - Collections and editorial spotlights
              - Personalised recommendations
              - Release scheduling and drops
              - Artwork and trailer selection
              - Regional catalogue tailoring
              - Featured and hero placement
              - Title performance tracking
            vocabulary:
              - { term: Programmer, runtime_type: Actor }
              - { term: Subscriber, runtime_type: Actor }
              - { term: Row, runtime_type: Object }
              - { term: Collection, runtime_type: Object }
              - { term: Title dropped, runtime_type: Event }
              - { term: Featured on home, runtime_type: State }
              - { term: Promote or bury the title, runtime_type: Decision }
              - { term: Schedule the release, runtime_type: Workflow }
              - { term: Curated home page, runtime_type: Artefact }
              - { term: "Title drove sign-ups", runtime_type: Outcome }
              - { term: "Play-through rate", runtime_type: Learning }
              - { term: Hero banner, runtime_type: Artefact }
          - name: "Subscriber Lifecycle & Billing"
            note: "Subscription auto-renewal disclosure and cancellation-ease rules are regulated in several markets."
            operating_domains:
              - "Sign-up and trial flows"
              - "Plan tiers and add-ons"
              - Billing and dunning
              - "Churn and win-back"
              - Profiles and household sharing
              - Promotions and bundles
              - "Payment-failure recovery"
              - Subscription analytics
            vocabulary:
              - { term: Growth manager, runtime_type: Actor }
              - { term: Subscriber, runtime_type: Actor }
              - { term: Subscription plan, runtime_type: Object }
              - { term: Trial, runtime_type: Object }
              - { term: Payment failed, runtime_type: Event }
              - { term: Subscriber cancelled, runtime_type: Event }
              - { term: At risk of churn, runtime_type: State }
              - { term: "Offer a win-back deal", runtime_type: Decision }
              - { term: Run the dunning sequence, runtime_type: Workflow }
              - { term: Invoice, runtime_type: Artefact }
              - { term: Subscriber retained, runtime_type: Outcome }
              - { term: Monthly churn rate, runtime_type: Learning }
          - name: "Streaming Quality & Delivery"
            operating_domains:
              - Playback sessions and QoE
              - Buffering and rebuffer events
              - Bitrate ladders and ABR
              - CDN routing and failover
              - Device and player coverage
              - "Concurrent-stream limits"
              - "Start-up time monitoring"
              - Incident response
            vocabulary:
              - { term: Streaming engineer, runtime_type: Actor }
              - { term: Viewer, runtime_type: Actor }
              - { term: Playback session, runtime_type: Object }
              - { term: Bitrate ladder, runtime_type: Object }
              - { term: Rebuffer occurred, runtime_type: Event }
              - { term: CDN failover triggered, runtime_type: Event }
              - { term: Degraded playback, runtime_type: State }
              - { term: Reroute or scale capacity, runtime_type: Decision }
              - { term: Run incident response, runtime_type: Workflow }
              - { term: Incident report, runtime_type: Artefact }
              - { term: Stream quality recovered, runtime_type: Outcome }
              - { term: Rebuffer ratio, runtime_type: Learning }
      - name: "n-advertisingOS"
        buyer: "Media buyer / ad-ops director at an agency, brand, or publisher who owns the campaign and yield budget."
        os_test: "Buyer is the advertiser/ad-ops side (distinct from editorial or social), with a state model around campaigns, inventory, and bids, ad-tech-native vocabulary (impressions, RTB, fill rate, attribution), and a deep repeatable population of agencies, ad networks, and publisher ad-ops teams."
        sectors:
          - name: "Campaign Management & Media Buying"
            note: "Targeting and consent are governed by privacy regimes (GDPR/CCPA); political-ad disclosure rules apply."
            operating_domains:
              - Campaign briefs and objectives
              - Audience targeting segments
              - Budget pacing and flighting
              - Creative trafficking
              - Bid strategies and caps
              - Insertion orders
              - Optimisation rules
              - "Cross-channel performance"
            vocabulary:
              - { term: Media buyer, runtime_type: Actor }
              - { term: Advertiser, runtime_type: Actor }
              - { term: Campaign, runtime_type: Object }
              - { term: Audience segment, runtime_type: Object }
              - { term: Budget exhausted, runtime_type: Event }
              - { term: Campaign live, runtime_type: State }
              - { term: Pause or scale the campaign, runtime_type: Decision }
              - { term: Launch and pace the buy, runtime_type: Workflow }
              - { term: Insertion order, runtime_type: Artefact }
              - { term: Campaign hit its goal, runtime_type: Outcome }
              - { term: Cost per acquisition, runtime_type: Learning }
              - { term: Conversion recorded, runtime_type: Event }
          - name: "Programmatic & Real-Time Bidding"
            note: "Ad-fraud, brand-safety and consent-string (TCF) handling are regulated/standardised."
            operating_domains:
              - Bid requests and auctions
              - Deal IDs and private marketplaces
              - "Supply-path optimisation"
              - Floor prices and bid shading
              - "Fraud and brand-safety filters"
              - Win/loss bid analysis
              - Frequency capping
              - Inventory forecasting
            vocabulary:
              - { term: Programmatic trader, runtime_type: Actor }
              - { term: Supply partner, runtime_type: Actor }
              - { term: Bid request, runtime_type: Object }
              - { term: Deal ID, runtime_type: Object }
              - { term: Auction won, runtime_type: Event }
              - { term: Bid throttled, runtime_type: State }
              - { term: Bid or skip the impression, runtime_type: Decision }
              - { term: Run the bidding strategy, runtime_type: Workflow }
              - { term: "Win-rate report", runtime_type: Artefact }
              - { term: Impressions delivered at target CPM, runtime_type: Outcome }
              - { term: Win rate, runtime_type: Learning }
              - { term: Invalid traffic flagged, runtime_type: Event }
          - name: "Ad Sales & Yield (Sell-Side)"
            operating_domains:
              - Inventory and avails
              - Rate cards and packages
              - Direct sold vs programmatic mix
              - Yield and fill optimisation
              - Order booking and forecasting
              - "Make-goods and shortfalls"
              - Sponsorships and takeovers
              - Revenue reconciliation
            vocabulary:
              - { term: Ad sales rep, runtime_type: Actor }
              - { term: Brand client, runtime_type: Actor }
              - { term: Ad inventory, runtime_type: Object }
              - { term: Booked order, runtime_type: Object }
              - { term: Inventory sold out, runtime_type: Event }
              - { term: Underdelivering, runtime_type: State }
              - { term: "Issue a make-good or refund", runtime_type: Decision }
              - { term: Book and forecast the order, runtime_type: Workflow }
              - { term: Media plan, runtime_type: Artefact }
              - { term: Revenue target met, runtime_type: Outcome }
              - { term: Fill rate, runtime_type: Learning }
              - { term: "Make-good credit", runtime_type: Artefact }
          - name: "Creative & Ad Operations"
            note: "Ad content policy, accessibility and political/financial-ad disclosure requirements apply."
            operating_domains:
              - Creative specs and assets
              - Ad tags and pixels
              - Trafficking and QA
              - Dynamic creative versions
              - Approval and policy review
              - Tracking and verification
              - Creative rotation
              - Discrepancy resolution
            vocabulary:
              - { term: Ad ops specialist, runtime_type: Actor }
              - { term: Creative agency, runtime_type: Actor }
              - { term: Ad creative, runtime_type: Object }
              - { term: Ad tag, runtime_type: Object }
              - { term: Creative approved, runtime_type: Event }
              - { term: Trafficking in progress, runtime_type: State }
              - { term: Approve or reject the creative, runtime_type: Decision }
              - { term: Traffic the creative live, runtime_type: Workflow }
              - { term: Tag sheet, runtime_type: Artefact }
              - { term: Creative served correctly, runtime_type: Outcome }
              - { term: Viewability rate, runtime_type: Learning }
              - { term: Discrepancy flagged, runtime_type: Event }
          - name: "Measurement & Attribution"
            note: "Cross-site tracking and identity resolution are constrained by privacy law and clean-room consent rules."
            operating_domains:
              - Conversion and event tracking
              - Attribution models
              - Incrementality and lift tests
              - "Brand-lift studies"
              - "Multi-touch journeys"
              - Audience overlap analysis
              - Reporting dashboards
              - Data clean rooms
            vocabulary:
              - { term: Measurement analyst, runtime_type: Actor }
              - { term: Advertiser, runtime_type: Actor }
              - { term: Conversion event, runtime_type: Object }
              - { term: Attribution model, runtime_type: Object }
              - { term: Lift test completed, runtime_type: Event }
              - { term: Results pending, runtime_type: State }
              - { term: Credit or discount the channel, runtime_type: Decision }
              - { term: Run the attribution analysis, runtime_type: Workflow }
              - { term: Attribution report, runtime_type: Artefact }
              - { term: Proven incremental sales, runtime_type: Outcome }
              - { term: Return on ad spend, runtime_type: Learning }
              - { term: "Brand-lift study", runtime_type: Artefact }
      - name: "n-publishingOS"
        buyer: "Publisher / managing editor at a book, journal, or digital-publishing house who owns the title and royalty budget."
        os_test: "Buyer is the publishing house (distinct from newsroom or streaming), with a state model around manuscripts, rights, and royalties, publishing-native vocabulary (galleys, ISBNs, advances, sell-through), and a repeatable population of book, academic, and content publishers."
        sectors:
          - name: "Editorial & Manuscript Workflow"
            note: "Author contracts, copyright and content-liability terms are legally binding."
            operating_domains:
              - Submissions and slush pile
              - Acquisition and contracts
              - Developmental and copy edits
              - Proofs and galleys
              - Cover and design briefs
              - Author revisions
              - Production schedule
              - Final files to print
            vocabulary:
              - { term: Commissioning editor, runtime_type: Actor }
              - { term: Author, runtime_type: Actor }
              - { term: Manuscript, runtime_type: Object }
              - { term: Submission, runtime_type: Object }
              - { term: Manuscript accepted, runtime_type: Event }
              - { term: "In copy-edit", runtime_type: State }
              - { term: Acquire or reject the manuscript, runtime_type: Decision }
              - { term: Move through the editorial stages, runtime_type: Workflow }
              - { term: Galley proof, runtime_type: Artefact }
              - { term: Title ready for print, runtime_type: Outcome }
              - { term: Turnaround time per stage, runtime_type: Learning }
              - { term: Publishing contract, runtime_type: Artefact }
          - name: "Rights & Royalties"
            note: "Copyright, sub-licensing and royalty-accounting obligations are legally governed."
            operating_domains:
              - Territory and translation rights
              - Subsidiary and adaptation rights
              - Royalty rates and tiers
              - "Advance and earn-out tracking"
              - Statements and payouts
              - Agent and author splits
              - "Reversion and out-of-print"
              - Licensing deals
            vocabulary:
              - { term: Rights manager, runtime_type: Actor }
              - { term: Literary agent, runtime_type: Actor }
              - { term: Rights deal, runtime_type: Object }
              - { term: Royalty account, runtime_type: Object }
              - { term: Advance earned out, runtime_type: Event }
              - { term: Rights reverted, runtime_type: Event }
              - { term: In negotiation, runtime_type: State }
              - { term: Sell or retain the rights, runtime_type: Decision }
              - { term: Calculate and issue royalties, runtime_type: Workflow }
              - { term: Royalty statement, runtime_type: Artefact }
              - { term: Translation rights sold, runtime_type: Outcome }
              - { term: "Earn-out rate", runtime_type: Learning }
          - name: "Production & Print Supply"
            operating_domains:
              - Print specifications and stock
              - Print runs and reprints
              - "Print-on-demand setup"
              - Ebook and audiobook conversion
              - ISBN and metadata assignment
              - Proofing and press checks
              - Warehouse and inventory
              - Distribution to retailers
            vocabulary:
              - { term: Production manager, runtime_type: Actor }
              - { term: Printer, runtime_type: Actor }
              - { term: Print run, runtime_type: Object }
              - { term: Title file, runtime_type: Object }
              - { term: Print run completed, runtime_type: Event }
              - { term: At the printer, runtime_type: State }
              - { term: "Reprint or go print-on-demand", runtime_type: Decision }
              - { term: Send to print and stock, runtime_type: Workflow }
              - { term: Finished book, runtime_type: Artefact }
              - { term: ISBN record, runtime_type: Artefact }
              - { term: Stock available to sell, runtime_type: Outcome }
              - { term: Stock turn rate, runtime_type: Learning }
          - name: "Sales, Marketing & Publicity"
            operating_domains:
              - Catalogue and seasonal lists
              - "Retailer and sales-rep orders"
              - Publicity and review copies
              - Launch campaigns and events
              - "Pre-orders and bestseller pushes"
              - "Co-op and promotional placement"
              - Author tours and media
              - "Sell-through tracking"
            vocabulary:
              - { term: Marketing manager, runtime_type: Actor }
              - { term: Bookseller, runtime_type: Actor }
              - { term: Title campaign, runtime_type: Object }
              - { term: Catalogue listing, runtime_type: Object }
              - { term: Book launched, runtime_type: Event }
              - { term: Hit the bestseller list, runtime_type: Event }
              - { term: "On pre-order", runtime_type: State }
              - { term: Reprint or hold on demand signal, runtime_type: Decision }
              - { term: Run the launch campaign, runtime_type: Workflow }
              - { term: Press kit, runtime_type: Artefact }
              - { term: Title sold through, runtime_type: Outcome }
              - { term: "Sell-through rate", runtime_type: Learning }
          - name: "Academic & Journal Publishing"
            note: "Research-integrity, open-access mandates and licensing (CC/copyright) are regulated."
            operating_domains:
              - Manuscript submissions portal
              - "Peer-review assignment"
              - Reviewer reports and rounds
              - Editorial decisions and revisions
              - DOI and metadata registration
              - "Open-access fees and licences"
              - Issue assembly and pagination
              - Citation and impact tracking
            vocabulary:
              - { term: Journal editor, runtime_type: Actor }
              - { term: Peer reviewer, runtime_type: Actor }
              - { term: Submitted paper, runtime_type: Object }
              - { term: Review assignment, runtime_type: Object }
              - { term: Reviews returned, runtime_type: Event }
              - { term: Under peer review, runtime_type: State }
              - { term: "Accept, revise or reject", runtime_type: Decision }
              - { term: Route through peer review, runtime_type: Workflow }
              - { term: Published paper, runtime_type: Artefact }
              - { term: DOI record, runtime_type: Artefact }
              - { term: Paper published in issue, runtime_type: Outcome }
              - { term: Citation impact factor, runtime_type: Learning }
  - name: "Travel & Hospitality"
    os:
      - name: "n-travelOS"
        buyer: "Travel agencies, OTAs, TMCs and DMCs who sell, package and service trips for travellers."
        os_test: "Distinct buyer (agency/TMC), distinct budget (GDS + booking-tool spend), distinct frontend (itinerary builder + sales desk), distinct state model (quote → booking → ticketed → travelled), distinct vocab (PNR, fare rules, service fee); thousands of repeatable agencies."
        sectors:
          - name: "Retail & Online Travel Agencies"
            note: "Sale of flights and packages is regulated under IATA accreditation and (UK) ATOL / package-travel rules."
            operating_domains:
              - "Trip search & shopping cart"
              - "Multi-supplier itinerary basket"
              - "Fare & rate comparison"
              - "Booking & ticketing desk"
              - "Customer service & post-sale changes"
              - "Service-fee & markup engine"
              - Supplier payment reconciliation
              - "Loyalty & member wallet"
            vocabulary:
              - { term: Traveller, runtime_type: Actor }
              - { term: Travel agent, runtime_type: Actor }
              - { term: Itinerary, runtime_type: Object }
              - { term: Booking, runtime_type: Object }
              - { term: Fare quote, runtime_type: Artefact }
              - { term: Search request submitted, runtime_type: Event }
              - { term: Held / on option, runtime_type: State }
              - { term: "Confirmed & ticketed", runtime_type: State }
              - { term: Add insurance or seat upsell, runtime_type: Decision }
              - { term: "Checkout & payment flow", runtime_type: Workflow }
              - { term: "E-ticket", runtime_type: Artefact }
              - { term: Trip departed successfully, runtime_type: Outcome }
              - { term: "Look-to-book conversion rate", runtime_type: Learning }
              - { term: Service fee, runtime_type: Object }
              - { term: Refund processed, runtime_type: Event }
          - name: Corporate Travel Management (TMC)
            note: "Duty-of-care traveller-tracking carries employer health-and-safety obligations."
            operating_domains:
              - Corporate travel policy engine
              - Employee trip approval desk
              - "Negotiated-rate & contract loading"
              - "Online self-booking tool"
              - "Duty-of-care traveller tracking"
              - "Expense & invoice integration"
              - "Savings & leakage reporting"
              - VIP / executive travel handling
            vocabulary:
              - { term: Traveller (employee), runtime_type: Actor }
              - { term: Travel arranger, runtime_type: Actor }
              - { term: Travel policy, runtime_type: Object }
              - { term: Trip request, runtime_type: Object }
              - { term: "Out-of-policy approval", runtime_type: Decision }
              - { term: Approval workflow, runtime_type: Workflow }
              - { term: Pending manager approval, runtime_type: State }
              - { term: Booking authorised, runtime_type: Event }
              - { term: Negotiated corporate rate, runtime_type: Object }
              - { term: Travel authorisation form, runtime_type: Artefact }
              - { term: Trip completed within policy, runtime_type: Outcome }
              - { term: Policy compliance rate, runtime_type: Learning }
              - { term: Saving vs benchmark, runtime_type: Learning }
              - { term: Traveller located during disruption, runtime_type: State }
          - name: "Tour Operators & Holiday Packaging"
            note: Packaged holidays fall under the Package Travel Regulations and require ATOL financial protection (UK).
            operating_domains:
              - Package build (flight + hotel + transfer)
              - "Capacity & allotment management"
              - "Brochure & departure calendar"
              - Dynamic packaging pricing
              - Supplier contract loading
              - "Departure-date passenger manifest"
              - "Trade & B2B distribution"
              - "Refund & repatriation handling"
            vocabulary:
              - { term: Holidaymaker, runtime_type: Actor }
              - { term: Product manager, runtime_type: Actor }
              - { term: Package, runtime_type: Object }
              - { term: Allotment, runtime_type: Object }
              - { term: Departure, runtime_type: Event }
              - { term: On sale, runtime_type: State }
              - { term: "Sold out / stop-sell", runtime_type: State }
              - { term: Build dynamic package, runtime_type: Workflow }
              - { term: Release unsold allotment, runtime_type: Decision }
              - { term: Confirmation voucher, runtime_type: Artefact }
              - { term: Passenger manifest, runtime_type: Artefact }
              - { term: Holiday delivered as sold, runtime_type: Outcome }
              - { term: Load factor per departure, runtime_type: Learning }
              - { term: Margin per pax, runtime_type: Learning }
          - name: "Travel Distribution & GDS Connectivity"
            operating_domains:
              - Content aggregation (GDS + NDC + direct)
              - "Availability & cache management"
              - "Fare-rule & schedule ingestion"
              - "PNR creation & management"
              - Queue management desk
              - "Mid-office automation rules"
              - "Robotic fulfilment & ticketing"
              - "Distribution-cost analytics"
            vocabulary:
              - { term: Content provider, runtime_type: Actor }
              - { term: PNR, runtime_type: Object }
              - { term: Segment, runtime_type: Object }
              - { term: Availability cache, runtime_type: Object }
              - { term: Schedule change received, runtime_type: Event }
              - { term: Queued for action, runtime_type: State }
              - { term: Ticketed, runtime_type: State }
              - { term: Apply automation rule, runtime_type: Decision }
              - { term: "Queue-processing workflow", runtime_type: Workflow }
              - { term: Fare rule, runtime_type: Artefact }
              - { term: Ticket image (TKT), runtime_type: Artefact }
              - { term: Booking fulfilled automatically, runtime_type: Outcome }
              - { term: "Robotic-touch ratio", runtime_type: Learning }
              - { term: Cost per segment, runtime_type: Learning }
          - name: "Travel Insurance & Ancillary Protection"
            note: Travel insurance sales and claims are regulated by the FCA (UK) / equivalent insurance authorities.
            operating_domains:
              - "Quote & cover selection"
              - Policy issuance
              - "Pre-existing condition screening"
              - "Claims intake & assessment"
              - "Assistance & repatriation coordination"
              - "Premium & commission accounting"
              - Underwriter rule sets
              - "Renewal & multi-trip management"
            vocabulary:
              - { term: Policyholder, runtime_type: Actor }
              - { term: Claims assessor, runtime_type: Actor }
              - { term: Policy, runtime_type: Object }
              - { term: Cover level, runtime_type: Object }
              - { term: Quote generated, runtime_type: Event }
              - { term: Active cover, runtime_type: State }
              - { term: Claim under review, runtime_type: State }
              - { term: Approve or decline claim, runtime_type: Decision }
              - { term: Claims assessment workflow, runtime_type: Workflow }
              - { term: Policy schedule (document), runtime_type: Artefact }
              - { term: Claim payout issued, runtime_type: Outcome }
              - { term: Loss ratio, runtime_type: Learning }
              - { term: Repatriation arranged, runtime_type: Event }
              - { term: Premium, runtime_type: Object }
      - name: "n-hospitalityOS"
        buyer: "Multi-property hospitality groups and venue operators running the guest experience across F&B, rooms and events."
        os_test: "Distinct buyer (group GM / ops director), distinct budget (hospitality-suite + venue-tech), distinct frontend (venue floor + guest-journey console), distinct state model (enquiry → reserved → in-house → departed → followed-up), distinct vocab (cover, turn, comp, RevPASH); repeatable across hotels, resorts and venues."
        sectors:
          - name: "Guest Experience & Loyalty"
            operating_domains:
              - Unified guest profile
              - "Preference & allergy capture"
              - "Loyalty tier & points engine"
              - Personalised offer targeting
              - "Feedback & review capture"
              - "Service-recovery case desk"
              - "Cross-property recognition"
              - "Guest-journey timeline"
            vocabulary:
              - { term: Guest, runtime_type: Actor }
              - { term: Guest relations manager, runtime_type: Actor }
              - { term: Guest profile, runtime_type: Object }
              - { term: Preference note, runtime_type: Object }
              - { term: Stay completed, runtime_type: Event }
              - { term: VIP / recognised, runtime_type: State }
              - { term: Complaint open, runtime_type: State }
              - { term: Offer a recovery gesture, runtime_type: Decision }
              - { term: "Service-recovery workflow", runtime_type: Workflow }
              - { term: Loyalty membership card, runtime_type: Artefact }
              - { term: Guest delighted / would return, runtime_type: Outcome }
              - { term: Net promoter score, runtime_type: Learning }
              - { term: Points balance, runtime_type: Object }
              - { term: Review received, runtime_type: Event }
          - name: "Events, Banqueting & Conferences (MICE)"
            operating_domains:
              - "Enquiry & lead desk"
              - "Function-space diary"
              - Banquet event order (BEO) build
              - "Catering & menu selection"
              - "Room-set & AV planning"
              - "Deposit & billing schedule"
              - "Day-of-event run sheet"
              - "Post-event debrief"
            vocabulary:
              - { term: Event organiser, runtime_type: Actor }
              - { term: Events coordinator, runtime_type: Actor }
              - { term: Function room, runtime_type: Object }
              - { term: Event booking, runtime_type: Object }
              - { term: Enquiry received, runtime_type: Event }
              - { term: Tentative / pencilled, runtime_type: State }
              - { term: Definite / contracted, runtime_type: State }
              - { term: Release or hold the space, runtime_type: Decision }
              - { term: Banquet event order, runtime_type: Artefact }
              - { term: Run sheet, runtime_type: Artefact }
              - { term: Event setup workflow, runtime_type: Workflow }
              - { term: Event delivered to brief, runtime_type: Outcome }
              - { term: Space conversion rate, runtime_type: Learning }
              - { term: "Revenue per available function space-hour", runtime_type: Learning }
          - name: "Spa, Wellness & Leisure Facilities"
            note: "Certain wellness treatments require licensed/qualified practitioners and local council treatment-premises licensing."
            operating_domains:
              - "Treatment & class scheduling"
              - "Therapist roster & rooms"
              - "Membership & day-pass management"
              - "Retail & product sales"
              - "Intake & consultation forms"
              - "Resource utilisation (pools, courts)"
              - "Package & gift voucher sales"
              - "No-show & cancellation control"
            vocabulary:
              - { term: Spa guest, runtime_type: Actor }
              - { term: Therapist, runtime_type: Actor }
              - { term: Treatment, runtime_type: Object }
              - { term: Appointment, runtime_type: Object }
              - { term: Booked in, runtime_type: State }
              - { term: "No-show", runtime_type: State }
              - { term: "Check-in completed", runtime_type: Event }
              - { term: Reassign therapist, runtime_type: Decision }
              - { term: Scheduling workflow, runtime_type: Workflow }
              - { term: Consultation form, runtime_type: Artefact }
              - { term: Gift voucher, runtime_type: Artefact }
              - { term: Treatment delivered, runtime_type: Outcome }
              - { term: Therapist utilisation, runtime_type: Learning }
              - { term: Membership, runtime_type: Object }
          - name: "Concierge & Guest Services"
            operating_domains:
              - Request intake (any channel)
              - "Task dispatch & routing"
              - "Local partner & supplier directory"
              - Reservation booking on behalf of guest
              - "Itinerary & recommendation build"
              - "Logbook & shift handover"
              - "Tipping & partner commission"
              - "Response-time tracking"
            vocabulary:
              - { term: Guest, runtime_type: Actor }
              - { term: Concierge, runtime_type: Actor }
              - { term: Service request, runtime_type: Object }
              - { term: Partner / vendor, runtime_type: Object }
              - { term: Request logged, runtime_type: Event }
              - { term: In progress, runtime_type: State }
              - { term: Fulfilled, runtime_type: State }
              - { term: Escalate or source alternative, runtime_type: Decision }
              - { term: Request fulfilment workflow, runtime_type: Workflow }
              - { term: Concierge logbook, runtime_type: Artefact }
              - { term: Curated itinerary, runtime_type: Artefact }
              - { term: Request resolved to guest delight, runtime_type: Outcome }
              - { term: Average response time, runtime_type: Learning }
              - { term: Shift handover, runtime_type: Event }
          - name: "Hospitality Workforce & Scheduling"
            note: "Tips/tronc distribution and right-to-work checks carry employment-law and (UK) Allocation of Tips Act obligations."
            operating_domains:
              - "Demand-based shift planning"
              - "Skills & certification matrix"
              - "Open-shift marketplace"
              - "Time & attendance clock"
              - "Tronc & tips distribution"
              - "Labour-cost vs revenue tracking"
              - "Onboarding & compliance checks"
              - "Absence & cover management"
            vocabulary:
              - { term: Team member, runtime_type: Actor }
              - { term: Duty manager, runtime_type: Actor }
              - { term: Shift, runtime_type: Object }
              - { term: Rota, runtime_type: Object }
              - { term: Clocked in, runtime_type: State }
              - { term: Shift uncovered, runtime_type: State }
              - { term: Shift swap requested, runtime_type: Event }
              - { term: Approve cover or call in, runtime_type: Decision }
              - { term: "Rota-publishing workflow", runtime_type: Workflow }
              - { term: Published rota, runtime_type: Artefact }
              - { term: Timesheet, runtime_type: Artefact }
              - { term: Service covered without overspend, runtime_type: Outcome }
              - { term: Labour cost percentage, runtime_type: Learning }
              - { term: Tronc allocation, runtime_type: Object }
      - name: "n-hotelOS"
        buyer: "Hotel owners and general managers running rooms, rate and revenue across one or many properties."
        os_test: "Distinct buyer (hotel GM / revenue manager), distinct budget (PMS + RMS spend), distinct frontend (front desk + room rack + rate grid), distinct state model (reserved → checked-in → in-house → checked-out), distinct vocab (ADR, RevPAR, room rack, night audit); millions of repeatable hotels."
        sectors:
          - name: "Front Office & Reservations"
            note: "Guest registration and ID capture are subject to local immigration/registration rules and data-protection law."
            operating_domains:
              - Reservation intake (all channels)
              - "Room rack & availability grid"
              - "Check-in / check-out desk"
              - "Room assignment & upgrades"
              - "Folio & incidental posting"
              - Group block management
              - Night audit run
              - "Walk-in & overbooking handling"
            vocabulary:
              - { term: Guest, runtime_type: Actor }
              - { term: "Front-desk agent", runtime_type: Actor }
              - { term: Reservation, runtime_type: Object }
              - { term: Room, runtime_type: Object }
              - { term: Folio, runtime_type: Object }
              - { term: "Check-in", runtime_type: Event }
              - { term: "In-house", runtime_type: State }
              - { term: "No-show", runtime_type: State }
              - { term: Upgrade or walk the guest, runtime_type: Decision }
              - { term: "Check-in workflow", runtime_type: Workflow }
              - { term: Registration card, runtime_type: Artefact }
              - { term: Stay completed, runtime_type: Outcome }
              - { term: Occupancy rate, runtime_type: Learning }
              - { term: Night audit run, runtime_type: Event }
          - name: "Revenue Management & Distribution"
            operating_domains:
              - "Rate plan & BAR setup"
              - Demand forecasting
              - "Dynamic pricing & yield rules"
              - "Channel manager & parity"
              - Competitor rate shopping
              - "Length-of-stay & restriction control"
              - Overbooking strategy
              - "Pickup & pace reporting"
            vocabulary:
              - { term: Revenue manager, runtime_type: Actor }
              - { term: OTA channel, runtime_type: Actor }
              - { term: Rate plan, runtime_type: Object }
              - { term: Best available rate (BAR), runtime_type: Object }
              - { term: Demand forecast, runtime_type: Artefact }
              - { term: Rate pushed to channels, runtime_type: Event }
              - { term: Open for sale, runtime_type: State }
              - { term: "Stop-sell / closed", runtime_type: State }
              - { term: "Raise, hold or drop the rate", runtime_type: Decision }
              - { term: "Yield-management workflow", runtime_type: Workflow }
              - { term: Pickup report, runtime_type: Artefact }
              - { term: RevPAR maximised, runtime_type: Outcome }
              - { term: Average daily rate (ADR), runtime_type: Learning }
              - { term: Booking pace, runtime_type: Learning }
          - name: "Housekeeping & Room Operations"
            operating_domains:
              - "Room-status board (clean/dirty/inspected)"
              - "Housekeeping assignment & credits"
              - "Turndown & deep-clean scheduling"
              - "Lost & found register"
              - "Linen & amenity par stock"
              - Maintenance fault reporting
              - "Inspection & quality scoring"
              - "Out-of-order room control"
            vocabulary:
              - { term: Room attendant, runtime_type: Actor }
              - { term: Housekeeping supervisor, runtime_type: Actor }
              - { term: Room, runtime_type: Object }
              - { term: Cleaning task, runtime_type: Object }
              - { term: Dirty / vacant, runtime_type: State }
              - { term: Inspected / ready, runtime_type: State }
              - { term: Room cleaned, runtime_type: Event }
              - { term: Prioritise an early arrival, runtime_type: Decision }
              - { term: "Board-clearing workflow", runtime_type: Workflow }
              - { term: "Lost & found record", runtime_type: Artefact }
              - { term: Inspection checklist, runtime_type: Artefact }
              - { term: Room ready on time, runtime_type: Outcome }
              - { term: Minutes per room, runtime_type: Learning }
              - { term: Maintenance fault raised, runtime_type: Event }
          - name: "Hotel F&B & In-Room Dining"
            note: "Food allergen labelling (Natasha's Law) and alcohol licensing apply to hotel F&B outlets."
            operating_domains:
              - "Restaurant & bar POS"
              - "In-room dining order desk"
              - Minibar posting
              - "Breakfast & meal-plan tracking"
              - "Charge-to-room (folio post)"
              - "Outlet stock & wastage"
              - "Daily covers & outlet revenue"
              - "Menu & allergen management"
            vocabulary:
              - { term: Diner (guest), runtime_type: Actor }
              - { term: Outlet server, runtime_type: Actor }
              - { term: Order, runtime_type: Object }
              - { term: Menu item, runtime_type: Object }
              - { term: Order placed, runtime_type: Event }
              - { term: Preparing, runtime_type: State }
              - { term: Charged to room, runtime_type: State }
              - { term: Charge to folio or settle now, runtime_type: Decision }
              - { term: "Order-to-table workflow", runtime_type: Workflow }
              - { term: Itemised bill, runtime_type: Artefact }
              - { term: Allergen matrix, runtime_type: Artefact }
              - { term: Meal served correctly, runtime_type: Outcome }
              - { term: Covers per outlet, runtime_type: Learning }
              - { term: Minibar restocked, runtime_type: Event }
          - name: "Owner, Asset & Multi-Property Performance"
            operating_domains:
              - "Portfolio P&L roll-up"
              - "Brand-standard compliance audit"
              - STR / market benchmarking
              - "Management-agreement fee tracking"
              - "CapEx & renovation planning"
              - "Cross-property rate strategy"
              - "Owner reporting & distributions"
              - "Cost-per-occupied-room control"
            vocabulary:
              - { term: Hotel owner, runtime_type: Actor }
              - { term: Asset manager, runtime_type: Actor }
              - { term: Property, runtime_type: Object }
              - { term: Management agreement, runtime_type: Object }
              - { term: Monthly close completed, runtime_type: Event }
              - { term: Outperforming comp set, runtime_type: State }
              - { term: Underperforming, runtime_type: State }
              - { term: Approve CapEx or defer, runtime_type: Decision }
              - { term: "Owner-reporting workflow", runtime_type: Workflow }
              - { term: Owner statement, runtime_type: Artefact }
              - { term: STR report, runtime_type: Artefact }
              - { term: Asset value protected, runtime_type: Outcome }
              - { term: GOPPAR, runtime_type: Learning }
              - { term: Market penetration index, runtime_type: Learning }
      - name: "n-airlineOS"
        buyer: "Airlines and air carriers managing flights, fares, crew and operations from schedule to gate."
        os_test: "Distinct buyer (airline commercial/ops director), distinct budget (PSS + ops-control spend), distinct frontend (ops-control wall + inventory & fare desk), distinct state model (scheduled → boarding → departed → arrived), distinct vocab (RBD, leg, IROPS, load factor); repeatable across hundreds of carriers."
        sectors:
          - name: Flight Operations Control
            note: "Flight dispatch, crew flight-time limitations and operations are regulated by the CAA / EASA / FAA."
            operating_domains:
              - Daily flight schedule board
              - "Aircraft & tail assignment"
              - "Crew pairing & legality"
              - Disruption (IROPS) recovery
              - "Slot & ATC coordination"
              - "Fuel & flight planning"
              - "Delay-code logging"
              - "On-time-performance tracking"
            vocabulary:
              - { term: Flight dispatcher, runtime_type: Actor }
              - { term: Operations controller, runtime_type: Actor }
              - { term: Flight (leg), runtime_type: Object }
              - { term: Aircraft (tail), runtime_type: Object }
              - { term: Scheduled, runtime_type: State }
              - { term: Delayed / disrupted, runtime_type: State }
              - { term: Departure, runtime_type: Event }
              - { term: "Cancel, delay or swap aircraft", runtime_type: Decision }
              - { term: "Disruption-recovery workflow", runtime_type: Workflow }
              - { term: Operational flight plan, runtime_type: Artefact }
              - { term: Delay code log, runtime_type: Artefact }
              - { term: "Flight operated safely & on time", runtime_type: Outcome }
              - { term: "On-time performance", runtime_type: Learning }
              - { term: Crew legality breach flagged, runtime_type: Event }
          - name: "Inventory, Pricing & Revenue Management"
            operating_domains:
              - "Booking-class (RBD) inventory"
              - "Fare filing & rules"
              - "Origin-destination yield optimisation"
              - "Overbooking & no-show modelling"
              - "Group & block-space requests"
              - "Codeshare & interline inventory"
              - Demand forecasting
              - "Bid-price & nesting control"
            vocabulary:
              - { term: Revenue analyst, runtime_type: Actor }
              - { term: Pricing manager, runtime_type: Actor }
              - { term: Booking class (RBD), runtime_type: Object }
              - { term: Fare, runtime_type: Object }
              - { term: Seat sold, runtime_type: Event }
              - { term: Class open, runtime_type: State }
              - { term: Class closed, runtime_type: State }
              - { term: Adjust the booking limit, runtime_type: Decision }
              - { term: "Yield-optimisation workflow", runtime_type: Workflow }
              - { term: Filed fare, runtime_type: Artefact }
              - { term: "Bid-price table", runtime_type: Artefact }
              - { term: Revenue per seat maximised, runtime_type: Outcome }
              - { term: Load factor, runtime_type: Learning }
              - { term: Yield (RASK), runtime_type: Learning }
          - name: "Passenger Services & Reservations (PSS)"
            note: "Denied boarding, delays and cancellations carry passenger-rights obligations (UK261/EC261)."
            operating_domains:
              - "Booking & PNR management"
              - "Check-in & seat selection"
              - "Baggage acceptance & tracking"
              - "Boarding & gate control"
              - "Ancillary sales (bags, seats, meals)"
              - "Rebooking & involuntary reaccommodation"
              - "Special-assistance handling"
              - "Frequent-flyer accrual"
            vocabulary:
              - { term: Passenger, runtime_type: Actor }
              - { term: Gate agent, runtime_type: Actor }
              - { term: Booking (PNR), runtime_type: Object }
              - { term: Boarding pass, runtime_type: Artefact }
              - { term: Checked in, runtime_type: State }
              - { term: Boarded, runtime_type: State }
              - { term: Bag tagged, runtime_type: Event }
              - { term: Reaccommodate or deny boarding, runtime_type: Decision }
              - { term: "Check-in-to-board workflow", runtime_type: Workflow }
              - { term: Baggage tag, runtime_type: Object }
              - { term: "Frequent-flyer account", runtime_type: Object }
              - { term: Passenger flown to destination, runtime_type: Outcome }
              - { term: "Mishandled-bag rate", runtime_type: Learning }
              - { term: "Denied-boarding compensation issued", runtime_type: Event }
          - name: "Cargo & Belly Freight"
            note: "Dangerous-goods and cargo security screening are governed by IATA DGR and aviation security regulation."
            operating_domains:
              - Air waybill booking
              - "Capacity & ULD allocation"
              - "Acceptance & screening"
              - "Build-up & load planning"
              - "Special cargo handling (DG, perishables, live)"
              - "Tracking & milestone scanning"
              - "Rate & spot-quote management"
              - "Claims & irregularity handling"
            vocabulary:
              - { term: Freight forwarder, runtime_type: Actor }
              - { term: Cargo agent, runtime_type: Actor }
              - { term: Air waybill, runtime_type: Object }
              - { term: Shipment, runtime_type: Object }
              - { term: Booking accepted, runtime_type: Event }
              - { term: Awaiting screening, runtime_type: State }
              - { term: Uplifted / flown, runtime_type: State }
              - { term: Offload or rebook shipment, runtime_type: Decision }
              - { term: "Acceptance-to-uplift workflow", runtime_type: Workflow }
              - { term: "Dangerous-goods declaration", runtime_type: Artefact }
              - { term: ULD, runtime_type: Object }
              - { term: "Cargo delivered intact & on time", runtime_type: Outcome }
              - { term: Cargo load factor, runtime_type: Learning }
              - { term: Milestone scan recorded, runtime_type: Event }
          - name: "Loyalty & Frequent Flyer Programme"
            operating_domains:
              - "Member enrolment & tiers"
              - Miles accrual engine
              - "Award redemption & availability"
              - "Partner & co-brand earning"
              - Status qualification tracking
              - Points liability accounting
              - "Promotion & bonus campaigns"
              - Member churn analysis
            vocabulary:
              - { term: Programme member, runtime_type: Actor }
              - { term: Loyalty manager, runtime_type: Actor }
              - { term: Miles balance, runtime_type: Object }
              - { term: Tier status, runtime_type: Object }
              - { term: Miles credited, runtime_type: Event }
              - { term: Qualified for status, runtime_type: State }
              - { term: Award seat available, runtime_type: State }
              - { term: Release award inventory, runtime_type: Decision }
              - { term: Redemption workflow, runtime_type: Workflow }
              - { term: Award ticket, runtime_type: Artefact }
              - { term: Member statement, runtime_type: Artefact }
              - { term: "Member retained & engaged", runtime_type: Outcome }
              - { term: Points liability, runtime_type: Learning }
              - { term: "Active-member rate", runtime_type: Learning }
      - name: "n-tourOS"
        buyer: "Tour, activity and experience operators selling guided trips, excursions and attractions."
        os_test: "Distinct buyer (activity operator owner), distinct budget (tour-booking + resource spend), distinct frontend (availability calendar + guide/manifest console), distinct state model (available → booked → checked-in → completed), distinct vocab (departure, capacity, manifest, guide, resource); repeatable across thousands of operators."
        sectors:
          - name: "Day Tours & Excursions"
            operating_domains:
              - "Departure & timeslot calendar"
              - "Capacity & seat allocation"
              - "Pickup-point & route management"
              - Guide assignment
              - Live availability distribution (OTAs/resellers)
              - "Manifest & headcount"
              - "Weather & cancellation handling"
              - "Per-tour review capture"
            vocabulary:
              - { term: Guest, runtime_type: Actor }
              - { term: Tour guide, runtime_type: Actor }
              - { term: Tour product, runtime_type: Object }
              - { term: Departure, runtime_type: Object }
              - { term: Booking confirmed, runtime_type: Event }
              - { term: Available, runtime_type: State }
              - { term: Sold out, runtime_type: State }
              - { term: Run or cancel the departure, runtime_type: Decision }
              - { term: "Departure-day workflow", runtime_type: Workflow }
              - { term: Manifest, runtime_type: Artefact }
              - { term: Mobile ticket / QR, runtime_type: Artefact }
              - { term: Tour delivered safely, runtime_type: Outcome }
              - { term: Seat fill rate, runtime_type: Learning }
              - { term: Guest checked in, runtime_type: Event }
          - name: "Multi-Day & Adventure Travel"
            note: "Multi-day packaged adventure trips fall under package-travel and (UK) ATOL protection rules."
            operating_domains:
              - "Itinerary & route builder"
              - Trip departure scheduling
              - "Accommodation & transport blocks"
              - "Participant fitness & waiver screening"
              - "Group leader & logistics"
              - Supplier coordination on the ground
              - "Trip-cost & margin tracking"
              - "Joining instructions & pre-departure"
            vocabulary:
              - { term: Trip participant, runtime_type: Actor }
              - { term: Trip leader, runtime_type: Actor }
              - { term: Trip itinerary, runtime_type: Object }
              - { term: Departure, runtime_type: Object }
              - { term: Deposit paid, runtime_type: Event }
              - { term: Guaranteed to run, runtime_type: State }
              - { term: Waitlisted, runtime_type: State }
              - { term: Guarantee or cancel departure, runtime_type: Decision }
              - { term: "Pre-departure workflow", runtime_type: Workflow }
              - { term: Joining instructions, runtime_type: Artefact }
              - { term: Signed waiver, runtime_type: Artefact }
              - { term: Trip completed without incident, runtime_type: Outcome }
              - { term: "Minimum-numbers threshold met", runtime_type: State }
              - { term: Margin per departure, runtime_type: Learning }
          - name: "Attractions & Visitor Venues"
            operating_domains:
              - "Timed-entry ticketing"
              - "Capacity & flow management"
              - "Membership & annual pass"
              - "Queue & fast-track control"
              - "Group & school bookings"
              - "On-site retail & F&B tie-in"
              - "Gate scanning & validation"
              - "Footfall & dwell analytics"
            vocabulary:
              - { term: Visitor, runtime_type: Actor }
              - { term: "Box-office staff", runtime_type: Actor }
              - { term: Admission ticket, runtime_type: Object }
              - { term: Time slot, runtime_type: Object }
              - { term: Ticket scanned at gate, runtime_type: Event }
              - { term: Slot open, runtime_type: State }
              - { term: At capacity, runtime_type: State }
              - { term: Open extra capacity or close gate, runtime_type: Decision }
              - { term: "Entry-validation workflow", runtime_type: Workflow }
              - { term: Annual pass, runtime_type: Artefact }
              - { term: Entry receipt, runtime_type: Artefact }
              - { term: Visitor admitted smoothly, runtime_type: Outcome }
              - { term: Footfall per slot, runtime_type: Learning }
              - { term: Secondary spend per head, runtime_type: Learning }
          - name: "Resource & Equipment Hire"
            operating_domains:
              - "Rentable-asset inventory (bikes, kayaks, gear)"
              - "Time-based availability calendar"
              - "Damage deposit & condition log"
              - "Check-out & check-in inspection"
              - "Maintenance & servicing cycle"
              - "Utilisation & idle-time tracking"
              - Loss/damage charge handling
              - "Multi-location stock transfer"
            vocabulary:
              - { term: Hirer, runtime_type: Actor }
              - { term: Rental clerk, runtime_type: Actor }
              - { term: Hire item, runtime_type: Object }
              - { term: Hire booking, runtime_type: Object }
              - { term: Checked out, runtime_type: State }
              - { term: Overdue, runtime_type: State }
              - { term: Item returned, runtime_type: Event }
              - { term: Charge for damage or release deposit, runtime_type: Decision }
              - { term: "Check-out / check-in workflow", runtime_type: Workflow }
              - { term: Condition report, runtime_type: Artefact }
              - { term: Hire agreement, runtime_type: Artefact }
              - { term: Equipment returned in good order, runtime_type: Outcome }
              - { term: Asset utilisation, runtime_type: Learning }
              - { term: Deposit held, runtime_type: Object }
          - name: "Experience Marketplace & Reseller Distribution"
            operating_domains:
              - "Channel & reseller connectivity"
              - "Real-time availability sync"
              - "Commission & net-rate management"
              - Booking allocation across channels
              - "Content & product feed publishing"
              - "Cut-off & lead-time rules"
              - "Settlement & payout reconciliation"
              - "Channel-mix performance"
            vocabulary:
              - { term: Reseller / OTA, runtime_type: Actor }
              - { term: Channel manager, runtime_type: Actor }
              - { term: Product listing, runtime_type: Object }
              - { term: Availability pool, runtime_type: Object }
              - { term: Booking pushed from channel, runtime_type: Event }
              - { term: Live on channel, runtime_type: State }
              - { term: "Past cut-off / closed", runtime_type: State }
              - { term: Allocate inventory to a channel, runtime_type: Decision }
              - { term: "Distribution-sync workflow", runtime_type: Workflow }
              - { term: "Net-rate agreement", runtime_type: Artefact }
              - { term: Settlement statement, runtime_type: Artefact }
              - { term: Inventory sold across channels, runtime_type: Outcome }
              - { term: Channel conversion rate, runtime_type: Learning }
              - { term: Commission cost per booking, runtime_type: Learning }
      - name: "n-bookingOS"
        buyer: "Online marketplaces, channel managers and direct-booking platforms that match travel demand to supply."
        os_test: "Distinct buyer (marketplace product/commercial owner), distinct budget (booking-platform + payments spend), distinct frontend (search-rank + supply console), distinct state model (search → cart → reserved → paid → fulfilled), distinct vocab (parity, conversion, take-rate, funnel); repeatable across OTAs, channel managers and metasearch."
        sectors:
          - name: "Search, Discovery & Ranking"
            operating_domains:
              - "Search query & filters"
              - "Availability fan-out to suppliers"
              - "Ranking & sort logic"
              - "Personalisation & recommendation"
              - "Price & deal badging"
              - A/B experiment framework
              - "Funnel & drop-off analytics"
              - "Fraud & abuse signals"
            vocabulary:
              - { term: Shopper, runtime_type: Actor }
              - { term: Merchandiser, runtime_type: Actor }
              - { term: Search query, runtime_type: Object }
              - { term: Result listing, runtime_type: Object }
              - { term: Search performed, runtime_type: Event }
              - { term: Shown in results, runtime_type: State }
              - { term: Filtered out, runtime_type: State }
              - { term: Reorder the ranking, runtime_type: Decision }
              - { term: Ranking workflow, runtime_type: Workflow }
              - { term: Ranking experiment, runtime_type: Artefact }
              - { term: Result clicked through, runtime_type: Outcome }
              - { term: "Click-through rate", runtime_type: Learning }
              - { term: "Search-to-detail conversion", runtime_type: Learning }
              - { term: Result impression logged, runtime_type: Event }
          - name: "Booking & Checkout"
            operating_domains:
              - "Cart & basket"
              - "Price-hold & re-validation"
              - "Guest & traveller details capture"
              - "Ancillary & cross-sell"
              - "Multi-supplier order assembly"
              - "Confirmation & voucher issue"
              - "Abandoned-cart recovery"
              - "Booking-error handling"
            vocabulary:
              - { term: Booker, runtime_type: Actor }
              - { term: Supplier, runtime_type: Actor }
              - { term: Cart, runtime_type: Object }
              - { term: Order, runtime_type: Object }
              - { term: Checkout started, runtime_type: Event }
              - { term: Price held, runtime_type: State }
              - { term: Confirmed, runtime_type: State }
              - { term: "Re-price or hold the offer", runtime_type: Decision }
              - { term: Checkout workflow, runtime_type: Workflow }
              - { term: Booking confirmation, runtime_type: Artefact }
              - { term: Voucher, runtime_type: Artefact }
              - { term: "Booking completed & confirmed", runtime_type: Outcome }
              - { term: Checkout conversion rate, runtime_type: Learning }
              - { term: Cart abandoned, runtime_type: Event }
          - name: "Payments, Settlement & Fraud"
            note: "Card payments, FX and merchant-of-record activity carry PCI-DSS, PSD2/SCA and money-handling obligations."
            operating_domains:
              - "Payment capture & methods"
              - "Currency & FX handling"
              - "Merchant-of-record routing"
              - "Supplier payout & settlement"
              - "Chargeback & dispute desk"
              - "Fraud scoring & 3DS"
              - "Refund & cancellation accounting"
              - "Reconciliation & ledger"
            vocabulary:
              - { term: Payer, runtime_type: Actor }
              - { term: Payments analyst, runtime_type: Actor }
              - { term: Transaction, runtime_type: Object }
              - { term: Payout, runtime_type: Object }
              - { term: Payment captured, runtime_type: Event }
              - { term: Authorised, runtime_type: State }
              - { term: Disputed / charged back, runtime_type: State }
              - { term: "Approve, hold or refund", runtime_type: Decision }
              - { term: Settlement workflow, runtime_type: Workflow }
              - { term: Settlement report, runtime_type: Artefact }
              - { term: Refund processed, runtime_type: Outcome }
              - { term: Chargeback rate, runtime_type: Learning }
              - { term: "Fraud-decline rate", runtime_type: Learning }
              - { term: Refund issued, runtime_type: Event }
          - name: "Supply Onboarding & Channel Management"
            operating_domains:
              - "Supplier sign-up & verification"
              - "Content & rate ingestion"
              - "Availability & calendar sync"
              - "Rate-parity monitoring"
              - "Contract & commission terms"
              - "Mapping & deduplication"
              - Supplier performance scoring
              - Connectivity health monitoring
            vocabulary:
              - { term: Supplier (host/property), runtime_type: Actor }
              - { term: Supply manager, runtime_type: Actor }
              - { term: Listing, runtime_type: Object }
              - { term: "Rate & availability feed", runtime_type: Object }
              - { term: Listing went live, runtime_type: Event }
              - { term: "Connected & syncing", runtime_type: State }
              - { term: Out of parity, runtime_type: State }
              - { term: Suspend or approve the listing, runtime_type: Decision }
              - { term: Onboarding workflow, runtime_type: Workflow }
              - { term: Supplier contract, runtime_type: Artefact }
              - { term: Connectivity health check, runtime_type: Artefact }
              - { term: Supply made bookable, runtime_type: Outcome }
              - { term: "Active-listing rate", runtime_type: Learning }
              - { term: Sync error rate, runtime_type: Learning }
          - name: "Trust, Reviews & Customer Care"
            operating_domains:
              - "Post-stay review collection"
              - "Moderation & authenticity checks"
              - "Dispute & resolution centre"
              - "Cancellation & rebooking support"
              - "Policy & guarantee enforcement"
              - "Case routing & SLA"
              - "Sentiment & quality scoring"
              - "Compensation & goodwill control"
            vocabulary:
              - { term: Customer, runtime_type: Actor }
              - { term: Support agent, runtime_type: Actor }
              - { term: Review, runtime_type: Object }
              - { term: Support case, runtime_type: Object }
              - { term: Review submitted, runtime_type: Event }
              - { term: Under moderation, runtime_type: State }
              - { term: Case escalated, runtime_type: State }
              - { term: "Refund, rebook or decline", runtime_type: Decision }
              - { term: Resolution workflow, runtime_type: Workflow }
              - { term: Resolution outcome record, runtime_type: Artefact }
              - { term: Published review, runtime_type: Artefact }
              - { term: Case resolved to satisfaction, runtime_type: Outcome }
              - { term: "First-contact resolution rate", runtime_type: Learning }
              - { term: Average handle time, runtime_type: Learning }
      - name: "n-restaurantOS"
        buyer: "Restaurants, bars and food-service operators running covers, kitchen and service."
        os_test: "Distinct buyer (restaurant owner / GM), distinct budget (POS + reservation + KDS spend), distinct frontend (table floor + kitchen display + order pad), distinct state model (booked → seated → fired → served → paid), distinct vocab (cover, turn, the pass, 86, comp); millions of repeatable venues."
        sectors:
          - name: "Reservations & Table Management"
            operating_domains:
              - "Booking & waitlist diary"
              - "Floor plan & table-status board"
              - "Seating & turn-time optimisation"
              - "Deposit & no-show protection"
              - "Guest preference & tag profile"
              - "Walk-in & wait-quote"
              - "Special-occasion & VIP flags"
              - "Cover & pacing forecast"
            vocabulary:
              - { term: Diner, runtime_type: Actor }
              - { term: "Host / maître d'", runtime_type: Actor }
              - { term: Reservation, runtime_type: Object }
              - { term: Table, runtime_type: Object }
              - { term: Party seated, runtime_type: Event }
              - { term: Booked, runtime_type: State }
              - { term: "No-show", runtime_type: State }
              - { term: Seat now or quote a wait, runtime_type: Decision }
              - { term: Seating workflow, runtime_type: Workflow }
              - { term: Run sheet / book, runtime_type: Artefact }
              - { term: Guest tag (allergy/VIP), runtime_type: Object }
              - { term: Table turned successfully, runtime_type: Outcome }
              - { term: Covers per service, runtime_type: Learning }
              - { term: "No-show rate", runtime_type: Learning }
          - name: "Order, Point-of-Sale & Payments"
            note: "Card payments, tips/service-charge allocation and cash handling carry PCI-DSS and tipping-law obligations."
            operating_domains:
              - "Order entry & modifiers"
              - "Course & seat-position firing"
              - "Split-bill & tab management"
              - "Discount, comp & void control"
              - "Tip & service-charge handling"
              - "Payment & settlement"
              - "Day-part sales reporting"
              - "Cash-up & end-of-day"
            vocabulary:
              - { term: Guest, runtime_type: Actor }
              - { term: Server, runtime_type: Actor }
              - { term: Order / check, runtime_type: Object }
              - { term: Menu item, runtime_type: Object }
              - { term: Order fired, runtime_type: Event }
              - { term: Open tab, runtime_type: State }
              - { term: Settled / closed, runtime_type: State }
              - { term: Comp or void the item, runtime_type: Decision }
              - { term: "Order-to-payment workflow", runtime_type: Workflow }
              - { term: Itemised check, runtime_type: Artefact }
              - { term: "End-of-day Z-report", runtime_type: Artefact }
              - { term: Bill settled correctly, runtime_type: Outcome }
              - { term: Average spend per head, runtime_type: Learning }
              - { term: Payment taken, runtime_type: Event }
          - name: "Kitchen & Production"
            note: "Food safety (HACCP), allergen control (Natasha's Law) and food-hygiene rating apply to kitchen operations."
            operating_domains:
              - "Kitchen display & ticket flow"
              - Course coordination at the pass
              - "86 / out-of-stock board"
              - "Recipe & spec adherence"
              - "Prep & mise-en-place lists"
              - "Ticket-time & speed-of-service"
              - "Allergen & cross-contamination control"
              - "Wastage & yield tracking"
            vocabulary:
              - { term: Line cook, runtime_type: Actor }
              - { term: Head chef / expeditor, runtime_type: Actor }
              - { term: Kitchen ticket, runtime_type: Object }
              - { term: Dish, runtime_type: Object }
              - { term: Ticket fired, runtime_type: Event }
              - { term: On the pass, runtime_type: State }
              - { term: "86'd / out of stock", runtime_type: State }
              - { term: Prioritise or rush a ticket, runtime_type: Decision }
              - { term: "Ticket-to-pass workflow", runtime_type: Workflow }
              - { term: Recipe spec, runtime_type: Artefact }
              - { term: Prep list, runtime_type: Artefact }
              - { term: "Dish sent correct & on time", runtime_type: Outcome }
              - { term: Average ticket time, runtime_type: Learning }
              - { term: Food waste percentage, runtime_type: Learning }
          - name: "Inventory, Purchasing & Menu Engineering"
            operating_domains:
              - "Stock & par-level tracking"
              - "Supplier ordering & GRN"
              - "Recipe costing & plate cost"
              - "Menu margin & popularity matrix"
              - "Stocktake & variance"
              - "Price-rise & spec management"
              - "Allergen & nutrition data"
              - "Theoretical-vs-actual usage"
            vocabulary:
              - { term: Kitchen manager, runtime_type: Actor }
              - { term: Supplier, runtime_type: Actor }
              - { term: Ingredient / stock item, runtime_type: Object }
              - { term: Purchase order, runtime_type: Object }
              - { term: Delivery received, runtime_type: Event }
              - { term: Below par, runtime_type: State }
              - { term: Out of stock, runtime_type: State }
              - { term: Reorder or substitute, runtime_type: Decision }
              - { term: "Stock-replenishment workflow", runtime_type: Workflow }
              - { term: "Goods-received note", runtime_type: Artefact }
              - { term: Recipe card, runtime_type: Artefact }
              - { term: Stock held at the right level, runtime_type: Outcome }
              - { term: Gross profit margin, runtime_type: Learning }
              - { term: Stock variance, runtime_type: Learning }
          - name: "Online Ordering, Delivery & Pickup"
            note: "Allergen disclosure on remote orders is required under Natasha's Law for prepacked-for-direct-sale and delivery."
            operating_domains:
              - "Direct & aggregator order intake"
              - "Menu & availability sync per channel"
              - Order routing to kitchen
              - Driver / dispatch coordination
              - "Prep-time & promise management"
              - "Channel-mix & commission tracking"
              - "Order accuracy & refunds"
              - Customer data capture from delivery
            vocabulary:
              - { term: Online customer, runtime_type: Actor }
              - { term: Delivery rider, runtime_type: Actor }
              - { term: Online order, runtime_type: Object }
              - { term: Delivery channel, runtime_type: Object }
              - { term: Order received, runtime_type: Event }
              - { term: Accepted / preparing, runtime_type: State }
              - { term: Out for delivery, runtime_type: State }
              - { term: Accept or reject the order, runtime_type: Decision }
              - { term: "Order-fulfilment workflow", runtime_type: Workflow }
              - { term: Kitchen docket, runtime_type: Artefact }
              - { term: Delivery receipt, runtime_type: Artefact }
              - { term: "Order delivered hot & accurate", runtime_type: Outcome }
              - { term: Order accuracy rate, runtime_type: Learning }
              - { term: "Average prep-to-handover time", runtime_type: Learning }
  - name: "Automotive & Mobility"
    os:
      - name: "n-autoOS"
        buyer: "Vehicle manufacturer (OEM) product, engineering and homologation teams who own how a vehicle is conceived, built and certified."
        os_test: "Its own buyer (OEM product/engineering org), capital-scale budget, a frontend built around vehicle programmes and bills-of-materials, a distinctive state model (concept→homologated→SOP→end-of-life), and a vocabulary (platform, variant, homologation, recall) shared by every car maker."
        sectors:
          - name: "Vehicle Programme & Platform Engineering"
            operating_domains:
              - Vehicle programmes
              - "Shared platforms & architectures"
              - "Model variants & trims"
              - Engineering change requests
              - Design gateways / milestones
              - "Target weight & cost books"
              - Supplier sourcing packages
            vocabulary:
              - { term: Programme, runtime_type: Object }
              - { term: Platform, runtime_type: Object }
              - { term: Variant, runtime_type: Object }
              - { term: Trim level, runtime_type: Object }
              - { term: Chief Engineer, runtime_type: Actor }
              - { term: Gateway review, runtime_type: Event }
              - { term: On programme / off track, runtime_type: State }
              - { term: Engineering change request, runtime_type: Decision }
              - { term: Sourcing decision, runtime_type: Decision }
              - { term: Cost book, runtime_type: Artefact }
              - { term: Design freeze, runtime_type: Event }
              - { term: "Stage-gate sign-off", runtime_type: Workflow }
              - { term: Start of production (SOP), runtime_type: Outcome }
              - { term: "Weight-to-target variance", runtime_type: Learning }
              - { term: "Lessons-learned log", runtime_type: Learning }
          - name: "Bill of Materials & Parts Catalogue"
            operating_domains:
              - Engineering BOM
              - Manufacturing BOM
              - "Part numbers & supersessions"
              - Component suppliers
              - Interchangeability rules
              - Part lifecycle status
              - Service parts catalogue
            vocabulary:
              - { term: Part number, runtime_type: Object }
              - { term: Bill of materials, runtime_type: Artefact }
              - { term: Component, runtime_type: Object }
              - { term: "Tier-1 supplier", runtime_type: Actor }
              - { term: Supersession, runtime_type: Event }
              - { term: Active / obsolete part, runtime_type: State }
              - { term: Interchangeability rule, runtime_type: Decision }
              - { term: "Make-or-buy decision", runtime_type: Decision }
              - { term: Engineering release, runtime_type: Event }
              - { term: Approved drawing, runtime_type: Artefact }
              - { term: BOM reconciliation, runtime_type: Workflow }
              - { term: Released to manufacturing, runtime_type: Outcome }
              - { term: Part defect rate, runtime_type: Learning }
              - { term: Commonality score, runtime_type: Learning }
          - name: "Homologation & Type Approval"
            note: "Regulated: vehicle type approval and certificates of conformity are issued under government/UNECE homologation law before a vehicle may be sold."
            operating_domains:
              - Type approval applications
              - Regulatory test campaigns
              - "Emissions & safety standards"
              - Certificates of conformity
              - "Market-specific requirements"
              - "Whole-vehicle approval files"
              - Technical service appointments
            vocabulary:
              - { term: Type approval, runtime_type: Artefact }
              - { term: Certificate of Conformity, runtime_type: Artefact }
              - { term: Homologation engineer, runtime_type: Actor }
              - { term: Technical service (test house), runtime_type: Actor }
              - { term: Test campaign, runtime_type: Object }
              - { term: Emissions test cycle, runtime_type: Event }
              - { term: Approved / pending approval, runtime_type: State }
              - { term: Market entry decision, runtime_type: Decision }
              - { term: Conformity of production audit, runtime_type: Event }
              - { term: Approval submission, runtime_type: Workflow }
              - { term: Granted approval number, runtime_type: Outcome }
              - { term: Regulatory standard, runtime_type: Object }
              - { term: "Non-conformance report", runtime_type: Artefact }
              - { term: "Pass-rate by market", runtime_type: Learning }
          - name: "Manufacturing & Plant Operations"
            operating_domains:
              - Assembly lines
              - Production schedules
              - "Build stations & takt"
              - Quality gates
              - Work orders / build sheets
              - "Tooling & fixtures"
              - "Plant inventory & line-side stock"
            vocabulary:
              - { term: Assembly line, runtime_type: Object }
              - { term: Build sheet, runtime_type: Artefact }
              - { term: Line operator, runtime_type: Actor }
              - { term: Takt time, runtime_type: Object }
              - { term: Line stop, runtime_type: Event }
              - { term: Running / stopped line, runtime_type: State }
              - { term: Quality gate hold, runtime_type: Decision }
              - { term: Vehicle off line (VOL), runtime_type: Event }
              - { term: Rework order, runtime_type: Workflow }
              - { term: Tooling change, runtime_type: Event }
              - { term: Units built today, runtime_type: Outcome }
              - { term: "First-time-through rate", runtime_type: Learning }
              - { term: Overall equipment effectiveness, runtime_type: Learning }
              - { term: VIN, runtime_type: Object }
          - name: "Recall & Field Quality"
            note: "Regulated: safety recalls are notifiable to vehicle safety regulators (e.g. NHTSA, DVSA) with mandatory remedy and reporting duties."
            operating_domains:
              - Field defect reports
              - Recall campaigns
              - Affected VIN populations
              - Remedy procedures
              - Regulator notifications
              - Warranty claim analysis
              - Technical service bulletins
            vocabulary:
              - { term: Recall campaign, runtime_type: Object }
              - { term: Affected VIN, runtime_type: Object }
              - { term: Field defect report, runtime_type: Event }
              - { term: Quality engineer, runtime_type: Actor }
              - { term: Safety recall decision, runtime_type: Decision }
              - { term: Open / closed campaign, runtime_type: State }
              - { term: Regulator notification, runtime_type: Event }
              - { term: Remedy procedure, runtime_type: Artefact }
              - { term: Technical service bulletin, runtime_type: Artefact }
              - { term: "Campaign roll-out", runtime_type: Workflow }
              - { term: Vehicles remedied, runtime_type: Outcome }
              - { term: Completion rate, runtime_type: Learning }
              - { term: "Defect-per-thousand trend", runtime_type: Learning }
          - name: "Connected Vehicle & Software (SDV)"
            note: "Regulated: connected-vehicle software and OTA updates fall under automotive cybersecurity and software-update type approval (UNECE R155/R156)."
            operating_domains:
              - Vehicle software builds
              - "Over-the-air campaigns"
              - ECU/control units
              - "Feature flags & functions-on-demand"
              - Telematics data streams
              - "Cybersecurity & key management"
              - Fleet of connected VINs
            vocabulary:
              - { term: Software build, runtime_type: Artefact }
              - { term: OTA campaign, runtime_type: Object }
              - { term: Electronic control unit, runtime_type: Object }
              - { term: Connected vehicle, runtime_type: Object }
              - { term: Feature flag, runtime_type: Decision }
              - { term: Update pushed, runtime_type: Event }
              - { term: "Up-to-date / stale software", runtime_type: State }
              - { term: "Roll-out wave decision", runtime_type: Decision }
              - { term: Telematics engineer, runtime_type: Actor }
              - { term: Update orchestration, runtime_type: Workflow }
              - { term: Vehicles updated, runtime_type: Outcome }
              - { term: Update success rate, runtime_type: Learning }
              - { term: Security incident, runtime_type: Event }
      - name: "n-fleetOS"
        buyer: Fleet manager / transport operations director at a company that runs many vehicles as a cost centre to deliver its own work.
        os_test: "Its own buyer (fleet/ops director), an operating budget, a frontend built around the live fleet and its drivers, a distinctive state model (vehicle available→assigned→in service→VOR), and a vocabulary (telematics, defect, VOR, duty-of-care) no dealer or lessor uses the same way."
        sectors:
          - name: Fleet Asset Management
            operating_domains:
              - Vehicle register
              - "Acquisition & disposal plan"
              - Replacement cycles
              - "Asset whole-life cost"
              - Vehicle utilisation
              - Pool vehicles
              - "Asset tagging & telematics units"
            vocabulary:
              - { term: Fleet vehicle, runtime_type: Object }
              - { term: Vehicle register, runtime_type: Artefact }
              - { term: Fleet manager, runtime_type: Actor }
              - { term: Replacement cycle, runtime_type: Object }
              - { term: Onboard a vehicle, runtime_type: Event }
              - { term: In service / disposed, runtime_type: State }
              - { term: Disposal decision, runtime_type: Decision }
              - { term: Vehicle handover, runtime_type: Event }
              - { term: Replacement approval, runtime_type: Workflow }
              - { term: "Whole-life cost", runtime_type: Outcome }
              - { term: Utilisation rate, runtime_type: Learning }
              - { term: "Cost-per-mile", runtime_type: Learning }
              - { term: Pool booking, runtime_type: Object }
          - name: "Telematics & Driver Behaviour"
            operating_domains:
              - Vehicle tracking
              - "Trip & journey logs"
              - "Driving events (harsh braking, speeding)"
              - Driver scorecards
              - "Geofences & routes"
              - "Idling & fuel waste"
              - Live map / vehicle status
            vocabulary:
              - { term: Telematics unit, runtime_type: Object }
              - { term: Trip, runtime_type: Object }
              - { term: Driver, runtime_type: Actor }
              - { term: "Harsh-braking event", runtime_type: Event }
              - { term: Geofence, runtime_type: Object }
              - { term: Moving / stationary, runtime_type: State }
              - { term: Coaching decision, runtime_type: Decision }
              - { term: Driver scorecard, runtime_type: Artefact }
              - { term: Route plan, runtime_type: Artefact }
              - { term: Geofence breach alert, runtime_type: Event }
              - { term: Behaviour review, runtime_type: Workflow }
              - { term: "Safe-driving score", runtime_type: Learning }
              - { term: "Idle-time reduction", runtime_type: Learning }
          - name: "Maintenance & Defect Management"
            note: "Regulated: HGV/PSV operators must keep statutory maintenance and inspection records under operator-licensing roadworthiness rules."
            operating_domains:
              - Service schedules
              - Defect reports
              - "Vehicle-off-road tracking"
              - Workshop bookings
              - "Tyres & consumables"
              - Inspection records
              - Approved repairers
            vocabulary:
              - { term: Defect, runtime_type: Event }
              - { term: Service schedule, runtime_type: Object }
              - { term: Technician, runtime_type: Actor }
              - { term: Workshop booking, runtime_type: Object }
              - { term: Raise a defect, runtime_type: Event }
              - { term: Roadworthy / VOR, runtime_type: State }
              - { term: Repair authorisation, runtime_type: Decision }
              - { term: Inspection record, runtime_type: Artefact }
              - { term: Service due, runtime_type: Event }
              - { term: Maintenance workflow, runtime_type: Workflow }
              - { term: Vehicle back on road, runtime_type: Outcome }
              - { term: VOR days, runtime_type: Learning }
              - { term: Mean time to repair, runtime_type: Learning }
          - name: "Compliance & Operator Licence"
            note: "Regulated: operator licensing, tachograph/drivers'-hours and walkaround-check duties are enforced by traffic commissioners / DVSA and EU equivalents."
            operating_domains:
              - Operator licence conditions
              - "Tachograph & drivers' hours"
              - Walkaround checks
              - Driver licence checks
              - Audit trail / earned recognition
              - Transport manager duties
              - Roadside encounter records
            vocabulary:
              - { term: Operator licence, runtime_type: Artefact }
              - { term: Transport manager, runtime_type: Actor }
              - { term: Walkaround check, runtime_type: Event }
              - { term: Tachograph record, runtime_type: Artefact }
              - { term: "Drivers' hours rules", runtime_type: Object }
              - { term: Compliant / in breach, runtime_type: State }
              - { term: Infringement decision, runtime_type: Decision }
              - { term: Licence check, runtime_type: Event }
              - { term: Compliance audit, runtime_type: Workflow }
              - { term: Earned recognition status, runtime_type: Outcome }
              - { term: Infringement rate, runtime_type: Learning }
              - { term: Driver CPC, runtime_type: Artefact }
              - { term: Roadside prohibition, runtime_type: Event }
          - name: "Fuel, Energy & EV Charging"
            operating_domains:
              - Fuel cards
              - Charging network access
              - "Home & depot charging"
              - Energy reimbursement
              - Charge sessions
              - "Range & SoC monitoring"
              - Tariff management
            vocabulary:
              - { term: Fuel card, runtime_type: Object }
              - { term: Charge session, runtime_type: Event }
              - { term: Charge point, runtime_type: Object }
              - { term: Energy provider, runtime_type: Actor }
              - { term: State of charge, runtime_type: State }
              - { term: Reimbursement rate decision, runtime_type: Decision }
              - { term: "Top-up event", runtime_type: Event }
              - { term: Tariff plan, runtime_type: Artefact }
              - { term: Energy reconciliation, runtime_type: Workflow }
              - { term: "Cost-per-kWh", runtime_type: Outcome }
              - { term: Energy spend per mile, runtime_type: Learning }
              - { term: "Home-charging reimbursement", runtime_type: Artefact }
          - name: "Accident & Risk Management"
            operating_domains:
              - Incident reports
              - FNOL (first notification of loss)
              - Damage assessment
              - "Claims & repairs"
              - Driver risk profiles
              - "Insurance & excess"
              - Dashcam / evidence
            vocabulary:
              - { term: Incident, runtime_type: Event }
              - { term: First notification of loss, runtime_type: Event }
              - { term: Claims handler, runtime_type: Actor }
              - { term: Damage report, runtime_type: Artefact }
              - { term: "At-fault / non-fault", runtime_type: State }
              - { term: Liability decision, runtime_type: Decision }
              - { term: Repair authorisation, runtime_type: Decision }
              - { term: Dashcam evidence, runtime_type: Artefact }
              - { term: Claim lifecycle, runtime_type: Workflow }
              - { term: Claim settled, runtime_type: Outcome }
              - { term: Driver risk profile, runtime_type: Object }
              - { term: Incident rate per million miles, runtime_type: Learning }
              - { term: Total cost of risk, runtime_type: Learning }
      - name: "n-leasingOS"
        buyer: "Leasing & contract-hire company finance/asset directors who own the vehicle as a financial asset and earn the spread on the contract."
        os_test: "Its own buyer (lessor finance/asset org), a balance-sheet of vehicles funded as assets, a frontend built around contracts and residual values, a distinctive state model (quoted→live contract→in arrears→terminated→remarketed), and a vocabulary (residual value, contract hire, early termination, RV risk) unique to asset finance."
        sectors:
          - name: "Quotation & Contract Origination"
            operating_domains:
              - Quote builder
              - Contract types (PCH/BCH/finance lease)
              - "Term & mileage profiles"
              - "Rate cards & funding rates"
              - Customer order pipeline
              - Manufacturer support
              - "Order-to-delivery tracking"
            vocabulary:
              - { term: Lease quote, runtime_type: Artefact }
              - { term: Contract hire agreement, runtime_type: Object }
              - { term: Account manager, runtime_type: Actor }
              - { term: "Term & mileage profile", runtime_type: Object }
              - { term: Rate card, runtime_type: Artefact }
              - { term: Quote accepted, runtime_type: Event }
              - { term: Quoted / live / cancelled, runtime_type: State }
              - { term: Pricing decision, runtime_type: Decision }
              - { term: Order placed, runtime_type: Event }
              - { term: Origination workflow, runtime_type: Workflow }
              - { term: Contract activated, runtime_type: Outcome }
              - { term: "Quote-to-order conversion", runtime_type: Learning }
              - { term: Funder, runtime_type: Actor }
          - name: "Credit & Affordability"
            note: "Regulated: consumer leasing/credit is a regulated financial activity (FCA in the UK) requiring affordability and creditworthiness assessment."
            operating_domains:
              - Customer credit applications
              - Affordability checks
              - "Credit limits & exposure"
              - Director guarantees
              - Decisioning rules
              - KYC / fraud checks
              - Approved customer book
            vocabulary:
              - { term: Credit application, runtime_type: Object }
              - { term: Underwriter, runtime_type: Actor }
              - { term: Affordability check, runtime_type: Event }
              - { term: Credit limit, runtime_type: Object }
              - { term: Approved / declined / referred, runtime_type: State }
              - { term: Underwriting decision, runtime_type: Decision }
              - { term: KYC verification, runtime_type: Event }
              - { term: Credit agreement, runtime_type: Artefact }
              - { term: Decisioning workflow, runtime_type: Workflow }
              - { term: Exposure approved, runtime_type: Outcome }
              - { term: Approval rate, runtime_type: Learning }
              - { term: "Default-loss rate", runtime_type: Learning }
              - { term: Director guarantee, runtime_type: Artefact }
          - name: "Residual Value & Asset Risk"
            operating_domains:
              - RV setting
              - "Used-market forecasts"
              - Portfolio RV exposure
              - Depreciation curves
              - Mileage adjustment
              - Provisioning
              - "Manufacturer future-value data"
            vocabulary:
              - { term: Residual value, runtime_type: Object }
              - { term: RV setter, runtime_type: Actor }
              - { term: Depreciation curve, runtime_type: Object }
              - { term: "Market re-forecast", runtime_type: Event }
              - { term: RV position (gain/loss), runtime_type: State }
              - { term: RV setting decision, runtime_type: Decision }
              - { term: RV review, runtime_type: Workflow }
              - { term: RV matrix, runtime_type: Artefact }
              - { term: Provision booked, runtime_type: Event }
              - { term: Residual gain/loss, runtime_type: Outcome }
              - { term: RV accuracy, runtime_type: Learning }
              - { term: "Forecast-vs-actual variance", runtime_type: Learning }
          - name: "Contract Servicing & Billing"
            operating_domains:
              - Live contract book
              - Rental invoicing
              - "Mid-term amendments"
              - Mileage reconciliation
              - "Arrears & collections"
              - Excess mileage charges
              - "Customer self-service portal"
            vocabulary:
              - { term: Live contract, runtime_type: Object }
              - { term: Rental invoice, runtime_type: Artefact }
              - { term: Servicing agent, runtime_type: Actor }
              - { term: "Mid-term amendment", runtime_type: Event }
              - { term: "Up-to-date / in arrears", runtime_type: State }
              - { term: "Excess-mileage decision", runtime_type: Decision }
              - { term: "Direct-debit collection", runtime_type: Event }
              - { term: Statement of account, runtime_type: Artefact }
              - { term: Billing run, runtime_type: Workflow }
              - { term: Payment collected, runtime_type: Outcome }
              - { term: Arrears rate, runtime_type: Learning }
              - { term: Days sales outstanding, runtime_type: Learning }
          - name: "End-of-Contract & Remarketing"
            operating_domains:
              - Contract maturities
              - "Vehicle returns & inspections"
              - "Fair-wear-and-tear assessment"
              - Damage recharges
              - Early terminations
              - "De-fleet & remarketing"
              - "Auction & disposal channels"
            vocabulary:
              - { term: Returned vehicle, runtime_type: Object }
              - { term: Inspection agent, runtime_type: Actor }
              - { term: Vehicle return, runtime_type: Event }
              - { term: Fair wear and tear standard, runtime_type: Object }
              - { term: Maturing / returned / sold, runtime_type: State }
              - { term: "Damage-recharge decision", runtime_type: Decision }
              - { term: Early termination request, runtime_type: Event }
              - { term: "End-of-contract report", runtime_type: Artefact }
              - { term: Remarketing workflow, runtime_type: Workflow }
              - { term: Disposal proceeds, runtime_type: Outcome }
              - { term: Damage recharge, runtime_type: Artefact }
              - { term: "Recovery-vs-RV ratio", runtime_type: Learning }
      - name: "n-dealerOS"
        buyer: Dealer principal / dealer group owner who buys and sells vehicles for margin and runs the showroom as a profit centre.
        os_test: "Its own buyer (dealer principal), trading-margin economics, a frontend built around stock and deals on the forecourt, a distinctive state model (lead→test drive→deal→delivered, stock in→aged→sold), and a vocabulary (forecourt, part-exchange, F&I, days-in-stock) the rest of the market doesn't share."
        sectors:
          - name: "Vehicle Stock & Inventory"
            operating_domains:
              - Forecourt stock
              - "Vehicle acquisition (PX, auction, trade)"
              - "Stock pricing & repricing"
              - "Ageing & overage stock"
              - "Prep & reconditioning"
              - Stock location / pitch
              - Online merchandising
            vocabulary:
              - { term: Stock vehicle, runtime_type: Object }
              - { term: Forecourt, runtime_type: Object }
              - { term: Buyer / stock controller, runtime_type: Actor }
              - { term: Vehicle taken in, runtime_type: Event }
              - { term: In stock / sold / SOR, runtime_type: State }
              - { term: Repricing decision, runtime_type: Decision }
              - { term: Reconditioning order, runtime_type: Workflow }
              - { term: Stock advert, runtime_type: Artefact }
              - { term: Vehicle prepped, runtime_type: Event }
              - { term: Vehicle sold, runtime_type: Outcome }
              - { term: Days in stock, runtime_type: Learning }
              - { term: Stock turn, runtime_type: Learning }
              - { term: "Price-to-market position", runtime_type: State }
          - name: "Sales & Showroom"
            operating_domains:
              - Enquiry / lead pipeline
              - Test drives
              - "Deal building & negotiation"
              - "Part-exchange valuations"
              - Order taking
              - Showroom appointments
              - Salesperson performance
            vocabulary:
              - { term: Enquiry / lead, runtime_type: Object }
              - { term: Salesperson, runtime_type: Actor }
              - { term: Test drive, runtime_type: Event }
              - { term: Deal, runtime_type: Object }
              - { term: "Part-exchange valuation", runtime_type: Decision }
              - { term: Open / won / lost, runtime_type: State }
              - { term: Order form, runtime_type: Artefact }
              - { term: Deal closed, runtime_type: Event }
              - { term: Sales handover, runtime_type: Workflow }
              - { term: Vehicle delivered, runtime_type: Outcome }
              - { term: "Lead-to-sale conversion", runtime_type: Learning }
              - { term: Units per salesperson, runtime_type: Learning }
              - { term: Customer, runtime_type: Actor }
          - name: "Finance & Insurance (F&I)"
            note: "Regulated: arranging motor finance and insurance add-ons is FCA-regulated, with mandatory affordability and commission-disclosure duties."
            operating_domains:
              - Finance products (HP/PCP)
              - "Lender panel & proposals"
              - "Add-on products (GAP, warranty)"
              - "Commission & disclosure"
              - "Finance documents & e-sign"
              - Affordability checks
              - "F&I penetration tracking"
            vocabulary:
              - { term: Finance proposal, runtime_type: Object }
              - { term: Business manager, runtime_type: Actor }
              - { term: Lender panel, runtime_type: Object }
              - { term: Proposal submitted, runtime_type: Event }
              - { term: Approved / declined, runtime_type: State }
              - { term: Product recommendation, runtime_type: Decision }
              - { term: Finance agreement, runtime_type: Artefact }
              - { term: Commission disclosure, runtime_type: Artefact }
              - { term: Finance signed, runtime_type: Event }
              - { term: "F&I workflow", runtime_type: Workflow }
              - { term: Finance income earned, runtime_type: Outcome }
              - { term: "F&I penetration", runtime_type: Learning }
              - { term: "Add-on attach rate", runtime_type: Learning }
          - name: "Aftersales & Workshop"
            note: "Regulated: MOT testing is statutory and conducted only at approved test stations under road-vehicle testing law."
            operating_domains:
              - Service bookings
              - Repair orders / job cards
              - Technician scheduling
              - Parts counter
              - "MOT & servicing"
              - "Upsell & VHC"
              - "Workshop loading & efficiency"
            vocabulary:
              - { term: Repair order, runtime_type: Object }
              - { term: Service advisor, runtime_type: Actor }
              - { term: Job card, runtime_type: Artefact }
              - { term: Booking made, runtime_type: Event }
              - { term: "Open / in-progress / invoiced", runtime_type: State }
              - { term: Authorise additional work, runtime_type: Decision }
              - { term: Vehicle health check, runtime_type: Artefact }
              - { term: Vehicle collected, runtime_type: Event }
              - { term: Aftersales workflow, runtime_type: Workflow }
              - { term: Hours sold, runtime_type: Outcome }
              - { term: Technician efficiency, runtime_type: Learning }
              - { term: Upsell per RO, runtime_type: Learning }
              - { term: MOT, runtime_type: Event }
          - name: "Dealer Finance & Profitability"
            operating_domains:
              - Stocking loans (floorplan)
              - "Departmental P&L"
              - Composite/benchmark reporting
              - "Manufacturer bonuses & targets"
              - "Vehicle gross-profit tracking"
              - VAT margin scheme
              - "Cash & overage exposure"
            vocabulary:
              - { term: Floorplan facility, runtime_type: Object }
              - { term: Dealer principal, runtime_type: Actor }
              - { term: Stocking interest accrual, runtime_type: Event }
              - { term: "Funded / paid-out", runtime_type: State }
              - { term: Manufacturer bonus decision, runtime_type: Decision }
              - { term: "Departmental P&L", runtime_type: Artefact }
              - { term: "Month-end close", runtime_type: Workflow }
              - { term: Composite report, runtime_type: Artefact }
              - { term: Gross profit per unit, runtime_type: Outcome }
              - { term: Return on sales, runtime_type: Learning }
              - { term: Stocking days exposure, runtime_type: Learning }
              - { term: "Margin-scheme VAT record", runtime_type: Artefact }
      - name: "n-serviceOS"
        buyer: "Independent garage / fast-fit / bodyshop owner who sells labour and parts on vehicles they do not own."
        os_test: "Its own buyer (workshop/bodyshop owner), labour-and-parts economics, a frontend built around the ramp and the job, a distinctive state model (booked→on ramp→awaiting parts→QC→collected), and a vocabulary (estimate, courtesy car, parts ETA, labour rate) distinct from a dealer's franchised aftersales."
        sectors:
          - name: "Booking & Workshop Scheduling"
            operating_domains:
              - "Online & phone bookings"
              - Ramp / bay capacity
              - Technician diary
              - Courtesy cars
              - "Wait-vs-leave jobs"
              - "Reminders & rebooking"
              - "Walk-ins"
            vocabulary:
              - { term: Booking, runtime_type: Object }
              - { term: Workshop bay, runtime_type: Object }
              - { term: Technician, runtime_type: Actor }
              - { term: Customer arrives, runtime_type: Event }
              - { term: "Booked / arrived / no-show", runtime_type: State }
              - { term: Slot allocation decision, runtime_type: Decision }
              - { term: Courtesy car, runtime_type: Object }
              - { term: Reminder sent, runtime_type: Event }
              - { term: Booking workflow, runtime_type: Workflow }
              - { term: Diary confirmation, runtime_type: Artefact }
              - { term: Bay utilisation, runtime_type: Learning }
              - { term: "No-show rate", runtime_type: Learning }
          - name: "Diagnostics & Estimating"
            operating_domains:
              - Fault diagnosis
              - Diagnostic trouble codes
              - "Estimates & quotes"
              - "Labour-time lookup"
              - Repair authorisation
              - Photo/video estimate evidence
              - Approval tracking
            vocabulary:
              - { term: Fault report, runtime_type: Object }
              - { term: Diagnostic code, runtime_type: Object }
              - { term: Diagnostic technician, runtime_type: Actor }
              - { term: Diagnosis performed, runtime_type: Event }
              - { term: Estimate, runtime_type: Artefact }
              - { term: Awaiting approval / approved, runtime_type: State }
              - { term: Repair authorisation, runtime_type: Decision }
              - { term: Video estimate, runtime_type: Artefact }
              - { term: Approval received, runtime_type: Event }
              - { term: Estimating workflow, runtime_type: Workflow }
              - { term: Estimate approval rate, runtime_type: Learning }
              - { term: Diagnostic accuracy, runtime_type: Learning }
          - name: "Repair Execution & Parts"
            operating_domains:
              - Job cards
              - Labour time recording
              - "Parts ordering & ETA"
              - Parts fitment
              - Sublet / specialist work
              - "Quality control sign-off"
              - "Vehicle ready-for-collection"
            vocabulary:
              - { term: Job card, runtime_type: Object }
              - { term: Part, runtime_type: Object }
              - { term: Parts supplier, runtime_type: Actor }
              - { term: Part ordered, runtime_type: Event }
              - { term: On ramp / awaiting parts / QC, runtime_type: State }
              - { term: Sublet decision, runtime_type: Decision }
              - { term: "QC sign-off", runtime_type: Event }
              - { term: Repair workflow, runtime_type: Workflow }
              - { term: Completed job, runtime_type: Artefact }
              - { term: Vehicle ready, runtime_type: Outcome }
              - { term: Comeback / rework rate, runtime_type: Learning }
              - { term: Parts ETA accuracy, runtime_type: Learning }
          - name: "Accident Repair & Bodyshop"
            note: "Regulated: accident repairers handling structural/safety repairs and refinishing work to insurer/industry approval standards (e.g. BSI Kitemark / PAS 125)."
            operating_domains:
              - "Insurer & work-provider jobs"
              - "Damage assessment & estimates"
              - "Paint & panel scheduling"
              - "Parts & paint mixing"
              - Courtesy car management
              - "Total-loss handling"
              - "Key-to-key cycle"
            vocabulary:
              - { term: Repair job, runtime_type: Object }
              - { term: Estimator, runtime_type: Actor }
              - { term: Insurer / work provider, runtime_type: Actor }
              - { term: Job authorised, runtime_type: Event }
              - { term: Repairable / total loss, runtime_type: State }
              - { term: "Repair-vs-write-off decision", runtime_type: Decision }
              - { term: Damage estimate, runtime_type: Artefact }
              - { term: Vehicle returned to customer, runtime_type: Event }
              - { term: Bodyshop workflow, runtime_type: Workflow }
              - { term: "Key-to-key time", runtime_type: Outcome }
              - { term: Cycle time, runtime_type: Learning }
              - { term: Touch time vs idle time, runtime_type: Learning }
          - name: "Statutory Testing (MOT & Inspections)"
            note: "Regulated: MOT testing is statutory; only DVSA-authorised testers at approved test stations may issue certificates."
            operating_domains:
              - MOT test slots
              - Test certificates
              - "Advisories & failures"
              - Retests
              - Tester credentials
              - "Test-station compliance"
              - Reminder marketing
            vocabulary:
              - { term: MOT test, runtime_type: Event }
              - { term: Nominated tester, runtime_type: Actor }
              - { term: Test certificate, runtime_type: Artefact }
              - { term: Pass / fail / advisory, runtime_type: State }
              - { term: Defect classification decision, runtime_type: Decision }
              - { term: Test slot, runtime_type: Object }
              - { term: Retest, runtime_type: Event }
              - { term: Testing workflow, runtime_type: Workflow }
              - { term: Certificate issued, runtime_type: Outcome }
              - { term: Test station, runtime_type: Object }
              - { term: "First-time pass rate", runtime_type: Learning }
              - { term: Advisory conversion rate, runtime_type: Learning }
      - name: "n-mobilityOS"
        buyer: "Mobility operator / product owner (car-share, rental, ride-hail, micromobility) who monetises access to vehicles by the trip or minute."
        os_test: "Its own buyer (mobility operator), trip/utilisation revenue model, a frontend built around the live trip and the rider, a distinctive state model (vehicle available→reserved→on trip→ended, rider requested→matched→completed), and a vocabulary (trip, ride, surge, dock, idle vehicle) no asset-finance or workshop user shares."
        sectors:
          - name: "Car-Sharing & Short-Term Rental"
            note: "Regulated: vehicle hire requires driver-licence verification and consumer-rental disclosure; insurance cover must be arranged for hirers."
            operating_domains:
              - Available vehicle fleet
              - "Reservations & bookings"
              - "Unlock / start-stop"
              - "Damage & cleanliness reports"
              - "Pricing & packages"
              - Fleet rebalancing
              - Member accounts
            vocabulary:
              - { term: Shared vehicle, runtime_type: Object }
              - { term: Member, runtime_type: Actor }
              - { term: Reservation, runtime_type: Object }
              - { term: Vehicle unlocked, runtime_type: Event }
              - { term: Available / reserved / on trip, runtime_type: State }
              - { term: Pricing decision, runtime_type: Decision }
              - { term: Rental agreement, runtime_type: Artefact }
              - { term: Trip ended, runtime_type: Event }
              - { term: Booking workflow, runtime_type: Workflow }
              - { term: Trip revenue, runtime_type: Outcome }
              - { term: Utilisation rate, runtime_type: Learning }
              - { term: Revenue per vehicle per day, runtime_type: Learning }
          - name: "Ride-Hailing & Dispatch"
            note: "Regulated: private-hire/taxi operation requires operator and driver licensing and vehicle licensing from the local licensing authority."
            operating_domains:
              - Ride requests
              - "Driver matching & dispatch"
              - Live trip tracking
              - Dynamic pricing / surge
              - "Driver supply & incentives"
              - "Ratings & disputes"
              - Service zones
            vocabulary:
              - { term: Ride request, runtime_type: Object }
              - { term: Rider, runtime_type: Actor }
              - { term: "Driver-partner", runtime_type: Actor }
              - { term: Trip matched, runtime_type: Event }
              - { term: Requested / matched / completed, runtime_type: State }
              - { term: "Surge-pricing decision", runtime_type: Decision }
              - { term: Trip receipt, runtime_type: Artefact }
              - { term: Dispatch workflow, runtime_type: Workflow }
              - { term: Trip completed, runtime_type: Outcome }
              - { term: Service zone, runtime_type: Object }
              - { term: Acceptance rate, runtime_type: Learning }
              - { term: Average wait time, runtime_type: Learning }
          - name: "Micromobility (Bikes & Scooters)"
            note: "Regulated: shared e-scooter/e-bike schemes operate under local-authority trial permits and parking/road-use bylaws."
            operating_domains:
              - Scooter/bike fleet
              - Geofenced zones
              - Parking compliance
              - "Battery swaps & charging"
              - Field operations / juicers
              - Ride sessions
              - "No-go & slow zones"
            vocabulary:
              - { term: "Scooter / e-bike", runtime_type: Object }
              - { term: Rider, runtime_type: Actor }
              - { term: Field operative, runtime_type: Actor }
              - { term: Ride started, runtime_type: Event }
              - { term: "Deployed / low-battery / impounded", runtime_type: State }
              - { term: Rebalancing decision, runtime_type: Decision }
              - { term: "No-go zone", runtime_type: Object }
              - { term: Battery swap, runtime_type: Event }
              - { term: "Field-ops workflow", runtime_type: Workflow }
              - { term: Rides per vehicle per day, runtime_type: Outcome }
              - { term: Fleet availability, runtime_type: Learning }
              - { term: "Parking-compliance rate", runtime_type: Learning }
          - name: "Subscription & Flexible Access"
            note: "Regulated: consumer subscription contracts and any embedded finance/insurance must meet consumer-credit and fair-terms rules."
            operating_domains:
              - Subscription plans
              - Vehicle swaps
              - "Onboarding & ID checks"
              - Recurring billing
              - "Pause & cancel"
              - "All-inclusive servicing"
              - Member retention
            vocabulary:
              - { term: Subscription, runtime_type: Object }
              - { term: Subscriber, runtime_type: Actor }
              - { term: Vehicle swap, runtime_type: Event }
              - { term: Active / paused / churned, runtime_type: State }
              - { term: "Swap-eligibility decision", runtime_type: Decision }
              - { term: Subscription agreement, runtime_type: Artefact }
              - { term: Recurring charge taken, runtime_type: Event }
              - { term: Onboarding workflow, runtime_type: Workflow }
              - { term: Monthly recurring revenue, runtime_type: Outcome }
              - { term: Churn rate, runtime_type: Learning }
              - { term: Lifetime value, runtime_type: Learning }
              - { term: Vehicle allocation, runtime_type: Object }
          - name: "Charging & Energy Operations (CPO)"
            note: "Regulated: public charge-point operators must meet reliability, pricing-transparency and payment-interoperability rules (e.g. UK Public Charge Point Regulations)."
            operating_domains:
              - "Charge-point network"
              - Charging sessions
              - "Tariffs & roaming"
              - "Uptime & faults"
              - Site host agreements
              - "Load & grid management"
              - "Driver app & payments"
            vocabulary:
              - { term: Charge point, runtime_type: Object }
              - { term: EV driver, runtime_type: Actor }
              - { term: Charging session, runtime_type: Event }
              - { term: Available / charging / faulted, runtime_type: State }
              - { term: "Dynamic-tariff decision", runtime_type: Decision }
              - { term: Session receipt, runtime_type: Artefact }
              - { term: Fault raised, runtime_type: Event }
              - { term: Maintenance workflow, runtime_type: Workflow }
              - { term: Energy delivered (kWh), runtime_type: Outcome }
              - { term: Site host, runtime_type: Actor }
              - { term: Network uptime, runtime_type: Learning }
              - { term: Utilisation per charger, runtime_type: Learning }
      - name: "n-transportOS"
        buyer: "Logistics / passenger-transport operations director who plans and runs vehicle movements to move goods or people on a schedule."
        os_test: "Its own buyer (logistics/transport ops director), movement-cost-and-service economics, a frontend built around routes, loads and timetables, a distinctive state model (planned→dispatched→in transit→delivered, on-time→delayed), and a vocabulary (consignment, route, depot, ETA, POD, headway) distinct from owning or trading a vehicle."
        sectors:
          - name: "Freight & Haulage Operations"
            note: "Regulated: goods-vehicle operators require an O-licence and must observe drivers'-hours and tachograph law."
            operating_domains:
              - Consignments / loads
              - "Vehicle & trailer allocation"
              - "Routes & drops"
              - Driver assignments
              - "Depots & yards"
              - Proof of delivery
              - "Backloads & utilisation"
            vocabulary:
              - { term: Consignment, runtime_type: Object }
              - { term: HGV driver, runtime_type: Actor }
              - { term: Load allocated, runtime_type: Event }
              - { term: Planned / in transit / delivered, runtime_type: State }
              - { term: "Load-planning decision", runtime_type: Decision }
              - { term: Proof of delivery, runtime_type: Artefact }
              - { term: Run sheet, runtime_type: Artefact }
              - { term: Dispatch workflow, runtime_type: Workflow }
              - { term: "On-time delivery", runtime_type: Outcome }
              - { term: Depot, runtime_type: Object }
              - { term: "Empty-running percentage", runtime_type: Learning }
              - { term: Cost per drop, runtime_type: Learning }
          - name: "Last-Mile Delivery"
            operating_domains:
              - Delivery routes
              - Parcels / stops
              - Courier allocation
              - "Time windows & SLAs"
              - "Customer tracking & notifications"
              - "Failed-delivery handling"
              - Returns
            vocabulary:
              - { term: Parcel, runtime_type: Object }
              - { term: Courier, runtime_type: Actor }
              - { term: Delivery route, runtime_type: Object }
              - { term: Out for delivery, runtime_type: Event }
              - { term: Delivered / failed / returned, runtime_type: State }
              - { term: "Re-attempt decision", runtime_type: Decision }
              - { term: Delivery proof / photo, runtime_type: Artefact }
              - { term: Route optimisation, runtime_type: Workflow }
              - { term: Successful delivery, runtime_type: Outcome }
              - { term: Estimated time of arrival, runtime_type: State }
              - { term: "First-time delivery rate", runtime_type: Learning }
              - { term: Stops per hour, runtime_type: Learning }
          - name: "Passenger Transport & Bus Operations"
            note: "Regulated: local bus services require PSV operator licensing and registered timetables with the traffic commissioner."
            operating_domains:
              - "Timetables & schedules"
              - "Routes & services"
              - "Vehicle & driver rosters"
              - "Stops & headways"
              - "Ticketing & fares"
              - Service disruptions
              - Punctuality monitoring
            vocabulary:
              - { term: Service / route, runtime_type: Object }
              - { term: Bus driver, runtime_type: Actor }
              - { term: Timetable, runtime_type: Artefact }
              - { term: Departure, runtime_type: Event }
              - { term: On time / delayed / cancelled, runtime_type: State }
              - { term: "Service-recovery decision", runtime_type: Decision }
              - { term: Duty roster, runtime_type: Artefact }
              - { term: Scheduling workflow, runtime_type: Workflow }
              - { term: Journeys operated, runtime_type: Outcome }
              - { term: Headway, runtime_type: Object }
              - { term: "Punctuality (on-time %)", runtime_type: Learning }
              - { term: Passenger journeys per mile, runtime_type: Learning }
          - name: "Route Planning & Optimisation"
            operating_domains:
              - "Demand & order intake"
              - Route building
              - "Constraints (windows, weights, skills)"
              - Scenario planning
              - "Plan-vs-actual"
              - "Re-routing"
              - Resource balancing
            vocabulary:
              - { term: Route plan, runtime_type: Artefact }
              - { term: Transport planner, runtime_type: Actor }
              - { term: Order / demand, runtime_type: Object }
              - { term: Plan published, runtime_type: Event }
              - { term: Draft / locked / executing, runtime_type: State }
              - { term: Optimisation decision, runtime_type: Decision }
              - { term: Constraint set, runtime_type: Object }
              - { term: Optimisation run, runtime_type: Workflow }
              - { term: Optimised plan, runtime_type: Outcome }
              - { term: "Re-route event", runtime_type: Event }
              - { term: "Plan-vs-actual variance", runtime_type: Learning }
              - { term: Vehicle fill rate, runtime_type: Learning }
          - name: "Cold Chain & Specialist Haulage"
            note: "Regulated: dangerous-goods carriage (ADR) and food cold-chain (HACCP) impose mandatory documentation, training and temperature-control duties."
            operating_domains:
              - "Temperature-controlled loads"
              - Reefer units
              - Temperature logging
              - Hazardous goods (ADR)
              - Compliance documents
              - Excursion alerts
              - "Chain-of-custody"
            vocabulary:
              - { term: "Temperature-controlled load", runtime_type: Object }
              - { term: Reefer unit, runtime_type: Object }
              - { term: Compliance officer, runtime_type: Actor }
              - { term: Temperature excursion, runtime_type: Event }
              - { term: In range / out of range, runtime_type: State }
              - { term: "Reject-or-accept decision", runtime_type: Decision }
              - { term: Temperature log, runtime_type: Artefact }
              - { term: "Dangerous-goods note", runtime_type: Artefact }
              - { term: "Cold-chain monitoring", runtime_type: Workflow }
              - { term: Load delivered in spec, runtime_type: Outcome }
              - { term: Excursion rate, runtime_type: Learning }
              - { term: "Chain-of-custody integrity", runtime_type: Learning }
  - name: Telecommunications
    os:
      - name: "n-telcoOS"
        buyer: "The communications service provider's commercial and operations leadership (CEO/COO/CFO of a telco operating a retail and wholesale comms business)."
        os_test: "A telco runs a distinct go-to-market business — products, tariffs, channels, billing, regulatory licences — with its own P&L owner, its own state model (subscriber lifecycle, product catalogue, settlement), and a vocabulary (ARPU, churn, MVNO, interconnect) that no other OS shares; repeatable across BT, Vodafone, Orange, AT&T."
        sectors:
          - name: "Retail Mobile & Plans"
            note: Mobile spectrum use and number allocation are licensed (Ofcom/national regulator); number porting timelines are mandated.
            operating_domains:
              - "Tariff and plan catalogue (pay-monthly, SIM-only, PAYG)"
              - Device financing and handset upgrade programmes
              - SIM and eSIM provisioning
              - "Add-on bundles (roaming passes, data boosters, content)"
              - "Family and shared-data accounts"
              - Number porting in and out
              - Retention and upgrade offers
            vocabulary:
              - { term: Tariff, runtime_type: Object }
              - { term: "SIM-only plan", runtime_type: Object }
              - { term: Subscriber, runtime_type: Actor }
              - { term: Handset upgrade, runtime_type: Decision }
              - { term: Number port, runtime_type: Workflow }
              - { term: eSIM activation, runtime_type: Event }
              - { term: Data booster, runtime_type: Object }
              - { term: Roaming pass, runtime_type: Object }
              - { term: Plan active, runtime_type: State }
              - { term: "Suspended for non-payment", runtime_type: State }
              - { term: Contract, runtime_type: Artefact }
              - { term: Upgrade eligibility check, runtime_type: Decision }
              - { term: Retention offer accepted, runtime_type: Outcome }
              - { term: Churn rate, runtime_type: Learning }
              - { term: ARPU, runtime_type: Learning }
              - { term: Welcome pack, runtime_type: Artefact }
          - name: "Fixed Broadband & Home"
            note: "Minimum-speed guarantees and migration (One Touch Switch) are regulator-mandated in many markets."
            operating_domains:
              - "Broadband product catalogue (FTTP, FTTC, cable, DSL tiers)"
              - Home install and engineer appointment scheduling
              - Router and CPE provisioning
              - Line activation and migration between providers
              - Home phone and VoIP lines
              - "Whole-home WiFi mesh and guarantee plans"
              - Fault diagnosis and repair dispatch
            vocabulary:
              - { term: Broadband package, runtime_type: Object }
              - { term: Router / CPE, runtime_type: Object }
              - { term: Engineer appointment, runtime_type: Event }
              - { term: Line activation, runtime_type: Workflow }
              - { term: Provider migration, runtime_type: Workflow }
              - { term: Account holder, runtime_type: Actor }
              - { term: Field engineer, runtime_type: Actor }
              - { term: Sync speed, runtime_type: State }
              - { term: Line live, runtime_type: State }
              - { term: Awaiting install, runtime_type: State }
              - { term: Installation order, runtime_type: Artefact }
              - { term: Speed guarantee, runtime_type: Decision }
              - { term: Fault ticket, runtime_type: Artefact }
              - { term: Connection restored, runtime_type: Outcome }
              - { term: "Right-first-time rate", runtime_type: Learning }
          - name: "Billing, Charging & Revenue"
            note: "Bill accuracy, spend caps and out-of-bundle alerts are regulated consumer-protection obligations."
            operating_domains:
              - Rating and charging of usage events
              - Invoice generation and bill cycles
              - Payment collection and direct debit runs
              - Dunning and debt management
              - "Discounts, promotions and bill credits"
              - Bill shock alerts and spend caps
              - Revenue assurance and leakage detection
            vocabulary:
              - { term: Usage record (CDR), runtime_type: Object }
              - { term: Invoice, runtime_type: Artefact }
              - { term: Bill cycle, runtime_type: Workflow }
              - { term: Rating, runtime_type: Workflow }
              - { term: Direct debit run, runtime_type: Event }
              - { term: Bill credit, runtime_type: Object }
              - { term: Spend cap, runtime_type: Object }
              - { term: In arrears, runtime_type: State }
              - { term: Paid in full, runtime_type: State }
              - { term: Dunning step, runtime_type: Decision }
              - { term: "Write-off decision", runtime_type: Decision }
              - { term: Billing agent, runtime_type: Actor }
              - { term: Payment received, runtime_type: Outcome }
              - { term: Revenue leakage, runtime_type: Learning }
              - { term: Collection rate, runtime_type: Learning }
          - name: "Wholesale & Interconnect"
            note: "Wholesale access and termination rates are price-regulated (significant market power remedies)."
            operating_domains:
              - Interconnect agreements with other carriers
              - Voice and SMS termination rates
              - Roaming agreements and IOT settlement
              - MVNO host capacity wholesale
              - "Inter-operator settlement and netting"
              - Carrier dispute and reconciliation
              - Wholesale line rental and access products
            vocabulary:
              - { term: Interconnect agreement, runtime_type: Artefact }
              - { term: Termination rate, runtime_type: Object }
              - { term: Roaming partner, runtime_type: Actor }
              - { term: Settlement run, runtime_type: Workflow }
              - { term: TAP file exchange, runtime_type: Event }
              - { term: Net position, runtime_type: State }
              - { term: Dispute open, runtime_type: State }
              - { term: Reconciliation, runtime_type: Workflow }
              - { term: Wholesale access product, runtime_type: Object }
              - { term: "Rate-change decision", runtime_type: Decision }
              - { term: Carrier, runtime_type: Actor }
              - { term: Settlement statement, runtime_type: Artefact }
              - { term: Balance settled, runtime_type: Outcome }
              - { term: Margin per minute, runtime_type: Learning }
          - name: "Enterprise & Business Comms"
            operating_domains:
              - Business mobile fleets and pooled data
              - Leased lines and dedicated internet access (DIA)
              - "SD-WAN and managed connectivity"
              - Unified communications (UCaaS) and SIP trunking
              - Service level agreement management
              - Bid and quote management for large accounts
              - Account onboarding and provisioning at scale
            vocabulary:
              - { term: Business account, runtime_type: Object }
              - { term: Leased line, runtime_type: Object }
              - { term: SIP trunk, runtime_type: Object }
              - { term: "SD-WAN service", runtime_type: Object }
              - { term: Account manager, runtime_type: Actor }
              - { term: SLA breach, runtime_type: Event }
              - { term: "Quote-to-order", runtime_type: Workflow }
              - { term: Provisioning, runtime_type: Workflow }
              - { term: In service, runtime_type: State }
              - { term: Under provisioning, runtime_type: State }
              - { term: Service credit decision, runtime_type: Decision }
              - { term: Master service agreement, runtime_type: Artefact }
              - { term: Service activated, runtime_type: Outcome }
              - { term: SLA attainment, runtime_type: Learning }
          - name: "Channels & Retail Distribution"
            operating_domains:
              - Physical store and franchise operations
              - Online sales journeys and basket
              - Dealer and indirect partner network
              - Stock and handset inventory across channels
              - Sales commissions and incentives
              - "Order fulfilment and click-and-collect"
              - Telesales and outbound campaigns
            vocabulary:
              - { term: Sales order, runtime_type: Object }
              - { term: Store, runtime_type: Object }
              - { term: Dealer partner, runtime_type: Actor }
              - { term: Sales advisor, runtime_type: Actor }
              - { term: Order placed, runtime_type: Event }
              - { term: "Click-and-collect", runtime_type: Workflow }
              - { term: Commission run, runtime_type: Workflow }
              - { term: In stock, runtime_type: State }
              - { term: Order fulfilled, runtime_type: State }
              - { term: "Credit-check decision", runtime_type: Decision }
              - { term: Sales receipt, runtime_type: Artefact }
              - { term: Conversion, runtime_type: Outcome }
              - { term: Channel mix, runtime_type: Learning }
              - { term: Cost per acquisition, runtime_type: Learning }
      - name: "n-networkOS"
        buyer: "The network operations and engineering organisation (CTO / VP of Network Operations) responsible for keeping the live radio, core and transport network running."
        os_test: "Network operations is a separate world from the commercial telco: its buyer owns a NOC budget and OSS stack, its state model is cells/nodes/alarms/SLAs (not subscribers and tariffs), and its vocabulary (KPI, alarm correlation, RAN, packet core) is meaningless to billing; repeatable across every operator and tower-network alike."
        sectors:
          - name: Radio Access Network (RAN) Operations
            note: Radio transmission operates under spectrum licences and EMF/RF exposure limits set by the national regulator.
            operating_domains:
              - Cell site and sector configuration
              - Coverage and capacity planning
              - Spectrum and carrier allocation per cell
              - Handover and neighbour relation tuning
              - "Drive-test and field measurement campaigns"
              - RAN software upgrades and rollouts
              - "Energy and sleep-mode management of radios"
            vocabulary:
              - { term: Cell site, runtime_type: Object }
              - { term: Sector, runtime_type: Object }
              - { term: Carrier / band, runtime_type: Object }
              - { term: Neighbour relation, runtime_type: Object }
              - { term: RF engineer, runtime_type: Actor }
              - { term: Handover failure, runtime_type: Event }
              - { term: Cell up, runtime_type: State }
              - { term: Cell down / outage, runtime_type: State }
              - { term: "Carrier re-tune", runtime_type: Workflow }
              - { term: "Power-tilt decision", runtime_type: Decision }
              - { term: "Drive-test campaign", runtime_type: Workflow }
              - { term: Coverage map, runtime_type: Artefact }
              - { term: Coverage restored, runtime_type: Outcome }
              - { term: "Dropped-call rate", runtime_type: Learning }
              - { term: Spectral efficiency, runtime_type: Learning }
          - name: "Core & Packet Network"
            note: "Lawful intercept and emergency-call (E911/112) routing are mandated in the core."
            operating_domains:
              - Packet core nodes (5GC / EPC) lifecycle
              - Subscriber session and bearer management
              - Voice core (IMS) and VoLTE/VoNR
              - Policy and charging control (PCF/PCRF)
              - "DNS, signalling (Diameter/SIP) routing"
              - Capacity scaling and pool balancing
              - Core software patching and change windows
            vocabulary:
              - { term: Core node (AMF/SMF/UPF), runtime_type: Object }
              - { term: Subscriber session, runtime_type: Object }
              - { term: Bearer, runtime_type: Object }
              - { term: Policy rule, runtime_type: Object }
              - { term: Core engineer, runtime_type: Actor }
              - { term: Signalling storm, runtime_type: Event }
              - { term: Session active, runtime_type: State }
              - { term: Node in maintenance, runtime_type: State }
              - { term: Change window, runtime_type: Workflow }
              - { term: Failover decision, runtime_type: Decision }
              - { term: "Capacity scale-out", runtime_type: Workflow }
              - { term: Change record, runtime_type: Artefact }
              - { term: Service stable, runtime_type: Outcome }
              - { term: Session setup success rate, runtime_type: Learning }
          - name: "Transport & Backhaul"
            operating_domains:
              - Fibre and microwave backhaul links
              - "IP/MPLS and segment-routing backbone"
              - DWDM optical transport and wavelengths
              - Synchronisation and timing distribution
              - Capacity and route planning
              - Link protection and rerouting
              - Peering and transit interconnection
            vocabulary:
              - { term: Backhaul link, runtime_type: Object }
              - { term: Wavelength / lambda, runtime_type: Object }
              - { term: MPLS path, runtime_type: Object }
              - { term: Timing source, runtime_type: Object }
              - { term: Transport engineer, runtime_type: Actor }
              - { term: Fibre cut, runtime_type: Event }
              - { term: Link up, runtime_type: State }
              - { term: Link degraded, runtime_type: State }
              - { term: Reroute, runtime_type: Workflow }
              - { term: "Path-protection switch", runtime_type: Decision }
              - { term: Capacity augment, runtime_type: Workflow }
              - { term: Network diagram, runtime_type: Artefact }
              - { term: Traffic restored, runtime_type: Outcome }
              - { term: Link utilisation, runtime_type: Learning }
              - { term: Latency budget, runtime_type: Learning }
          - name: "Network Assurance & NOC"
            note: Major outages affecting emergency services must be reported to the regulator within mandated timeframes.
            operating_domains:
              - Fault and alarm monitoring across domains
              - "Alarm correlation and root-cause analysis"
              - "Incident bridge and major-incident management"
              - Performance KPI dashboards and thresholds
              - "Trouble-ticket lifecycle and escalation"
              - "Service-impact analysis and customer comms"
              - "Post-incident review and problem management"
            vocabulary:
              - { term: Alarm, runtime_type: Event }
              - { term: Incident, runtime_type: Object }
              - { term: Trouble ticket, runtime_type: Artefact }
              - { term: Correlation rule, runtime_type: Object }
              - { term: NOC operator, runtime_type: Actor }
              - { term: Major incident declared, runtime_type: Event }
              - { term: Open / acknowledged, runtime_type: State }
              - { term: Resolved, runtime_type: State }
              - { term: Triage, runtime_type: Workflow }
              - { term: Escalation decision, runtime_type: Decision }
              - { term: "Root-cause analysis", runtime_type: Workflow }
              - { term: "Post-incident report", runtime_type: Artefact }
              - { term: Service restored, runtime_type: Outcome }
              - { term: Mean time to repair, runtime_type: Learning }
              - { term: Network availability, runtime_type: Learning }
          - name: "Network Planning & Optimisation"
            operating_domains:
              - Demand forecasting and traffic modelling
              - Site acquisition and rollout planning
              - Capacity expansion and densification
              - "Self-organising network (SON) tuning"
              - "Parameter audit and golden-config baselines"
              - "What-if simulation of network changes"
              - Investment prioritisation across regions
            vocabulary:
              - { term: Forecast model, runtime_type: Object }
              - { term: Rollout plan, runtime_type: Artefact }
              - { term: Candidate site, runtime_type: Object }
              - { term: Golden config, runtime_type: Object }
              - { term: Planning engineer, runtime_type: Actor }
              - { term: Densification project, runtime_type: Workflow }
              - { term: SON loop, runtime_type: Workflow }
              - { term: Planned / on hold, runtime_type: State }
              - { term: Congested cell, runtime_type: State }
              - { term: "Investment-priority decision", runtime_type: Decision }
              - { term: "What-if simulation", runtime_type: Event }
              - { term: Capacity plan, runtime_type: Artefact }
              - { term: Bottleneck cleared, runtime_type: Outcome }
              - { term: "Busy-hour utilisation", runtime_type: Learning }
          - name: "Network Security & Resilience"
            note: "Telecom security obligations (e.g. UK Telecoms Security Act, lawful intercept, data retention) are statutory."
            operating_domains:
              - DDoS detection and mitigation
              - Signalling firewall (SS7/Diameter/GTP) defence
              - "SIM-swap and fraud signalling monitoring"
              - "Supply-chain and vendor equipment assurance"
              - Network slicing isolation and policy
              - "Disaster recovery and geo-redundancy drills"
              - "Lawful intercept and data-retention gateways"
            vocabulary:
              - { term: Threat signature, runtime_type: Object }
              - { term: Signalling firewall, runtime_type: Object }
              - { term: Security analyst, runtime_type: Actor }
              - { term: DDoS attack, runtime_type: Event }
              - { term: Mitigation engaged, runtime_type: State }
              - { term: Under attack, runtime_type: State }
              - { term: Block / scrub decision, runtime_type: Decision }
              - { term: DR failover drill, runtime_type: Workflow }
              - { term: Intercept warrant, runtime_type: Artefact }
              - { term: Threat contained, runtime_type: Outcome }
              - { term: Incident log, runtime_type: Artefact }
              - { term: Slice isolation policy, runtime_type: Object }
              - { term: Vendor assurance review, runtime_type: Workflow }
              - { term: Mean time to detect, runtime_type: Learning }
      - name: "n-subscriberOS"
        buyer: "The customer experience / care organisation (VP of Customer Operations) that owns the subscriber relationship, support cost and satisfaction."
        os_test: "Subscriber care is its own discipline with a care-centre budget, a CRM/care-desk frontend, a state model centred on cases, sentiment and loyalty (not network nodes or wholesale settlement), and a vocabulary (NPS, first-contact resolution, win-back) distinct from both selling tariffs and running cells; repeatable across every consumer operator."
        sectors:
          - name: "Customer Care & Support"
            operating_domains:
              - "Inbound contact across voice, chat, social"
              - Case and ticket lifecycle management
              - Knowledge base and guided resolution flows
              - "Tier escalation and back-office handoff"
              - Callback and queue management
              - Customer sentiment and complaint capture
              - Quality monitoring of agent interactions
            vocabulary:
              - { term: Customer case, runtime_type: Object }
              - { term: Contact, runtime_type: Event }
              - { term: Care agent, runtime_type: Actor }
              - { term: Customer, runtime_type: Actor }
              - { term: Knowledge article, runtime_type: Object }
              - { term: Case open, runtime_type: State }
              - { term: Awaiting customer, runtime_type: State }
              - { term: Case resolved, runtime_type: State }
              - { term: Escalation, runtime_type: Workflow }
              - { term: Routing decision, runtime_type: Decision }
              - { term: Resolution note, runtime_type: Artefact }
              - { term: Issue resolved, runtime_type: Outcome }
              - { term: "First-contact resolution", runtime_type: Learning }
              - { term: CSAT score, runtime_type: Learning }
          - name: "Onboarding & Activation"
            note: "Identity verification at activation is required under KYC/anti-fraud and SIM-registration rules in many markets."
            operating_domains:
              - "New-customer welcome and identity verification"
              - Device setup and eSIM/QR activation
              - "Number transfer and port-in coordination"
              - "Service-readiness checks and first-use nudges"
              - "Account configuration (notifications, autopay)"
              - "Early-life support and friction reduction"
              - "Welcome offers and add-on activation"
            vocabulary:
              - { term: New subscriber, runtime_type: Actor }
              - { term: Activation step, runtime_type: Object }
              - { term: Identity check, runtime_type: Decision }
              - { term: eSIM QR scan, runtime_type: Event }
              - { term: "Port-in", runtime_type: Workflow }
              - { term: Onboarding journey, runtime_type: Workflow }
              - { term: Pending activation, runtime_type: State }
              - { term: Fully onboarded, runtime_type: State }
              - { term: Welcome offer, runtime_type: Object }
              - { term: Setup guide, runtime_type: Artefact }
              - { term: First successful call/data, runtime_type: Outcome }
              - { term: Activation confirmation, runtime_type: Artefact }
              - { term: "Time-to-first-use", runtime_type: Learning }
              - { term: Activation completion rate, runtime_type: Learning }
          - name: "Retention & Loyalty"
            operating_domains:
              - Churn risk scoring and save desk
              - "Win-back of lapsed customers"
              - "Loyalty tiers, points and rewards"
              - Renewal and recontracting offers
              - "Proactive value reviews and right-plan nudges"
              - Cancellation and downgrade handling
              - Loyalty partner perks and redemptions
            vocabulary:
              - { term: Loyalty member, runtime_type: Actor }
              - { term: Reward / perk, runtime_type: Object }
              - { term: Churn risk score, runtime_type: Object }
              - { term: Cancellation request, runtime_type: Event }
              - { term: Save offer, runtime_type: Object }
              - { term: At risk, runtime_type: State }
              - { term: Lapsed, runtime_type: State }
              - { term: "Win-back campaign", runtime_type: Workflow }
              - { term: "Retain-or-release decision", runtime_type: Decision }
              - { term: Reward redemption, runtime_type: Workflow }
              - { term: Loyalty statement, runtime_type: Artefact }
              - { term: Customer retained, runtime_type: Outcome }
              - { term: Save rate, runtime_type: Learning }
              - { term: Customer lifetime value, runtime_type: Learning }
          - name: "Self-Service & Digital Channels"
            operating_domains:
              - Mobile app and web account management
              - Usage and balance dashboards
              - "Self-serve plan changes and add-ons"
              - Automated chatbot / virtual assistant
              - "In-app payments and bill management"
              - Notifications and proactive alerts
              - "Self-diagnostics and outage checker"
            vocabulary:
              - { term: Account dashboard, runtime_type: Object }
              - { term: Usage meter, runtime_type: Object }
              - { term: App user, runtime_type: Actor }
              - { term: "Self-serve plan change", runtime_type: Event }
              - { term: Virtual assistant, runtime_type: Actor }
              - { term: Logged in, runtime_type: State }
              - { term: Action pending, runtime_type: State }
              - { term: "Top-up flow", runtime_type: Workflow }
              - { term: Containment decision, runtime_type: Decision }
              - { term: Push notification, runtime_type: Artefact }
              - { term: "Task completed in-app", runtime_type: Outcome }
              - { term: Outage checker result, runtime_type: Object }
              - { term: Digital adoption rate, runtime_type: Learning }
              - { term: "Self-serve containment", runtime_type: Learning }
          - name: "Billing Care & Disputes"
            note: "Billing complaints unresolved within statutory windows escalate to the regulator's alternative dispute resolution scheme."
            operating_domains:
              - Bill explanation and walkthrough
              - Charge dispute and adjustment handling
              - "Refunds, credits and goodwill gestures"
              - Payment arrangement and hardship plans
              - "Fraudulent-charge investigation"
              - Bill shock and overage resolution
              - "Final-bill and account-closure queries"
            vocabulary:
              - { term: Disputed charge, runtime_type: Object }
              - { term: Adjustment, runtime_type: Object }
              - { term: Billing query, runtime_type: Event }
              - { term: Care agent, runtime_type: Actor }
              - { term: Payment arrangement, runtime_type: Object }
              - { term: Dispute under review, runtime_type: State }
              - { term: Credit applied, runtime_type: State }
              - { term: Goodwill decision, runtime_type: Decision }
              - { term: Dispute resolution, runtime_type: Workflow }
              - { term: Credit note, runtime_type: Artefact }
              - { term: Hardship plan, runtime_type: Workflow }
              - { term: Dispute settled, runtime_type: Outcome }
              - { term: Adjustment rate, runtime_type: Learning }
              - { term: Complaint repeat rate, runtime_type: Learning }
          - name: "Vulnerable Customers & Accessibility"
            note: "Treatment of vulnerable customers, social tariffs and accessibility are regulatory obligations (Ofcom fairness rules / equivalent)."
            operating_domains:
              - Vulnerability flagging and tailored handling
              - "Priority fault repair for at-risk households"
              - Accessible formats and assistive services
              - Social tariffs and affordability support
              - "Bereavement and power-of-attorney handling"
              - Debt and affordability safeguarding
              - "Consent and communication-preference management"
            vocabulary:
              - { term: Vulnerability flag, runtime_type: Object }
              - { term: Priority customer, runtime_type: Actor }
              - { term: Social tariff, runtime_type: Object }
              - { term: Accessibility request, runtime_type: Event }
              - { term: Safeguarding case, runtime_type: Object }
              - { term: Flagged as vulnerable, runtime_type: State }
              - { term: Priority repair active, runtime_type: State }
              - { term: "Tailored-support decision", runtime_type: Decision }
              - { term: Bereavement handling, runtime_type: Workflow }
              - { term: Consent record, runtime_type: Artefact }
              - { term: Customer safeguarded, runtime_type: Outcome }
              - { term: Affordability review, runtime_type: Workflow }
              - { term: Support coverage rate, runtime_type: Learning }
      - name: "n-connectivityOS"
        buyer: "The connectivity product owner — at MVNOs, IoT/M2M providers and connectivity platforms (eSIM, CPaaS) — who buys network capacity wholesale and resells managed connectivity."
        os_test: "A connectivity provider owns no physical network yet runs a real business: it buys capacity, manages SIM/eSIM fleets and APIs as products, with a state model of connections/data-plans/API-keys and a vocabulary (eSIM profile, data pool, A2P SMS, connectivity-as-a-service) distinct from both the host operator's network and a retail telco; repeatable across Twilio, 1NCE, Truphone, Tesco Mobile."
        sectors:
          - name: "MVNO & Brand Operations"
            note: MVNOs operate under wholesale access regulation and must register number ranges with the regulator.
            operating_domains:
              - "Host-network capacity and rate-plan sourcing"
              - "Own-brand tariff and proposition design"
              - Subscriber base management on host APIs
              - "Wholesale cost vs retail-price margin control"
              - Brand marketing and acquisition funnels
              - Number ranges and porting on host network
              - "Switching between host operators (multi-IMSI)"
            vocabulary:
              - { term: MVNO brand, runtime_type: Object }
              - { term: Host agreement, runtime_type: Artefact }
              - { term: Wholesale rate plan, runtime_type: Object }
              - { term: Reseller, runtime_type: Actor }
              - { term: Subscriber base, runtime_type: Object }
              - { term: "Capacity-buy decision", runtime_type: Decision }
              - { term: Live on host, runtime_type: State }
              - { term: Margin squeezed, runtime_type: State }
              - { term: Onboard to host, runtime_type: Workflow }
              - { term: Host migration, runtime_type: Workflow }
              - { term: Activation event, runtime_type: Event }
              - { term: Margin per subscriber, runtime_type: Outcome }
              - { term: Wholesale margin, runtime_type: Learning }
              - { term: Net adds, runtime_type: Learning }
          - name: "IoT & M2M Connectivity"
            operating_domains:
              - Device SIM fleet provisioning at scale
              - "Data pools and shared-allowance management"
              - "Connectivity profiles (NB-IoT, LTE-M, 5G)"
              - "Device lifecycle states (test, live, retired)"
              - Global roaming and steering for devices
              - "Connectivity rules and rate-limiting policies"
              - "Fleet diagnostics and stuck-device detection"
            vocabulary:
              - { term: Device SIM, runtime_type: Object }
              - { term: Data pool, runtime_type: Object }
              - { term: Connectivity profile, runtime_type: Object }
              - { term: Fleet manager, runtime_type: Actor }
              - { term: Device, runtime_type: Actor }
              - { term: SIM test state, runtime_type: State }
              - { term: Device live, runtime_type: State }
              - { term: Device retired, runtime_type: State }
              - { term: Bulk activation, runtime_type: Workflow }
              - { term: "Rate-plan-change decision", runtime_type: Decision }
              - { term: Attach event, runtime_type: Event }
              - { term: Connectivity report, runtime_type: Artefact }
              - { term: Device connected, runtime_type: Outcome }
              - { term: Pool utilisation, runtime_type: Learning }
          - name: "eSIM & Remote Provisioning"
            note: "eSIM provisioning follows GSMA SGP standards and remains subject to SIM-registration/KYC rules."
            operating_domains:
              - eSIM profile catalogue and generation
              - "Remote SIM provisioning (SM-DP+/SM-SR)"
              - "QR and activation-code distribution"
              - "Profile download, enable, disable lifecycle"
              - Travel/local eSIM packs for roaming
              - Device compatibility and entitlement checks
              - "Profile swap and operator change in-device"
            vocabulary:
              - { term: eSIM profile, runtime_type: Object }
              - { term: Activation code, runtime_type: Object }
              - { term: "Provisioning platform (SM-DP+)", runtime_type: Object }
              - { term: End user, runtime_type: Actor }
              - { term: Profile download, runtime_type: Event }
              - { term: Profile enabled, runtime_type: State }
              - { term: Profile disabled, runtime_type: State }
              - { term: Released / pending, runtime_type: State }
              - { term: Remote provisioning, runtime_type: Workflow }
              - { term: "Entitlement-check decision", runtime_type: Decision }
              - { term: Profile package, runtime_type: Artefact }
              - { term: eSIM active on device, runtime_type: Outcome }
              - { term: Download success rate, runtime_type: Learning }
          - name: "Messaging & CPaaS"
            note: "A2P messaging and OTP traffic are subject to anti-spam, sender-ID registration and consumer-consent rules."
            operating_domains:
              - A2P SMS and RCS campaign delivery
              - Programmable voice and verification (OTP)
              - Sender IDs and number provisioning
              - "Message routing and least-cost selection"
              - "Deliverability and spam/grey-route filtering"
              - "Channel APIs (WhatsApp, viber, chat)"
              - "Throughput, rate limits and queueing"
            vocabulary:
              - { term: Message, runtime_type: Object }
              - { term: Sender ID, runtime_type: Object }
              - { term: Campaign, runtime_type: Object }
              - { term: Developer, runtime_type: Actor }
              - { term: Message submitted, runtime_type: Event }
              - { term: Delivery receipt, runtime_type: Artefact }
              - { term: Queued, runtime_type: State }
              - { term: Delivered, runtime_type: State }
              - { term: Failed / undelivered, runtime_type: State }
              - { term: Routing, runtime_type: Workflow }
              - { term: "Least-cost-route decision", runtime_type: Decision }
              - { term: Message delivered, runtime_type: Outcome }
              - { term: Delivery rate, runtime_type: Learning }
              - { term: "Grey-route leakage", runtime_type: Learning }
          - name: "Connectivity APIs & Platform"
            operating_domains:
              - API key and credential management
              - Programmable connectivity endpoints
              - "Usage metering and rate-limiting per tenant"
              - Webhooks and event subscriptions
              - Developer onboarding and sandbox
              - Tenant isolation and access scopes
              - Service catalogue and product tiers
            vocabulary:
              - { term: API key, runtime_type: Object }
              - { term: Endpoint, runtime_type: Object }
              - { term: Tenant / account, runtime_type: Object }
              - { term: Integrator, runtime_type: Actor }
              - { term: API call, runtime_type: Event }
              - { term: Webhook fired, runtime_type: Event }
              - { term: Key active, runtime_type: State }
              - { term: "Rate-limited", runtime_type: State }
              - { term: Provision tenant, runtime_type: Workflow }
              - { term: "Scope-grant decision", runtime_type: Decision }
              - { term: Usage record, runtime_type: Artefact }
              - { term: Integration live, runtime_type: Outcome }
              - { term: API success rate, runtime_type: Learning }
              - { term: "Time-to-first-call", runtime_type: Learning }
          - name: "Roaming & Travel Connectivity"
            note: "Roaming surcharges and intra-region caps (e.g. EU Roam-Like-At-Home) are price-regulated."
            operating_domains:
              - "Travel eSIM and local-data pack catalogue"
              - "Partner-network selection and steering"
              - "Roaming usage and fair-use policy control"
              - "Inter-operator roaming settlement (TADIG)"
              - "Coverage and partner-quality monitoring"
              - "Bill-shock protection abroad"
              - "Multi-country pack bundling"
            vocabulary:
              - { term: Travel pack, runtime_type: Object }
              - { term: Roaming partner, runtime_type: Actor }
              - { term: Traveller, runtime_type: Actor }
              - { term: "Fair-use policy", runtime_type: Object }
              - { term: Network attach abroad, runtime_type: Event }
              - { term: Roaming active, runtime_type: State }
              - { term: "Fair-use exceeded", runtime_type: State }
              - { term: Steering decision, runtime_type: Decision }
              - { term: Pack activation, runtime_type: Workflow }
              - { term: Roaming settlement, runtime_type: Workflow }
              - { term: Roaming statement, runtime_type: Artefact }
              - { term: Connected abroad, runtime_type: Outcome }
              - { term: Roaming margin, runtime_type: Learning }
              - { term: Partner coverage quality, runtime_type: Learning }
      - name: "n-infrastructureOS"
        buyer: "The passive-infrastructure owner/operator — tower companies, fibre/altnets, data-centre and neutral-host operators — who builds and leases the physical assets that carriers run on."
        os_test: "Infrastructure is an asset-leasing business, not a service operator: its buyer owns capex-heavy assets and lease revenue, its state model is sites/ducts/leases/permits (not subscribers, alarms or SIMs), and its vocabulary (tenancy, build-to-suit, dark fibre, neutral host) is alien to a retail telco; repeatable across Cellnex, American Tower, Openreach, Crown Castle."
        sectors:
          - name: "Tower & Site Leasing"
            note: "Mast/site deployment requires planning permission and code-powers/wayleave rights under the Electronic Communications Code."
            operating_domains:
              - Tower and rooftop site portfolio
              - "Tenant lease and co-location management"
              - Structural loading and capacity assessment
              - "Ground-lease and landlord management"
              - Amendment and upgrade requests from carriers
              - Site access and key/permit control
              - Rent escalation and billing to tenants
            vocabulary:
              - { term: Tower site, runtime_type: Object }
              - { term: Tenancy / lease, runtime_type: Object }
              - { term: Carrier tenant, runtime_type: Actor }
              - { term: Landlord, runtime_type: Actor }
              - { term: "Co-location request", runtime_type: Event }
              - { term: Structural assessment, runtime_type: Decision }
              - { term: Site available, runtime_type: State }
              - { term: Fully loaded, runtime_type: State }
              - { term: "Lease-up workflow", runtime_type: Workflow }
              - { term: Lease agreement, runtime_type: Artefact }
              - { term: New tenancy signed, runtime_type: Outcome }
              - { term: Tenancy ratio, runtime_type: Learning }
              - { term: Rent per site, runtime_type: Learning }
              - { term: Site occupancy, runtime_type: State }
          - name: "Fibre & Duct Infrastructure"
            note: "Duct-and-pole access (PIA), street works and reinstatement are governed by code powers and highway authority permits."
            operating_domains:
              - Fibre route and duct network inventory
              - "Dark-fibre and wavelength leasing"
              - "Build planning, trenching and reinstatement"
              - "Pole, duct and wayleave access (PIA)"
              - "Splice points and street-cabinet management"
              - "Open-access wholesale onboarding of ISPs"
              - "Network records and as-built documentation"
            vocabulary:
              - { term: Fibre route, runtime_type: Object }
              - { term: Duct / pole, runtime_type: Object }
              - { term: Dark fibre, runtime_type: Object }
              - { term: Build manager, runtime_type: Actor }
              - { term: ISP customer, runtime_type: Actor }
              - { term: Dig event, runtime_type: Event }
              - { term: Planned route, runtime_type: State }
              - { term: Ready for service, runtime_type: State }
              - { term: Build workflow, runtime_type: Workflow }
              - { term: Wayleave decision, runtime_type: Decision }
              - { term: "As-built record", runtime_type: Artefact }
              - { term: Premises passed, runtime_type: Outcome }
              - { term: Cost per premises passed, runtime_type: Learning }
              - { term: "Take-up rate", runtime_type: Learning }
          - name: "Data Centre & Edge Hosting"
            operating_domains:
              - "Rack, cage and colocation space inventory"
              - Power (kW) and cooling capacity allocation
              - "Cross-connect and meet-me-room management"
              - "Edge node and micro-data-centre deployment"
              - "Environmental monitoring (temp, humidity)"
              - "Remote-hands and smart-hands requests"
              - "Power-usage efficiency and sustainability"
            vocabulary:
              - { term: Rack / cage, runtime_type: Object }
              - { term: "Cross-connect", runtime_type: Object }
              - { term: Power circuit, runtime_type: Object }
              - { term: Colocation tenant, runtime_type: Actor }
              - { term: "Remote-hands request", runtime_type: Event }
              - { term: Space available, runtime_type: State }
              - { term: At capacity, runtime_type: State }
              - { term: Provision rack, runtime_type: Workflow }
              - { term: "Power-allocation decision", runtime_type: Decision }
              - { term: Service order, runtime_type: Artefact }
              - { term: "Cross-connect live", runtime_type: Outcome }
              - { term: Power usage effectiveness, runtime_type: Learning }
              - { term: Space utilisation, runtime_type: Learning }
              - { term: Environmental alarm, runtime_type: Event }
          - name: "Neutral Host & Shared RAN"
            note: Shared RAN and neutral host use of spectrum require operator licences and frequency coordination.
            operating_domains:
              - "In-building and venue coverage systems (DAS)"
              - "Multi-operator shared radio (MORAN/MOCN)"
              - Venue and landlord agreements
              - Operator onboarding onto shared system
              - "Small-cell and street-furniture deployment"
              - Capacity sharing and slice allocation
              - Coverage acceptance testing per operator
            vocabulary:
              - { term: "Neutral-host system", runtime_type: Object }
              - { term: DAS / small cell, runtime_type: Object }
              - { term: Venue, runtime_type: Object }
              - { term: Onboarding operator, runtime_type: Actor }
              - { term: Venue owner, runtime_type: Actor }
              - { term: Operator onboard request, runtime_type: Event }
              - { term: System live, runtime_type: State }
              - { term: Acceptance pending, runtime_type: State }
              - { term: Operator onboarding, runtime_type: Workflow }
              - { term: "Capacity-share decision", runtime_type: Decision }
              - { term: Acceptance certificate, runtime_type: Artefact }
              - { term: Coverage accepted, runtime_type: Outcome }
              - { term: Operators per system, runtime_type: Learning }
              - { term: "In-building coverage quality", runtime_type: Learning }
          - name: "Site Build & Civil Works"
            note: "Telecom site construction requires planning permission, environmental consents and CDM health-and-safety compliance."
            operating_domains:
              - Site acquisition and candidate evaluation
              - Planning and permitting submissions
              - Construction and installation scheduling
              - Contractor and crew dispatch
              - "Health-and-safety and method statements"
              - "Snagging, handover and commissioning"
              - "Build-to-suit projects for anchor tenants"
            vocabulary:
              - { term: Candidate site, runtime_type: Object }
              - { term: Build project, runtime_type: Object }
              - { term: Permit application, runtime_type: Artefact }
              - { term: Project manager, runtime_type: Actor }
              - { term: Construction crew, runtime_type: Actor }
              - { term: Site survey, runtime_type: Event }
              - { term: In planning, runtime_type: State }
              - { term: Under construction, runtime_type: State }
              - { term: Commissioned, runtime_type: State }
              - { term: "Build-to-suit workflow", runtime_type: Workflow }
              - { term: "Go/no-go decision", runtime_type: Decision }
              - { term: Handover certificate, runtime_type: Artefact }
              - { term: Site on air, runtime_type: Outcome }
              - { term: Build cycle time, runtime_type: Learning }
          - name: "Asset & Lease Management"
            note: "Lease renewals and site rents are governed by the Electronic Communications Code, which constrains landlord terms."
            operating_domains:
              - Asset register and portfolio valuation
              - "Lease renewals, escalations and rent reviews"
              - "Ground-rent and landlord payment runs"
              - Permit and consent compliance tracking
              - Energy procurement and grid connections
              - Decommission and site exit management
              - Capex planning and depreciation schedules
            vocabulary:
              - { term: Asset, runtime_type: Object }
              - { term: Lease record, runtime_type: Object }
              - { term: Ground rent, runtime_type: Object }
              - { term: Asset manager, runtime_type: Actor }
              - { term: Landlord, runtime_type: Actor }
              - { term: Rent review, runtime_type: Event }
              - { term: Lease active, runtime_type: State }
              - { term: Lease expiring, runtime_type: State }
              - { term: Decommissioned, runtime_type: State }
              - { term: Renewal workflow, runtime_type: Workflow }
              - { term: "Renew-or-exit decision", runtime_type: Decision }
              - { term: Lease schedule, runtime_type: Artefact }
              - { term: Portfolio value realised, runtime_type: Outcome }
              - { term: Lease cost ratio, runtime_type: Learning }
  - name: "Agriculture & Food"
    os:
      - name: "n-agriOS"
        buyer: "Arable & mixed crop farm owner-operators and farm business managers who run the whole farming enterprise (land, agronomy, machinery, subsidies)."
        os_test: "Distinct buyer (the farm business itself), its own budget line (farm software / FMS subscription), a frontend organised around fields and seasons, a state model of growing crops through a cropping year, and thousands of repeatable arable/mixed farm businesses."
        sectors:
          - name: "Arable & Combinable Crops"
            note: Pesticide application requires PA certificates and a legally retained spray/field record; product use governed by approved label conditions.
            operating_domains:
              - Fields and field parcels
              - Cropping plan / rotation
              - "Crop establishment (drilling & cultivation)"
              - "Nutrition & fertiliser programme"
              - Crop protection (spraying)
              - "Harvest & grain handling"
              - Grain store and moisture management
            vocabulary:
              - { term: Field, runtime_type: Object }
              - { term: Crop in the ground, runtime_type: State }
              - { term: Variety, runtime_type: Object }
              - { term: Agronomist, runtime_type: Actor }
              - { term: Drilling pass, runtime_type: Event }
              - { term: Spray application, runtime_type: Event }
              - { term: Spray recommendation, runtime_type: Decision }
              - { term: Field record / spray diary, runtime_type: Artefact }
              - { term: Harvest run, runtime_type: Workflow }
              - { term: Yield (t/ha), runtime_type: Outcome }
              - { term: Tonnage off the field, runtime_type: Outcome }
              - { term: "Grain moisture %", runtime_type: State }
              - { term: Gross margin per hectare, runtime_type: Learning }
              - { term: Variety performance benchmark, runtime_type: Learning }
              - { term: Weather window, runtime_type: State }
          - name: "Precision Agronomy & Variable Rate"
            note: Nutrient management plans must comply with nitrate vulnerable zone (NVZ) and Farming Rules for Water; closed periods for spreading apply.
            operating_domains:
              - Soil sampling zones
              - Yield maps
              - "Variable-rate prescription maps"
              - Satellite / NDVI biomass imagery
              - Nutrient management plan
              - "Field boundaries & buffer zones"
              - Trial / tramline plots
            vocabulary:
              - { term: Management zone, runtime_type: Object }
              - { term: Soil sample, runtime_type: Object }
              - { term: "Soil index (P, K, pH)", runtime_type: State }
              - { term: NDVI biomass map, runtime_type: Artefact }
              - { term: "Variable-rate prescription", runtime_type: Decision }
              - { term: Prescription map, runtime_type: Artefact }
              - { term: "Application-as-applied map", runtime_type: Event }
              - { term: Agronomist, runtime_type: Actor }
              - { term: Apply prescription workflow, runtime_type: Workflow }
              - { term: Lime / nutrient recommendation, runtime_type: Decision }
              - { term: Saved input cost, runtime_type: Outcome }
              - { term: Yield response to rate, runtime_type: Learning }
              - { term: Zone performance, runtime_type: Learning }
              - { term: Field trial result, runtime_type: Outcome }
          - name: "Farm Machinery & Workshop"
            operating_domains:
              - "Tractor & machine fleet"
              - "Implements & attachments"
              - "Service & maintenance schedule"
              - "Parts & consumables store"
              - Fuel (red diesel) tank
              - "Operator timesheets & jobs"
              - "Telematics & machine hours"
            vocabulary:
              - { term: Machine, runtime_type: Object }
              - { term: Implement, runtime_type: Object }
              - { term: Operator, runtime_type: Actor }
              - { term: Engine hours, runtime_type: State }
              - { term: Service due, runtime_type: State }
              - { term: Breakdown, runtime_type: Event }
              - { term: Service job, runtime_type: Workflow }
              - { term: "Repair-or-replace call", runtime_type: Decision }
              - { term: Service record, runtime_type: Artefact }
              - { term: Fuel use (l/ha), runtime_type: Outcome }
              - { term: Fleet uptime, runtime_type: Outcome }
              - { term: Cost per machine hour, runtime_type: Learning }
              - { term: Parts order, runtime_type: Event }
              - { term: Telematics alert, runtime_type: Event }
          - name: "Subsidies, Stewardship & Compliance"
            note: "Subsidy and agri-environment claims (e.g. RPA / SFI / Countryside Stewardship) are regulated; false declarations and failed inspections trigger statutory penalties and clawback."
            operating_domains:
              - Land parcel register (RPA/RLR)
              - "Subsidy & stewardship scheme applications"
              - "Cross-compliance / conditionality checklist"
              - "Buffer strips & environmental features"
              - Inspection evidence pack
              - Cropping declaration
              - Carbon / sustainability baseline
            vocabulary:
              - { term: Land parcel (RLR), runtime_type: Object }
              - { term: Scheme agreement, runtime_type: Artefact }
              - { term: Stewardship option, runtime_type: Object }
              - { term: Scheme adviser, runtime_type: Actor }
              - { term: Submit claim, runtime_type: Workflow }
              - { term: Claim window open, runtime_type: State }
              - { term: Eligibility decision, runtime_type: Decision }
              - { term: Inspection, runtime_type: Event }
              - { term: Compliance breach, runtime_type: Event }
              - { term: Evidence pack, runtime_type: Artefact }
              - { term: Subsidy payment received, runtime_type: Outcome }
              - { term: Penalty / reduction, runtime_type: Outcome }
              - { term: Area in agreement, runtime_type: State }
              - { term: Scheme income per hectare, runtime_type: Learning }
          - name: "Grain Marketing & Commodity Trading"
            note: "Grain movements require a completed grain passport and assured-scheme (e.g. Red Tractor / Combinable Crops) status for most buyers."
            operating_domains:
              - Grain in store / stock positions
              - "Forward & spot contracts"
              - "Market price & basis tracking"
              - "Haulage & movement scheduling"
              - "Quality samples & specification"
              - Buyer / merchant relationships
              - Hedging position
            vocabulary:
              - { term: Grain lot, runtime_type: Object }
              - { term: Forward contract, runtime_type: Artefact }
              - { term: Merchant / buyer, runtime_type: Actor }
              - { term: Sell decision, runtime_type: Decision }
              - { term: Contract priced, runtime_type: State }
              - { term: Movement / collection, runtime_type: Event }
              - { term: Quality sample result, runtime_type: State }
              - { term: Spec rejection, runtime_type: Event }
              - { term: Marketing plan, runtime_type: Workflow }
              - { term: Passport / movement note, runtime_type: Artefact }
              - { term: Average price achieved (£/t), runtime_type: Outcome }
              - { term: Open tonnage, runtime_type: State }
              - { term: Basis vs futures, runtime_type: Learning }
              - { term: Margin over market, runtime_type: Learning }
      - name: "n-farmOS"
        buyer: "Smallholders, mixed/regenerative farms, market gardens and farm-estate managers who run a diversified holding (people, land, animals, enterprises) rather than a single crop."
        os_test: "Different buyer to commercial arable (whole-holding manager / estate), its own budget (smallholding & estate management tools), a frontend organised around the holding and its enterprises, a state model spanning land + livestock + diversification simultaneously, and many repeatable mixed-farm businesses."
        sectors:
          - name: "Holding & Land Management"
            operating_domains:
              - "Holding & enterprise map"
              - "Fields, paddocks & grazing blocks"
              - "Hedges, water & infrastructure"
              - "Tenancies & land agreements"
              - "Soil & pasture health"
              - Seasonal jobs calendar
              - "Boundary & access points"
            vocabulary:
              - { term: Holding, runtime_type: Object }
              - { term: Paddock, runtime_type: Object }
              - { term: Enterprise, runtime_type: Object }
              - { term: Land manager, runtime_type: Actor }
              - { term: Tenancy agreement, runtime_type: Artefact }
              - { term: Pasture condition, runtime_type: State }
              - { term: Job logged, runtime_type: Event }
              - { term: Seasonal jobs plan, runtime_type: Workflow }
              - { term: Where to put which enterprise, runtime_type: Decision }
              - { term: Map / holding plan, runtime_type: Artefact }
              - { term: Land in good heart, runtime_type: State }
              - { term: Output per acre, runtime_type: Outcome }
              - { term: Enterprise profitability, runtime_type: Learning }
          - name: "Rotational & Regenerative Grazing"
            operating_domains:
              - Mob / herd on grass
              - "Grazing wedge & cover"
              - "Paddock moves & rest periods"
              - "Water & fence infrastructure"
              - "Grass growth & sward height"
              - "Soil carbon & biodiversity"
              - Forage budget
            vocabulary:
              - { term: Grazing mob, runtime_type: Object }
              - { term: Grass cover (kg DM/ha), runtime_type: State }
              - { term: Sward height, runtime_type: State }
              - { term: Grazier, runtime_type: Actor }
              - { term: Paddock move, runtime_type: Event }
              - { term: Rest period, runtime_type: State }
              - { term: When to move the mob, runtime_type: Decision }
              - { term: Grazing plan / rotation, runtime_type: Workflow }
              - { term: Grass measurement (plate meter), runtime_type: Event }
              - { term: Grazing wedge chart, runtime_type: Artefact }
              - { term: Days of grazing ahead, runtime_type: Outcome }
              - { term: "Utilisation %", runtime_type: Learning }
              - { term: Growth rate trend, runtime_type: Learning }
              - { term: Soil carbon baseline, runtime_type: State }
          - name: "Market Garden & Horticulture"
            operating_domains:
              - "Beds & growing tunnels"
              - Succession planting plan
              - "Propagation & nursery"
              - Crop plan by week / harvest calendar
              - "Irrigation & feeding"
              - "Pest & disease scouting"
              - "Harvest, wash & pack"
            vocabulary:
              - { term: Bed, runtime_type: Object }
              - { term: Crop succession, runtime_type: Object }
              - { term: Grower, runtime_type: Actor }
              - { term: Sowing, runtime_type: Event }
              - { term: Transplant, runtime_type: Event }
              - { term: Ready to harvest, runtime_type: State }
              - { term: What to plant this week, runtime_type: Decision }
              - { term: Crop plan / harvest calendar, runtime_type: Workflow }
              - { term: Planting plan, runtime_type: Artefact }
              - { term: Pest pressure, runtime_type: State }
              - { term: Harvest weight per bed, runtime_type: Outcome }
              - { term: Saleable yield, runtime_type: Outcome }
              - { term: "Revenue per bed-metre", runtime_type: Learning }
              - { term: Crop turnaround time, runtime_type: Learning }
          - name: "Farm Diversification & Direct Sales"
            note: "On-farm food sales and catering require food business registration and food-hygiene compliance; lettings/glamping may need planning and licensing."
            operating_domains:
              - "Farm shop & box scheme"
              - Veg / meat box subscriptions
              - "Farmers' markets & pitches"
              - "On-farm experiences & lettings"
              - Customer / member list
              - "Price list & packing"
              - Glamping / event bookings
            vocabulary:
              - { term: Box scheme, runtime_type: Object }
              - { term: Member / subscriber, runtime_type: Actor }
              - { term: Product / box, runtime_type: Object }
              - { term: Order placed, runtime_type: Event }
              - { term: Subscription active, runtime_type: State }
              - { term: "Set this week's box", runtime_type: Decision }
              - { term: "Pack & deliver run", runtime_type: Workflow }
              - { term: Delivery note / invoice, runtime_type: Artefact }
              - { term: Delivered, runtime_type: Event }
              - { term: Sales takings, runtime_type: Outcome }
              - { term: Repeat customer, runtime_type: State }
              - { term: Churn rate, runtime_type: Learning }
              - { term: Margin per box, runtime_type: Learning }
              - { term: Booking, runtime_type: Event }
          - name: "Farm Labour & Health-and-Safety"
            note: "Agriculture is HSE-regulated; risk assessments, COSHH and certain machinery/chemical certifications are legally required and inspectable."
            operating_domains:
              - "Workforce & seasonal staff"
              - "Rotas & timesheets"
              - "Training & certificates"
              - "Risk assessments & method statements"
              - "Incident & near-miss log"
              - "PPE & equipment checks"
              - COSHH / chemical store
            vocabulary:
              - { term: Worker, runtime_type: Actor }
              - { term: Rota, runtime_type: Artefact }
              - { term: "Certificate (PA, telehandler)", runtime_type: Object }
              - { term: Certificate expiring, runtime_type: State }
              - { term: Shift worked, runtime_type: Event }
              - { term: Risk assessment, runtime_type: Artefact }
              - { term: Incident reported, runtime_type: Event }
              - { term: Safety check workflow, runtime_type: Workflow }
              - { term: "Stand-down decision", runtime_type: Decision }
              - { term: Hours worked, runtime_type: Outcome }
              - { term: Days lost to injury, runtime_type: Outcome }
              - { term: "Trained & competent", runtime_type: State }
              - { term: Incident rate, runtime_type: Learning }
      - name: "n-foodOS"
        buyer: "Food manufacturers, processors, packers and food-service operators who turn raw agricultural product into sellable food and must run production, safety and traceability."
        os_test: "Entirely different buyer (factory / kitchen operator, not a farmer), large dedicated budget (food ERP / safety / MES), a frontend organised around production lines, recipes and batches, a state model of ingredients becoming finished goods under HACCP control, and a huge repeatable population of food businesses."
        sectors:
          - name: "Food Manufacturing & Processing"
            note: "Food manufacturers must be approved/registered, operate a HACCP-based food safety management system, and are subject to regulatory inspection."
            operating_domains:
              - "Production lines & equipment"
              - "Recipes & bills of materials"
              - "Production batches & runs"
              - "Raw material & ingredient inventory"
              - "Finished goods & packing"
              - "Changeovers & cleaning"
              - "Yield & waste tracking"
            vocabulary:
              - { term: Production line, runtime_type: Object }
              - { term: Recipe / BOM, runtime_type: Artefact }
              - { term: Batch, runtime_type: Object }
              - { term: Line operator, runtime_type: Actor }
              - { term: Production run, runtime_type: Workflow }
              - { term: Batch in progress, runtime_type: State }
              - { term: Changeover, runtime_type: Event }
              - { term: Run this product next, runtime_type: Decision }
              - { term: Finished goods made, runtime_type: Outcome }
              - { term: "Batch yield %", runtime_type: Outcome }
              - { term: Production record, runtime_type: Artefact }
              - { term: Line downtime event, runtime_type: Event }
              - { term: OEE (line efficiency), runtime_type: Learning }
              - { term: "Waste / give-away rate", runtime_type: Learning }
          - name: "Food Safety, Quality & HACCP"
            note: "Legally mandated HACCP, allergen labelling (e.g. Natasha's Law) and food-safety certification; deviations can trigger recalls and enforcement."
            operating_domains:
              - HACCP / food safety plan
              - "Critical control points & checks"
              - Allergen management
              - "Cleaning & hygiene schedules (CCP/CIP)"
              - "Non-conformances & CAPA"
              - "Audits & certification (BRCGS etc.)"
              - "Lab & micro testing"
            vocabulary:
              - { term: Critical control point (CCP), runtime_type: Object }
              - { term: Quality manager, runtime_type: Actor }
              - { term: CCP check, runtime_type: Event }
              - { term: Within limits, runtime_type: State }
              - { term: "Out-of-spec / deviation", runtime_type: Event }
              - { term: Hold / release decision, runtime_type: Decision }
              - { term: "Non-conformance (NCR)", runtime_type: Artefact }
              - { term: Corrective action (CAPA), runtime_type: Workflow }
              - { term: Allergen declaration, runtime_type: Artefact }
              - { term: Audit, runtime_type: Event }
              - { term: Audit grade, runtime_type: Outcome }
              - { term: Complaint rate, runtime_type: Learning }
              - { term: "Right-first-time %", runtime_type: Learning }
              - { term: Certification status, runtime_type: State }
          - name: "Traceability & Recall"
            note: "One-up/one-down traceability and effective recall capability are statutory under food law (e.g. EU 178/2002 / retained UK law); mock recalls are audited."
            operating_domains:
              - Lot / batch genealogy
              - "Supplier & raw-material lots"
              - "Forward & backward trace"
              - "Recall & withdrawal process"
              - Mock recall exercises
              - Customer despatch records
              - "Quarantine & stock hold"
            vocabulary:
              - { term: Lot / batch code, runtime_type: Object }
              - { term: Raw material lot, runtime_type: Object }
              - { term: Recall coordinator, runtime_type: Actor }
              - { term: Trace request, runtime_type: Workflow }
              - { term: On quarantine hold, runtime_type: State }
              - { term: Recall triggered, runtime_type: Event }
              - { term: Withdraw or recall decision, runtime_type: Decision }
              - { term: Recall notice, runtime_type: Artefact }
              - { term: Mock recall, runtime_type: Event }
              - { term: Trace report, runtime_type: Artefact }
              - { term: Stock accounted for, runtime_type: Outcome }
              - { term: "Time-to-trace", runtime_type: Learning }
              - { term: "Recall completeness %", runtime_type: Learning }
          - name: "Food Supply Chain & Logistics"
            note: "Cold-chain and temperature records are legally required for chilled/frozen food; transport must meet food-hygiene transport rules."
            operating_domains:
              - "Inbound goods & supplier deliveries"
              - "Warehouse & cold store"
              - "Stock & shelf-life rotation (FEFO)"
              - "Picking & despatch"
              - "Temperature-controlled transport"
              - "Customer orders & service levels"
              - "Demand & replenishment planning"
            vocabulary:
              - { term: "Stock-keeping unit (SKU)", runtime_type: Object }
              - { term: Pallet / lot location, runtime_type: Object }
              - { term: Supplier, runtime_type: Actor }
              - { term: "Goods-in booking", runtime_type: Event }
              - { term: "Use-by approaching", runtime_type: State }
              - { term: Allocate stock decision, runtime_type: Decision }
              - { term: "Pick & despatch run", runtime_type: Workflow }
              - { term: Despatch note / EPCIS, runtime_type: Artefact }
              - { term: Temperature excursion, runtime_type: Event }
              - { term: Order fulfilled, runtime_type: Outcome }
              - { term: "On-time in-full (OTIF)", runtime_type: Learning }
              - { term: Stock cover (days), runtime_type: State }
              - { term: "Wastage / spoilage %", runtime_type: Learning }
              - { term: Forecast accuracy, runtime_type: Learning }
          - name: "Food Service & Commercial Kitchens"
            note: "Commercial kitchens must be food-hygiene registered, keep temperature/cleaning records, and provide accurate allergen information by law."
            operating_domains:
              - "Menus & dishes"
              - "Recipe costing & portioning"
              - "Prep & service production"
              - "Ingredient stock & GP control"
              - Allergen matrix per dish
              - "Kitchen hygiene & temperature logs"
              - Supplier ordering
            vocabulary:
              - { term: Dish, runtime_type: Object }
              - { term: Menu, runtime_type: Artefact }
              - { term: Head chef, runtime_type: Actor }
              - { term: Prep list, runtime_type: Workflow }
              - { term: Service / cover sold, runtime_type: Event }
              - { term: "86'd / out of stock", runtime_type: State }
              - { term: Menu engineering decision, runtime_type: Decision }
              - { term: Allergen matrix, runtime_type: Artefact }
              - { term: Fridge temp check, runtime_type: Event }
              - { term: Gross profit per dish, runtime_type: Outcome }
              - { term: Plate cost, runtime_type: State }
              - { term: "Food cost %", runtime_type: Learning }
              - { term: Wastage trend, runtime_type: Learning }
      - name: "n-agritechOS"
        buyer: "Agritech operators and service providers — drone/robotics contractors, vertical farms, agri-data platforms and precision-service firms whose product IS the technology applied to growing."
        os_test: "A distinct buyer (technology operator, not a traditional farmer), its own budget (capex + platform spend on robotics/sensors/CEA), a frontend organised around devices, missions and data pipelines, a state model of autonomous assets and controlled environments rather than fields-and-seasons, and a growing repeatable population of agritech companies."
        sectors:
          - name: "Controlled-Environment & Vertical Farming"
            note: "Indoor food production still requires food-business registration and food-safety controls on the edible output."
            operating_domains:
              - "Grow rooms & racks/tiers"
              - "Climate & lighting recipes"
              - "Nutrient dosing & irrigation"
              - "Crop cycles & batches"
              - Environmental sensors
              - "Energy & resource use"
              - "Harvest & packhouse"
            vocabulary:
              - { term: Grow room / module, runtime_type: Object }
              - { term: Climate recipe, runtime_type: Artefact }
              - { term: Crop cycle / batch, runtime_type: Object }
              - { term: Grow technician, runtime_type: Actor }
              - { term: Setpoint adjustment, runtime_type: Event }
              - { term: Within target band, runtime_type: State }
              - { term: Climate excursion alarm, runtime_type: Event }
              - { term: Tune the recipe, runtime_type: Decision }
              - { term: Grow cycle workflow, runtime_type: Workflow }
              - { term: Yield per square metre, runtime_type: Outcome }
              - { term: Energy per kg produced, runtime_type: Outcome }
              - { term: kWh / litre used, runtime_type: State }
              - { term: Recipe performance, runtime_type: Learning }
              - { term: Cost per head / per kg, runtime_type: Learning }
          - name: "Drone & Aerial Services"
            note: "Drone operations are aviation-regulated (CAA operator ID / flyer ID / Operational Authorisation); aerial spraying is tightly restricted."
            operating_domains:
              - "Drone fleet & sensors"
              - "Survey & spray missions"
              - "Flight plans & airspace"
              - "Pilot certificates & logbooks"
              - "Imagery & data capture"
              - Field reports for clients
              - "Maintenance & battery cycles"
            vocabulary:
              - { term: Drone / UAV, runtime_type: Object }
              - { term: Mission / flight plan, runtime_type: Artefact }
              - { term: Remote pilot, runtime_type: Actor }
              - { term: "Pre-flight check", runtime_type: Workflow }
              - { term: Flight flown, runtime_type: Event }
              - { term: Cleared to fly, runtime_type: State }
              - { term: "Go / no-go decision", runtime_type: Decision }
              - { term: Captured imagery, runtime_type: Object }
              - { term: Survey report, runtime_type: Artefact }
              - { term: Airspace breach, runtime_type: Event }
              - { term: Hectares surveyed, runtime_type: Outcome }
              - { term: Coverage per battery, runtime_type: Learning }
              - { term: Mission success rate, runtime_type: Learning }
          - name: "Farm Robotics & Autonomous Machines"
            operating_domains:
              - Robot / autonomous machine fleet
              - "Field tasks & job assignments"
              - "Geofences & safe zones"
              - "Charging & docking"
              - "Sensor & vision data"
              - "Fault & intervention log"
              - "Job results & coverage maps"
            vocabulary:
              - { term: Field robot, runtime_type: Object }
              - { term: Job / task order, runtime_type: Object }
              - { term: Fleet supervisor, runtime_type: Actor }
              - { term: Autonomous run, runtime_type: Workflow }
              - { term: Operating autonomously, runtime_type: State }
              - { term: Obstacle stop, runtime_type: Event }
              - { term: Human intervention, runtime_type: Event }
              - { term: Reassign / override, runtime_type: Decision }
              - { term: Coverage map, runtime_type: Artefact }
              - { term: Area worked, runtime_type: Outcome }
              - { term: Autonomy uptime, runtime_type: Outcome }
              - { term: Interventions per hectare, runtime_type: Learning }
              - { term: Battery state, runtime_type: State }
          - name: "Agri-Data, Connectivity & IoT"
            operating_domains:
              - "Sensor & gateway network"
              - "Data feeds & integrations"
              - Field/asset data lake
              - "Alerts & thresholds"
              - "Models & analytics"
              - API connections to FMS/buyers
              - "Device health & firmware"
            vocabulary:
              - { term: Sensor / node, runtime_type: Object }
              - { term: Data feed, runtime_type: Object }
              - { term: Data engineer, runtime_type: Actor }
              - { term: Reading ingested, runtime_type: Event }
              - { term: Threshold breach alert, runtime_type: Event }
              - { term: Sensor offline, runtime_type: State }
              - { term: Act on alert, runtime_type: Decision }
              - { term: Data pipeline run, runtime_type: Workflow }
              - { term: Analytics dashboard, runtime_type: Artefact }
              - { term: Insight / recommendation, runtime_type: Outcome }
              - { term: Data coverage, runtime_type: Outcome }
              - { term: Uptime / data quality, runtime_type: Learning }
              - { term: Model accuracy, runtime_type: Learning }
          - name: "Carbon, MRV & Sustainability Tech"
            note: "Carbon credit issuance and MRV are governed by registry standards and emerging assurance rules; mis-stated credits carry legal and reputational liability."
            operating_domains:
              - "Carbon & emissions baseline"
              - "Soil carbon sampling & modelling"
              - Practice change tracking (MRV)
              - "Credit issuance & registry"
              - Scope 3 / supplier data
              - "Verification & audit evidence"
              - Sustainability reporting
            vocabulary:
              - { term: Carbon project / parcel, runtime_type: Object }
              - { term: Emissions baseline, runtime_type: State }
              - { term: MRV analyst, runtime_type: Actor }
              - { term: Practice change logged, runtime_type: Event }
              - { term: Measurement / sampling round, runtime_type: Workflow }
              - { term: Verification decision, runtime_type: Decision }
              - { term: Verified, runtime_type: State }
              - { term: Carbon credit issued, runtime_type: Event }
              - { term: Verification report, runtime_type: Artefact }
              - { term: Credits issued (tCO2e), runtime_type: Outcome }
              - { term: Emissions reduced, runtime_type: Outcome }
              - { term: Carbon intensity per tonne, runtime_type: Learning }
              - { term: Additionality / leakage, runtime_type: Learning }
      - name: "n-livestockOS"
        buyer: "Livestock farmers (dairy, beef, sheep, pig, poultry) and their vets/herd managers who run animals as the core enterprise and must manage health, breeding and movements."
        os_test: "A distinct buyer (livestock keeper / herd manager / vet), its own budget (herd-management software, EID, milking/feeding systems), a frontend organised around individual animals and groups, a state model of animals moving through health/breeding/production lifecycles, and a very large repeatable population of livestock holdings."
        sectors:
          - name: Dairy Herd Management
            note: "Dairy is regulated for milk hygiene, antibiotic/medicine records and cattle identification; bulk-tank quality results affect legal saleability."
            operating_domains:
              - "Cow & herd records"
              - "Milking & yield"
              - "Breeding & reproduction (heat/AI)"
              - "Health & mastitis"
              - "Feed & ration"
              - "Dry-off & calving"
              - "Milk quality & bulk tank"
            vocabulary:
              - { term: Cow, runtime_type: Object }
              - { term: Herd manager, runtime_type: Actor }
              - { term: In milk / dry, runtime_type: State }
              - { term: Heat detected, runtime_type: Event }
              - { term: Serve / AI decision, runtime_type: Decision }
              - { term: Insemination (AI), runtime_type: Event }
              - { term: Calving, runtime_type: Event }
              - { term: Breeding programme, runtime_type: Workflow }
              - { term: Milk yield (litres/cow), runtime_type: Outcome }
              - { term: Somatic cell count, runtime_type: State }
              - { term: Milk record sheet, runtime_type: Artefact }
              - { term: Pregnancy rate, runtime_type: Learning }
              - { term: Margin over feed, runtime_type: Learning }
          - name: "Beef & Sheep Production"
            note: "Cattle/sheep require statutory ID, movement reporting (BCMS / livestock movement service) and standstill rules; slaughter routes are regulated."
            operating_domains:
              - Herd / flock groups
              - "Tagging & EID"
              - "Grazing & finishing groups"
              - "Weighing & growth (DLWG)"
              - "Breeding & lambing/calving"
              - "Movements & markets"
              - Selection for slaughter
            vocabulary:
              - { term: Animal (EID tag), runtime_type: Object }
              - { term: Mob / batch, runtime_type: Object }
              - { term: Stockperson, runtime_type: Actor }
              - { term: Weighing, runtime_type: Event }
              - { term: Fit to sell, runtime_type: State }
              - { term: Draw for slaughter decision, runtime_type: Decision }
              - { term: Movement (off / on), runtime_type: Event }
              - { term: Finishing workflow, runtime_type: Workflow }
              - { term: Movement licence, runtime_type: Artefact }
              - { term: Daily liveweight gain, runtime_type: Outcome }
              - { term: Deadweight / grade, runtime_type: Outcome }
              - { term: Days to finish, runtime_type: Learning }
              - { term: Cost of production per kg, runtime_type: Learning }
          - name: "Animal Health & Veterinary"
            note: "Veterinary medicines are prescription-controlled with mandatory records and withdrawal periods; notifiable diseases (e.g. TB) trigger statutory reporting and restrictions."
            operating_domains:
              - Animal health plan
              - "Medicine cabinet & records"
              - "Treatments & withdrawal periods"
              - "Vet visits & diagnostics"
              - Vaccination programmes
              - "Disease surveillance & testing"
              - "Mortality & post-mortem"
            vocabulary:
              - { term: Patient animal, runtime_type: Object }
              - { term: Vet, runtime_type: Actor }
              - { term: Medicine / product, runtime_type: Object }
              - { term: Treatment given, runtime_type: Event }
              - { term: Under withdrawal, runtime_type: State }
              - { term: Treat / cull decision, runtime_type: Decision }
              - { term: Vaccination round, runtime_type: Workflow }
              - { term: Medicine record book, runtime_type: Artefact }
              - { term: Test result (e.g. TB), runtime_type: State }
              - { term: Recovery, runtime_type: Outcome }
              - { term: Mortality / loss, runtime_type: Outcome }
              - { term: Antibiotic usage (mg/PCU), runtime_type: Learning }
              - { term: Disease incidence, runtime_type: Learning }
          - name: "Poultry & Egg Production"
            note: "Poultry/egg production is regulated for registration, salmonella controls, egg marketing standards and avian-influenza biosecurity (housing orders are statutory)."
            operating_domains:
              - "Flocks & houses"
              - "Lay & growth performance"
              - "Feed & water systems"
              - "House environment & ventilation"
              - "Biosecurity & vaccination"
              - "Egg grading & packing"
              - "Mortality & culling"
            vocabulary:
              - { term: Flock, runtime_type: Object }
              - { term: House / shed, runtime_type: Object }
              - { term: Poultry manager, runtime_type: Actor }
              - { term: Daily check, runtime_type: Event }
              - { term: In lay, runtime_type: State }
              - { term: Depopulate / clear decision, runtime_type: Decision }
              - { term: Crop / batch cycle, runtime_type: Workflow }
              - { term: Biosecurity breach, runtime_type: Event }
              - { term: Flock record, runtime_type: Artefact }
              - { term: "Lay rate (%)", runtime_type: Outcome }
              - { term: Eggs packed / birds out, runtime_type: Outcome }
              - { term: Feed conversion ratio, runtime_type: Learning }
              - { term: "Mortality %", runtime_type: Learning }
          - name: "Feed, Nutrition & Rations"
            note: Feed businesses must be registered/approved; medicated feed and certain ingredients are regulated with traceability and labelling requirements.
            operating_domains:
              - "Rations & diet formulations"
              - "Feed ingredients & stock"
              - "Forage stocks & analysis"
              - "Mixing & feeding-out"
              - Feed plan by group
              - "Intake & refusals"
              - Feed cost tracking
            vocabulary:
              - { term: Ration / diet, runtime_type: Artefact }
              - { term: Feed ingredient, runtime_type: Object }
              - { term: Nutritionist, runtime_type: Actor }
              - { term: Forage analysis result, runtime_type: State }
              - { term: Reformulate ration, runtime_type: Decision }
              - { term: "Mix & feed-out", runtime_type: Workflow }
              - { term: Feed delivered, runtime_type: Event }
              - { term: Out of feed, runtime_type: State }
              - { term: Load sheet / mix record, runtime_type: Artefact }
              - { term: Dry matter intake, runtime_type: Outcome }
              - { term: Feed cost per head/day, runtime_type: Outcome }
              - { term: Feed conversion efficiency, runtime_type: Learning }
              - { term: Mix accuracy, runtime_type: Learning }
  - name: "Security, Risk & Intelligence"
    os:
      - name: "n-securityOS"
        buyer: "Chief Security Officer / Head of Physical Security at corporates, venues, critical-infrastructure and security-guarding firms who pay for guard force, access control and incident response."
        os_test: "Distinct buyer (CSO/physical security), distinct state model (posts, patrols, access events, incidents on-site), distinct vocabulary (guard tour, badge, muster, lockdown) and repeatable companies (Allied Universal, G4S, Verkada-using estates) — not just reworded cyber."
        sectors:
          - name: "Manned Guarding & Guard Force Management"
            note: "Security guarding is licensed (SIA in the UK, state PERC/guard cards in the US); officers must hold valid licences to be deployed."
            operating_domains:
              - "Guard roster & post assignments"
              - "Patrol routes & checkpoint tours"
              - "Sites & posts under contract"
              - "Shift handovers & briefings"
              - Incident reports from the field
              - "Lone-worker & guard welfare checks"
              - "Client SLAs & billable hours"
            vocabulary:
              - { term: Guard / Security Officer, runtime_type: Actor }
              - { term: Post, runtime_type: Object }
              - { term: Patrol Route, runtime_type: Object }
              - { term: Checkpoint Scan, runtime_type: Event }
              - { term: Shift, runtime_type: Object }
              - { term: "On-Post / Off-Post", runtime_type: State }
              - { term: Deployment Decision, runtime_type: Decision }
              - { term: Guard Tour, runtime_type: Workflow }
              - { term: Shift Handover Log, runtime_type: Artefact }
              - { term: Daily Occurrence Book (DOB), runtime_type: Artefact }
              - { term: Incident at Site, runtime_type: Event }
              - { term: "Lone-Worker Check-In", runtime_type: Event }
              - { term: Missed Checkpoint, runtime_type: State }
              - { term: SLA Met / Breached, runtime_type: Outcome }
              - { term: Patrol Coverage Rate, runtime_type: Learning }
          - name: "Access Control & Identity Management"
            operating_domains:
              - "Badge & credential issuance"
              - "Door & turnstile controllers"
              - "Access groups & permission levels"
              - "Visitor pre-registration"
              - "Tailgating & forced-door alarms"
              - "Anti-passback & zone occupancy"
              - Lost/stolen credential revocation
            vocabulary:
              - { term: Cardholder, runtime_type: Actor }
              - { term: Access Badge / Credential, runtime_type: Object }
              - { term: Door / Reader, runtime_type: Object }
              - { term: Access Group, runtime_type: Object }
              - { term: Badge Swipe, runtime_type: Event }
              - { term: Access Granted / Denied, runtime_type: Decision }
              - { term: "Forced-Door Alarm", runtime_type: Event }
              - { term: Door State (Locked/Unlocked), runtime_type: State }
              - { term: Credential Provisioning, runtime_type: Workflow }
              - { term: Access Policy, runtime_type: Artefact }
              - { term: Revocation Order, runtime_type: Decision }
              - { term: "Anti-Passback Violation", runtime_type: State }
              - { term: Audit Trail Export, runtime_type: Artefact }
              - { term: Tailgating Detected, runtime_type: Outcome }
              - { term: Zone Occupancy Count, runtime_type: Learning }
          - name: "Video Surveillance & Command Centre Operations"
            note: Monitoring of CCTV in public space and any biometric/facial analytics is regulated under GDPR/UK DPA and the Surveillance Camera Code; remote monitoring centres carry BS 8418 / SIA ARC accreditation.
            operating_domains:
              - "Camera feeds & video walls"
              - "Motion & line-cross analytics zones"
              - Alarm verification queue
              - Operator dispatch to field units
              - "Footage retrieval & evidence clips"
              - "Camera health & blind-spot monitoring"
              - Live monitoring SLAs
            vocabulary:
              - { term: Camera Operator, runtime_type: Actor }
              - { term: Camera / Channel, runtime_type: Object }
              - { term: Analytics Zone, runtime_type: Object }
              - { term: "Motion / Line-Cross Alert", runtime_type: Event }
              - { term: Alarm Verification, runtime_type: Decision }
              - { term: Camera Online / Offline, runtime_type: State }
              - { term: Dispatch to Field, runtime_type: Workflow }
              - { term: Evidence Clip, runtime_type: Artefact }
              - { term: Bookmarked Footage, runtime_type: Artefact }
              - { term: False Alarm / True Alarm, runtime_type: Outcome }
              - { term: Operator Acknowledgement, runtime_type: Event }
              - { term: Blind Spot Flagged, runtime_type: State }
              - { term: Footage Retention Window, runtime_type: Object }
              - { term: Average Verification Time, runtime_type: Learning }
              - { term: Suspect Identified, runtime_type: Outcome }
          - name: "Event & Crowd Security"
            note: "Crowd safety at licensed venues falls under the Licensing Act, the forthcoming Martyn's Law (Protect Duty), and the Green Guide for sports grounds."
            operating_domains:
              - "Venue zones & ingress lanes"
              - "Crowd density & flow monitoring"
              - "Bag-search & screening lanes"
              - "Ejection & ban records"
              - Stewarding deployment
              - "Pitch-side / stage barrier control"
              - Emergency evacuation muster
            vocabulary:
              - { term: Steward / Marshal, runtime_type: Actor }
              - { term: Patron / Attendee, runtime_type: Actor }
              - { term: Ingress Lane, runtime_type: Object }
              - { term: Screening Point, runtime_type: Object }
              - { term: Ejection, runtime_type: Event }
              - { term: Crowd Density Level, runtime_type: State }
              - { term: "Hold-and-Release Decision", runtime_type: Decision }
              - { term: Evacuation / Muster, runtime_type: Workflow }
              - { term: Ban / Exclusion Record, runtime_type: Artefact }
              - { term: Incident Log, runtime_type: Artefact }
              - { term: Bag Search, runtime_type: Event }
              - { term: Zone at Capacity, runtime_type: State }
              - { term: Safe Egress Achieved, runtime_type: Outcome }
              - { term: Confiscation, runtime_type: Event }
              - { term: "Incidents per 1,000 Attendees", runtime_type: Learning }
          - name: "Executive Protection & Travel Security"
            note: "Close protection work is SIA-licensed in the UK; armed protection abroad is governed by host-country firearms and PMSC licensing."
            operating_domains:
              - "Principal profiles & threat levels"
              - Advance reconnaissance of venues/routes
              - Protective detail rosters
              - "Secure transport & route planning"
              - Travel risk briefings
              - "Real-time location & check-in tracking"
              - Residence security surveys
            vocabulary:
              - { term: Close Protection Officer (CPO), runtime_type: Actor }
              - { term: Principal, runtime_type: Actor }
              - { term: Route / Itinerary, runtime_type: Object }
              - { term: Advance Recce, runtime_type: Workflow }
              - { term: Threat Level (of Principal), runtime_type: State }
              - { term: "Go / No-Go Call", runtime_type: Decision }
              - { term: Travel Risk Briefing, runtime_type: Artefact }
              - { term: "Check-In Ping", runtime_type: Event }
              - { term: Security Survey, runtime_type: Artefact }
              - { term: Convoy / Motorcade, runtime_type: Object }
              - { term: "Incident En-Route", runtime_type: Event }
              - { term: Safe Arrival, runtime_type: Outcome }
              - { term: Evacuation Plan, runtime_type: Artefact }
              - { term: Principal Located, runtime_type: State }
              - { term: Detail Hours Logged, runtime_type: Learning }
          - name: "Security Systems Installation & Maintenance"
            note: "Intruder-alarm and fire-system installers must hold NSI/SSAIB approval and certify to relevant standards (PD 6662, BS 5839)."
            operating_domains:
              - "Site survey & system design"
              - Engineer job dispatch
              - "Device commissioning & as-builts"
              - Preventive maintenance schedules
              - "Fault tickets & call-outs"
              - "Spare-parts inventory"
              - Compliance certification (alarm/fire)
            vocabulary:
              - { term: Field Engineer, runtime_type: Actor }
              - { term: Installed Device, runtime_type: Object }
              - { term: Job / Work Order, runtime_type: Object }
              - { term: Site Survey, runtime_type: Workflow }
              - { term: Commissioning, runtime_type: Event }
              - { term: Device Faulty / Healthy, runtime_type: State }
              - { term: "Call-Out Decision", runtime_type: Decision }
              - { term: "As-Built Drawing", runtime_type: Artefact }
              - { term: Maintenance Visit, runtime_type: Event }
              - { term: Compliance Certificate, runtime_type: Artefact }
              - { term: Spare Part, runtime_type: Object }
              - { term: System Handover, runtime_type: Outcome }
              - { term: "Out-of-Service Window", runtime_type: State }
              - { term: "First-Time Fix Rate", runtime_type: Learning }
      - name: "n-fraudOS"
        buyer: "Head of Fraud / Financial Crime at banks, payment processors, fintechs, insurers and e-commerce who fund fraud-prevention teams and own chargeback and loss budgets."
        os_test: "Distinct buyer (Fraud/FinCrime lead, not security or cyber), distinct state model (transactions, cases, holds, chargebacks), distinct vocabulary (SAR, mule, chargeback, decline) and repeatable companies (banks, Stripe Radar, Featurespace) — its money-loss logic is its own world."
        sectors:
          - name: "Payment & Transaction Fraud"
            note: "Payment fraud controls operate under PSD2/SCA, card-scheme rules (Visa/Mastercard) and PCI-DSS."
            operating_domains:
              - "Real-time transaction scoring"
              - "Decline & step-up rules"
              - "Card-not-present authorisation"
              - "Velocity & spending-pattern monitoring"
              - Block / allow lists
              - "Friendly-fraud disputes"
              - "False-positive review queue"
            vocabulary:
              - { term: Cardholder, runtime_type: Actor }
              - { term: Transaction, runtime_type: Object }
              - { term: Risk Score, runtime_type: State }
              - { term: Authorisation Request, runtime_type: Event }
              - { term: "Approve / Decline / Step-Up", runtime_type: Decision }
              - { term: Fraud Rule, runtime_type: Object }
              - { term: Velocity Breach, runtime_type: Event }
              - { term: Transaction Held, runtime_type: State }
              - { term: Manual Review, runtime_type: Workflow }
              - { term: Block List Entry, runtime_type: Artefact }
              - { term: Confirmed Fraud, runtime_type: Outcome }
              - { term: False Positive, runtime_type: Outcome }
              - { term: Chargeback Recovered, runtime_type: Outcome }
              - { term: Approval Rate, runtime_type: Learning }
          - name: "Identity & Account-Takeover Fraud"
            note: Identity verification must meet KYC/CDD obligations under AML regulations and (in the EU) eIDAS.
            operating_domains:
              - "Device & behavioural fingerprinting"
              - "Login risk & impossible-travel checks"
              - "Synthetic-identity detection"
              - Account recovery flows
              - "Step-up authentication challenges"
              - "Bot & credential-stuffing defence"
              - "New-account application screening"
            vocabulary:
              - { term: Account Holder, runtime_type: Actor }
              - { term: User Account, runtime_type: Object }
              - { term: Device Fingerprint, runtime_type: Object }
              - { term: Login Attempt, runtime_type: Event }
              - { term: Impossible Travel Flag, runtime_type: State }
              - { term: "Step-Up Challenge", runtime_type: Decision }
              - { term: Account Locked, runtime_type: State }
              - { term: Identity Verification (KYC), runtime_type: Workflow }
              - { term: Synthetic Identity, runtime_type: Object }
              - { term: Verification Result, runtime_type: Artefact }
              - { term: Takeover Confirmed, runtime_type: Outcome }
              - { term: Bot Attack, runtime_type: Event }
              - { term: Trust Score, runtime_type: State }
              - { term: Account Recovered, runtime_type: Outcome }
              - { term: ATO Rate, runtime_type: Learning }
          - name: "Anti-Money-Laundering & Transaction Monitoring"
            note: "AML is heavily regulated — MLR 2017, the EU AML Directives, FATF guidance and mandatory SAR filing to the national FIU (NCA in the UK, FinCEN in the US)."
            operating_domains:
              - "Customer due diligence & risk rating"
              - "Sanctions & PEP screening"
              - "Transaction-monitoring scenarios"
              - Alert investigation queue
              - "Suspicious-activity case building"
              - SAR/STR filing to regulator
              - "Mule-account network detection"
            vocabulary:
              - { term: Customer, runtime_type: Actor }
              - { term: Beneficial Owner, runtime_type: Actor }
              - { term: Monitoring Scenario, runtime_type: Object }
              - { term: AML Alert, runtime_type: Event }
              - { term: Customer Risk Rating, runtime_type: State }
              - { term: Sanctions Hit, runtime_type: Event }
              - { term: Disposition Decision, runtime_type: Decision }
              - { term: Investigation Case, runtime_type: Workflow }
              - { term: Suspicious Activity Report (SAR), runtime_type: Artefact }
              - { term: Mule Account, runtime_type: Object }
              - { term: Case Under Review, runtime_type: State }
              - { term: Filed to FIU, runtime_type: Outcome }
              - { term: Account Exited, runtime_type: Outcome }
              - { term: "Alert-to-SAR Conversion", runtime_type: Learning }
          - name: Insurance Claims Fraud
            note: "Claims handling and SIU activity is FCA-regulated; data sharing runs through IFB/CIFAS and must respect GDPR."
            operating_domains:
              - "Claim intake & triage"
              - "Fraud-indicator scoring"
              - "Staged-accident & ring detection"
              - SIU (Special Investigations Unit) referrals
              - Medical/repair invoice review
              - Claimant interview scheduling
              - "Recovery & repudiation decisions"
            vocabulary:
              - { term: Claimant, runtime_type: Actor }
              - { term: Claim, runtime_type: Object }
              - { term: Fraud Indicator, runtime_type: Object }
              - { term: Claim Submitted, runtime_type: Event }
              - { term: Suspicion Flag, runtime_type: State }
              - { term: SIU Referral, runtime_type: Decision }
              - { term: Investigation, runtime_type: Workflow }
              - { term: Fraud Ring, runtime_type: Object }
              - { term: Investigation Report, runtime_type: Artefact }
              - { term: Claim Repudiated, runtime_type: Outcome }
              - { term: Claim Paid, runtime_type: Outcome }
              - { term: Interview Held, runtime_type: Event }
              - { term: Recovery Amount, runtime_type: Outcome }
              - { term: Fraud Save Rate, runtime_type: Learning }
          - name: "E-Commerce & Marketplace Fraud"
            operating_domains:
              - Order risk scoring
              - "Promo & coupon abuse detection"
              - "Seller & listing integrity"
              - "Refund & return abuse"
              - "Reshipper / drop-address detection"
              - Chargeback representment
              - "Trust & safety actioning"
            vocabulary:
              - { term: Buyer, runtime_type: Actor }
              - { term: Seller, runtime_type: Actor }
              - { term: Order, runtime_type: Object }
              - { term: Order Placed, runtime_type: Event }
              - { term: Order Risk Level, runtime_type: State }
              - { term: Hold / Cancel / Fulfil, runtime_type: Decision }
              - { term: Promo Abuse Pattern, runtime_type: Object }
              - { term: Chargeback Representment, runtime_type: Workflow }
              - { term: Evidence Package, runtime_type: Artefact }
              - { term: Account Suspended, runtime_type: State }
              - { term: Refund Abuse Confirmed, runtime_type: Outcome }
              - { term: Dispute Won, runtime_type: Outcome }
              - { term: Listing Removed, runtime_type: Event }
              - { term: Loss Rate (bps), runtime_type: Learning }
          - name: "Internal & Occupational Fraud"
            operating_domains:
              - "Employee expense & T&E anomalies"
              - "Procurement & vendor collusion"
              - "Segregation-of-duties conflicts"
              - Whistleblower hotline intake
              - "Privileged-access abuse review"
              - Forensic accounting workpapers
              - "Disciplinary & recovery outcomes"
            vocabulary:
              - { term: Employee, runtime_type: Actor }
              - { term: Vendor, runtime_type: Actor }
              - { term: Expense / Transaction, runtime_type: Object }
              - { term: Anomaly Flagged, runtime_type: Event }
              - { term: "Segregation-of-Duties Conflict", runtime_type: State }
              - { term: Open Investigation, runtime_type: Decision }
              - { term: Whistleblower Report, runtime_type: Event }
              - { term: Forensic Review, runtime_type: Workflow }
              - { term: Workpaper / Evidence File, runtime_type: Artefact }
              - { term: Substantiated / Unsubstantiated, runtime_type: Outcome }
              - { term: Disciplinary Action, runtime_type: Outcome }
              - { term: Recovery Made, runtime_type: Outcome }
              - { term: Case Closed, runtime_type: State }
              - { term: Detection Lead Time, runtime_type: Learning }
      - name: "n-cyberOS"
        buyer: "CISO / Head of Security Operations who owns the cyber budget, the SOC, and accountability for breaches and audit findings."
        os_test: "Distinct buyer (CISO, separate budget from physical security and fraud), distinct state model (assets, vulns, alerts, incidents in a kill-chain), distinct vocabulary (CVE, EDR, IOC, MTTR) and repeatable companies (CrowdStrike, Splunk, Wiz customers) — unmistakably its own OS."
        sectors:
          - name: "Security Operations Centre (SOC) & Detection"
            operating_domains:
              - Alert triage queue
              - "Detection rules & correlation logic"
              - "Log & telemetry pipelines"
              - "Threat-hunting hypotheses"
              - "Tier-1/2/3 escalation paths"
              - "Shift coverage & handover"
              - "Detection-coverage mapping (MITRE)"
            vocabulary:
              - { term: SOC Analyst, runtime_type: Actor }
              - { term: Alert, runtime_type: Event }
              - { term: Detection Rule, runtime_type: Object }
              - { term: Log Source, runtime_type: Object }
              - { term: Triage Decision, runtime_type: Decision }
              - { term: Alert Status (Open/Closed), runtime_type: State }
              - { term: Escalation, runtime_type: Workflow }
              - { term: Threat Hunt, runtime_type: Workflow }
              - { term: Investigation Notes, runtime_type: Artefact }
              - { term: True Positive / False Positive, runtime_type: Outcome }
              - { term: Indicator of Compromise (IOC), runtime_type: Object }
              - { term: Alert Acknowledged, runtime_type: Event }
              - { term: Mean Time to Detect (MTTD), runtime_type: Learning }
              - { term: Coverage Gap Identified, runtime_type: Learning }
          - name: "Incident Response & Forensics"
            note: "Confirmed personal-data breaches trigger statutory notification (GDPR 72-hour rule, NIS2, sector regulators)."
            operating_domains:
              - "Incident declaration & severity grading"
              - "Containment & isolation actions"
              - "Forensic image & memory capture"
              - "Kill-chain reconstruction"
              - "War-room coordination"
              - "Eradication & recovery steps"
              - "Post-incident lessons-learned"
            vocabulary:
              - { term: Incident Responder, runtime_type: Actor }
              - { term: Security Incident, runtime_type: Object }
              - { term: Severity Level, runtime_type: State }
              - { term: Containment Action, runtime_type: Decision }
              - { term: Host Isolated, runtime_type: Event }
              - { term: Forensic Image, runtime_type: Artefact }
              - { term: "Eradication & Recovery", runtime_type: Workflow }
              - { term: Indicator Extracted, runtime_type: Event }
              - { term: Incident Contained, runtime_type: State }
              - { term: "Root-Cause Report", runtime_type: Artefact }
              - { term: Service Restored, runtime_type: Outcome }
              - { term: Breach Confirmed, runtime_type: Outcome }
              - { term: Lessons Learned, runtime_type: Learning }
              - { term: Mean Time to Respond (MTTR), runtime_type: Learning }
          - name: "Vulnerability & Attack-Surface Management"
            operating_domains:
              - "Asset & service inventory"
              - "Vulnerability scanning & findings"
              - "Risk-based prioritisation (CVSS/EPSS)"
              - "Patch & remediation tickets"
              - "External attack-surface discovery"
              - "SLA & exception tracking"
              - Remediation verification rescans
            vocabulary:
              - { term: Asset Owner, runtime_type: Actor }
              - { term: Asset, runtime_type: Object }
              - { term: Vulnerability (CVE), runtime_type: Object }
              - { term: Scan Run, runtime_type: Event }
              - { term: Severity / CVSS, runtime_type: State }
              - { term: Prioritisation Decision, runtime_type: Decision }
              - { term: Remediation Ticket, runtime_type: Workflow }
              - { term: Exception / Risk Acceptance, runtime_type: Artefact }
              - { term: Patched / Unpatched, runtime_type: State }
              - { term: Exposed Service Found, runtime_type: Event }
              - { term: Vulnerability Closed, runtime_type: Outcome }
              - { term: SLA Breach, runtime_type: Outcome }
              - { term: Remediation Plan, runtime_type: Artefact }
              - { term: Mean Time to Remediate, runtime_type: Learning }
          - name: "Identity & Access Security (IAM/PAM)"
            operating_domains:
              - "Joiner-mover-leaver provisioning"
              - "Privileged-account vaulting"
              - "Access-review certification campaigns"
              - "MFA & conditional-access policy"
              - "Entitlement & role mining"
              - "Session monitoring & break-glass"
              - "Orphan & toxic-combination cleanup"
            vocabulary:
              - { term: Identity / User, runtime_type: Actor }
              - { term: Entitlement / Role, runtime_type: Object }
              - { term: Privileged Account, runtime_type: Object }
              - { term: Access Request, runtime_type: Event }
              - { term: Grant / Deny / Revoke, runtime_type: Decision }
              - { term: Access Certification, runtime_type: Workflow }
              - { term: Account Active / Disabled, runtime_type: State }
              - { term: "Break-Glass Session", runtime_type: Event }
              - { term: Attestation Record, runtime_type: Artefact }
              - { term: Orphan Account, runtime_type: State }
              - { term: Toxic Combination, runtime_type: Object }
              - { term: Access Revoked, runtime_type: Outcome }
              - { term: Certification Completed, runtime_type: Outcome }
              - { term: "Privileged-Access Coverage", runtime_type: Learning }
          - name: "Governance, Risk & Compliance (Cyber)"
            note: "Maps to certifiable/regulated regimes — ISO 27001, SOC 2, PCI-DSS, NIS2, DORA — with formal external audit."
            operating_domains:
              - Control framework mapping
              - "Audit & evidence collection"
              - Policy lifecycle management
              - "Risk register & treatment plans"
              - "Third-party / vendor risk assessment"
              - Compliance attestation reporting
              - "Findings & remediation tracking"
            vocabulary:
              - { term: Control Owner, runtime_type: Actor }
              - { term: Control, runtime_type: Object }
              - { term: Framework (ISO 27001/SOC 2), runtime_type: Object }
              - { term: Evidence Request, runtime_type: Event }
              - { term: Control Effective / Failing, runtime_type: State }
              - { term: Risk Treatment Decision, runtime_type: Decision }
              - { term: Audit, runtime_type: Workflow }
              - { term: Evidence Artefact, runtime_type: Artefact }
              - { term: Audit Finding, runtime_type: Event }
              - { term: Policy Document, runtime_type: Artefact }
              - { term: Certification Achieved, runtime_type: Outcome }
              - { term: Finding Remediated, runtime_type: Outcome }
              - { term: Vendor Risk Tier, runtime_type: State }
              - { term: Control Maturity Score, runtime_type: Learning }
          - name: "Cyber Threat Intelligence & Hunting"
            operating_domains:
              - "Threat-actor & campaign tracking"
              - "IOC & TTP feeds ingestion"
              - Intelligence requirements (PIRs)
              - "Malware & sandbox detonation"
              - "Dark-web & leak monitoring"
              - "Intel-to-detection enrichment"
              - "Finished-intelligence reporting"
            vocabulary:
              - { term: Threat Analyst, runtime_type: Actor }
              - { term: Threat Actor, runtime_type: Actor }
              - { term: Campaign / TTP, runtime_type: Object }
              - { term: Intel Feed Item, runtime_type: Event }
              - { term: Priority Intelligence Requirement, runtime_type: Object }
              - { term: Confidence Level, runtime_type: State }
              - { term: Enrichment Decision, runtime_type: Decision }
              - { term: Sandbox Detonation, runtime_type: Workflow }
              - { term: Indicator (IOC), runtime_type: Object }
              - { term: Intel Report, runtime_type: Artefact }
              - { term: Detection Created, runtime_type: Outcome }
              - { term: Leak / Credential Exposure, runtime_type: Event }
              - { term: Actor Attributed, runtime_type: Outcome }
              - { term: Feed Hit Rate, runtime_type: Learning }
      - name: "n-enforcementOS"
        buyer: Chief Constable / Sheriff / Head of Operations in policing and statutory enforcement agencies funded by public budgets and accountable to oversight bodies.
        os_test: "Distinct buyer (public law-enforcement command, not corporate security), distinct state model (calls, custody, charges, court flow), distinct vocabulary (CAD, custody record, caution, disclosure) and repeatable bodies (police forces, regulators) — a sovereign world with statutory powers, not a corporate one."
        sectors:
          - name: "Command & Dispatch (999/911 Response)"
            note: "Emergency-call handling and grading are governed by statutory policing standards and inspected by HMICFRS."
            operating_domains:
              - "Emergency call intake & grading"
              - "Resource availability & status"
              - "Incident assignment & dispatch"
              - Live unit tracking on map
              - "Backup & escalation requests"
              - "Multi-agency mutual aid"
              - "Response-time performance"
            vocabulary:
              - { term: Dispatcher / Controller, runtime_type: Actor }
              - { term: Response Unit, runtime_type: Actor }
              - { term: Incident / Call, runtime_type: Object }
              - { term: 999 Call Received, runtime_type: Event }
              - { term: Grading (Emergency/Priority), runtime_type: State }
              - { term: Dispatch Decision, runtime_type: Decision }
              - { term: "Unit Status (Available/On-Scene)", runtime_type: State }
              - { term: Dispatch Workflow, runtime_type: Workflow }
              - { term: "Computer-Aided Dispatch Log", runtime_type: Artefact }
              - { term: "On-Scene Arrival", runtime_type: Event }
              - { term: Incident Resolved, runtime_type: Outcome }
              - { term: Backup Requested, runtime_type: Event }
              - { term: Response Time, runtime_type: Learning }
              - { term: Incident Log, runtime_type: Artefact }
          - name: "Custody & Detention Management"
            note: "Custody is governed by PACE and its Codes of Practice (detention clocks, reviews, rights to legal advice)."
            operating_domains:
              - "Booking-in & risk assessment"
              - Detainee welfare checks
              - "Property & evidence handling"
              - "Detention-clock & review timings"
              - "Appropriate-adult & legal-rep notifications"
              - "Cell allocation & occupancy"
              - Charge / bail / release decisions
            vocabulary:
              - { term: Custody Officer, runtime_type: Actor }
              - { term: Detainee, runtime_type: Actor }
              - { term: Custody Record, runtime_type: Object }
              - { term: "Booking-In", runtime_type: Event }
              - { term: Detention Status, runtime_type: State }
              - { term: Charge / Bail / Release, runtime_type: Decision }
              - { term: Welfare Check, runtime_type: Workflow }
              - { term: Detention Clock, runtime_type: State }
              - { term: Property Log, runtime_type: Artefact }
              - { term: Detention Review, runtime_type: Event }
              - { term: Released Under Investigation, runtime_type: Outcome }
              - { term: Charged, runtime_type: Outcome }
              - { term: Cell Allocation, runtime_type: Decision }
              - { term: Detention Hours, runtime_type: Learning }
          - name: "Investigation & Case Management"
            note: Investigation and disclosure follow CPIA 1996 and CPS charging standards; PACE governs interview and arrest.
            operating_domains:
              - "Crime recording & classification"
              - Investigation lines of enquiry
              - "Suspect & witness management"
              - "Evidence & exhibit register"
              - Disclosure scheduling
              - "Case-file build for prosecution"
              - "Outcome & detection coding"
            vocabulary:
              - { term: Investigating Officer, runtime_type: Actor }
              - { term: Suspect, runtime_type: Actor }
              - { term: Crime Record, runtime_type: Object }
              - { term: Line of Enquiry, runtime_type: Object }
              - { term: Statement Taken, runtime_type: Event }
              - { term: Case Status, runtime_type: State }
              - { term: Charging Decision, runtime_type: Decision }
              - { term: "Case-File Build", runtime_type: Workflow }
              - { term: Exhibit / Evidence, runtime_type: Artefact }
              - { term: Disclosure Schedule, runtime_type: Artefact }
              - { term: Suspect Identified, runtime_type: Event }
              - { term: Charged / NFA, runtime_type: Outcome }
              - { term: Case Solved, runtime_type: Outcome }
              - { term: Detection Rate, runtime_type: Learning }
          - name: "Digital & Body-Worn Evidence (DEMS)"
            note: Digital evidence handling must preserve continuity for court admissibility and comply with MoPI retention rules and DPA.
            operating_domains:
              - "Body-worn camera ingest"
              - "Digital exhibit storage & chain of custody"
              - Redaction for disclosure
              - "Retention & deletion scheduling"
              - "Access audit & sharing with CPS"
              - "Mobile-device extraction"
              - "Court-bundle export"
            vocabulary:
              - { term: Evidence Handler, runtime_type: Actor }
              - { term: Digital Exhibit, runtime_type: Object }
              - { term: "Body-Worn Footage", runtime_type: Object }
              - { term: Footage Uploaded, runtime_type: Event }
              - { term: Chain of Custody, runtime_type: State }
              - { term: Redaction Decision, runtime_type: Decision }
              - { term: Redaction Workflow, runtime_type: Workflow }
              - { term: Disclosure Package, runtime_type: Artefact }
              - { term: Sealed / Restricted, runtime_type: State }
              - { term: Shared with CPS, runtime_type: Event }
              - { term: Evidence Admitted, runtime_type: Outcome }
              - { term: Retention Expiry, runtime_type: Event }
              - { term: Court Bundle, runtime_type: Artefact }
              - { term: Disclosure Turnaround, runtime_type: Learning }
          - name: "Regulatory & Statutory Enforcement"
            note: "Statutory enforcement (e.g. HSE, trading standards, environmental regulators) operates under specific empowering Acts and the Regulators' Code."
            operating_domains:
              - "Licence & permit register"
              - "Inspection scheduling & visits"
              - "Breach & non-compliance findings"
              - "Notices & sanctions issuance"
              - Prosecution referral
              - Appeals tracking
              - "Compliance-rate reporting"
            vocabulary:
              - { term: Enforcement Officer, runtime_type: Actor }
              - { term: Regulated Entity, runtime_type: Actor }
              - { term: Licence / Permit, runtime_type: Object }
              - { term: Inspection, runtime_type: Event }
              - { term: Compliance Status, runtime_type: State }
              - { term: Sanction Decision, runtime_type: Decision }
              - { term: Enforcement Workflow, runtime_type: Workflow }
              - { term: Improvement / Prohibition Notice, runtime_type: Artefact }
              - { term: Breach Recorded, runtime_type: Event }
              - { term: Under Appeal, runtime_type: State }
              - { term: Prosecution Referred, runtime_type: Outcome }
              - { term: Compliance Achieved, runtime_type: Outcome }
              - { term: Case File, runtime_type: Artefact }
              - { term: Compliance Rate, runtime_type: Learning }
          - name: "Offender Management & Probation"
            note: "Offender management runs under the Offender Management Act and MAPPA arrangements for high-risk offenders."
            operating_domains:
              - "Offender risk assessment & tiering"
              - "Licence-condition monitoring"
              - Supervision appointments
              - "Breach & recall decisions"
              - "Electronic-tag compliance"
              - Rehabilitation programme referrals
              - Reoffending tracking
            vocabulary:
              - { term: Probation Officer, runtime_type: Actor }
              - { term: Offender, runtime_type: Actor }
              - { term: Licence Condition, runtime_type: Object }
              - { term: Supervision Appointment, runtime_type: Event }
              - { term: Risk Tier, runtime_type: State }
              - { term: Recall Decision, runtime_type: Decision }
              - { term: Supervision Plan, runtime_type: Workflow }
              - { term: Breach of Licence, runtime_type: Event }
              - { term: "Compliant / Non-Compliant", runtime_type: State }
              - { term: Tag Data Log, runtime_type: Artefact }
              - { term: Assessment Report, runtime_type: Artefact }
              - { term: Recalled to Custody, runtime_type: Outcome }
              - { term: Sentence Completed, runtime_type: Outcome }
              - { term: Reoffending Rate, runtime_type: Learning }
      - name: "n-intelligenceOS"
        buyer: "Head of Intelligence / Director of Analysis in national-security agencies, defence, corporate-intelligence units and OSINT firms, funded for the intelligence cycle itself."
        os_test: "Distinct buyer (intelligence director, not a SOC or investigation lead), distinct state model (requirements → collection → analysis → dissemination), distinct vocabulary (RFI, source grading, ICD-203 confidence, all-source) and repeatable bodies (agencies, threat-intel firms) — the intelligence cycle is its own backbone."
        sectors:
          - name: "Requirements & Collection Management"
            operating_domains:
              - "Intelligence-requirement intake (RFIs)"
              - "Collection-plan tasking"
              - "Source & sensor tasking"
              - "Priority & gap tracking"
              - "Collection-asset deconfliction"
              - Feedback to collectors
              - "Requirement-satisfaction tracking"
            vocabulary:
              - { term: Collection Manager, runtime_type: Actor }
              - { term: Requirement (RFI), runtime_type: Object }
              - { term: Collection Plan, runtime_type: Object }
              - { term: Tasking Issued, runtime_type: Event }
              - { term: Priority Level, runtime_type: State }
              - { term: Tasking Decision, runtime_type: Decision }
              - { term: Tasking Workflow, runtime_type: Workflow }
              - { term: Collection Gap, runtime_type: State }
              - { term: Tasking Order, runtime_type: Artefact }
              - { term: Asset / Sensor, runtime_type: Object }
              - { term: Requirement Satisfied, runtime_type: Outcome }
              - { term: Collection Received, runtime_type: Event }
              - { term: Collection Yield, runtime_type: Learning }
          - name: "OSINT & Open-Source Collection"
            note: "OSINT on individuals engages GDPR/data-protection and (for public bodies) RIPA/IPA authorisation thresholds."
            operating_domains:
              - "Source monitoring & feeds"
              - "Entity & alias resolution"
              - "Geolocation & media verification"
              - "Network & link discovery"
              - "Translation & vetting"
              - "Persona & sock-puppet management"
              - Source reliability grading
            vocabulary:
              - { term: OSINT Analyst, runtime_type: Actor }
              - { term: Source, runtime_type: Object }
              - { term: Entity / Alias, runtime_type: Object }
              - { term: Collection Hit, runtime_type: Event }
              - { term: Source Reliability, runtime_type: State }
              - { term: Verify / Discard, runtime_type: Decision }
              - { term: Verification Workflow, runtime_type: Workflow }
              - { term: Research Persona, runtime_type: Object }
              - { term: Geolocation Pinned, runtime_type: Event }
              - { term: Source Dossier, runtime_type: Artefact }
              - { term: Entity Resolved, runtime_type: Outcome }
              - { term: Corroborated / Uncorroborated, runtime_type: State }
              - { term: Corroboration Rate, runtime_type: Learning }
          - name: "All-Source Analysis & Assessment"
            operating_domains:
              - "Multi-source fusion"
              - "Hypothesis & ACH structuring"
              - "Confidence & probability calibration"
              - "Link & network charting"
              - "Pattern-of-life analysis"
              - "Analytic-tradecraft review"
              - "Estimate & assessment authoring"
            vocabulary:
              - { term: "All-Source Analyst", runtime_type: Actor }
              - { term: Report / Reporting, runtime_type: Object }
              - { term: Hypothesis, runtime_type: Object }
              - { term: Fusion Event, runtime_type: Event }
              - { term: Confidence Level, runtime_type: State }
              - { term: Analytic Judgement, runtime_type: Decision }
              - { term: Analysis Workflow, runtime_type: Workflow }
              - { term: Link Chart, runtime_type: Artefact }
              - { term: Intelligence Assessment, runtime_type: Artefact }
              - { term: Pattern Identified, runtime_type: Event }
              - { term: Assessment Published, runtime_type: Outcome }
              - { term: Key Judgement, runtime_type: Outcome }
              - { term: Forecast Accuracy, runtime_type: Learning }
          - name: "HUMINT & Source Handling"
            note: "Covert human intelligence sources are regulated under RIPA/IPA Part II with formal authorisation, oversight by IPCO, and the CHIS code of practice."
            operating_domains:
              - "Source recruitment & vetting"
              - "Tasking & meeting management"
              - "Reporting & debrief capture"
              - "Source-reliability grading"
              - "Welfare & risk management"
              - "Payment & reward tracking"
              - Source deconfliction
            vocabulary:
              - { term: Source Handler, runtime_type: Actor }
              - { term: Human Source (CHIS), runtime_type: Actor }
              - { term: Tasking, runtime_type: Object }
              - { term: Meeting / Debrief, runtime_type: Event }
              - { term: Source Grading, runtime_type: State }
              - { term: Tasking Decision, runtime_type: Decision }
              - { term: Handling Workflow, runtime_type: Workflow }
              - { term: Contact Report, runtime_type: Artefact }
              - { term: Source Active / Dormant, runtime_type: State }
              - { term: Intelligence Reported, runtime_type: Event }
              - { term: Source Authorised, runtime_type: Outcome }
              - { term: Reward Payment, runtime_type: Object }
              - { term: Source Reliability Trend, runtime_type: Learning }
          - name: "Geospatial & Imagery Intelligence (GEOINT)"
            operating_domains:
              - "Imagery tasking & acquisition"
              - "Image exploitation & annotation"
              - Change detection over time
              - "Object & facility identification"
              - "Map & overlay production"
              - "Coordinate & target packs"
              - "Confidence-graded reporting"
            vocabulary:
              - { term: Imagery Analyst, runtime_type: Actor }
              - { term: Image / Scene, runtime_type: Object }
              - { term: Area of Interest, runtime_type: Object }
              - { term: Image Acquired, runtime_type: Event }
              - { term: Exploitation State, runtime_type: State }
              - { term: Identification Call, runtime_type: Decision }
              - { term: Exploitation Workflow, runtime_type: Workflow }
              - { term: Annotated Imagery, runtime_type: Artefact }
              - { term: Change Detected, runtime_type: Event }
              - { term: Target Pack, runtime_type: Artefact }
              - { term: Facility Identified, runtime_type: Outcome }
              - { term: Confidence Rating, runtime_type: State }
              - { term: Exploitation Throughput, runtime_type: Learning }
          - name: "Dissemination & Briefing"
            note: "Dissemination of classified material is governed by national security classification policy and need-to-know handling caveats."
            operating_domains:
              - "Product packaging & classification"
              - "Distribution-list & tearline control"
              - "Briefing-pack assembly"
              - "Customer-feedback capture"
              - "Release & downgrade decisions"
              - Audit of who saw what
              - "Product-impact tracking"
            vocabulary:
              - { term: Intelligence Officer, runtime_type: Actor }
              - { term: Intelligence Product, runtime_type: Object }
              - { term: Customer / Consumer, runtime_type: Actor }
              - { term: Product Released, runtime_type: Event }
              - { term: Classification / Handling, runtime_type: State }
              - { term: Release Decision, runtime_type: Decision }
              - { term: Dissemination Workflow, runtime_type: Workflow }
              - { term: Briefing Pack, runtime_type: Artefact }
              - { term: Tearline, runtime_type: Artefact }
              - { term: Consumer Feedback, runtime_type: Event }
              - { term: Product Actioned, runtime_type: Outcome }
              - { term: Read Receipt, runtime_type: State }
              - { term: Customer Satisfaction, runtime_type: Learning }
      - name: "n-riskOS"
        buyer: "Chief Risk Officer / Head of Enterprise Risk & Resilience who owns the risk register, board risk reporting, and business-continuity budgets."
        os_test: "Distinct buyer (CRO, governance not operations), distinct state model (risks → controls → appetite → treatment over a register), distinct vocabulary (inherent/residual risk, appetite, KRI, BIA) and repeatable companies (every regulated enterprise's risk function) — a governance OS, not an incident-response one."
        sectors:
          - name: "Enterprise & Operational Risk"
            note: "Operational-risk management is mandated for regulated firms under Basel/PRA operational-risk and SMCR accountability rules."
            operating_domains:
              - "Risk-register maintenance"
              - Inherent vs residual scoring
              - "Control mapping & effectiveness"
              - "Risk-appetite thresholds"
              - "Risk-event & loss capture"
              - "Treatment & action plans"
              - "Board & committee reporting"
            vocabulary:
              - { term: Risk Owner, runtime_type: Actor }
              - { term: Risk, runtime_type: Object }
              - { term: Control, runtime_type: Object }
              - { term: Risk Event / Loss, runtime_type: Event }
              - { term: Inherent / Residual Rating, runtime_type: State }
              - { term: Treatment Decision, runtime_type: Decision }
              - { term: Risk Assessment Cycle, runtime_type: Workflow }
              - { term: Risk Register, runtime_type: Artefact }
              - { term: Within / Outside Appetite, runtime_type: State }
              - { term: Mitigation Action, runtime_type: Object }
              - { term: Risk Mitigated, runtime_type: Outcome }
              - { term: Key Risk Indicator (KRI), runtime_type: Learning }
              - { term: Board Risk Report, runtime_type: Artefact }
              - { term: Loss Event Recorded, runtime_type: Event }
          - name: "Business Continuity & Resilience"
            note: "Operational resilience and impact-tolerance setting are mandated for financial firms (PRA/FCA, DORA) and follow ISO 22301."
            operating_domains:
              - "Business-impact analysis"
              - "Critical-process & dependency mapping"
              - "Recovery-time/point objectives"
              - "Continuity-plan maintenance"
              - "Exercise & test scheduling"
              - "Disruption invocation & response"
              - "Lessons-learned from tests"
            vocabulary:
              - { term: Continuity Manager, runtime_type: Actor }
              - { term: Critical Process, runtime_type: Object }
              - { term: Dependency, runtime_type: Object }
              - { term: Disruption Event, runtime_type: Event }
              - { term: Process Status (Up/Down), runtime_type: State }
              - { term: Invoke Plan Decision, runtime_type: Decision }
              - { term: Continuity Exercise, runtime_type: Workflow }
              - { term: Continuity Plan, runtime_type: Artefact }
              - { term: Recovery Time Objective, runtime_type: State }
              - { term: Plan Invoked, runtime_type: Event }
              - { term: Service Recovered, runtime_type: Outcome }
              - { term: Test Report, runtime_type: Artefact }
              - { term: Lessons Learned, runtime_type: Learning }
          - name: "Third-Party & Supply-Chain Risk"
            note: "Third-party oversight is regulated for financial firms under PRA SS2/21, DORA ICT-provider rules and outsourcing guidance."
            operating_domains:
              - "Vendor onboarding & due diligence"
              - "Inherent-risk tiering"
              - "Security & financial assessments"
              - "Concentration & nth-party mapping"
              - "Contract & SLA risk clauses"
              - "Ongoing monitoring & rescoring"
              - "Offboarding & exit plans"
            vocabulary:
              - { term: Vendor Manager, runtime_type: Actor }
              - { term: Third Party / Supplier, runtime_type: Actor }
              - { term: Assessment Questionnaire, runtime_type: Object }
              - { term: Onboarding Request, runtime_type: Event }
              - { term: Risk Tier, runtime_type: State }
              - { term: Approve / Reject Vendor, runtime_type: Decision }
              - { term: "Due-Diligence Workflow", runtime_type: Workflow }
              - { term: Assessment Report, runtime_type: Artefact }
              - { term: Approved / Restricted, runtime_type: State }
              - { term: Finding Raised, runtime_type: Event }
              - { term: Vendor Onboarded, runtime_type: Outcome }
              - { term: Concentration Risk, runtime_type: Object }
              - { term: Portfolio Risk Score, runtime_type: Learning }
          - name: "Credit & Counterparty Risk"
            note: "Credit-risk measurement and capital are governed by Basel III/CRR, IFRS 9 impairment and PRA model approval."
            operating_domains:
              - "Counterparty credit-limit setting"
              - "Exposure & utilisation monitoring"
              - "Rating & scorecard reviews"
              - "Watchlist & early-warning signals"
              - "Collateral & margin tracking"
              - "Default & impairment decisions"
              - Portfolio concentration reporting
            vocabulary:
              - { term: Credit Officer, runtime_type: Actor }
              - { term: Counterparty, runtime_type: Actor }
              - { term: Credit Limit, runtime_type: Object }
              - { term: Limit Breach, runtime_type: Event }
              - { term: Credit Rating, runtime_type: State }
              - { term: Approve / Decline Facility, runtime_type: Decision }
              - { term: Credit Review, runtime_type: Workflow }
              - { term: Watchlist Entry, runtime_type: Artefact }
              - { term: Exposure Utilisation, runtime_type: State }
              - { term: Default Event, runtime_type: Event }
              - { term: Facility Approved, runtime_type: Outcome }
              - { term: Impairment Booked, runtime_type: Outcome }
              - { term: Expected Loss, runtime_type: Learning }
          - name: Insurance Underwriting Risk
            note: "Underwriting is regulated under FCA/PRA and (for the London Market) Lloyd's minimum standards and conduct rules."
            operating_domains:
              - "Submission intake & triage"
              - "Risk appraisal & exposure rating"
              - "Pricing & quote generation"
              - "Referral & authority limits"
              - "Treaty & facultative reinsurance"
              - "Accumulation & catastrophe modelling"
              - Bind / decline decisions
            vocabulary:
              - { term: Underwriter, runtime_type: Actor }
              - { term: Risk / Submission, runtime_type: Object }
              - { term: Exposure, runtime_type: Object }
              - { term: Submission Received, runtime_type: Event }
              - { term: Pricing State, runtime_type: State }
              - { term: Bind / Decline / Refer, runtime_type: Decision }
              - { term: Underwriting Workflow, runtime_type: Workflow }
              - { term: Quote, runtime_type: Artefact }
              - { term: Within Authority, runtime_type: State }
              - { term: Referral Raised, runtime_type: Event }
              - { term: Risk Bound, runtime_type: Outcome }
              - { term: Policy Issued, runtime_type: Artefact }
              - { term: Loss Ratio, runtime_type: Learning }
          - name: "Model Risk & Validation"
            note: "Model risk is regulated under SR 11-7 (US), PRA SS1/23 model-risk principles, and equivalent supervisory expectations."
            operating_domains:
              - "Model inventory & tiering"
              - "Validation & challenge testing"
              - "Performance & drift monitoring"
              - "Assumption & limitation tracking"
              - "Findings & remediation"
              - "Approval & sign-off gates"
              - Periodic revalidation scheduling
            vocabulary:
              - { term: Model Validator, runtime_type: Actor }
              - { term: Model, runtime_type: Object }
              - { term: Validation Test, runtime_type: Object }
              - { term: Validation Run, runtime_type: Event }
              - { term: Model Status (Approved/Restricted), runtime_type: State }
              - { term: Approval Decision, runtime_type: Decision }
              - { term: Validation Workflow, runtime_type: Workflow }
              - { term: Validation Report, runtime_type: Artefact }
              - { term: Drift Detected, runtime_type: Event }
              - { term: Finding / Limitation, runtime_type: Artefact }
              - { term: Model Approved, runtime_type: Outcome }
              - { term: Model Decommissioned, runtime_type: Outcome }
              - { term: Performance Stability, runtime_type: Learning }
      - name: "n-investigationOS"
        buyer: "Head of Corporate Investigations / Litigation & eDiscovery lead at law firms, corporates and investigation agencies funded per-matter or by a standing investigations team."
        os_test: "Distinct buyer (investigations/legal lead, not fraud-scoring or SOC), distinct state model (matters → evidence → review → findings), distinct vocabulary (custodian, hold, privilege, due-diligence report) and repeatable firms (Kroll, K2, eDiscovery vendors) — case-and-evidence centric, separate from real-time fraud or cyber."
        sectors:
          - name: "Corporate & Internal Investigations"
            note: "Internal investigations may engage employment law, legal professional privilege, and whistleblowing protections (PIDA)."
            operating_domains:
              - "Allegation intake & triage"
              - "Investigation-plan scoping"
              - "Interview scheduling & notes"
              - "Evidence collection & custody"
              - "Privilege & confidentiality handling"
              - "Findings & recommendation drafting"
              - "Remediation & referral decisions"
            vocabulary:
              - { term: Investigator, runtime_type: Actor }
              - { term: Subject, runtime_type: Actor }
              - { term: Matter / Case, runtime_type: Object }
              - { term: Allegation Received, runtime_type: Event }
              - { term: Case Status, runtime_type: State }
              - { term: Substantiation Decision, runtime_type: Decision }
              - { term: Investigation Plan, runtime_type: Workflow }
              - { term: Interview Note, runtime_type: Artefact }
              - { term: Evidence Item, runtime_type: Object }
              - { term: Interview Conducted, runtime_type: Event }
              - { term: Substantiated / Unfounded, runtime_type: Outcome }
              - { term: Investigation Report, runtime_type: Artefact }
              - { term: Referral Made, runtime_type: Outcome }
              - { term: Cycle Time, runtime_type: Learning }
          - name: "eDiscovery & Litigation Support"
            note: eDiscovery follows court disclosure rules (CPR PD 51U / FRCP 26) and preservation obligations; spoliation carries sanctions.
            operating_domains:
              - "Legal-hold & custodian management"
              - "Data collection & processing"
              - "Document review & coding"
              - "Privilege & responsiveness review"
              - "Technology-assisted review (TAR)"
              - "Production & load-file export"
              - "Review-rate & QC metrics"
            vocabulary:
              - { term: Reviewer, runtime_type: Actor }
              - { term: Custodian, runtime_type: Actor }
              - { term: Document, runtime_type: Object }
              - { term: Legal Hold Issued, runtime_type: Event }
              - { term: Review State (Coded/Uncoded), runtime_type: State }
              - { term: Responsiveness Call, runtime_type: Decision }
              - { term: Review Workflow, runtime_type: Workflow }
              - { term: Privilege Log, runtime_type: Artefact }
              - { term: Privileged / Responsive, runtime_type: State }
              - { term: Document Produced, runtime_type: Event }
              - { term: Production Set, runtime_type: Artefact }
              - { term: Production Delivered, runtime_type: Outcome }
              - { term: Review Throughput, runtime_type: Learning }
          - name: "Due Diligence & Background Screening"
            note: "Pre-employment screening and consumer-data checks are governed by GDPR/DPA, FCRA (US) and BS 7858 vetting standards."
            operating_domains:
              - "Subject scoping & screening tiers"
              - "Identity & credential verification"
              - "Adverse-media & sanctions checks"
              - "Litigation & corporate-record search"
              - "Source vetting & corroboration"
              - "Red-flag adjudication"
              - "Report writing & sign-off"
            vocabulary:
              - { term: Analyst, runtime_type: Actor }
              - { term: Subject of Enquiry, runtime_type: Actor }
              - { term: Screening Check, runtime_type: Object }
              - { term: Search Run, runtime_type: Event }
              - { term: Clearance Status, runtime_type: State }
              - { term: Adjudication Decision, runtime_type: Decision }
              - { term: Diligence Workflow, runtime_type: Workflow }
              - { term: Red Flag, runtime_type: Object }
              - { term: Adverse Media Hit, runtime_type: Event }
              - { term: "Due-Diligence Report", runtime_type: Artefact }
              - { term: Cleared / Escalated, runtime_type: Outcome }
              - { term: Sanctions Match, runtime_type: Event }
              - { term: Turnaround Time, runtime_type: Learning }
          - name: "Asset Tracing & Recovery"
            note: "Asset tracing and freezing engage civil-recovery law (e.g. POCA, freezing injunctions) and cross-jurisdiction disclosure."
            operating_domains:
              - "Asset & ownership mapping"
              - "Corporate-structure unravelling"
              - "Beneficial-owner identification"
              - "Cross-border records search"
              - "Freezing & preservation actions"
              - "Enforcement & recovery strategy"
              - "Recovered-value tracking"
            vocabulary:
              - { term: Tracing Investigator, runtime_type: Actor }
              - { term: Target Entity, runtime_type: Actor }
              - { term: Asset, runtime_type: Object }
              - { term: Ownership Link Found, runtime_type: Event }
              - { term: Asset Status (Frozen/Free), runtime_type: State }
              - { term: Pursue / Abandon Decision, runtime_type: Decision }
              - { term: Tracing Workflow, runtime_type: Workflow }
              - { term: Asset Map / Chart, runtime_type: Artefact }
              - { term: Freezing Order Obtained, runtime_type: Event }
              - { term: Beneficial Owner Identified, runtime_type: Outcome }
              - { term: Asset Recovered, runtime_type: Outcome }
              - { term: Recovery Memo, runtime_type: Artefact }
              - { term: Recovery Rate, runtime_type: Learning }
          - name: "Digital Forensics & eCrime"
            note: Digital forensics must follow ACPO/ISO 17025 principles for evidential integrity and court admissibility.
            operating_domains:
              - "Device seizure & imaging"
              - "Chain-of-custody logging"
              - "Artefact & timeline extraction"
              - "Deleted-data recovery"
              - "Malware & log analysis"
              - "Forensic-report production"
              - "Expert-witness preparation"
            vocabulary:
              - { term: Forensic Examiner, runtime_type: Actor }
              - { term: Exhibit Device, runtime_type: Object }
              - { term: Forensic Image, runtime_type: Object }
              - { term: Acquisition Performed, runtime_type: Event }
              - { term: Chain of Custody, runtime_type: State }
              - { term: Analysis Decision, runtime_type: Decision }
              - { term: Examination Workflow, runtime_type: Workflow }
              - { term: Recovered Artefact, runtime_type: Artefact }
              - { term: Sealed / Examined, runtime_type: State }
              - { term: Timeline Reconstructed, runtime_type: Event }
              - { term: Forensic Report, runtime_type: Artefact }
              - { term: Evidence Admissible, runtime_type: Outcome }
              - { term: Examination Throughput, runtime_type: Learning }
          - name: "Surveillance & Field Investigation"
            note: Directed/covert surveillance by public bodies requires RIPA authorisation; private surveillance must comply with GDPR/DPA and ICO guidance.
            operating_domains:
              - "Tasking & operation planning"
              - "Subject & location profiling"
              - "Static & mobile surveillance logs"
              - Covertly captured media handling
              - "Observation-evidence recording"
              - "Authorisation & proportionality review"
              - "Surveillance-report compilation"
            vocabulary:
              - { term: Field Operative, runtime_type: Actor }
              - { term: Subject, runtime_type: Actor }
              - { term: Operation / Tasking, runtime_type: Object }
              - { term: Observation Logged, runtime_type: Event }
              - { term: Operation Status, runtime_type: State }
              - { term: "Deploy / Stand-Down", runtime_type: Decision }
              - { term: Surveillance Workflow, runtime_type: Workflow }
              - { term: Surveillance Log, runtime_type: Artefact }
              - { term: Captured Media, runtime_type: Object }
              - { term: Subject Sighted, runtime_type: Event }
              - { term: Authorisation Granted, runtime_type: Outcome }
              - { term: Surveillance Report, runtime_type: Artefact }
              - { term: Objective Achieved, runtime_type: Outcome }
              - { term: Hours on Target, runtime_type: Learning }
  - name: "Non-Profit & Membership"
    os:
      - name: "n-charityOS"
        buyer: "Charity CEO / Director of Finance & Operations at a registered charity or non-profit"
        os_test: "Distinct buyer (charity trustees/exec), own budget line, regulator-shaped state model (restricted vs unrestricted funds, grant conditions, Gift Aid), and vocabulary no commercial CRM uses — passes the OS test against fundraising and membership tooling."
        sectors:
          - name: "Grant-Making Foundations"
            note: "Regulated by the Charity Commission; grant due diligence must meet anti-terrorism/anti-money-laundering and safeguarding duties."
            operating_domains:
              - open and rolling funding calls
              - applicant pipeline and eligibility screening
              - assessment panels and scoring
              - award letters and grant agreements
              - payment schedules and tranche releases
              - grantee monitoring reports and milestones
              - "endowment and spend-down policy"
              - "due-diligence and safeguarding checks"
            vocabulary:
              - { term: Applicant organisation, runtime_type: Actor }
              - { term: Grant programme, runtime_type: Object }
              - { term: Application, runtime_type: Object }
              - { term: Eligibility check, runtime_type: Decision }
              - { term: Assessment panel sitting, runtime_type: Event }
              - { term: Funding decision, runtime_type: Decision }
              - { term: Award letter, runtime_type: Artefact }
              - { term: Grant agreement, runtime_type: Artefact }
              - { term: In progress, runtime_type: State }
              - { term: Awarded, runtime_type: State }
              - { term: Payment tranche released, runtime_type: Event }
              - { term: Monitoring report, runtime_type: Artefact }
              - { term: Reporting cycle workflow, runtime_type: Workflow }
              - { term: Outcomes achieved by grantee, runtime_type: Outcome }
              - { term: "Cost-per-outcome learning", runtime_type: Learning }
          - name: "Service-Delivery Charities (frontline care)"
            note: "Handles special-category personal data and safeguarding; bound by GDPR, DBS checks, and CQC/Ofsted regimes for regulated care or education services."
            operating_domains:
              - service user referrals and intake
              - case files and support plans
              - session and appointment scheduling
              - "key-worker caseloads"
              - safeguarding incidents and escalation
              - service contracts and outcomes frameworks
              - frontline staff and volunteer rotas
              - "outcome-star and wellbeing assessments"
            vocabulary:
              - { term: Service user / beneficiary, runtime_type: Actor }
              - { term: Key worker, runtime_type: Actor }
              - { term: Referral, runtime_type: Object }
              - { term: Case file, runtime_type: Object }
              - { term: Support plan, runtime_type: Artefact }
              - { term: Intake assessment, runtime_type: Event }
              - { term: Eligibility / consent decision, runtime_type: Decision }
              - { term: On the waiting list, runtime_type: State }
              - { term: Active case, runtime_type: State }
              - { term: Safeguarding incident, runtime_type: Event }
              - { term: Escalation to designated lead, runtime_type: Decision }
              - { term: Support session delivered, runtime_type: Event }
              - { term: Case closure workflow, runtime_type: Workflow }
              - { term: Outcome Star progress, runtime_type: Outcome }
              - { term: "Distance-travelled learning", runtime_type: Learning }
          - name: "International NGOs & Humanitarian Aid"
            note: "Subject to donor compliance (FCDO/USAID/ECHO), sanctions screening, and counter-terrorism financing rules on fund transfers."
            operating_domains:
              - country programmes and field offices
              - humanitarian appeals and emergency responses
              - restricted donor grants and compliance
              - beneficiary registration and distribution
              - "in-kind aid and supply logistics"
              - "partner sub-grants and capacity building"
              - field safety and security incidents
              - donor reporting against logframes
            vocabulary:
              - { term: Beneficiary household, runtime_type: Actor }
              - { term: Implementing partner, runtime_type: Actor }
              - { term: Country programme, runtime_type: Object }
              - { term: Restricted donor grant, runtime_type: Object }
              - { term: Emergency appeal launched, runtime_type: Event }
              - { term: "Go / no-go response decision", runtime_type: Decision }
              - { term: Distribution, runtime_type: Event }
              - { term: Logframe / results framework, runtime_type: Artefact }
              - { term: Mobilising, runtime_type: State }
              - { term: "Grant under-spend flagged", runtime_type: State }
              - { term: Security incident report, runtime_type: Artefact }
              - { term: "Sub-grant disbursement workflow", runtime_type: Workflow }
              - { term: Beneficiaries reached, runtime_type: Outcome }
              - { term: "Cost-efficiency learning", runtime_type: Learning }
          - name: "Faith & Religious Organisations"
            note: Religious charities sit under Charity Commission registration and statutory safeguarding duties for children and vulnerable adults.
            operating_domains:
              - congregation and membership rolls
              - weekly services and liturgical calendar
              - "giving, tithes and planned offerings"
              - pastoral care and prayer requests
              - "rites of passage (baptisms, weddings, funerals)"
              - "ministries, small groups and rotas"
              - building usage and facilities hire
              - safeguarding and pastoral incidents
            vocabulary:
              - { term: Congregant / member, runtime_type: Actor }
              - { term: Minister / clergy, runtime_type: Actor }
              - { term: Membership roll, runtime_type: Object }
              - { term: Service / liturgy, runtime_type: Object }
              - { term: Tithe / offering, runtime_type: Object }
              - { term: Service held, runtime_type: Event }
              - { term: Rite of passage booked, runtime_type: Decision }
              - { term: In good standing, runtime_type: State }
              - { term: Pastoral visit, runtime_type: Event }
              - { term: Giving statement, runtime_type: Artefact }
              - { term: Rota / serving schedule, runtime_type: Artefact }
              - { term: Service planning workflow, runtime_type: Workflow }
              - { term: Safeguarding concern raised, runtime_type: Event }
              - { term: Discipleship / spiritual growth, runtime_type: Outcome }
              - { term: "Attendance & giving trend learning", runtime_type: Learning }
          - name: "Community & Social Enterprises"
            note: "Community Interest Companies and asset-locked enterprises are regulated by the CIC Regulator alongside trading-subsidiary tax rules."
            operating_domains:
              - community projects and activity programmes
              - local membership and participation
              - "trading income and social-enterprise services"
              - "community shares and asset-locked governance"
              - venue and facilities management
              - small grants and crowdfunding
              - social value and impact tracking
              - local partnerships and referrals
            vocabulary:
              - { term: Community member, runtime_type: Actor }
              - { term: Project lead, runtime_type: Actor }
              - { term: Community project, runtime_type: Object }
              - { term: Activity programme, runtime_type: Object }
              - { term: Trading transaction, runtime_type: Object }
              - { term: Activity session run, runtime_type: Event }
              - { term: "Project go-ahead decision", runtime_type: Decision }
              - { term: Pilot stage, runtime_type: State }
              - { term: Funded, runtime_type: State }
              - { term: Community share offer, runtime_type: Artefact }
              - { term: Impact report, runtime_type: Artefact }
              - { term: Programme delivery workflow, runtime_type: Workflow }
              - { term: Social value generated, runtime_type: Outcome }
              - { term: "Participation-rate learning", runtime_type: Learning }
          - name: "Grant-Seeking & Trust Fundraising Teams"
            operating_domains:
              - prospect research and funder pipelines
              - bid and proposal development
              - deadline calendar and submissions
              - restricted income forecasting
              - funder relationship cultivation
              - grant claims and acquittals
              - compliance with funder conditions
              - win/loss tracking and feedback
            vocabulary:
              - { term: Funder / trust, runtime_type: Actor }
              - { term: Bid writer, runtime_type: Actor }
              - { term: Funding prospect, runtime_type: Object }
              - { term: Bid / proposal, runtime_type: Object }
              - { term: Submission deadline, runtime_type: Event }
              - { term: Bid submitted, runtime_type: Event }
              - { term: "Apply / decline-to-apply decision", runtime_type: Decision }
              - { term: In cultivation, runtime_type: State }
              - { term: Awarded / declined, runtime_type: State }
              - { term: Acquittal report, runtime_type: Artefact }
              - { term: Funder feedback note, runtime_type: Artefact }
              - { term: "Pipeline-to-claim workflow", runtime_type: Workflow }
              - { term: Restricted income secured, runtime_type: Outcome }
              - { term: "Bid win-rate learning", runtime_type: Learning }
      - name: "n-membershipOS"
        buyer: "Head of Membership / Membership Director at a member-based body (society, club, professional body)"
        os_test: "Buyer owns a dedicated membership P&L; the core state model is the recurring member lifecycle (join→renew→lapse→win-back) with tiered entitlements and dues — a distinctive runtime no fundraising or association governance tool replicates."
        sectors:
          - name: "Professional Bodies & Institutes"
            note: Chartered bodies and statutory regulators (e.g. healthcare/legal/engineering registers) operate under Privy Council charters or statutory regulation of the protected register.
            operating_domains:
              - membership grades and progression
              - qualifications and chartered status
              - CPD logging and audit
              - annual subscriptions and dues
              - registers and designatory letters
              - "events, branches and special-interest groups"
              - "code-of-conduct and disciplinary cases"
              - member benefits and entitlements
            vocabulary:
              - { term: Member, runtime_type: Actor }
              - { term: Assessor, runtime_type: Actor }
              - { term: Membership grade, runtime_type: Object }
              - { term: Subscription, runtime_type: Object }
              - { term: CPD record, runtime_type: Object }
              - { term: Grade upgrade application, runtime_type: Event }
              - { term: "Chartered-status decision", runtime_type: Decision }
              - { term: In good standing, runtime_type: State }
              - { term: Lapsed, runtime_type: State }
              - { term: Membership certificate, runtime_type: Artefact }
              - { term: Professional register entry, runtime_type: Artefact }
              - { term: Renewal workflow, runtime_type: Workflow }
              - { term: Disciplinary case raised, runtime_type: Event }
              - { term: Continued competence, runtime_type: Outcome }
              - { term: "Retention-rate learning", runtime_type: Learning }
          - name: "Trade Associations & Industry Bodies"
            note: "Accreditation and standards schemes may carry consumer-protection or competition-law obligations on information sharing between members."
            operating_domains:
              - corporate membership and seats
              - sector advocacy and consultations
              - "standards, codes and accreditation"
              - member committees and working groups
              - industry events and conferences
              - market intelligence and benchmarking
              - member directory and kitemarks
              - tiered corporate dues
            vocabulary:
              - { term: Member company, runtime_type: Actor }
              - { term: Primary contact, runtime_type: Actor }
              - { term: Corporate membership, runtime_type: Object }
              - { term: Accreditation scheme, runtime_type: Object }
              - { term: Consultation response, runtime_type: Artefact }
              - { term: Accreditation audit, runtime_type: Event }
              - { term: Accreditation pass/fail decision, runtime_type: Decision }
              - { term: Accredited, runtime_type: State }
              - { term: Suspended, runtime_type: State }
              - { term: Member kitemark / badge, runtime_type: Artefact }
              - { term: Working group convened, runtime_type: Event }
              - { term: Accreditation renewal workflow, runtime_type: Workflow }
              - { term: Policy win for sector, runtime_type: Outcome }
              - { term: "Member-value benchmarking", runtime_type: Learning }
          - name: "Membership Clubs & Societies"
            note: "Members' clubs serving alcohol require a club premises certificate under the Licensing Act."
            operating_domains:
              - membership categories and waiting lists
              - joining and proposer/seconder process
              - club facilities and bookings
              - member account and bar/dining tabs
              - events and social calendar
              - house rules and member conduct
              - annual dues and joining fees
              - guest passes and reciprocal clubs
            vocabulary:
              - { term: Club member, runtime_type: Actor }
              - { term: Proposer, runtime_type: Actor }
              - { term: Membership category, runtime_type: Object }
              - { term: Member account / tab, runtime_type: Object }
              - { term: Application proposed, runtime_type: Event }
              - { term: Committee admission decision, runtime_type: Decision }
              - { term: On the waiting list, runtime_type: State }
              - { term: Active member, runtime_type: State }
              - { term: Facility booking made, runtime_type: Event }
              - { term: Membership card, runtime_type: Artefact }
              - { term: Statement of account, runtime_type: Artefact }
              - { term: Joining workflow, runtime_type: Workflow }
              - { term: Conduct breach logged, runtime_type: Event }
              - { term: Member satisfaction, runtime_type: Outcome }
              - { term: "Lapse-risk learning", runtime_type: Learning }
          - name: "Subscription Communities & Memberships (digital)"
            operating_domains:
              - paid tiers and entitlements
              - content gating and access control
              - recurring billing and dunning
              - community spaces and forums
              - onboarding and activation flows
              - "perks, discounts and partner offers"
              - "churn and win-back campaigns"
              - member engagement scoring
            vocabulary:
              - { term: Subscriber, runtime_type: Actor }
              - { term: Community manager, runtime_type: Actor }
              - { term: Membership tier, runtime_type: Object }
              - { term: Entitlement, runtime_type: Object }
              - { term: Recurring charge attempted, runtime_type: Event }
              - { term: Upgrade / downgrade decision, runtime_type: Decision }
              - { term: Trialing, runtime_type: State }
              - { term: Past due / dunning, runtime_type: State }
              - { term: Access pass / licence, runtime_type: Artefact }
              - { term: Onboarding flow completed, runtime_type: Event }
              - { term: "Win-back workflow", runtime_type: Workflow }
              - { term: Engagement score, runtime_type: Outcome }
              - { term: "Churn-driver learning", runtime_type: Learning }
              - { term: Lifetime value, runtime_type: Outcome }
          - name: "Alumni & Affinity Networks"
            operating_domains:
              - alumni records and graduation cohorts
              - chapters and regional groups
              - reunions and signature events
              - mentoring and career networks
              - affinity giving and class campaigns
              - "lifelong-learning offers"
              - "wall-of-fame and recognition"
              - engagement segmentation
            vocabulary:
              - { term: Alumnus / alumna, runtime_type: Actor }
              - { term: Chapter lead, runtime_type: Actor }
              - { term: Alumni record, runtime_type: Object }
              - { term: Graduation cohort, runtime_type: Object }
              - { term: Reunion held, runtime_type: Event }
              - { term: "Mentor-match decision", runtime_type: Decision }
              - { term: Engaged, runtime_type: State }
              - { term: Lost / no contact, runtime_type: State }
              - { term: Class gift appeal, runtime_type: Artefact }
              - { term: Mentoring match made, runtime_type: Event }
              - { term: "Re-engagement workflow", runtime_type: Workflow }
              - { term: Alumni engagement uplift, runtime_type: Outcome }
              - { term: "Affinity-giving learning", runtime_type: Learning }
              - { term: Network directory, runtime_type: Artefact }
          - name: "Unions & Worker Membership Bodies"
            note: "Trade unions are statutorily regulated by the Certification Officer; industrial-action ballots must meet legal thresholds and notice rules."
            operating_domains:
              - member recruitment and workplace branches
              - "dues and check-off payroll deduction"
              - casework and grievances
              - collective bargaining and ballots
              - reps and stewards network
              - legal support and representation
              - campaigns and industrial action
              - membership density tracking
            vocabulary:
              - { term: Union member, runtime_type: Actor }
              - { term: Workplace rep / steward, runtime_type: Actor }
              - { term: Branch, runtime_type: Object }
              - { term: Dues / subscription, runtime_type: Object }
              - { term: Casework / grievance, runtime_type: Object }
              - { term: "Industrial-action ballot held", runtime_type: Event }
              - { term: "Take-case decision", runtime_type: Decision }
              - { term: In dispute, runtime_type: State }
              - { term: In arrears, runtime_type: State }
              - { term: Recognition agreement, runtime_type: Artefact }
              - { term: Grievance hearing, runtime_type: Event }
              - { term: Bargaining round workflow, runtime_type: Workflow }
              - { term: Case outcome won, runtime_type: Outcome }
              - { term: "Membership-density learning", runtime_type: Learning }
      - name: "n-associationOS"
        buyer: "Company Secretary / Governance & Operations Lead at an association, federation or governing body"
        os_test: "The buyer is a governance owner, not a membership marketer; the runtime is built around constitutional state — committees, motions, votes, mandates and terms of office — a distinct model from membership lifecycle or fundraising."
        sectors:
          - name: "Sports Governing Bodies & Leagues"
            note: "Bound by anti-doping (WADA/UKAD), safeguarding in sport, and integrity/anti-corruption regulation; some hold statutory or public-funding (e.g. Sport England) duties."
            operating_domains:
              - affiliated clubs and registrations
              - player and official licensing
              - competition fixtures and results
              - discipline and integrity cases
              - talent pathways and squads
              - coaching qualifications and CPD
              - facilities and venue sanctioning
              - grants and funding distribution
            vocabulary:
              - { term: Affiliated club, runtime_type: Actor }
              - { term: Registered player, runtime_type: Actor }
              - { term: Competition, runtime_type: Object }
              - { term: Player registration, runtime_type: Object }
              - { term: Fixture played, runtime_type: Event }
              - { term: Eligibility ruling, runtime_type: Decision }
              - { term: Registered / cleared to play, runtime_type: State }
              - { term: Suspended, runtime_type: State }
              - { term: Disciplinary charge, runtime_type: Event }
              - { term: Match report, runtime_type: Artefact }
              - { term: Coaching licence, runtime_type: Artefact }
              - { term: Sanctioning workflow, runtime_type: Workflow }
              - { term: Participation growth, runtime_type: Outcome }
              - { term: "Pathway-conversion learning", runtime_type: Learning }
          - name: "Federations & Umbrella Bodies"
            operating_domains:
              - affiliated member organisations
              - national / regional / local structure
              - council and delegate representation
              - "shared policy and position-setting"
              - affiliation fees and quotas
              - "capacity-building and toolkits"
              - "sector-wide standards"
              - collective campaigns
            vocabulary:
              - { term: Affiliated organisation, runtime_type: Actor }
              - { term: Delegate, runtime_type: Actor }
              - { term: Affiliation, runtime_type: Object }
              - { term: Policy position, runtime_type: Object }
              - { term: Council meeting held, runtime_type: Event }
              - { term: "Position-adoption decision", runtime_type: Decision }
              - { term: Affiliated, runtime_type: State }
              - { term: Quota unmet, runtime_type: State }
              - { term: Joint statement, runtime_type: Artefact }
              - { term: Toolkit / guidance pack, runtime_type: Artefact }
              - { term: Affiliation renewal workflow, runtime_type: Workflow }
              - { term: Sector alignment achieved, runtime_type: Outcome }
              - { term: "Member-coverage learning", runtime_type: Learning }
              - { term: Delegate vote cast, runtime_type: Event }
          - name: "Boards & Governance (trustee/committee operations)"
            note: "Trustee duties, conflict-of-interest registers and statutory filings sit under Charity Commission and Companies House obligations."
            operating_domains:
              - board and committee structure
              - meeting agendas and board packs
              - "motions, resolutions and voting"
              - trustee terms and succession
              - registers of interest and conflicts
              - delegated authority and policies
              - minutes and action tracking
              - AGM and statutory filings
            vocabulary:
              - { term: Trustee / director, runtime_type: Actor }
              - { term: Company secretary, runtime_type: Actor }
              - { term: Committee, runtime_type: Object }
              - { term: Motion / resolution, runtime_type: Object }
              - { term: Board meeting convened, runtime_type: Event }
              - { term: Vote / resolution decision, runtime_type: Decision }
              - { term: Quorate, runtime_type: State }
              - { term: Conflict declared, runtime_type: State }
              - { term: Board pack, runtime_type: Artefact }
              - { term: Minutes, runtime_type: Artefact }
              - { term: Resolution carried, runtime_type: Event }
              - { term: AGM workflow, runtime_type: Workflow }
              - { term: Decision enacted, runtime_type: Outcome }
              - { term: "Governance-health learning", runtime_type: Learning }
          - name: "Standards & Certification Bodies"
            note: Certification bodies are themselves accredited (e.g. UKAS/ISO 17021) and must maintain impartiality and competence rules.
            operating_domains:
              - certification schemes and scopes
              - applicant assessment and audits
              - auditor competence and assignment
              - certificates and registers
              - "surveillance and re-certification"
              - "non-conformities and corrective actions"
              - scheme rules and impartiality
              - appeals and complaints
            vocabulary:
              - { term: Certified organisation, runtime_type: Actor }
              - { term: Lead auditor, runtime_type: Actor }
              - { term: Certification scheme, runtime_type: Object }
              - { term: Audit, runtime_type: Object }
              - { term: Audit conducted, runtime_type: Event }
              - { term: Certification decision, runtime_type: Decision }
              - { term: Certified, runtime_type: State }
              - { term: "Non-conformity open", runtime_type: State }
              - { term: Certificate, runtime_type: Artefact }
              - { term: Audit report, runtime_type: Artefact }
              - { term: Corrective action closed, runtime_type: Event }
              - { term: "Re-certification workflow", runtime_type: Workflow }
              - { term: Conformance assured, runtime_type: Outcome }
              - { term: "Non-conformity-trend learning", runtime_type: Learning }
          - name: "Self-Regulatory & Disciplinary Bodies"
            note: "Statutory regulators run fitness-to-practise/conduct proceedings under their governing legislation with rights of appeal."
            operating_domains:
              - registrant and licensee records
              - complaints intake and triage
              - investigations and case examiners
              - "fitness-to-practise / conduct hearings"
              - sanctions and undertakings
              - appeals and review panels
              - standards and code of conduct
              - publication of determinations
            vocabulary:
              - { term: Registrant, runtime_type: Actor }
              - { term: Case examiner, runtime_type: Actor }
              - { term: Complaint, runtime_type: Object }
              - { term: Investigation case, runtime_type: Object }
              - { term: Hearing held, runtime_type: Event }
              - { term: "Fitness-to-practise decision", runtime_type: Decision }
              - { term: Under investigation, runtime_type: State }
              - { term: Sanctioned / struck off, runtime_type: State }
              - { term: Determination / ruling, runtime_type: Artefact }
              - { term: Undertaking, runtime_type: Artefact }
              - { term: Sanction imposed, runtime_type: Event }
              - { term: Casework workflow, runtime_type: Workflow }
              - { term: Public protection upheld, runtime_type: Outcome }
              - { term: "Complaint-pattern learning", runtime_type: Learning }
      - name: "n-fundraisingOS"
        buyer: "Director of Fundraising / Development at a charity or cause-led organisation"
        os_test: "Owns the income-generation budget and targets; runtime is built around the donor journey and income pipeline (prospect→ask→gift→steward) with consent, Gift Aid and appeal attribution — distinct from grant assessment, governance or membership dues."
        sectors:
          - name: "Individual Giving & Direct Marketing"
            note: Regulated by the Fundraising Regulator and ICO; Gift Aid claims to HMRC and consent/PECR rules govern marketing contact.
            operating_domains:
              - supporter database and segmentation
              - "appeals and direct-mail campaigns"
              - regular giving and Direct Debits
              - donation pages and online forms
              - Gift Aid declarations and claims
              - consent and preference management
              - donor journeys and welcome series
              - attribution and campaign ROI
            vocabulary:
              - { term: Supporter / donor, runtime_type: Actor }
              - { term: Fundraiser, runtime_type: Actor }
              - { term: Appeal / campaign, runtime_type: Object }
              - { term: Donation, runtime_type: Object }
              - { term: Regular gift / Direct Debit, runtime_type: Object }
              - { term: Gift received, runtime_type: Event }
              - { term: "Ask-amount decision", runtime_type: Decision }
              - { term: Active donor, runtime_type: State }
              - { term: Lapsed donor, runtime_type: State }
              - { term: Gift Aid declaration, runtime_type: Artefact }
              - { term: "Thank-you / receipt", runtime_type: Artefact }
              - { term: Donor journey workflow, runtime_type: Workflow }
              - { term: Income raised, runtime_type: Outcome }
              - { term: "Return-on-investment learning", runtime_type: Learning }
          - name: "Major Gifts & Philanthropy"
            note: "Subject to ethical-acceptance/due-diligence policies and the Fundraising Regulator's code on high-value relationships."
            operating_domains:
              - prospect portfolios and wealth screening
              - cultivation and stewardship plans
              - solicitation and the ask
              - "pledges and multi-year commitments"
              - gift agreements and naming rights
              - donor recognition and events
              - capital and endowment campaigns
              - moves management pipeline
            vocabulary:
              - { term: Major donor / prospect, runtime_type: Actor }
              - { term: Relationship manager, runtime_type: Actor }
              - { term: Prospect portfolio, runtime_type: Object }
              - { term: Pledge, runtime_type: Object }
              - { term: Cultivation meeting held, runtime_type: Event }
              - { term: "Move-to-ask decision", runtime_type: Decision }
              - { term: In cultivation, runtime_type: State }
              - { term: Pledged, runtime_type: State }
              - { term: Gift agreement, runtime_type: Artefact }
              - { term: Proposal / case for support, runtime_type: Artefact }
              - { term: Ask made, runtime_type: Event }
              - { term: "Moves-management workflow", runtime_type: Workflow }
              - { term: Major gift secured, runtime_type: Outcome }
              - { term: "Pipeline-velocity learning", runtime_type: Learning }
          - name: "Corporate Partnerships & Sponsorship"
            note: "Cause-related marketing claims must meet ASA/CAP advertising rules and commercial-participator disclosure under charity law."
            operating_domains:
              - corporate prospect pipeline
              - "charity-of-the-year and partnerships"
              - sponsorship packages and benefits
              - employee fundraising and matched giving
              - payroll giving schemes
              - partnership agreements and reporting
              - "cause-related marketing campaigns"
              - account management and renewals
            vocabulary:
              - { term: Corporate partner, runtime_type: Actor }
              - { term: Partnerships manager, runtime_type: Actor }
              - { term: Partnership, runtime_type: Object }
              - { term: Sponsorship package, runtime_type: Object }
              - { term: Pitch delivered, runtime_type: Event }
              - { term: "Partnership go/no-go decision", runtime_type: Decision }
              - { term: Live partnership, runtime_type: State }
              - { term: Up for renewal, runtime_type: State }
              - { term: Partnership agreement, runtime_type: Artefact }
              - { term: Impact report to partner, runtime_type: Artefact }
              - { term: "Matched-giving claim", runtime_type: Event }
              - { term: "Account-management workflow", runtime_type: Workflow }
              - { term: "Partnership income & reach", runtime_type: Outcome }
              - { term: "Renewal-likelihood learning", runtime_type: Learning }
          - name: "Events & Community Fundraising"
            note: "Public collections require local-authority/Metropolitan Police street and house-to-house collection licences."
            operating_domains:
              - "challenge and mass-participation events"
              - community groups and volunteer organisers
              - fundraising pages and sponsorship
              - "DIY and in-memory fundraising"
              - event logistics and registrations
              - income reconciliation per event
              - supporter recruitment and retention
              - merchandise and collections
            vocabulary:
              - { term: Participant / fundraiser, runtime_type: Actor }
              - { term: Community organiser, runtime_type: Actor }
              - { term: Fundraising event, runtime_type: Object }
              - { term: Fundraising page, runtime_type: Object }
              - { term: Registration received, runtime_type: Event }
              - { term: "Place-allocation decision", runtime_type: Decision }
              - { term: Registered, runtime_type: State }
              - { term: Target reached, runtime_type: State }
              - { term: Sponsorship form, runtime_type: Artefact }
              - { term: Event completed, runtime_type: Event }
              - { term: Income reconciliation workflow, runtime_type: Workflow }
              - { term: Net event income, runtime_type: Outcome }
              - { term: "Cost-per-acquired-supporter learning", runtime_type: Learning }
              - { term: "In-memory tribute fund", runtime_type: Artefact }
          - name: "Legacy & In-Memory Giving"
            note: "Estate administration intersects probate law and HMRC inheritance-tax exemptions for charitable gifts."
            operating_domains:
              - legacy pledger relationships
              - "will-writing and gift-in-will promotion"
              - estate notifications and probate cases
              - legacy income forecasting
              - executor and solicitor liaison
              - "in-memory and tribute funds"
              - legacy stewardship and recognition
              - "case-by-case estate administration"
            vocabulary:
              - { term: Legacy pledger, runtime_type: Actor }
              - { term: Executor / solicitor, runtime_type: Actor }
              - { term: Legacy pledge, runtime_type: Object }
              - { term: Estate case, runtime_type: Object }
              - { term: Estate notified, runtime_type: Event }
              - { term: "Estate-acceptance decision", runtime_type: Decision }
              - { term: Pledged in will, runtime_type: State }
              - { term: In probate, runtime_type: State }
              - { term: Notification of death / will extract, runtime_type: Artefact }
              - { term: Legacy payment received, runtime_type: Event }
              - { term: "Estate-administration workflow", runtime_type: Workflow }
              - { term: Legacy income realised, runtime_type: Outcome }
              - { term: "Pledge-to-realisation learning", runtime_type: Learning }
              - { term: Legacy forecast, runtime_type: Artefact }
          - name: "Grants & Statutory Income (income side)"
            note: "Public procurement and grant funding (e.g. National Lottery, local authorities) carries subsidy-control and full-cost-recovery compliance."
            operating_domains:
              - statutory and lottery funding pipelines
              - tenders and service contracts
              - "full-cost recovery and budgets"
              - drawdown claims and invoicing
              - outcome and KPI reporting
              - contract compliance and variations
              - "restricted-income tracking"
              - funder relationship management
            vocabulary:
              - { term: Statutory funder / commissioner, runtime_type: Actor }
              - { term: Contracts manager, runtime_type: Actor }
              - { term: Funding contract, runtime_type: Object }
              - { term: Drawdown claim, runtime_type: Object }
              - { term: Claim submitted, runtime_type: Event }
              - { term: "Bid-or-pass decision", runtime_type: Decision }
              - { term: Contracted, runtime_type: State }
              - { term: Claim overdue, runtime_type: State }
              - { term: Contract variation, runtime_type: Artefact }
              - { term: KPI report, runtime_type: Artefact }
              - { term: Payment milestone met, runtime_type: Event }
              - { term: Claims workflow, runtime_type: Workflow }
              - { term: Statutory income secured, runtime_type: Outcome }
              - { term: "Full-cost-recovery learning", runtime_type: Learning }
      - name: "n-volunteerOS"
        buyer: "Head of Volunteering / Volunteer Manager at a charity, public body or community organisation"
        os_test: "Distinct buyer owning volunteer capacity as a managed resource; runtime is built around the volunteer lifecycle (recruit→vet→deploy→recognise) with shift scheduling, DBS clearance and hours-tracking — a model neither HR nor donor systems carry."
        sectors:
          - name: "Episodic & Event Volunteering"
            operating_domains:
              - volunteer roles and shift patterns
              - "event rotas and self-sign-up"
              - "check-in and attendance"
              - team leaders and zones
              - "kit, briefings and induction"
              - "no-show and standby cover"
              - hours and recognition
              - "post-event feedback"
            vocabulary:
              - { term: Volunteer, runtime_type: Actor }
              - { term: Team leader, runtime_type: Actor }
              - { term: Volunteer role, runtime_type: Object }
              - { term: Shift, runtime_type: Object }
              - { term: "Sign-up received", runtime_type: Event }
              - { term: "Shift-allocation decision", runtime_type: Decision }
              - { term: Confirmed, runtime_type: State }
              - { term: "No-show", runtime_type: State }
              - { term: Checked in, runtime_type: Event }
              - { term: Rota / schedule, runtime_type: Artefact }
              - { term: Hours logged, runtime_type: Outcome }
              - { term: Scheduling workflow, runtime_type: Workflow }
              - { term: Certificate of thanks, runtime_type: Artefact }
              - { term: "Fill-rate learning", runtime_type: Learning }
          - name: "Regular & Vetted Volunteer Roles"
            note: "Roles with children or vulnerable adults require DBS checks and safer-recruitment practice under safeguarding law."
            operating_domains:
              - ongoing role descriptions
              - applications and interviews
              - DBS / background checks and references
              - induction and training records
              - "supervision and one-to-ones"
              - ongoing availability and rotas
              - expenses and reimbursements
              - retention and exit
            vocabulary:
              - { term: Regular volunteer, runtime_type: Actor }
              - { term: Volunteer supervisor, runtime_type: Actor }
              - { term: Role profile, runtime_type: Object }
              - { term: Application, runtime_type: Object }
              - { term: Interview held, runtime_type: Event }
              - { term: Recruitment decision, runtime_type: Decision }
              - { term: Awaiting clearance, runtime_type: State }
              - { term: Active / deployed, runtime_type: State }
              - { term: DBS clearance received, runtime_type: Event }
              - { term: Reference / DBS certificate, runtime_type: Artefact }
              - { term: Training record, runtime_type: Artefact }
              - { term: Onboarding workflow, runtime_type: Workflow }
              - { term: Volunteer retention, runtime_type: Outcome }
              - { term: "Drop-off-point learning", runtime_type: Learning }
          - name: "Trustee & Skilled / Pro-Bono Volunteering"
            note: Trustee appointments require eligibility/disqualification checks under the Charities Act.
            operating_domains:
              - trustee and board vacancies
              - "skills-matching and brokerage"
              - "pro-bono project scoping"
              - term limits and rotation
              - skills audits and gap analysis
              - mentoring and advisory roles
              - induction packs and inductions
              - impact of skilled contributions
            vocabulary:
              - { term: Skilled volunteer, runtime_type: Actor }
              - { term: Brokerage / matcher, runtime_type: Actor }
              - { term: "Pro-bono project", runtime_type: Object }
              - { term: Role / vacancy, runtime_type: Object }
              - { term: Match proposed, runtime_type: Event }
              - { term: Appointment decision, runtime_type: Decision }
              - { term: Shortlisted, runtime_type: State }
              - { term: Appointed, runtime_type: State }
              - { term: Skills audit, runtime_type: Artefact }
              - { term: Project delivered, runtime_type: Event }
              - { term: Matching workflow, runtime_type: Workflow }
              - { term: Skills gap closed, runtime_type: Outcome }
              - { term: "Match-success learning", runtime_type: Learning }
              - { term: Induction pack, runtime_type: Artefact }
          - name: "Community & Mutual-Aid Networks"
            note: "Informal befriending and home-visit help still trigger safeguarding and lone-working duties of care."
            operating_domains:
              - neighbourhood help requests
              - local volunteer responders
              - task matching and dispatch
              - "befriending and check-in calls"
              - "good-neighbour rounds"
              - local coordinators and hubs
              - safeguarding for informal help
              - reach and response times
            vocabulary:
              - { term: Community responder, runtime_type: Actor }
              - { term: Person needing help, runtime_type: Actor }
              - { term: Help request / task, runtime_type: Object }
              - { term: Local hub, runtime_type: Object }
              - { term: Request raised, runtime_type: Event }
              - { term: "Task-assignment decision", runtime_type: Decision }
              - { term: Open / unassigned, runtime_type: State }
              - { term: In progress, runtime_type: State }
              - { term: Task completed, runtime_type: Event }
              - { term: Match / dispatch note, runtime_type: Artefact }
              - { term: Dispatch workflow, runtime_type: Workflow }
              - { term: Need met / isolation reduced, runtime_type: Outcome }
              - { term: "Response-time learning", runtime_type: Learning }
              - { term: Safeguarding flag, runtime_type: State }
          - name: "Volunteer-Led Operations (charity shops & services)"
            note: "Retail Gift Aid on donated goods requires HMRC agency-sale agreements; food/electrical resale carries trading-standards duties."
            operating_domains:
              - shop and site rotas
              - till and stock handled by volunteers
              - Gift Aid on donated goods
              - volunteer team management
              - "opening cover and key-holders"
              - donation processing and sorting
              - "health-and-safety and training"
              - shop performance and hours
            vocabulary:
              - { term: Shop volunteer, runtime_type: Actor }
              - { term: Shop manager, runtime_type: Actor }
              - { term: Shop rota, runtime_type: Object }
              - { term: Donated goods, runtime_type: Object }
              - { term: Shift covered, runtime_type: Event }
              - { term: "Cover-gap decision", runtime_type: Decision }
              - { term: Open / staffed, runtime_type: State }
              - { term: Uncovered shift, runtime_type: State }
              - { term: Gift Aid on goods signed, runtime_type: Event }
              - { term: Volunteer agreement, runtime_type: Artefact }
              - { term: Sales / till report, runtime_type: Artefact }
              - { term: "Rota-cover workflow", runtime_type: Workflow }
              - { term: "Hours contributed & shop income", runtime_type: Outcome }
              - { term: "Cover-reliability learning", runtime_type: Learning }
  - name: "AI-Native & Emerging"
    os:
      - name: "n-agentOS"
        buyer: Heads of AI / platform engineering leaders at companies deploying autonomous LLM agents into production workflows.
        os_test: "Distinct buyer (AI platform team), own budget line (agent infra spend), unique state model (agent runs, tool calls, memory, traces) and vocabulary that no CRM/RPA tool shares; repeatable vendors (LangChain, CrewAI, Sierra) prove the category."
        sectors:
          - name: "Agent Orchestration & Runtime"
            operating_domains:
              - Agent definitions
              - Tool registries
              - Run executions
              - Planner/router logic
              - "Concurrency & queues"
              - "Fallback & retry policies"
              - Sandboxed execution environments
              - "Agent versions & rollouts"
            vocabulary:
              - { term: Agent, runtime_type: Actor }
              - { term: Tool, runtime_type: Object }
              - { term: Run, runtime_type: Workflow }
              - { term: Tool call, runtime_type: Event }
              - { term: Plan, runtime_type: Artefact }
              - { term: Step, runtime_type: Event }
              - { term: Routing decision, runtime_type: Decision }
              - { term: Run status, runtime_type: State }
              - { term: Handoff, runtime_type: Event }
              - { term: Final answer, runtime_type: Outcome }
              - { term: Token budget, runtime_type: State }
              - { term: Retry policy, runtime_type: Decision }
              - { term: Trajectory, runtime_type: Artefact }
              - { term: Success rate, runtime_type: Learning }
          - name: "Agent Memory & Knowledge"
            operating_domains:
              - Vector stores
              - Memory namespaces
              - Retrieval pipelines
              - Embedding models
              - "Knowledge sources & connectors"
              - "Chunking & indexing jobs"
              - Recall scoring
              - Memory consolidation
            vocabulary:
              - { term: Memory store, runtime_type: Object }
              - { term: Memory item, runtime_type: Artefact }
              - { term: Knowledge source, runtime_type: Object }
              - { term: Embedding, runtime_type: Artefact }
              - { term: Index job, runtime_type: Workflow }
              - { term: Retrieval, runtime_type: Event }
              - { term: Recall hit, runtime_type: Event }
              - { term: Relevance score, runtime_type: Learning }
              - { term: Consolidation, runtime_type: Workflow }
              - { term: Forget decision, runtime_type: Decision }
              - { term: Freshness, runtime_type: State }
              - { term: Context window, runtime_type: State }
              - { term: Retriever, runtime_type: Actor }
              - { term: Grounded answer, runtime_type: Outcome }
          - name: "Agent Evaluation & Observability"
            operating_domains:
              - Eval suites
              - Golden datasets
              - Trace timelines
              - "LLM-judge graders"
              - Regression dashboards
              - "Live monitors & alerts"
              - A/B agent comparisons
              - Failure clustering
            vocabulary:
              - { term: Trace, runtime_type: Artefact }
              - { term: Span, runtime_type: Event }
              - { term: Eval suite, runtime_type: Object }
              - { term: Golden dataset, runtime_type: Object }
              - { term: Judge, runtime_type: Actor }
              - { term: Grade, runtime_type: Outcome }
              - { term: Eval run, runtime_type: Workflow }
              - { term: Regression, runtime_type: Event }
              - { term: Pass rate, runtime_type: Learning }
              - { term: Latency, runtime_type: State }
              - { term: Alert, runtime_type: Event }
              - { term: Failure cluster, runtime_type: Artefact }
              - { term: Baseline, runtime_type: State }
              - { term: Promotion decision, runtime_type: Decision }
          - name: "Agent Guardrails & Safety"
            note: "Touches data-protection (PII/GDPR) and sector-specific AI compliance where agents act on regulated data."
            operating_domains:
              - Policy rules
              - Input/output filters
              - PII redaction
              - Jailbreak detection
              - "Human-in-the-loop gates"
              - Permission scopes
              - Incident reviews
              - "Red-team probes"
            vocabulary:
              - { term: Guardrail, runtime_type: Object }
              - { term: Policy, runtime_type: Artefact }
              - { term: Filter, runtime_type: Object }
              - { term: Violation, runtime_type: Event }
              - { term: Block decision, runtime_type: Decision }
              - { term: Approval gate, runtime_type: Decision }
              - { term: Reviewer, runtime_type: Actor }
              - { term: Redaction, runtime_type: Event }
              - { term: Risk level, runtime_type: State }
              - { term: Incident, runtime_type: Event }
              - { term: "Red-team probe", runtime_type: Workflow }
              - { term: Audit log, runtime_type: Artefact }
              - { term: Compliance verdict, runtime_type: Outcome }
              - { term: Block rate, runtime_type: Learning }
          - name: "Conversational & Customer-Facing Agents"
            operating_domains:
              - Bot personas
              - Conversation flows
              - Intent catalogues
              - Channel integrations
              - Escalation rules
              - Knowledge answers
              - Transcript reviews
              - Containment dashboards
            vocabulary:
              - { term: Assistant, runtime_type: Actor }
              - { term: Persona, runtime_type: Object }
              - { term: Conversation, runtime_type: Workflow }
              - { term: User message, runtime_type: Event }
              - { term: Intent, runtime_type: Artefact }
              - { term: Reply, runtime_type: Event }
              - { term: Escalation, runtime_type: Decision }
              - { term: Handoff to human, runtime_type: Event }
              - { term: Session state, runtime_type: State }
              - { term: Resolution, runtime_type: Outcome }
              - { term: Transcript, runtime_type: Artefact }
              - { term: Containment rate, runtime_type: Learning }
              - { term: CSAT, runtime_type: Learning }
              - { term: Live agent, runtime_type: Actor }
          - name: "Multi-Agent Teams & Workflows"
            operating_domains:
              - "Agent crews & roles"
              - Task graphs
              - Shared scratchpads
              - Coordination protocols
              - Delegation rules
              - Blackboard state
              - Workflow templates
              - "Team-level metrics"
            vocabulary:
              - { term: Crew, runtime_type: Actor }
              - { term: Role, runtime_type: Object }
              - { term: Task, runtime_type: Workflow }
              - { term: Delegation, runtime_type: Decision }
              - { term: Message bus, runtime_type: Object }
              - { term: Broadcast, runtime_type: Event }
              - { term: Shared scratchpad, runtime_type: Artefact }
              - { term: Coordination state, runtime_type: State }
              - { term: "Sub-task result", runtime_type: Outcome }
              - { term: Manager agent, runtime_type: Actor }
              - { term: Workflow template, runtime_type: Object }
              - { term: Deadlock, runtime_type: State }
              - { term: Completion, runtime_type: Event }
              - { term: Throughput, runtime_type: Learning }
      - name: "n-robotOS"
        buyer: "VPs of automation / robotics engineering leads at warehouses, factories, and robotics OEMs deploying physical robot fleets."
        os_test: "Buyer owns capital robot budget; state model is physical (joints, payloads, battery, collisions, maps) which no software-agent OS shares; vocabulary (waypoint, gripper, teach pendant) is robotics-native; repeatable vendors (Boston Dynamics, Locus, Formant) confirm category."
        sectors:
          - name: "Fleet Operations & Dispatch"
            note: "Workplace machinery safety (OSHA/ISO 10218 collaborative-robot standards) applies on the floor."
            operating_domains:
              - Robot fleet
              - Mission queues
              - "Charging & docking"
              - Zone maps
              - Traffic management
              - Operator dashboards
              - Shift schedules
              - Throughput targets
            vocabulary:
              - { term: Robot, runtime_type: Actor }
              - { term: Fleet, runtime_type: Object }
              - { term: Mission, runtime_type: Workflow }
              - { term: Dispatch, runtime_type: Decision }
              - { term: Waypoint, runtime_type: Object }
              - { term: Battery level, runtime_type: State }
              - { term: Docking event, runtime_type: Event }
              - { term: Operator, runtime_type: Actor }
              - { term: Mission complete, runtime_type: Outcome }
              - { term: Robot status, runtime_type: State }
              - { term: Traffic conflict, runtime_type: Event }
              - { term: Shift report, runtime_type: Artefact }
              - { term: Picks per hour, runtime_type: Learning }
              - { term: Reroute, runtime_type: Decision }
          - name: "Manipulation & Pick Programming"
            operating_domains:
              - "Grippers & end effectors"
              - Pick poses
              - Object models / SKUs
              - Grasp planners
              - Bin layouts
              - Force/torque limits
              - Cycle programs
              - Reject handling
            vocabulary:
              - { term: End effector, runtime_type: Object }
              - { term: Grasp, runtime_type: Event }
              - { term: Pick pose, runtime_type: Artefact }
              - { term: Object model, runtime_type: Object }
              - { term: Grasp plan, runtime_type: Decision }
              - { term: Pick cycle, runtime_type: Workflow }
              - { term: Place, runtime_type: Event }
              - { term: Drop / fault, runtime_type: Event }
              - { term: Grip force, runtime_type: State }
              - { term: Robot arm, runtime_type: Actor }
              - { term: Successful pick, runtime_type: Outcome }
              - { term: Bin, runtime_type: Object }
              - { term: Pick success rate, runtime_type: Learning }
              - { term: Reachability, runtime_type: State }
          - name: "Perception & Mapping"
            operating_domains:
              - "Sensor streams (LiDAR/RGB-D)"
              - Point clouds
              - Occupancy maps
              - Localization
              - Object detection models
              - Calibration jobs
              - Map versions
              - "No-go zones"
            vocabulary:
              - { term: Sensor, runtime_type: Object }
              - { term: Point cloud, runtime_type: Artefact }
              - { term: Map, runtime_type: Artefact }
              - { term: Detection, runtime_type: Event }
              - { term: Localization, runtime_type: State }
              - { term: Calibration, runtime_type: Workflow }
              - { term: Perception model, runtime_type: Object }
              - { term: Obstacle, runtime_type: Object }
              - { term: Map update, runtime_type: Event }
              - { term: Pose estimate, runtime_type: Outcome }
              - { term: "No-go zone", runtime_type: Object }
              - { term: Drift, runtime_type: State }
              - { term: "Re-localization decision", runtime_type: Decision }
              - { term: Detection accuracy, runtime_type: Learning }
          - name: "Teleoperation & Human Oversight"
            operating_domains:
              - Remote control stations
              - Live video feeds
              - Intervention requests
              - Latency budgets
              - Takeover sessions
              - Operator queues
              - "Assisted-autonomy modes"
              - Session recordings
            vocabulary:
              - { term: Teleoperator, runtime_type: Actor }
              - { term: Control station, runtime_type: Object }
              - { term: Takeover, runtime_type: Decision }
              - { term: Intervention request, runtime_type: Event }
              - { term: Video feed, runtime_type: Object }
              - { term: Control session, runtime_type: Workflow }
              - { term: Latency, runtime_type: State }
              - { term: Command, runtime_type: Event }
              - { term: Autonomy mode, runtime_type: State }
              - { term: Handback, runtime_type: Event }
              - { term: Session recording, runtime_type: Artefact }
              - { term: Resolved incident, runtime_type: Outcome }
              - { term: Intervention rate, runtime_type: Learning }
              - { term: Robot under control, runtime_type: Actor }
          - name: "Maintenance & Reliability"
            operating_domains:
              - Health telemetry
              - Fault codes
              - Work orders
              - Spare parts
              - Service technicians
              - Predictive models
              - Uptime SLAs
              - Recall campaigns
            vocabulary:
              - { term: Robot unit, runtime_type: Object }
              - { term: Telemetry, runtime_type: Artefact }
              - { term: Fault code, runtime_type: Event }
              - { term: Work order, runtime_type: Workflow }
              - { term: Technician, runtime_type: Actor }
              - { term: Health status, runtime_type: State }
              - { term: Service decision, runtime_type: Decision }
              - { term: Spare part, runtime_type: Object }
              - { term: Repair, runtime_type: Event }
              - { term: Restored unit, runtime_type: Outcome }
              - { term: Maintenance log, runtime_type: Artefact }
              - { term: Uptime, runtime_type: Learning }
              - { term: MTBF, runtime_type: Learning }
              - { term: Recall, runtime_type: Workflow }
          - name: Robot Behaviour Programming
            operating_domains:
              - Behaviour trees
              - Skill libraries
              - "Teach-pendant programs"
              - Motion primitives
              - Simulation tests
              - Parameter tuning
              - Deployment rings
              - Skill versions
            vocabulary:
              - { term: Skill, runtime_type: Object }
              - { term: Behaviour tree, runtime_type: Artefact }
              - { term: Motion primitive, runtime_type: Object }
              - { term: Teach program, runtime_type: Artefact }
              - { term: Program author, runtime_type: Actor }
              - { term: Sim test, runtime_type: Workflow }
              - { term: Parameter set, runtime_type: State }
              - { term: Deploy decision, runtime_type: Decision }
              - { term: Skill trigger, runtime_type: Event }
              - { term: Validated skill, runtime_type: Outcome }
              - { term: Rollout ring, runtime_type: State }
              - { term: Skill version, runtime_type: Artefact }
              - { term: Execution success, runtime_type: Learning }
              - { term: Skill execution, runtime_type: Event }
      - name: "n-autonomyOS"
        buyer: "Heads of autonomy / safety at AV, drone, and self-driving programmes; fleet operators of autonomous vehicles."
        os_test: "Distinct buyer (autonomy programme), unique safety-case state model (ODD, disengagements, miles, scenario coverage) and vocabulary (stack, perception, planner, safety driver) absent from generic robotics; repeatable companies (Waymo, Zipline, Wayve) confirm it."
        sectors:
          - name: Driving / Flight Stack
            note: "Subject to road-vehicle (UNECE, NHTSA AV) or airspace (FAA Part 135/BVLOS) certification depending on domain."
            operating_domains:
              - Perception stack
              - Prediction module
              - Motion planner
              - Controller
              - World model
              - Operational design domain (ODD)
              - Stack versions
              - Compute budgets
            vocabulary:
              - { term: Autonomy stack, runtime_type: Object }
              - { term: Ego vehicle, runtime_type: Actor }
              - { term: Planner, runtime_type: Object }
              - { term: Trajectory, runtime_type: Artefact }
              - { term: Planning decision, runtime_type: Decision }
              - { term: Prediction, runtime_type: Artefact }
              - { term: Maneuver, runtime_type: Event }
              - { term: ODD, runtime_type: State }
              - { term: Stack version, runtime_type: Object }
              - { term: Safe stop, runtime_type: Outcome }
              - { term: Compute headroom, runtime_type: State }
              - { term: Tick, runtime_type: Event }
              - { term: Drive session, runtime_type: Workflow }
              - { term: Comfort score, runtime_type: Learning }
          - name: "Safety Case & Disengagements"
            note: "Regulated: safety-case and disengagement reporting mandated by AV/aviation authorities."
            operating_domains:
              - Disengagement log
              - Safety driver shifts
              - Hazard registers
              - "Safety-case arguments"
              - Incident reports
              - Miles tracker
              - Mitigation actions
              - Regulator submissions
            vocabulary:
              - { term: Disengagement, runtime_type: Event }
              - { term: Safety driver, runtime_type: Actor }
              - { term: Hazard, runtime_type: Object }
              - { term: Safety case, runtime_type: Artefact }
              - { term: Incident report, runtime_type: Artefact }
              - { term: Severity, runtime_type: State }
              - { term: Mitigation, runtime_type: Decision }
              - { term: Mitigation action, runtime_type: Workflow }
              - { term: Autonomous miles, runtime_type: Learning }
              - { term: "Near-miss", runtime_type: Event }
              - { term: Regulator submission, runtime_type: Artefact }
              - { term: Closed hazard, runtime_type: Outcome }
              - { term: Safety officer, runtime_type: Actor }
              - { term: MPI (miles per intervention), runtime_type: Learning }
          - name: "Scenario & Validation"
            operating_domains:
              - Scenario library
              - "Edge-case catalogue"
              - Replay drives
              - Coverage matrix
              - Regression scenarios
              - Test campaigns
              - Pass/fail gates
              - Scenario mining
            vocabulary:
              - { term: Scenario, runtime_type: Object }
              - { term: Edge case, runtime_type: Object }
              - { term: Replay, runtime_type: Event }
              - { term: Test campaign, runtime_type: Workflow }
              - { term: Coverage matrix, runtime_type: Artefact }
              - { term: Scenario mining, runtime_type: Workflow }
              - { term: Pass/fail gate, runtime_type: Decision }
              - { term: Verdict, runtime_type: Outcome }
              - { term: Test engineer, runtime_type: Actor }
              - { term: Scenario run, runtime_type: Event }
              - { term: Coverage level, runtime_type: State }
              - { term: Failure case, runtime_type: Event }
              - { term: Validation report, runtime_type: Artefact }
              - { term: Coverage growth, runtime_type: Learning }
          - name: "Remote Assistance & Mission Control"
            operating_domains:
              - Assistance requests
              - Remote operators
              - Live vehicle map
              - Path approvals
              - "Stuck-vehicle queue"
              - Geofences
              - Mission schedules
              - Resolution logs
            vocabulary:
              - { term: Remote operator, runtime_type: Actor }
              - { term: Assistance request, runtime_type: Event }
              - { term: Stuck vehicle, runtime_type: State }
              - { term: Path approval, runtime_type: Decision }
              - { term: Geofence, runtime_type: Object }
              - { term: Mission, runtime_type: Workflow }
              - { term: Vehicle, runtime_type: Actor }
              - { term: Guidance command, runtime_type: Event }
              - { term: Resolution, runtime_type: Outcome }
              - { term: Queue position, runtime_type: State }
              - { term: Assistance log, runtime_type: Artefact }
              - { term: Resume, runtime_type: Event }
              - { term: Assists per hour, runtime_type: Learning }
              - { term: Route plan, runtime_type: Artefact }
          - name: "Map & Localization Operations"
            operating_domains:
              - HD maps
              - Map change detection
              - Localization layers
              - Survey runs
              - Map releases
              - Lane / sign annotations
              - Map QA
              - Coverage regions
            vocabulary:
              - { term: HD map, runtime_type: Object }
              - { term: Map layer, runtime_type: Object }
              - { term: Map change, runtime_type: Event }
              - { term: Survey run, runtime_type: Workflow }
              - { term: Annotation, runtime_type: Artefact }
              - { term: Map release, runtime_type: Event }
              - { term: Publish decision, runtime_type: Decision }
              - { term: Localization accuracy, runtime_type: State }
              - { term: Mapping vehicle, runtime_type: Actor }
              - { term: Validated map, runtime_type: Outcome }
              - { term: Coverage region, runtime_type: State }
              - { term: QA review, runtime_type: Workflow }
              - { term: Map freshness, runtime_type: Learning }
              - { term: Map artefact, runtime_type: Artefact }
      - name: "n-digitaltwinOS"
        buyer: "Heads of operations / engineering at asset-heavy firms (energy, manufacturing, smart cities) running live virtual replicas of physical assets."
        os_test: "Buyer pays for asset-modelling platform; state model is the live-synced twin (telemetry binding, what-if state, drift between physical/virtual) unique vs robotics/simulation; vocabulary (twin, asset graph, live binding) is native; vendors (Bentley iTwin, Siemens, Cesium) confirm."
        sectors:
          - name: "Asset Modelling & Twin Graph"
            operating_domains:
              - Asset hierarchy
              - Twin models
              - Component library
              - Property schemas
              - Relationship graph
              - 3D geometry / BIM
              - Twin versions
              - Model imports
            vocabulary:
              - { term: Digital twin, runtime_type: Object }
              - { term: Asset, runtime_type: Object }
              - { term: Twin graph, runtime_type: Artefact }
              - { term: Component, runtime_type: Object }
              - { term: Property, runtime_type: State }
              - { term: Relationship, runtime_type: Object }
              - { term: Model import, runtime_type: Workflow }
              - { term: Twin version, runtime_type: Artefact }
              - { term: Modeller, runtime_type: Actor }
              - { term: Publish decision, runtime_type: Decision }
              - { term: Validated twin, runtime_type: Outcome }
              - { term: Geometry update, runtime_type: Event }
              - { term: Schema, runtime_type: Object }
              - { term: Model completeness, runtime_type: Learning }
          - name: Live Telemetry Binding
            operating_domains:
              - Sensor bindings
              - Data streams
              - Tag mappings
              - Sync jobs
              - "Twin-to-physical drift"
              - Connector health
              - Update intervals
              - Stream backfills
            vocabulary:
              - { term: Sensor binding, runtime_type: Object }
              - { term: Data stream, runtime_type: Object }
              - { term: Telemetry update, runtime_type: Event }
              - { term: Sync job, runtime_type: Workflow }
              - { term: Live value, runtime_type: State }
              - { term: Drift, runtime_type: State }
              - { term: Connector, runtime_type: Actor }
              - { term: "Re-sync decision", runtime_type: Decision }
              - { term: Tag mapping, runtime_type: Artefact }
              - { term: Synced twin, runtime_type: Outcome }
              - { term: Stale data, runtime_type: State }
              - { term: Backfill, runtime_type: Workflow }
              - { term: Sync latency, runtime_type: Learning }
              - { term: Dropout, runtime_type: Event }
          - name: "Simulation & What-If Analysis"
            operating_domains:
              - Scenario builder
              - Physics solvers
              - Parameter sweeps
              - "What-if comparisons"
              - Optimisation goals
              - Run results
              - Baseline vs proposed
              - Result archive
            vocabulary:
              - { term: Scenario, runtime_type: Object }
              - { term: "What-if run", runtime_type: Workflow }
              - { term: Solver, runtime_type: Actor }
              - { term: Parameter sweep, runtime_type: Workflow }
              - { term: Run trigger, runtime_type: Event }
              - { term: Result set, runtime_type: Artefact }
              - { term: Optimisation goal, runtime_type: Decision }
              - { term: Recommended setting, runtime_type: Outcome }
              - { term: Baseline, runtime_type: State }
              - { term: Convergence, runtime_type: State }
              - { term: Analyst, runtime_type: Actor }
              - { term: Comparison report, runtime_type: Artefact }
              - { term: Predicted savings, runtime_type: Learning }
              - { term: Sweep complete, runtime_type: Event }
          - name: "Predictive Maintenance & Health"
            operating_domains:
              - Condition monitors
              - Anomaly models
              - "Remaining-useful-life estimates"
              - Maintenance triggers
              - Health scores
              - Failure modes (FMEA)
              - "Work-order handoff"
              - Alert thresholds
            vocabulary:
              - { term: Health score, runtime_type: State }
              - { term: Anomaly, runtime_type: Event }
              - { term: Failure mode, runtime_type: Object }
              - { term: Condition monitor, runtime_type: Object }
              - { term: Maintenance trigger, runtime_type: Decision }
              - { term: Remaining useful life, runtime_type: Learning }
              - { term: Alert, runtime_type: Event }
              - { term: Inspection workflow, runtime_type: Workflow }
              - { term: Reliability engineer, runtime_type: Actor }
              - { term: Prevented failure, runtime_type: Outcome }
              - { term: Risk level, runtime_type: State }
              - { term: Diagnosis report, runtime_type: Artefact }
              - { term: Threshold breach, runtime_type: Event }
              - { term: Detection lead time, runtime_type: Learning }
          - name: "Operations Visualisation & Control"
            note: "Critical-infrastructure control (energy/utilities) sits under NERC CIP / IEC 62443 cybersecurity regimes."
            operating_domains:
              - 3D / map viewer
              - Dashboards
              - Live alarms
              - Operator actions
              - Control commands
              - Camera viewpoints
              - Annotations
              - Shift handover
            vocabulary:
              - { term: Operator, runtime_type: Actor }
              - { term: Twin viewer, runtime_type: Object }
              - { term: Dashboard, runtime_type: Artefact }
              - { term: Alarm, runtime_type: Event }
              - { term: Control command, runtime_type: Event }
              - { term: Acknowledge decision, runtime_type: Decision }
              - { term: Setpoint, runtime_type: State }
              - { term: Annotation, runtime_type: Artefact }
              - { term: Viewpoint, runtime_type: Object }
              - { term: Stabilised asset, runtime_type: Outcome }
              - { term: Shift handover, runtime_type: Workflow }
              - { term: Active alarms, runtime_type: State }
              - { term: Response time, runtime_type: Learning }
              - { term: Acknowledged alarm, runtime_type: Event }
      - name: "n-spaceOS"
        buyer: "Mission operations directors / flight directors at satellite operators, launch providers, and ground-station networks."
        os_test: "Buyer funds mission ops; state model is orbital (ephemeris, passes, conjunctions, telemetry/command) entirely unlike terrestrial twins; vocabulary (spacecraft bus, ground segment, TT&C) is space-native; vendors (Kubos, LeoLabs, Cognitive Space, Slingshot) confirm."
        sectors:
          - name: "Mission Operations & Commanding"
            note: "Spacecraft commanding requires radio-frequency licensing (ITU/FCC/Ofcom) and mission authorisation."
            operating_domains:
              - Spacecraft bus
              - Command stack
              - Telemetry channels
              - Pass schedule
              - Procedures / sequences
              - Flight rules
              - Anomaly board
              - Mode transitions
            vocabulary:
              - { term: Spacecraft, runtime_type: Actor }
              - { term: Command, runtime_type: Event }
              - { term: Telemetry, runtime_type: Artefact }
              - { term: Procedure, runtime_type: Workflow }
              - { term: Flight rule, runtime_type: Object }
              - { term: Spacecraft mode, runtime_type: State }
              - { term: "Go/no-go decision", runtime_type: Decision }
              - { term: Anomaly, runtime_type: Event }
              - { term: Flight controller, runtime_type: Actor }
              - { term: Safe mode, runtime_type: State }
              - { term: Command executed, runtime_type: Outcome }
              - { term: Command log, runtime_type: Artefact }
              - { term: Pass utilisation, runtime_type: Learning }
              - { term: Uplink, runtime_type: Event }
          - name: "Ground Segment & Scheduling"
            operating_domains:
              - Ground stations
              - Antenna pool
              - Contact scheduling
              - Pass predictions
              - Link budgets
              - Station keeping windows
              - Network conflicts
              - Booking calendar
            vocabulary:
              - { term: Ground station, runtime_type: Actor }
              - { term: Antenna, runtime_type: Object }
              - { term: Contact (pass), runtime_type: Event }
              - { term: Schedule, runtime_type: Workflow }
              - { term: Booking decision, runtime_type: Decision }
              - { term: Pass prediction, runtime_type: Artefact }
              - { term: Link budget, runtime_type: Artefact }
              - { term: Station availability, runtime_type: State }
              - { term: Conflict, runtime_type: Event }
              - { term: Established link, runtime_type: Outcome }
              - { term: Acquisition of signal, runtime_type: Event }
              - { term: Booking, runtime_type: Object }
              - { term: Contact success rate, runtime_type: Learning }
              - { term: Signal strength, runtime_type: State }
          - name: "Flight Dynamics & Orbits"
            note: "Conjunction/collision-avoidance reporting governed by space-traffic regulators (FCC/ESA/Space Force)."
            operating_domains:
              - Ephemeris
              - Orbit determination
              - Maneuver planning
              - Propellant budget
              - Conjunction assessment
              - "Station-keeping"
              - TLE catalogue
              - Reentry prediction
            vocabulary:
              - { term: Orbit, runtime_type: Object }
              - { term: Ephemeris, runtime_type: Artefact }
              - { term: Maneuver, runtime_type: Event }
              - { term: Burn plan, runtime_type: Workflow }
              - { term: Maneuver decision, runtime_type: Decision }
              - { term: Propellant remaining, runtime_type: State }
              - { term: Conjunction, runtime_type: Event }
              - { term: Flight dynamics analyst, runtime_type: Actor }
              - { term: Orbit solution, runtime_type: Outcome }
              - { term: Collision risk, runtime_type: State }
              - { term: TLE, runtime_type: Artefact }
              - { term: Reentry prediction, runtime_type: Artefact }
              - { term: Position accuracy, runtime_type: Learning }
              - { term: Avoidance maneuver, runtime_type: Decision }
          - name: "Payload & Tasking"
            operating_domains:
              - Imaging / sensor payload
              - Tasking orders
              - Acquisition plans
              - Downlink queue
              - Data products
              - Customer requests
              - "Cloud-cover filters"
              - Delivery SLAs
            vocabulary:
              - { term: Payload, runtime_type: Object }
              - { term: Tasking order, runtime_type: Workflow }
              - { term: Acquisition, runtime_type: Event }
              - { term: Tasking decision, runtime_type: Decision }
              - { term: Customer, runtime_type: Actor }
              - { term: Data product, runtime_type: Artefact }
              - { term: Downlink, runtime_type: Event }
              - { term: Collection window, runtime_type: State }
              - { term: Delivered image, runtime_type: Outcome }
              - { term: Cloud cover, runtime_type: State }
              - { term: Acquisition plan, runtime_type: Artefact }
              - { term: Request queue, runtime_type: State }
              - { term: Tasking fulfilment rate, runtime_type: Learning }
              - { term: Capture complete, runtime_type: Event }
          - name: "Constellation Health & Fleet"
            operating_domains:
              - Constellation fleet
              - Subsystem health
              - Battery / power
              - Thermal limits
              - Firmware updates
              - Spare satellites
              - Coverage gaps
              - Fleet alerts
            vocabulary:
              - { term: Constellation, runtime_type: Object }
              - { term: Satellite, runtime_type: Actor }
              - { term: Subsystem health, runtime_type: State }
              - { term: Health alert, runtime_type: Event }
              - { term: Firmware update, runtime_type: Workflow }
              - { term: Battery state of charge, runtime_type: State }
              - { term: Replace decision, runtime_type: Decision }
              - { term: Spare satellite, runtime_type: Object }
              - { term: Coverage gap, runtime_type: Event }
              - { term: Healthy fleet, runtime_type: Outcome }
              - { term: Update log, runtime_type: Artefact }
              - { term: Operations engineer, runtime_type: Actor }
              - { term: Fleet availability, runtime_type: Learning }
              - { term: Coverage map, runtime_type: Artefact }
      - name: "n-simulationOS"
        buyer: "Heads of simulation / R&D engineering generating synthetic worlds and data for training, testing, and design."
        os_test: "Buyer pays for synthetic-world/compute; state model is the run graph (scene, domain randomisation, render jobs, dataset lineage) distinct from a live twin (no physical binding) and from autonomy validation; vocabulary (synthetic data, sim-to-real, render farm) is native; vendors (NVIDIA Omniverse, Applied Intuition, Parallel Domain) confirm."
        sectors:
          - name: Synthetic Data Generation
            operating_domains:
              - Scene templates
              - Domain randomisation
              - Asset libraries
              - Label generators
              - Render farm
              - Dataset versions
              - Distribution targets
              - Quality filters
            vocabulary:
              - { term: Scene, runtime_type: Object }
              - { term: Synthetic dataset, runtime_type: Artefact }
              - { term: Domain randomisation, runtime_type: Workflow }
              - { term: Render job, runtime_type: Event }
              - { term: Label, runtime_type: Artefact }
              - { term: Asset, runtime_type: Object }
              - { term: Generation decision, runtime_type: Decision }
              - { term: Data engineer, runtime_type: Actor }
              - { term: Generated frame, runtime_type: Outcome }
              - { term: Render status, runtime_type: State }
              - { term: Dataset version, runtime_type: Object }
              - { term: Quality filter, runtime_type: Decision }
              - { term: "Sim-to-real gap", runtime_type: Learning }
              - { term: Distribution coverage, runtime_type: Learning }
          - name: "Scenario Authoring & Worlds"
            operating_domains:
              - World builder
              - Actor behaviours
              - Map / terrain
              - Event scripts
              - "Weather & lighting"
              - Scenario library
              - Parameter ranges
              - Scenario reviews
            vocabulary:
              - { term: World, runtime_type: Object }
              - { term: Scenario, runtime_type: Object }
              - { term: Sim actor, runtime_type: Actor }
              - { term: Behaviour script, runtime_type: Artefact }
              - { term: Trigger event, runtime_type: Event }
              - { term: Weather preset, runtime_type: State }
              - { term: Authoring decision, runtime_type: Decision }
              - { term: Scenario author, runtime_type: Actor }
              - { term: Published scenario, runtime_type: Outcome }
              - { term: Authoring workflow, runtime_type: Workflow }
              - { term: Parameter range, runtime_type: State }
              - { term: Scenario library, runtime_type: Object }
              - { term: Reuse rate, runtime_type: Learning }
              - { term: Map, runtime_type: Artefact }
          - name: "Physics & Engine Runs"
            operating_domains:
              - Physics engine
              - Solver settings
              - Timestep config
              - Run batches
              - Determinism checks
              - Compute clusters
              - Run logs
              - Crash recovery
            vocabulary:
              - { term: Physics engine, runtime_type: Object }
              - { term: Sim run, runtime_type: Workflow }
              - { term: Timestep, runtime_type: Event }
              - { term: Solver config, runtime_type: State }
              - { term: Determinism check, runtime_type: Decision }
              - { term: Compute node, runtime_type: Actor }
              - { term: Run batch, runtime_type: Object }
              - { term: Run log, runtime_type: Artefact }
              - { term: Run state, runtime_type: State }
              - { term: Completed run, runtime_type: Outcome }
              - { term: Crash, runtime_type: Event }
              - { term: Replay artefact, runtime_type: Artefact }
              - { term: "Wall-clock per run", runtime_type: Learning }
              - { term: Restart decision, runtime_type: Decision }
          - name: "Closed-Loop Testing & SIL/HIL"
            operating_domains:
              - "System-under-test bindings"
              - SIL / HIL rigs
              - Test suites
              - Metric extractors
              - Pass criteria
              - Regression baselines
              - Rig schedules
              - Result dashboards
            vocabulary:
              - { term: System under test, runtime_type: Object }
              - { term: Test rig, runtime_type: Actor }
              - { term: Test suite, runtime_type: Object }
              - { term: Test run, runtime_type: Workflow }
              - { term: Metric extraction, runtime_type: Event }
              - { term: Pass criterion, runtime_type: Decision }
              - { term: Rig status, runtime_type: State }
              - { term: Test result, runtime_type: Outcome }
              - { term: Test engineer, runtime_type: Actor }
              - { term: Baseline, runtime_type: State }
              - { term: Result report, runtime_type: Artefact }
              - { term: Regression, runtime_type: Event }
              - { term: Pass rate, runtime_type: Learning }
              - { term: Coverage delta, runtime_type: Learning }
          - name: "Asset & Environment Pipeline"
            operating_domains:
              - 3D asset ingest
              - Material / texture sets
              - USD scene graph
              - LOD generation
              - Asset validation
              - Version control
              - Asset catalogue
              - Licensing metadata
            vocabulary:
              - { term: 3D asset, runtime_type: Object }
              - { term: Material, runtime_type: Object }
              - { term: Scene graph, runtime_type: Artefact }
              - { term: Ingest job, runtime_type: Workflow }
              - { term: Import event, runtime_type: Event }
              - { term: Validation decision, runtime_type: Decision }
              - { term: Asset status, runtime_type: State }
              - { term: Approved asset, runtime_type: Outcome }
              - { term: Asset artist, runtime_type: Actor }
              - { term: Asset version, runtime_type: Object }
              - { term: LOD level, runtime_type: State }
              - { term: Catalogue entry, runtime_type: Artefact }
              - { term: Asset reuse, runtime_type: Learning }
              - { term: Validation pass rate, runtime_type: Learning }
