Skip to content

User Interface

Minyu’s user interface is designed for continuous, professional back-office work. It is built around the assumption that users work with complex, related information over extended periods, not isolated screens or single tasks.

Rather than separating search, analysis, and navigation into disconnected tools, Minyu provides a unified workspace where all interaction is driven directly by the data model, its relations, and its rules.

A workspace that preserves context

On desktop, Minyu uses a snap-based window manager that allows users to work with multiple views side by side, stacked into tabs, or arranged into reference panels. Layouts, open views, filters, and navigation state are persisted across sessions, allowing work to resume exactly where it was left off.

This is critical for investigative workflows where users move back and forth between datasets, individual records, rules, and audit trails without losing context.

Instead of forcing users through linear navigation, Minyu supports parallel thinking: comparing data, validating assumptions, and making changes while keeping the broader picture visible.

Minyu offers two primary ways of exploring data, both operating on the same underlying model.

The Data Explorer is optimized for high-volume analysis. Users build datasets by selecting a source table, traversing relations, and applying classifications as filters. Once loaded, filtering, grouping, sorting, and inline editing happen directly in the browser, enabling fast, exploratory work without repeated server round-trips.

The Data Navigator is optimized for record-centric traversal. Starting from any record, users can follow relations transitively while preserving a visible navigation trail that shows exactly how they arrived at the current context. This makes deep, multi-step investigations predictable and reversible rather than fragile.

Both views enforce the same permissions, rules, and classifications. They differ only in how users choose to explore the model.

Minyu provides a single global search that operates across the entire system. Users do not need to know which table to search in. Results are ranked and presented based on relevance and relationships, not just text matching.

Search respects read rules and classifications, meaning users only ever see results they are allowed to see. In practice, search becomes another way of traversing the model — complementary to navigation rather than separate from it.

Visualizing time, structure, and aggregates

Because all views are model-driven, Minyu can project the same underlying data into different representations without duplicating logic.

The Calendar View renders date and date-range data into structured temporal layouts without introducing a separate calendar schema. Any valid relational path to a time range can be visualized, and all rules and permissions apply identically.

The Charts View provides schema-based, multi-dimensional analysis directly on the relational model. Charts can traverse relations, combine dimensions, and aggregate values while respecting read rules — meaning different users may see different values from the same chart definition.

Because these views are derived from the model, they evolve automatically as the schema changes.

Understanding the system as a whole

For administrators and advanced users, Minyu exposes an Architecture View that visualizes tables, relations, filters, and rules as a live dependency graph. This makes it possible to understand how structure and behavior are connected before making changes, reducing risk in complex systems.

One interface, many perspectives

What ties all of this together is that Minyu does not have separate interfaces for browsing, searching, reporting, or scheduling. Instead, it offers multiple perspectives on the same model.

Search, navigation, charts, calendars, and workspaces all operate on the same definitions of structure, meaning, and access. Users do not need to reconcile conflicting views of the system — the interface consistently reflects how the organization has chosen to model itself.

In Minyu, the UI is not a layer on top of the system. It is how the system is explored.