# Product

## Register

product

## Platform

web

## Users

People who live in documents. They read and manage large collections — PDFs and the like — and they produce new documents: text, spreadsheets, presentations. They are working, not browsing; on any given screen they are either reading and organizing a collection, or authoring inside a document. Ziran ships first as a Deno desktop app built on web technology; a web version may follow.

## Product Purpose

Ziran is a document environment built on DASL tiles: a unified, safe document format in which each document carries the code to edit itself. Tiles are local-first and travel without a cloud. A tile saved without its data becomes a model — a template from which new, similar documents are created. With CRDT support, the same document can be edited live by several people at once. Documents can be published to the Atmosphere as tiles. Success means ziran replaces the fragmented document stack — PDF, Word, Google Docs, Excel, Google Sheets, PowerPoint, Keynote, and more — with one medium.

## Positioning

One safe, self-editing document medium — local-first, verifiable, publishable — instead of a shelf of rented apps.

## Brand Personality

Next-generation, liberating, reliable. In order: confident and quietly radical; calm, natural, and unobtrusive; precise, fast, and professional. Familiar enough to trust at first sight, with the ambition showing in the details — the tool recedes and the document is everything. Closest existing reference: Linear, for its crisp, keyboard-first professionalism, but with stronger accents than Linear allows itself.

## Anti-references

- Office ribbon maximalism: toolbars everywhere, every feature visible at once, chrome crowding the document.
- Google-suite blandness: generic Material chrome; competent, interchangeable, no point of view.
- Notion-style SaaS minimalism: gray-on-white, emoji icons, the interchangeable startup look.
- Retro computing nostalgia: terminal aesthetics, pixel fonts, deliberately old-looking.

## Design Principles

1. The document is the interface. Chrome earns its place or disappears; on any screen the user's document, not ziran, is the protagonist.
2. Familiar outside, radical inside. Every surface must be immediately trustworthy to someone arriving from Word or Docs, while the new capabilities — self-editing tiles, models, offline sync, publishing — reveal themselves in the details.
3. Liberation is legible. Local-first, ownership, and portability should be felt in the interface — documents that visibly live on your machine, travel as files, and never depend on a cloud — not just claimed in marketing.
4. One medium, many shapes. Text, tables, and slides are expressions of one document model, and the interface should make that unity perceptible rather than reproducing five app silos inside one window.
5. Reliability is a feeling. Fast, precise, never lossy: every interaction reinforces that documents here are safe — safer than the formats ziran replaces.

## Accessibility & Inclusion

WCAG 2.2 AA for the application UI: contrast, full keyboard support, reduced motion, focus management. Accessible output is a first-class requirement in its own right: documents ziran produces carry real semantics and are screen-reader-grade artifacts, not visual approximations.