@aitne-sh/aitne 0.1.0

package/agent-assets/docs/features/routines/morning-routine.md

@@ -0,0 +1,123 @@
+---
+schema_version: 1
+slug: features/routines/morning-routine
+title: Morning Routine
+id: morning-routine
+aliases:
+  - morning_routine
+  - daily morning routine
+  - morning report
+  - morning briefing
+category: features
+summary: |
+  The autonomous routine that runs once per agent-day at the configured
+  morning hour to produce today.md and the day's plan.
+section: routines
+tags:
+  - routine
+  - autonomous
+  - daily
+  - heavy-tier
+  - core
+status: stable
+ask_examples:
+  - When does morning routine run?
+  - How do I disable morning routine?
+  - Where does its output go?
+  - What model does morning routine use?
+locale: en-US
+created: 2026-04-25
+updated: 2026-04-25
+keywords:
+  - morning
+  - day plan
+  - 04:00
+  - day boundary
+related:
+  - concepts/agent-day
+  - features/memory-files/today
+prerequisites:
+  - concepts/agent-day
+ui_anchors:
+  - /settings/routines
+  - /
+process_keys:
+  - routine.morning_routine
+  - routine.morning_routine_initial
+config_keys:
+  - dayBoundaryHour
+context_files:
+  - today.md
+  - daily/<date>.md
+---
+
+# Morning Routine
+
+## In One Sentence
+
+Once per agent day, at `dayBoundaryHour` local time, Aitne
+rebuilds `today.md` and the day's schedule from your calendar, mail,
+roadmap, and recent observations.
+
+## What It Does
+
+The morning routine is the single highest-value process in Aitne.
+It runs at the **heavy tier** (default Opus 4.7 on Claude, GPT-5.5 on
+Codex, Gemini 3 Pro on Gemini) because every downstream routine for
+the next 24 hours reads its output. A bad morning briefing degrades
+the entire day.
+
+In sequence, the routine:
+
+1. Reads the previous day's `today.md` and rolls forward unfinished items.
+2. Pulls today's calendar events from any connected calendar integration.
+3. Scans recent unread mail and surfaces the few that need owner attention.
+4. Walks the roadmap looking for items whose **Preparation Timeline** rows fire today.
+5. Consumes any pending observations the hourly check has already dropped into the queue.
+6. Writes the rebuilt `today.md` and the per-date snapshot at `daily/YYYY-MM-DD.md`.
+7. Logs a single status line to the dashboard activity feed.
+
+## When It Runs / How It Is Triggered
+
+The morning routine fires at **`dayBoundaryHour`** local time (default
+`4`). The scheduler uses the agent-day boundary, not the calendar day,
+so a post-midnight install does not run two morning routines back-to-back.
+There is no separate `morningRoutineHour` — the morning routine and the
+agent-day rollover are the same instant.
+
+`routine.morning_routine_initial` is a one-shot heavy-tier variant fired
+during the setup wizard's first day. After the first run, only
+`routine.morning_routine` triggers.
+
+## What It Outputs
+
+- A rebuilt `today.md` with sections for User Schedule, Tasks, Agent Plan, Agent Log, and Handoff.
+- A per-date `daily/YYYY-MM-DD.md` capturing the day's calendar snapshot.
+- A short notification ("Good morning, here's today...") when notifications are enabled and quiet hours have ended.
+- An entry in the Activity feed.
+
+## Where in the Dashboard
+
+- **Schedule view** — the column for today is rebuilt against the new schedule file.
+- **Activity feed** — a `routine.morning_routine` row appears at the run timestamp.
+- **Settings → Models** — the routine's backend, model, max-turns, and budget cap are configured here.
+
+## Configuration
+
+| Setting | Default | Notes |
+|---|---|---|
+| `dayBoundaryHour` | `4` | Both the agent-day boundary and the morning-routine fire time. See [Agent Day](../../concepts/agent-day.md). |
+| Tier (heavy/light) | heavy | Forced heavy by default — Sonnet/Flash routines tend to skip critical context. |
+| Max turns | 50 (router cap, P95+) | Adjustable per-process in Settings → Models. |
+| Max budget USD | 5.00 | Per-execute cap. The router enforces this before token costs accumulate. |
+
+## When Something Goes Wrong
+
+- The most common failure is **morning routine did not run** because the daemon was offline at the trigger window. The next launch picks the run up via the catch-up scheduler if it is still the same agent day.
+- A failed morning routine emits a fallback-success notification when the secondary backend caught the run, or a fallback-failed notification (high priority) when both failed.
+- Heavy-tier quota exhaustion (Claude Max5/Max20 5-hour Opus window) is the second most common cause. Switch the routine's model to a different heavy-tier option in Settings → Models or wait out the window.
+
+## Related
+
+- [Agent Day](../../concepts/agent-day.md) — boundary semantics that shift "today".
+- [today.md](../memory-files/today.md) — the file the routine rebuilds.

