Continuity Pillars: Persistent Dev Environment

This library is about continuity of work: a dev environment that keeps running, keeps state, and stays usable across disconnects, switches, and long gaps. It is not about a device. It is about time and state.

If you want the live system behind this thinking:

• Phone Terminal Codex: /phone-terminal-codex/
• Pricing: /pricing/

Pillar pages (money pages)

Persistent Dev Environment

A dev environment that never resets, keeps state, and survives long-running sessions.

• /persistent-dev-environment/

Always-On Terminal Workspace

The terminal as a durable workspace you can resume without re-running context.

• /always-on-terminal-workspace/

Remote Development Without Reconnect Friction

Remote dev without babysitting SSH or losing context on reconnects.

• /remote-development-without-reconnect-friction/

Jupyter / Codespaces Alternatives

Comparison traffic for teams outgrowing notebook and cloud IDE workflows.

• /jupyter-codespaces-alternatives/

Session Persistence & Output Replay

Why replayable output and resumable sessions matter for real work.

• /session-persistence-output-replay/

Supporting pages (gravity wells)

Each supporting page teaches one idea and links upward to a pillar.

Persistent Dev Environment

• /why-dev-environments-reset/
• /stateless-vs-stateful-dev-environments/
• /long-running-dev-sessions/
• /terminal-dies-mid-task/

Always-On Terminal Workspace

• /what-is-a-terminal-workspace/
• /why-tmux-isnt-enough/
• /terminal-sessions-vs-workspaces/
• /resume-terminal-after-disconnect/

Remote Dev Without Reconnect Friction

• /why-ssh-drops-break-deep-work/
• /remote-dev-without-babysitting/
• /latency-vs-continuity-remote-dev/
• /reconnecting-is-wrong-abstraction/

Jupyter / Codespaces Alternatives

• /when-jupyter-falls-apart/
• /why-codespaces-feels-slow/
• /cloud-ide-vs-persistent-terminal/
• /what-colab-optimizes-for/

Session Persistence & Output Replay

• /why-replayable-output-matters/
• /reproducibility-outside-notebooks/
• /debug-long-running-jobs-without-reruns/

More supporting pages: /continuity/supporting/

How this maps to the product

The product is a persistent dev environment that stays alive across time and device changes. The terminal is the interface; the continuity is the value. Every pillar and supporting page points back to:

• /phone-terminal-codex/
• /pricing/