Workflow

A deliberate path from private memory work to public story publishing.

Sipura is structured to keep private archive work bounded while still making selective public publishing easy.

Capture and shape

Build the archive privately in the app through spoken memories, interviews, media, and AI-assisted structure.

Choose the public-safe version

Before publishing, Sipura exports only the story title, approved narrative, and any public-safe assets.

Publish to a stable page

Each published story receives a stable URL on sipura.space, ready for family, collaborators, or the public.

Revise without breaking the link

Republishing refreshes the page content while preserving the same story address whenever the slug stays the same.

Guardrails

The workflow is designed to reduce accidental oversharing.

Private by default

Sipura is not a silent cloud sync product. The device remains the primary home of private story content unless a user explicitly invokes cloud-backed features.

Publishing is explicit

Public pages are generated from a bounded export. Publishing is not a live mirror of every private edit, transcript, or note.

Public-safe fields only

Raw transcripts, private notes, private graph relationships, and full edit history stay outside the public page by design.