package/agent-assets/docs/features/routines/weekly-review.md

@@ -0,0 +1,70 @@
+---
+schema_version: 1
+slug: features/routines/weekly-review
+title: Weekly Review
+id: weekly-review
+aliases:
+  - weekly retro
+  - sunday review
+category: features
+summary: |
+  Once a week, the agent reads the past seven days of journal
+  entries, completed tasks, and roadmap progress, then writes a
+  weekly retro into the weekly/ directory.
+section: routines
+tags:
+  - routine
+  - autonomous
+  - light-tier
+status: stable
+ask_examples:
+  - When does the weekly review run?
+  - What does the weekly retro look at?
+  - Where do weekly retros get stored?
+locale: en-US
+created: 2026-04-25
+updated: 2026-04-25
+related:
+  - concepts/routines
+  - features/memory-files/agent-journal
+process_keys:
+  - routine.weekly_review
+---
+
+# Weekly Review
+
+## In One Sentence
+
+A light-tier weekly retro fires once per week and writes a synthesis
+into `weekly/<YYYY-MM-DD>.md`.
+
+## What It Does
+
+- Reads journal entries since the last weekly retro.
+- Reads completed tasks and roadmap movement.
+- Writes a synthesis: what shipped, what slipped, what surprised.
+
+## When It Runs / How It Is Triggered
+
+Every **Friday at 18:00 local time**. The schedule is fixed in
+`packages/daemon/src/core/scheduler.ts` and is not operator-configurable.
+
+## What It Outputs
+
+- One file per week under `~/.personal-agent/context/weekly/`.
+
+## Configuration
+
+This routine has no operator-tunable knobs. The fire time, day-of-week,
+and tier are fixed in code.
+
+## When Something Goes Wrong
+
+- The retro **doesn't fire**: catch-up does not span more than one
+  week — if the daemon was offline for several days the retro is
+  skipped.
+
+## Related
+
+- [Evening Review](evening-review.md)
+- [Monthly Review](monthly-review.md)

package/agent-assets/docs/getting-started/01-what-is-this.md

