Postep is a self-improvement companion that treats your Emacs Org directories as the source of truth while delivering a touch-first Slate interface on Android and other platforms. It combines a high-performance Rust core with a React Native (Expo) surface so agenda planning, habit tracking, and org-roam knowledge work stay in sync across devices.

• Org-first database: Point Postep at any Org directory (local, Google Drive, or both) and it mirrors the files without converting them to a proprietary format.
• Agenda focus: Render the full Org agenda, including scheduled items, deadlines, and backlog triage, with inline actions to capture, complete, or reschedule tasks.
• Habit coaching: Surface Org habit streaks, punch cards, and trendlines so daily routines stay on track.
• Calendar integration: Map Org timestamps to Google Calendar for reminders and availability overlays while keeping Org as the canonical store.
• Org-roam graph: Explore backlinks, tags, and daily notes from your roam vault to support long-term self-improvement ecosystems.

The detailed architecture blueprint lives in docs/architecture.md with the orgro-inspired Slate UX in docs/ui-redesign.md. At a glance, the stack looks like this:

1. Rust core crates (crates/): Parse Org files, generate agendas, compute habit metrics, sync storage providers, and build org-roam graphs. The crates compile both to native binaries (for tooling) and cdylib targets that feed the UI.
2. TypeScript bridge (packages/bridge, WIP): A napi-rs layer that exposes the Rust services to the Slate UI with declarative hooks (useAgendaQuery, useHabitSignals, useOrgRoamGraph, etc.).
3. Slate UI (apps/mobile, WIP): An Expo (React Native) application using the DOM runtime so Slate renders natively on Android. Screens include Agenda, Habits, Org-roam, and a full Org editor.

This repository is in the middle of migrating from an egui prototype to the Slate architecture. The existing crates remain buildable while the new UI and bridge are being staged.

crates/
  org_core        # Legacy core logic slated to become org_domain + companions
  org_app         # Legacy egui shell kept for desktop testing during migration
docs/
  architecture.md # New architecture blueprint
  android-storage.md # SAF + Google Drive onboarding prototype
mobile/
  android         # NativeActivity wrapper – will be superseded by Expo Android packaging
orgro/
  ...             # Reference sources cloned from the Orgro project

1. Rust toolchain: rustup target add aarch64-linux-android armv7-linux-androideabi x86_64-linux-android
2. Node/Expo toolchain (coming soon): pnpm install inside apps/mobile once the bridge lands.
3. Desktop prototype: cargo run -p org_app still launches the legacy egui app for testing Org parsing changes.
4. Android smoke build: follow mobile/android/README while the Expo pipeline is being bootstrapped.

• Launch the app and open the Library tab. The root manager at the top lets you paste filesystem paths or, on Android, tap Pick via Android SAF to grant access to a Google Drive or local directory.
• Add your main Org directory under “Org Roots” and (optionally) your Org-roam vault under “Org-roam Roots”. The selections are passed to the Rust bridge, registered with OrgSyncService, and synced across the Agenda, Habits, Roam, and Capture screens automatically.
• You can remove roots at any time; the bridge will stop watching them and the UI will refresh to match.

• Set environment variables before launching: ORG_ROOT=/path/to/org cargo run -p org_app.
• For multiple directories use ORG_ROOTS, e.g. ORG_ROOTS="/path/to/org:/path/to/projects" cargo run -p org_app (use ; on Windows).

• Integration tests now generate synthetic Org data on the fly (see crates/org_domain/tests/). Use your own directories in development; the repository does not ship personal Org content.

Expect rapid changes as the bridge and Slate layers come online. See docs/architecture.md for the implementation roadmap and module responsibilities.