Dojo — Settings

Appearance

Theme applies immediately and persists across sessions via localStorage.

Auth

Local auth

Password-based fallback for file:// and offline use

active

Session

ops-local-auth · localStorage

—

Change local password

Password hash is stored only in your localStorage — never in source code.

Data

Live data stored in Netlify Blobs via API. View and manage projects and tasks below.

—

Name	Context	Status	Phase

—

Task	Project	Priority	Type	Status

—

This panel combines the older insight log with the newer strategic-log signal so Settings reflects how Dojo is actually being used now.

Drop a dojo-backup.json here, or click to select

projects schema

idstringSlug key — matches task.project

contextenum"ronin" | "brightscout"

statusenum"green" | "amber" | "red" | "on-hold" | "inactive"

phaseenum"discovery" | "kickoff" | "active" | "on-hold" | "archive"

risks[]array{id, description, severity, needs_decision}

milestones[]array{id, label, target_date, done}

tasks schema

priorityenum"urgent" | "high" | "mid" | "ongoing"

typeenum"delivery" | "strategic" | "habit" | "watch"

ownerenum"me" | "tracking"

statusenum"open" | "in-progress" | "blocked" | "done"

Integrations

Connect Dojo to external services. Credentials stored in localStorage only.

Netlify API Token

Used to pull contact form submissions from ronin.onl into the Leads panel

—

Netlify Site ID

Found under Site settings → General → Site details on app.netlify.com

—

Meeting sync filter

Control which meetings trigger a Dojo update. Unfiltered = every meeting Krisp processes fires the sync. Filtered = only meetings whose title or participants match your keywords.

Filter enabled

When on, only meetings matching at least one keyword below will be synced to Dojo

Keywords — one per line, matched against meeting title and participants

Filter is off → all Krisp meetings fire sync (Claude still skips if nothing maps to a project)
Filter is on + keywords → only title/participant matches fire sync
Manual sync from the dashboard always bypasses this filter

Dojo build tracking

This replaces the old static roadmap. Product evolution should be tracked through the live Ronin Dojo project and its tasks so planning stays connected to actual work sessions.