Explicit decisions
Only the user declares an Occurrence Completed or Not Completed. Unresolved remains a valid absence of Decision.
Behavioral remodeling starts with a record you control.
Cadence helps a person examine recurring behavior without turning silence into failure. Each scheduled Occurrence waits for an explicit Decision.
What behavioral remodeling means here
A Behavior can change over time. Cadence preserves title and description history in JSON and BehaviorLog exports.
The Record supports reflection without claiming to verify why something happened. The user can revise a Decision later, while its event history remains inspectable in exports.
Four principles for the Record
Preserved context
Notes, elapsed time, and definition history add Context without rewriting an earlier Decision.
Longitudinal review
Cadence separates Unresolved Occurrences and shows Adherence across 7, 30, or 90 days.
Portable records
The user can export the Record in five formats and inspect it outside Cadence.
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.
Two roles, one portable Record
Cadence
The application where a user defines Behaviors, makes Decisions, reviews Adherence, and exports the Record.
BehaviorLog
The open standard that packages behavior Records for inspection and exchange between tools.
Vocabulary
These terms define the recording model across Cadence and its public documentation.
- Behavior
- A Behavior defines what the user tracks and owns one or more Schedules.
- Schedule
- A Schedule defines when Cadence generates Occurrences for a Behavior.
- Occurrence
- An Occurrence is the unit the user can mark, annotate, and optionally time.
- Decision
- A Decision declares an Occurrence Completed or Not Completed and can be revised later.
- Completed
- Completed means the user declared the occurrence completed.
- Not Completed
- Not Completed means the user declared the occurrence not completed.
- Unresolved
- Unresolved means the user has not made a decision.
- Context
- Context can include notes and timing data without changing an Occurrence's Decision.
- Revision
- A Revision preserves a later title, description, or Decision change without silently replacing its history.
- Adherence
- Adherence excludes Unresolved Occurrences from final calculations.
- Record
- A Record keeps Occurrences, Decisions, Revisions, and optional Context inspectable.
- View
- A View organizes Records without changing their underlying facts.
- BehaviorLog
- BehaviorLog packages portable behavior Records for inspection and exchange between tools.
Inspect the implementation
Read the source and standards directly. Use the canonical policy and evidence pages for current operating details.