human: Given a node-centered hypergraph: <hypergraph>, where nodes represent papers and hyperedges represent sets of papers co-cited by a source paper.

Details of the hypergraph:
Center node: "distributed system contract monitoring"
  Abstract: The use of behavioural contracts, to specify, regulate and verify systems, is particularly relevant to runtime monitoring of distributed systems. System distribution poses major challenges to contract monitoring, from monitoring-induced information leaks to computation load balancing, communication overheads and fault-tolerance. We present mDPi, a location-aware process calculus, for reasoning about monitoring of distributed systems. We define a family of Labelled Transition Systems for this calculus, which allow formal reasoning about different monitoring strategies at different levels of abstractions. We also illustrate the expressivity of the calculus by showing how contracts in a simple contract language can be synthesised into different mDPi monitors.

Connected through hyperedge HE-1 (induced by source paper "who is to blame runtime verification of distributed objects with active monitors"):
  with members:
    - "multiactive objects and their applications"

Connected through hyperedge HE-2 (induced by source paper "a survey of challenges for runtime verification from advanced application domains beyond software"):
  with members:
    - "adventures in monitorability from branching to linear time and back again"
    - "after you please browser extensions order attacks and countermeasures"
    - "selective monitoring"
    - "monitoring data minimisation"
    - "on the monitoring of decentralized specifications semantics properties analysis and simulation"
    - "an algebraic framework for runtime verification"
    - "learning to protect communications with adversarial neural cryptography"
    - "a web based tool for analysing normative documents in english"

Connected through hyperedge HE-3 (induced by source paper "reliability and fault tolerance by choreographic design"):
  with members:
    - "choreographies for automatic recovery"
    - "an abstract semantics of the global view of choreographies"
    - "mutually testing processes"

Connected through hyperedge HE-4 (induced by source paper "device centric monitoring for mobile device management"):
  with members:
    - "efficient runtime monitoring with metric temporal logic a case study in the android operating system"

Connected through hyperedge HE-5 (induced by source paper "improving runtime overheads for detecter"):
  with members:
    - "on synchronous and asynchronous monitor instrumentation for actor based systems"
    - "decentralised ltl monitoring"

Connected through hyperedge HE-6 (induced by source paper "on synchronous and asynchronous monitor instrumentation for actor based systems"):
  with members:
    - "modelling and simulation of asynchronous real time systems using timed rebeca"

Question: Please tell me which class the center node belongs to. The 40 classes are: cs.NA(Numerical Analysis), cs.MM(Multimedia), cs.LO(Logic in Computer Science), cs.CY(Computers and Society), cs.CR(Cryptography and Security), cs.DC(Distributed, Parallel, and Cluster Computing), cs.HC(Human-Computer Interaction), cs.CE(Computational Engineering, Finance, and Science), cs.NI(Networking and Internet Architecture), cs.CC(Computational Complexity), cs.AI(Artificial Intelligence), cs.MA(Multiagent Systems), cs.GL(General Literature), cs.NE(Neural and Evolutionary Computing), cs.SC(Symbolic Computation), cs.AR(Hardware Architecture), cs.CV(Computer Vision and Pattern Recognition), cs.GR(Graphics), cs.ET(Emerging Technologies), cs.SY(Systems and Control), cs.CG(Computational Geometry), cs.OH(Other Computer Science), cs.PL(Programming Languages), cs.SE(Software Engineering), cs.LG(Machine Learning), cs.SD(Sound), cs.SI(Social and Information Networks), cs.RO(Robotics), cs.IT(Information Theory), cs.PF(Performance), cs.CL(Computation and Language), cs.IR(Information Retrieval), cs.MS(Mathematical Software), cs.FL(Formal Languages and Automata Theory), cs.DS(Data Structures and Algorithms), cs.OS(Operating Systems), cs.GT(Computer Science and Game Theory), cs.DB(Databases), cs.DL(Digital Libraries), cs.DM(Discrete Mathematics). Directly output the class name.

gpt: cs.LO(Logic in Computer Science)