The System Architect role in PEGA primarily works with Properties and data modeling, defining the data structure and property definitions for applications. While flows and harnesses are important, they are typically owned by Process Architects or Developers. Correspondence rules are template-based and not the primary focus of System Architects.