@@ -0,0 +1,192 @@
+---
+schema_version: 1
+slug: getting-started/01-what-is-this
+title: What is Aitne?
+id: what-is-this
+category: getting-started
+summary: |
+  Aitne is a local-first proactive personal AI agent. It runs
+  as a daemon on your own machine, uses your Claude / Codex / Gemini
+  subscription, and stores all memory as plain Markdown files.
+section: getting-started
+tags:
+  - core
+  - getting-started
+status: stable
+ask_examples:
+  - What is Aitne?
+  - How is this different from ChatGPT?
+  - Where does my data live?
+  - What can Aitne actually do for me?
+locale: en-US
+created: 2026-04-25
+updated: 2026-04-27
+related:
+  - getting-started/02-first-steps
+  - getting-started/03-what-can-this-do
+  - getting-started/04-first-day
+  - concepts/memory-model
+  - concepts/backends-and-tiers
+---
+
+# What is Aitne?
+
+Aitne is a local-first personal AI agent. It runs as a long-running
+daemon on your own machine, uses an LLM subscription you already own
+(Claude, Codex, or Gemini), and keeps all of its memory as plain
+Markdown files under `~/.personal-agent/`.
+
+Unlike a chat assistant that only responds when you type, Aitne also
+runs on its own — on a schedule, in reaction to changes it sees in
+your apps, or when you DM it from a messenger.
+
+## What It Can Do
+
+### Run on a schedule
+
+Aitne can run [routines](../concepts/routines.md) without being asked.
+By default:
+
+- Every morning, it reads your calendar, unread mail, open tasks, and
+  recent notes, and writes today's plan into
+  [`today.md`](../features/memory-files/today.md).
+- Every evening, it reviews how the day went and updates
+  [`journal.md`](../features/memory-files/agent-journal.md).
+- Once a week and once a month, it rolls those journals up.
+- Once an hour during active hours, it checks
+  [observations](../concepts/observations.md) it has collected from
+  the integrations below.
+
+You can change the times, disable any of them, or add your own.
+
+→ [Morning Routine](../features/routines/morning-routine.md) ·
+[Evening Review](../features/routines/evening-review.md) ·
+[Hourly Check](../features/routines/hourly-check.md) ·
+[Custom Routines](../features/routines/custom-routines.md)
+
+### Reach you through a messenger
+
+When something the agent notices needs your attention — a moved
+meeting, a flight confirmation it wants to file, a reply you said
+you'd send — it can DM you. You can also DM it back to ask questions
+or give instructions.
+
+Supported channels:
+
+- [Telegram](../features/messaging/telegram.md)
+- [Slack](../features/messaging/slack.md)
+- [Discord](../features/messaging/discord.md)
+- [WhatsApp](../features/messaging/whatsapp.md)
+- [Dashboard chat](../features/messaging/dashboard-chat.md) (built in)
+
+Pairing is one-time per channel.
+
+→ [Messaging Overview](../features/messaging/overview.md) ·
+[Pairing & Magic Phrase](../features/messaging/pairing-and-magic-phrase.md)
+
+### Watch the apps you connect
+
+When you connect an integration, the agent polls it on a schedule and
+records anything that looks relevant as an
+[observation](../concepts/observations.md). The hourly routine then
+decides what (if anything) is worth telling you about.
+
+- [Mail](../features/integrations/mail.md) — Gmail, Outlook, Yahoo,
+  iCloud, or any IMAP server. Searches your messages locally via
+  FTS5. Auto-classifies into
+  [reading list](../features/lifestyle/reading.md),
+  [receipts](../features/lifestyle/receipts.md), and
+  [travel bookings](../features/lifestyle/travel-bookings.md).
+- [Calendar](../features/integrations/calendar.md) — including
+  [travel-time](../features/lifestyle/travel-time.md) lookups before
+  events.
+- [Obsidian](../features/integrations/obsidian.md) — watches a vault
+  for new notes.
+- [Notion](../features/integrations/notion.md) — watches selected
+  pages and databases.
+- [Git](../features/integrations/git.md) /
+  [GitHub](../features/integrations/github.md) — watches local repos
+  and tracked GitHub repositories.
+
+### Remember things in plain Markdown
+
+Everything the agent learns about you is written as Markdown files
+you can read, edit, and version yourself. Nothing important lives in
+an opaque vector store.
+
+- [`user/profile.md`](../features/memory-files/user-profile.md) —
+  what the agent knows about you.
+- [`projects/*.md`](../features/memory-files/projects.md) — one file
+  per active project.
+- [`roadmap.md`](../features/memory-files/roadmap.md) — longer-term
+  goals.
+- [`schedule/YYYY-MM-DD.md`](../features/memory-files/schedule.md) —
+  per-day plans.
+- [`today.md`](../features/memory-files/today.md) — today's plan.
+- [`agent/journal.md`](../features/memory-files/agent-journal.md) —
+  what the agent did and noticed.
+
+→ [Memory Model](../concepts/memory-model.md)
+
+### Use the LLM subscription you already have
+
+You can point Aitne at one or more of your existing subscriptions.
+Each kind of work (heavy reasoning vs. a quick reply) is mapped to a
+backend; you can change the mapping any time.
+
+- Claude (via Claude Code)
+- Codex (via Codex CLI)
+- Gemini (via Gemini CLI)
+
+→ [Backends and Tiers](../concepts/backends-and-tiers.md) ·
+[Costs and Quotas](../concepts/costs-and-quotas.md) ·
+[Backend Routing](../features/operations/backend-routing.md)
+
+### Stay within limits you set
+
+- [Quiet hours](../features/operations/quiet-hours.md) — windows
+  during which the agent will not DM you or run autonomous routines.
+- [Approvals](../features/operations/approvals.md) — write actions
+  the agent must ask about before executing.
+- An always-disallowed list of operations the agent cannot perform
+  even with permission widened (see
+  [safety model](../concepts/safety-model.md)).
+- No automated social posting and no financial transactions, by
+  design.
+
+→ [Safety Model](../concepts/safety-model.md) ·
+[Safety and Execution](../concepts/safety-and-execution.md)
+
+## What It Is Not
+
+- **Cloud-hosted**: nothing leaves your machine except per-turn LLM
+  calls (and only the prompt text, not your raw vault).
+- **Multi-user**: single-owner by design. DMs and mentions only;
+  group chats are filtered out.
+- **An IDE plugin**: Claude Code is one of its backends, but the
+  agent daemon is the surface, not the editor.
+- **A separate subscription**: Aitne itself does not bill you; you
+  pay your LLM provider directly.
+
+## Where to Start
+
+If the dashboard is already open, the daemon is running — start here:
+
+- [First Steps](02-first-steps.md) — finish the setup wizard, pair
+  messaging.
+- [What This App Can Do](03-what-can-this-do.md) — the full
+  capability tour with one-line summaries.
+- [Your First Day](04-first-day.md) — what to expect once the agent
+  starts running on its own.
+
+If you are still installing:
+
+- [Install and Run](../guides/install-and-run.md)
+- [CLI Commands](../reference/cli-commands.md)
+
+## Related
+
+- [Memory Model](../concepts/memory-model.md)
+- [Backends and Tiers](../concepts/backends-and-tiers.md)
+- [Routines](../concepts/routines.md)
+- [Agent Day](../concepts/agent-day.md)

