# Cadence Full Agent Text Generated from route manifest. Last updated: 2026-09-17. This file is intentionally small. Prefer the per-route Markdown files when targeting one page. Canonical Trust page: https://app.cadence-me.com/trust Normalized Trust evidence: https://app.cadence-me.com/api/public/trust-evidence Canonical Privacy HTML: https://app.cadence-me.com/privacy Canonical Terms HTML: https://app.cadence-me.com/terms Legal and Trust pages are application routes, not marketing routes, and have no Markdown mirrors. ## Source: / Canonical: https://cadence-me.com/ Markdown: https://cadence-me.com/index.md Last updated: 2026-09-17 # Cadence Cadence is an open-source personal behavior tracker. You define Behaviors with Schedules, and Cadence generates Occurrences on a today-first timeline. Completed means the user declared the occurrence completed. Not Completed means the user declared the occurrence not completed. Unresolved means the user has not made a decision. Prior-day Unresolved Occurrences surface in Needs decision. The full history exports as JSONL, JSON, CSV, Markdown, BehaviorLog bundle. Google Calendar context is optional and currently limited to Google OAuth test users. Where enabled, choose which calendars appear in Timeline. Cadence requests read-only access and cannot create, change, or delete Google Calendar events. Disconnect Google Calendar in Settings at any time. ## How Cadence Works 1. Define a behavior with a title and a schedule: daily, every N days, weekly, or monthly, at exact times or time ranges. Categories, descriptions, and reminders are optional. 2. Each Schedule produces Occurrences on a today-first timeline. Prior-day Unresolved Occurrences collect in Needs decision. 3. Make a Decision for each Occurrence, with an optional note. Every Decision writes an append-only status event. 4. Review adherence across 7, 30, or 90 days on a calendar heatmap, then export the full history anytime. ## Philosophy Cadence deliberately has no streaks, badges, points, or guilt mechanics. Streaks collapse effort into one number that resets on one bad day. Cadence shows Adherence across 7, 30, or 90 days instead. Unresolved means the user has not made a decision. Silence is never converted into failure. The product records facts about behavioral Adherence and leaves motivation to the user. Interfaces are no longer fixed: in the agentic era, an AI tool can read a personal history and build whatever View or coaching layer its owner prefers. Cadence therefore invests in the data backbone, a factual and portable Record, rather than a prescribed interface. Cadence provides prepared prompts, but it does not send behavior data to an AI provider. The user exports data and chooses any external AI service. ## Time Tracking Any current-day Occurrence, or one visible in Needs decision, can carry an elapsed-time timer with start, stop, and reset. Reviews show per-Occurrence totals and range averages alongside Adherence. Exports omit time-tracking data unless the user explicitly opts in because exact session timestamps can reveal activity patterns. ## Read First - Use Cadence to track recurring behaviors one account at a time. - Use BehaviorLog when a behavior history needs to move between tools without losing local dates, timezones, or explicit status history. - Status values are unresolved, completed, and not_completed. - Needs decision is a derived Cadence UI group, not a stored BehaviorLog status. ## Source: /faq Canonical: https://cadence-me.com/faq Markdown: https://cadence-me.com/faq.md Last updated: 2026-09-17 # Frequently Asked Questions Detailed answers about Cadence's recording model, context, review, privacy, and portability. ## Recording model ### What is Cadence? Cadence is an open-source tracker for recurring behaviors. You define a Behavior and its Schedule, and Cadence creates each Occurrence on a today-first timeline. Completed means the user declared the occurrence completed. Not Completed means the user declared the occurrence not completed. Unresolved means the user has not made a decision. ### What happens if I do not make a decision? Unresolved means the user has not made a decision. Prior-day Unresolved Occurrences collect in Needs decision until you decide them. Cadence never converts silence into failure. ### Why are there no streaks, badges, or points? Cadence keeps the Record focused on explicit Decisions. It shows Adherence over 7, 30, or 90 days without turning a streak or score into the goal. ## Context and history ### Can I track how long a behavior takes? Yes. An Occurrence scheduled for today, or one still in Needs decision, can carry elapsed time. Start, stop, and reset the timer. Reviews show totals and averages alongside Adherence. ### What happens when I rename or redefine a Behavior? Cadence preserves title and description revision history in JSON and BehaviorLog exports. The current app does not provide a full revision browser. ### What Context can I add? You can add an optional note and elapsed time to an Occurrence. Context does not decide whether the Occurrence is Completed or Not Completed. ## Review and analysis ### How does Adherence work? Cadence shows Adherence across 7, 30, or 90 days. Adherence is the share of decided Occurrences marked Completed. Unresolved Occurrences remain separate from final calculations. ### Can I analyze my Record with an AI service? Cadence provides prepared prompts. You export the data and choose an external AI service. Cadence does not send behavior data to an AI provider. ## Google Calendar ### Is Google Calendar required? No. Cadence tracking works without Calendar. The optional connector is currently available only to Google OAuth test users while the app remains in Testing mode. ### What can Cadence read from Google Calendar? After separate consent with the same Google identity used for Cadence sign-in, Google grants read-only access to your subscribed calendar list and events on calendars you can access. Cadence reads the list so you can choose calendars, then fetches events only from selected calendars for the days displayed in Timeline. Depending on Google permissions and event data, details can include titles, descriptions, times, locations, organizers, attendees, conference details, attachment links, and Google event links. ### Can Cadence change my Google Calendar events? No. Cadence requests read-only Calendar access. It cannot create, change, or delete Google events, and it does not download attachments automatically. ### How do I disconnect Google Calendar? Choose Disconnect Google Calendar in Settings. This removes the live server credential and requests global revocation of the Calendar grant. Web sign-out ends only that Cadence session and leaves the account-level Calendar connection active. Disconnecting a Cadence account on desktop clears that Mac's Calendar cache but does not revoke the global grant. An offline device may retain stale cached event details until it reconnects or its Cadence account is disconnected. ## Privacy and portability ### Who can see my data? Cadence is single-player by design. There is no social feed or collaboration layer. Read the Privacy page for the current data practices and the Trust page for bounded operational evidence. ### Can I leave and take my Record with me? Yes. Export your history as JSONL, JSON, CSV, Markdown, BehaviorLog bundle. These files can be inspected without Cadence. ### Is tracked time included in my exports? Only when you choose to include it. Exports omit timing data by default because exact session timestamps can reveal activity patterns. ### What is BehaviorLog? BehaviorLog is the open portability standard used by Cadence. A bundle contains plain JSONL files, a manifest, schemas, and SHA-256 checksums. The standard lives at https://github.com/emixd12/BehaviorLog-Bundle. ### What does Cadence cost? Cadence is currently available without charge. ## Source: /examples Canonical: https://cadence-me.com/examples Markdown: https://cadence-me.com/examples.md Last updated: 2026-09-17 # Example BehaviorLog Bundle The example bundle is generated from demo behavior data and is intended for format inspection, tests, and agent workflows. It contains no real account or reminder-provider data. ## Included Concepts - Behavior records. - Calendar-simple schedules. - Occurrences with local_date, timezone, and current status. - Status event history. - A short AGENTS.md file that tells coding agents how to inspect the bundle. Download path: /examples/cadence-demo.behaviorlog.zip ## Source: /docs Canonical: https://cadence-me.com/docs Markdown: https://cadence-me.com/docs.md Last updated: 2026-09-17 # Cadence Docs This route is optimized for coding agents, retrieval tools, and developers evaluating Cadence exports. Prefer the Markdown mirrors and route manifest when context budget matters. ## Machine Files - https://app.cadence-me.com/trust is the canonical human Trust page. - https://app.cadence-me.com/api/public/trust-evidence is the normalized current Trust evidence route. - /llms.txt is the curated agent index. - /llms-full.txt contains scoped page text for this small marketing site. - /data/route-manifest.json is the source route manifest exposed as JSON. - /faq.md, /examples.md, /docs.md, /about.md, and /index.md are clean Markdown mirrors. - /sitemap.xml lists canonical HTML routes. - /robots.txt advertises the sitemap. ## Analysis Rule Use status_events.jsonl as the BehaviorLog history authority. Treat occurrences.jsonl current_status as a snapshot only. Adherence includes only decided Occurrences. Unresolved Occurrences remain separate. Do not infer causes, clinical meaning, or motivation from a Record. ## Canonical Application Pages - https://app.cadence-me.com/trust is canonical HTML for Trust. - https://app.cadence-me.com/privacy is canonical HTML for Privacy. - https://app.cadence-me.com/terms is canonical HTML for Terms. These application-origin pages are not marketing routes and have no marketing Markdown mirrors. ## Source: /about Canonical: https://cadence-me.com/about Markdown: https://cadence-me.com/about.md Last updated: 2026-09-17 # About Cadence Behavioral remodeling starts with a Record the user controls. Cadence records recurring behavior through explicit Decisions, preserved Context, longitudinal review, and portable BehaviorLog data. ## Behavioral Remodeling A Behavior can change over time. Cadence keeps its Schedule, Occurrences, Decisions, and optional Context available for review. JSON and BehaviorLog exports preserve title and description definition history; Cadence does not present a full in-app revision browser. Completed means the user declared the occurrence completed. Not Completed means the user declared the occurrence not completed. Unresolved means the user has not made a decision. ## Four Record Principles 1. Explicit Decisions: only the user declares an Occurrence Completed or Not Completed. 2. Preserved Context: notes and elapsed time do not rewrite an earlier Decision. JSON and BehaviorLog exports preserve title and description definition history. 3. Longitudinal review: Cadence separates Unresolved Occurrences and shows Adherence across 7, 30, or 90 days. 4. Portable Records: export the Record as JSONL, JSON, CSV, Markdown, BehaviorLog bundle. ## Current Product Scope Cadence is a single-player web app for Behavior creation, recurring Schedules, a timeline of Occurrences, explicit Decisions, notes, reminders, basic Adherence review, elapsed-time capture, and portable exports. It is not a social tracker, collaboration product, medical dosing app, payment system, or AI coach. Cadence provides prepared prompts, but the user exports data and chooses any external AI service. Cadence does not send behavior data to an AI provider. ## Cadence and BehaviorLog Cadence is the application where a user creates and reviews a Record. BehaviorLog is the open standard that packages behavior Records for inspection and exchange between tools. ## Implementation - Cadence source: https://github.com/emixd12/habit-tracking-app - BehaviorLog standard: https://github.com/emixd12/BehaviorLog-Bundle - Trust: https://app.cadence-me.com/trust - Privacy: https://app.cadence-me.com/privacy