Arpeggio AWARE investigates the intersection of socio-technical systems involving software development, systems science, distributed systems engineering, and cloud-native resilience. Our work spans theoretical foundations and applied practice.
"Life is the present experience. Experience begins with awareness."
— Buckminster Fuller
Focus Areas
Systems Science
Complex systems thinking applied to software infrastructure. Feedback dynamics, emergence, and non-linear behavior in large-scale socio-technical systems. We draw on cybernetics, network theory, and dynamical systems to inform design.
Socio-Technical Systems
The social dynamics of software development — how teams, organizations, and communities shape (and are shaped by) the technical systems they build and operate. We study the interplay between human coordination and system architecture.
Distributed Systems Engineering
Coordination protocols, consensus mechanisms, and fault-tolerant architectures. We study how systems that span nodes, networks, and organizational boundaries maintain correctness and liveness under real-world conditions.
Cloud-Native Resilience
Building systems that are observable by default and degrade gracefully under stress. Structured observability (logs, metrics, traces), adaptive load management, chaos engineering methodology, and the human factors of incident response.
Learning and Self-Improving Systems
How people, teams, and the systems they build learn together — and how that mutual learning changes all of them. We study the conditions under which socio-technical systems become contexts for genuine co-evolution, including computer science education research and the design of environments that support both independent inquiry and collaborative sense-making.
"Value judgments are destructive to our proper business, which is curiosity and awareness."
― John Cage
How We Work
We learn by doing. Our research philosophy centers on building real things — tools, prototypes, systems — and treating the act of building as a primary mode of inquiry. Theory informs practice, and practice interrogates theory. The loop between them is where understanding lives.
Our research process is an arpeggio — each cycle plays the same notes in ascending sequence, but every pass through deepens understanding. Like PDCA reframed for applied research, each step lifts us higher before we loop back to begin again:
- Inquiry — notice something, ask a question, follow a thread
- Hypothesize — frame the question, state assumptions explicitly
- Experiment — build something, run something, try something
- Reflect — what happened? what surprised us? what did we learn?
- Adapt — revise understanding, adjust the next hypothesis
- Sharing — publish, present, teach, contribute back
Documentation is a continuous practice woven through every turn of the cycle.
"Awareness of universals is called conceiving, and a universal of which we are aware is called a concept."
— Bertrand Russell. The Problem of Philosophy