package/agent-assets/docs/getting-started/02-first-steps.md

@@ -0,0 +1,80 @@
+---
+schema_version: 1
+slug: getting-started/02-first-steps
+title: First Steps in the Dashboard
+id: first-steps
+category: getting-started
+summary: |
+  What to do the moment the dashboard opens — finish the setup wizard,
+  pair a messaging app, and arrive at a green health pill.
+section: getting-started
+tags:
+  - core
+  - getting-started
+status: stable
+ask_examples:
+  - I just opened the dashboard. What now?
+  - How do I get the agent to talk to me?
+  - Do I have to connect every integration?
+locale: en-US
+created: 2026-04-27
+updated: 2026-04-27
+related:
+  - getting-started/01-what-is-this
+  - getting-started/03-what-can-this-do
+  - getting-started/04-first-day
+  - guides/setup-wizard
+---
+
+# First Steps in the Dashboard
+
+## Goal
+
+Get from a fresh dashboard to "the agent can reach me" — a green
+health pill, a paired messaging app, and a backend the agent can call.
+
+## What you should see right now
+
+If the dashboard just opened, you are on `/setup` — the setup wizard.
+The dashboard refuses to leave this page until the minimum is filled
+in (a backend, a messaging pair). Run through it once, top to bottom.
+
+## Steps
+
+1. **Finish the setup wizard.** Each step is small and rerunnable.
+   The walkthrough — what each step asks for and why — lives in
+   [Setup Wizard](../guides/setup-wizard.md).
+2. **Pair at least one messaging app.** Telegram is the easiest. The
+   wizard's Messaging step prints a magic phrase you DM to the bot;
+   the daemon claims you as the owner. See
+   [Messaging Overview](../features/messaging/overview.md) for the
+   list of supported apps and what each one does well.
+3. **Pick a main backend and plan.** This is the LLM the agent uses
+   for "think hard" turns. Defaults are sensible; you can change it
+   later from `/settings/models`. Background:
+   [Backends and Tiers](../concepts/backends-and-tiers.md).
+4. **Skip integrations you do not need yet.** Mail, calendar, git,
+   Notion, Obsidian are all optional and re-runnable any time from
+   `/connections`.
+
+## Verification
+
+- The Overview page (`/`) shows a green health pill.
+- The Messaging card lists at least one paired app.
+- A DM you send from the paired app shows up in
+  `/activity` within a few seconds.
+
+## If It Fails
+
+- Can't get past a wizard step → check `pnpm logs` and look for the
+  underlying daemon error. Most failures are credential-shape issues.
+- Backend won't authenticate → see [Auth Failed](../troubleshooting/auth-failed.md).
+- Messaging never claims you → see [Messaging Not Pairing](../troubleshooting/messaging-not-pairing.md).
+
+## Related
+
+- [What is Aitne?](01-what-is-this.md) — the orientation.
+- [What This App Can Do](03-what-can-this-do.md) — once setup is
+  done, here is the tour.
+- [Your First Day](04-first-day.md) — what happens once the agent
+  starts running on its own.

