Hanus Interface Model

HANUS defines interface as the mediating structure that relates a person’s intention and attention to an organized information environment. The model emphasizes orientation, context, representation, relational structure, and action pathways rather than reducing interface to visible screens and controls.

HANUS is an interface model that treats interface as more than a visible software surface. In this view, interface is the mediating structure through which a person becomes meaningfully related to an organized information system. It connects intention, context, representation, and action so that a system can be navigated and used as a coherent environment rather than as a collection of isolated screens.

Why ordinary definitions of interface are too narrow

In everyday software language, interface is often reduced to presentation: pages, controls, menus, layouts, and styling. That description is useful, but incomplete. A user does not engage a system only by looking at displayed elements. The user must orient within a structured environment, interpret what is present, understand how parts relate, and act in ways that remain intelligible within the system's logic.

When interface is defined too narrowly, design drifts toward appearance without mediation. The result may be visually polished while still leaving the deeper problem unresolved: how a subject becomes operationally connected to structured information. HANUS begins from the claim that interface should be defined at that deeper level.

Emergence of the concept

The HANUS concept emerged through repeated work on portals, network views, data-engine thinking, and systems explanation within the broader Mycite context. Across those efforts, the same design problem kept returning: how to make information legible, navigable, and actionable without collapsing it into disconnected pages or features.

HANUS names the common logic behind those efforts. It is not identical to any single portal, workspace, article, or software component. It is the abstraction that recurs when a system is designed as an environment for orientation and relation rather than as a flat presentation layer.

Definition

The HANUS interface model defines interface as a mediating conceptual structure through which human intention, contextual information, and system action become mutually intelligible and operational.

Several parts of that definition matter. It is mediating because it stands between subject and system, shaping how each becomes legible to the other. It is conceptual because the model is not reducible to any single implementation surface. It is operational because the interface does more than display information; it organizes what can be understood, traversed, and acted upon.

Core components

The recurring components of the model are:

• Orientation: the user's situated relation to the information environment.
• Intention: the purpose or direction that guides movement through the system.
• Context: the conditions that make information meaningful rather than isolated.
• Representation: the forms through which entities, states, and relations become visible.
• Object of attention: the entity, process, or structure with which the user is engaging.
• Action pathway: the available ways a system can be queried, navigated, or transformed.
• Relational structure: the links among parts that make navigation and interpretation possible.

These components do not describe a specific screen layout. They describe the minimum conceptual pieces required for interface to function as mediation.

Interface as mediation rather than presentation

The central claim of HANUS is that interface should be understood as mediation, not merely presentation. Presentation concerns what is shown. Mediation concerns the ordered relation through which a subject encounters, interprets, and acts within a system.

That distinction matters because the same information can be presented in many ways while remaining poorly mediated. A display may expose data without clarifying relation. A dashboard may show metrics without supporting orientation. A page may list entities without making their context or consequences intelligible. HANUS shifts the focus from surface arrangement to the structure that makes meaningful engagement possible.

Independence from implementation

HANUS is not a page template, a user-interface library, or a portal product. A portal can express the model, but the model is not exhausted by that form. The same conceptual structure could appear in a network view, a compositional workspace, a data engine, or another future interface form without losing its identity.

This independence is essential. If the model were tied to one implementation, it would be a pattern or product decision rather than an interface concept. HANUS remains useful precisely because it can guide many implementations while staying distinct from each one.

Architectural implications

Treating interface as mediation changes how systems should be designed.

• Systems should be organized around intelligible relations, not only around visible features.
• Context should travel with representations rather than being treated as optional annotation.
• Navigation should reveal structural relation, not merely offer page-to-page movement.
• Actions should remain interpretable within the broader state of the system.
• Information environments should support orientation before optimization of presentation details.

In practice, this means interface design cannot be separated cleanly from information architecture, relation modeling, and system behavior. Those layers are part of the interface when interface is understood conceptually.

Consequences for networked information systems

HANUS is especially relevant in networked systems where information is distributed, layered, and context-dependent. In those settings, the interface problem is not only how to show data, but how to preserve intelligibility across changing relations, multiple entities, and evolving structures.

The model therefore aligns with a broader concern in structured information work: systems fail when they expose fragments without preserving the relational logic that makes those fragments meaningful. HANUS offers a way to frame interface as the disciplined mediation of that logic.

Conclusion

HANUS should be understood as a conceptual model of interface. It defines interface not as a decorative surface or a narrow UX layer, but as the mediating structure through which human intention, contextualized information, and system action become coherent with one another.

That is why HANUS can guide multiple implementations without being reducible to any one of them. Its importance lies in the stability of the underlying relation it describes: the ordered connection between subject and structured information.