Skip to content

Related Work

POOKA is not developed in isolation. It builds upon concepts that have emerged across multiple disciplines, including Information Architecture, Software Architecture, Knowledge Management, Identity & Access Management, Object-Oriented Design, graph-based modeling and Human–Computer Interaction.

Rather than replacing these disciplines, POOKA brings together selected principles within a single architectural perspective focused on sustainable Human–AI collaboration.

Source of truth

Each perspective below carries its opening statement verbatim from Chapter 6: Existing Perspectives, which remains authoritative and describes for each discipline both what POOKA adopts and where it differs. The bibliography collects the underlying literature.

Information Architecture

Traditional Information Architecture focuses on organizing, structuring and presenting information so that it can be effectively understood and accessed by people.

Section 6.1 in the Design Paper

Knowledge Management

Knowledge Management addresses the creation, organization, sharing and preservation of organizational knowledge.

Section 6.2 in the Design Paper

Object-Oriented Design

Object-Oriented Design introduced concepts such as encapsulation, composition and explicit relationships between objects.

Section 6.3 in the Design Paper

Domain-Driven Design

Domain-Driven Design emphasizes the importance of modeling complex domains through explicit language, bounded contexts and domain concepts.

Section 6.4 in the Design Paper

Identity & Access Management

Identity & Access Management defines how identities are authenticated, authorized and represented within digital systems.

Section 6.5 in the Design Paper

Graph-Based Modeling

Graph-based models represent knowledge through nodes and explicit relationships.

Section 6.6 in the Design Paper

Local-First Computing

Local-First Computing promotes user ownership, resilience and long-term control over information.

Section 6.7 in the Design Paper

Software Architecture

Software Architecture is concerned with the structure of software systems, including their components, responsibilities and the principles that guide their design and evolution.

Section 6.8 in the Design Paper

Human–Computer Interaction

Human–Computer Interaction studies how people interact with computing systems and how those systems can be designed to support human understanding and control.

Section 6.9 in the Design Paper

Context-Aware Computing

Context-Aware Computing studies how systems can perceive and respond to the situation in which they are used. Within this field, context is commonly understood as any information that characterizes the situation of an entity.

Section 6.10 in the Design Paper

Provenance Models

Provenance models, such as the W3C PROV family of specifications, describe how information came into existence by modeling entities, activities and agents, including agents acting on behalf of other agents.

Section 6.11 in the Design Paper

Personal Data Stores

Personal data store initiatives, such as Solid, place personal information under the control of an identity and allow applications and agents to access that information through explicit permissions.

Section 6.12 in the Design Paper

Multi-Agent Systems

Research on multi-agent systems addresses how autonomous software agents cooperate, including how norms and organizational rules constrain agent behavior.

Section 6.13 in the Design Paper

Positioning

POOKA should not be viewed as an alternative to these disciplines. Instead, it can be understood as an architectural synthesis that combines established concepts into a coherent model for Human–AI Information Architecture.

Its contribution lies not in replacing existing theories, but in connecting them within a common architectural language designed specifically for collaboration between humans and AI.

As the Discussion states: the primary contribution of POOKA is not the invention of entirely new concepts, but the architectural synthesis of existing principles into a model that explicitly separates information, governance and behavior while treating context as a persistent architectural construct rather than transient conversational state.

Read Chapter 6: Existing Perspectives · Read section 6.14: Positioning · Bibliography