package/agent-assets/docs/getting-started/03-what-can-this-do.md

@@ -0,0 +1,110 @@
+---
+schema_version: 1
+slug: getting-started/03-what-can-this-do
+title: What This App Can Do
+id: what-can-this-do
+category: getting-started
+summary: |
+  A tour of Aitne's capabilities at a beginner-friendly
+  granularity, with a link to the detailed feature doc for each.
+section: getting-started
+tags:
+  - core
+  - getting-started
+  - overview
+status: stable
+ask_examples:
+  - What can Aitne actually do?
+  - What features should I try first?
+  - How does the agent reach out to me?
+locale: en-US
+created: 2026-04-27
+updated: 2026-04-27
+related:
+  - getting-started/01-what-is-this
+  - getting-started/02-first-steps
+  - getting-started/04-first-day
+  - concepts/routines
+  - concepts/memory-model
+---
+
+# What This App Can Do
+
+A short tour. Each capability has a one-line summary plus a link to
+the doc that goes deep.
+
+## Plan your day, on its own
+
+The agent runs **routines** on a schedule. The morning routine builds
+`today.md` from your calendar, mail, tasks, and notes; the evening
+review writes a journal entry; weekly and monthly summaries roll up.
+
+- [Routines](../concepts/routines.md) — what runs and when.
+- [Morning Routine](../features/routines/morning-routine.md)
+- [Evening Review](../features/routines/evening-review.md)
+
+## Talk to it from any messaging app
+
+DM the agent from Telegram, Slack, Discord, WhatsApp, or the
+dashboard's own chat. It answers, remembers, and can DM you back when
+something comes up.
+
+- [Messaging Overview](../features/messaging/overview.md) — supported
+  apps and how pairing works.
+- [Dashboard Chat](../features/messaging/dashboard-chat.md) — the
+  in-dashboard chat surface.
+
+## Watch what changes around you
+
+Mail, calendar, git repos, your Obsidian vault, and Notion — the
+agent watches the ones you connect and reacts when something worth
+noticing happens.
+
+- [Mail](../features/integrations/mail.md)
+- [Calendar](../features/integrations/calendar.md)
+- [Git](../features/integrations/git.md)
+- [Obsidian](../features/integrations/obsidian.md)
+- [Notion](../features/integrations/notion.md)
+
+## Remember things in plain Markdown
+
+Everything the agent learns about you lives as Markdown files under
+`~/.personal-agent/context/`. You can read them, edit them, version
+them — the agent reads what's there next time it runs.
+
+- [Memory Model](../concepts/memory-model.md) — the layout and the
+  rules around it.
+- [user/profile.md](../features/memory-files/user-profile.md) — what
+  the agent knows about you.
+- [today.md](../features/memory-files/today.md) — today's plan.
+- [agent/journal.md](../features/memory-files/agent-journal.md) —
+  what the agent did and what it noticed.
+
+## Help with the small lifestyle stuff
+
+Reading lists, receipts, travel bookings, travel-time estimates — the
+agent collects what arrives in mail and surfaces it in the right tab.
+
+- [Reading](../features/lifestyle/reading.md)
+- [Receipts](../features/lifestyle/receipts.md)
+- [Travel Bookings](../features/lifestyle/travel-bookings.md)
+- [Travel Time](../features/lifestyle/travel-time.md)
+
+## Stay in control
+
+Quiet hours, approvals, and a strict set of always-disallowed
+operations keep the agent from doing anything you don't want.
+
+- [Safety Model](../concepts/safety-model.md) — what the agent will
+  never do.
+- [Approvals](../features/operations/approvals.md) — when it asks
+  before acting.
+- [Quiet Hours](../features/operations/quiet-hours.md) — when it
+  stays silent.
+
+## Related
+
+- [Your First Day](04-first-day.md) — what to expect when the agent
+  begins running on its own.
+- [What is Aitne?](01-what-is-this.md) — the elevator pitch.
+- [First Steps](02-first-steps.md) — finish setup before exploring.