10. Architectural Patterns¶
POOKA defines an architectural style rather than a single architecture. As a result, multiple architectural patterns may conform to POOKA while serving different purposes, scales and organizational contexts.
The following patterns illustrate how the Core Concepts may be combined without prescribing specific technologies, software platforms or implementation approaches.
10.1 Personal Knowledge Environment¶
A Personal Knowledge Environment represents the information architecture of a single Identity.
The Identity owns one or more Domains containing Contexts, Artifacts, Relations and Semantics. Human Actors, AI assistants and technical systems may collaborate through explicit Delegation while operating within the same architectural model.
This pattern provides a persistent information architecture independent of individual AI conversations.
10.2 Shared Knowledge Environment¶
A Shared Knowledge Environment enables multiple Identities to collaborate within a common Ecosystem.
Each Identity retains its own governance while sharing selected Domains, Contexts or Artifacts through explicitly defined Boundaries and Delegations.
The architecture supports collaboration without requiring ownership, authority or behavioral responsibilities to become implicit.
10.3 Organizational Knowledge Environment¶
Organizations often consist of multiple Domains, teams, departments and operational responsibilities.
POOKA enables these organizational structures to be represented explicitly while allowing human Actors, AI systems and technical services to operate within clearly defined architectural Boundaries.
Governance remains separated from implementation technology, allowing organizational responsibilities to evolve independently of software systems.
10.4 Distributed Knowledge Environment¶
Knowledge increasingly exists across multiple applications, cloud services, repositories and devices.
Rather than attempting to centralize all information, POOKA allows distributed information sources to participate within a common architectural model, provided their semantics, relationships and governance remain explicit.
The architecture therefore emphasizes conceptual consistency rather than physical centralization.
10.5 Federated Knowledge Environment¶
Independent Ecosystems may collaborate without becoming a single architecture.
Federation allows information, Contexts and selected Artifacts to be shared across Ecosystem Boundaries while preserving the autonomy, governance and Identity of each participating Ecosystem.
This pattern supports collaboration between individuals, organizations and technical platforms without requiring complete architectural integration.
10.6 Pattern Independence¶
These patterns are illustrative rather than exhaustive.
POOKA intentionally does not prescribe how architectural concepts should be combined for specific use cases. Additional patterns may emerge as practical experience with Human–AI Information Architecture evolves.
Conformance to POOKA is determined by adherence to its architectural principles and Core Concepts rather than by adopting a predefined architectural pattern.