Section 17 – Prior Art and Related Systems

JanOS is not conceived in isolation. It draws from several decades of research and practice in operating systems, human–computer interaction, security, distributed systems, and sustainability-aware computing.

Rather than attempting to supersede this body of work, JanOS is intentionally situated within it. This section reviews selected prior efforts that inform the design, and clarifies how JanOS differs in scope, emphasis, and synthesis.

Clean-Slate Operating System Research

Several research systems have explored clean-slate operating-system design, often motivated by safety, verification, or architectural clarity. Notable examples include:

• EROS/CapROS/Coyotos: capability-based systems emphasizing strict isolation and provable security
• Microsoft Singularity: a managed-code operating system focused on software isolation
• Barrelfish: a multi-kernel architecture designed for heterogeneous and multicore environments
• IBM System/38 and AS/400 lineage: object-based systems with unusually coherent storage and execution models.

These systems demonstrate that rethinking kernel boundaries and execution models is both possible and valuable. However, they largely focus on machine-centric concerns such as isolation, verification, and scalability. JanOS extends the clean-slate tradition toward human-centric concerns: intent, semantic storage, narrative time, and organizational context.

Declarative User Interface Models

Modern application frameworks increasingly separate interface description from rendering. Examples include:

• React
• SwiftUI
• QML
• XAML and related technologies.

These systems show the practical benefits of declarative UI models at the application level. JanOS builds on this idea by treating declarative interfaces as an operating-system concern rather than an application framework feature. This enables system-enforced consistency, accessibility guarantees, and policy-driven adaptation across all applications.

The contribution of JanOS is not the declarative paradigm itself, but its elevation to a system-level abstraction.

Versioned and Semantic File Systems

Prior systems have introduced versioning, snapshotting, or alternative storage abstractions, including:

• ZFS
• APFS
• Plan 9’s file model
• WinFS (unreleased).

These systems improve reliability, recovery, or organization, but typically treat versioning and history as technical artifacts rather than as representations of human work. JanOS differs in that storage is organized around intent, tasks and narrative progression. Versions correspond to meaningful transitions in work, and time is treated as a semantic dimension rather than a sequence of blocks.

Identity-Centric Computing and Zero-Trust Models

Identity-focused approaches such as Zero Trust architectures, OAuth/OIDC, capability systems, and cloud identity platforms emphasize authentication, authorization, and perimeter reduction.

JanOS incorporates these ideas but embeds identity more deeply: at the level of applications, actions, storage access and intent. Identity in JanOS is not only a security mechanism, but a foundation for attribution, accountability and interpretability across the system.

Telemetry, Observability and Usage Analytics

Existing observability platforms focus on statistical telemetry, performance metrics, and error aggregation. While valuable, these systems are typically disconnected from human intent and rely on continuous data collection.

JanOS introduces intent-level observability, where signals relate to completed work rather than raw interaction streams. Insights are derived from task outcomes and contextual patterns, allowing shared learning without persistent behavioral monitoring.

Carbon-Aware and Environmental Scheduling

Research and industrial efforts have explored carbon-aware scheduling primarily in data-center and high-performance computing contexts.

JanOS extends this awareness to end-user systems and organizational workflows, integrating environmental context into everyday computing decisions. The novelty lies not in optimization algorithms, but in treating environmental context as a first-class system input alongside intent and policy.

Visualization, Narrative, and Temporal Computing

Work in visualization, simulation, and workflow representation has explored spatial and temporal metaphors for complex systems.

JanOS draws inspiration from these approaches while applying them to operating-system state itself. Optional visualizations may reflect system evolution, task history, and compatibility over time, providing a human-aligned representation of change rather than a purely diagnostic view.

These visualizations are intended to support comprehension and memory, not to gamify activity or aestheticize behavior.

Summary

Many of the technical components underlying JanOS have clear predecessors in existing research and systems.

JanOS is structured around:

• human intent as a first-class system entity
• explicit recognition of completion and closure
• semantic, narrative-oriented storage
• identity and lineage as interpretive foundations
• constrained, accountable AI assistance
• environmental context as part of system reasoning.

In this sense, JanOS belongs to an established lineage while deliberately shifting the axis of system design. It is informed by prior work but explores a conceptual space that earlier systems were not designed to inhabit.