An AI-assisted personal strategy system that connects long-term direction to what you do next.
Ariadne exists to close the gap between strategy and execution. Long-term direction, projects, opportunities, and daily tasks often live in separate systems; Ariadne keeps them connected so prioritization can reflect what is actually important rather than treating every task as an isolated item.
Ariadne models desired movement and turns it into executable work:
Vectors → Directions → Strategic Objectives → Projects / Tasks → Progress Signals
Directions describe where the user wants to move across an eight-vector life map. Strategic Objectives identify the major changes required. Projects and tasks represent the concrete work, while progress signals help show whether that work is actually moving the strategy forward.
Ariadne also includes an Opportunity Landscape for tracking relevant opportunities and applications. Discovered or externally supplied candidates enter a separate review inbox first, preserving a boundary between untrusted candidate records and accepted canonical opportunities.
Ari Bot can reason over a bounded strategy/task control surface and use strategic relevance alongside urgency, leverage, obligations, and actionability when reprioritizing work. The system is designed to support judgment rather than replace it.
Ariadne is one part of a broader personal-systems architecture:
- Heracles measures and analyses a specific domain: resistance training and physical performance.
- Kleos models current state from evidence across multiple life domains.
- Ariadne owns desired movement, priorities, opportunities, projects, tasks, and execution.
Personal measurement and benchmarking are owned by the separate NeoLorenzo/Kleos application. Ariadne may use current-state context, but it does not recreate Kleos's measurement workflows.
Put differently, Kleos asks where am I now? Ariadne asks given where I am and where I want to go, what should I do next?
- Dashboard with concurrent multidimensional Directions and Strategic Objectives
- Task planning with subtasks, scheduling, numeric
0–4priority, and time-pressure indicators - Coding-project management with GitHub repository synchronization
- Opportunity Landscape with canonical opportunities, application tracking, eligibility assessment, and a separate candidate review inbox
- Candidate ingestion with provenance, deduplication, review state, and explicit acceptance into the canonical Opportunity Landscape
- Notice board generated from project and publication signals
- Ari Bot-compatible strategy/task control surface for automated reprioritization
- Google OAuth through Supabase
- Local-first project, task, and opportunity behavior with authenticated cloud synchronization
- PWA support and static deployment through GitHub Pages
Ariadne uses a deliberately small hierarchy:
Vectors → Directions → Strategic Objectives → Projects / Tasks → Progress Signals
Directions describe desired movement through the eight-dimensional life map. Strategic Objectives decompose that movement into the major changes currently required. Strategic Objectives are the lowest-level persistent strategy entity; concrete deliverables, deadlines, and next actions belong in ordinary projects and tasks.
Task priority has only five numeric values: 0, 1, 2, 3, and 4. There is no special Directional task priority. Ari Bot can infer how current tasks contribute to enabled Directions and active Strategic Objectives and use that relevance as one input into task priority.
Outcome Goals are retained only as legacy history where applicable and are not part of the active strategy model.
The Opportunity Landscape separates trusted canonical records from discovered candidates:
External discovery / manual candidate
↓
Candidate review inbox
↓
accept / reject / duplicate
↓
Canonical opportunity
↓
Application
Candidate records retain provenance and review state. Acceptance is explicit; future discovery automation does not get to write directly into the canonical Opportunity Landscape simply because it found something.
Personal measurement and benchmarking are fully owned by the separate NeoLorenzo/Kleos application. Ariadne no longer exposes or contains the former GOAT Lab application surface.
Existing goat_* records remain physically located in the shared Supabase project. Their schema, RLS policy definitions, application logic, and future persistence changes are owned by Kleos.
- Next.js 16 with the App Router
- React 19
- Supabase Auth and PostgreSQL
- Tailwind/PostCSS plus application CSS
- GitHub Actions and GitHub Pages
Install and run:
npm ci
npm run devThe default local URL is http://localhost:3000.
Create .env.local:
NEXT_PUBLIC_SUPABASE_URL=...
NEXT_PUBLIC_SUPABASE_ANON_KEY=...Only the public Supabase URL and anon key are used client-side.
supabase/schema.sql is the baseline Ariadne-owned persistence bootstrap. After applying that baseline to a fresh project, apply the timestamped SQL files in supabase/migrations/ in filename order. The migrations are the source of truth for schema evolution after the baseline; an existing project should apply only migrations that have not already been deployed.
The resulting current schema provides:
- user task and task-backup storage
- user project and project-backup storage
- concurrent Directions with lifecycle/order metadata and explicit many-to-many links to the eight canonical navigation vectors
- user-managed Direction revisions, including vector metadata for revisions created after the multidirectional migration
- Strategic Objectives without an arbitrary active-objective cap
- canonical Opportunity Landscape, application, candidate-review, and eligibility-assessment persistence
- bounded semantic operations used by the browser and ChatGPT/Ari Bot control surfaces
- numeric-only task priority (
0–4) with legacy goal-generated tasks normalized into ordinary tasks
Kleos-owned goat_* persistence is documented and maintained in NeoLorenzo/Kleos. Ariadne intentionally excludes Kleos persistence definitions from its own schema; the Kleos repository is the source of truth.
All private tables use row-level security keyed by authenticated ownership.
In Supabase Auth URL Configuration:
- Set Site URL to the deployed Ariadne application URL.
- Add local and deployed Ariadne URLs under Additional Redirect URLs.
- Because the Supabase project is shared, also allow the production/local redirect URLs used by Kleos.
- A typical local redirect is
http://localhost:3000/.
The workflow at .github/workflows/deploy-pages.yml:
- installs dependencies with
npm ci; - runs regression tests and privacy checks;
- resolves the repository base path;
- performs a static Next.js export;
- uploads and deploys the
out/artifact.
Required GitHub Actions secrets:
NEXT_PUBLIC_SUPABASE_URLNEXT_PUBLIC_SUPABASE_ANON_KEY
app/manifest.webmanifestpublic/sw.jscomponents/PwaRegistrar.jsxpublic/icons/
- Tasks and projects are stored locally for responsive startup.
- Opportunities use local-first behavior with authenticated cloud synchronization.
- Candidate opportunities remain separate from canonical opportunities until explicitly accepted.
- Authenticated users synchronize private data to Supabase.
- Version checks protect task and project collections from silent concurrent overwrites.
- Direction/objective edits use durable local-first strategy reconciliation with optimistic conflict detection.
- Legacy Outcome Goal-generated tasks are retained as ordinary tasks; Outcome Goals are not part of the active data model.
- Dashboard publication signals are read only after owner authorization.
- Personal records are never seeded from repository code.
- GitHub Pages and this repository contain only the downloadable Ariadne application client.
- The application mounts only for the authorized Google account.
- Private Ariadne records live in Supabase and are protected by owner-only Row Level Security policies.
- Kleos uses the same physical Supabase project but owns its own
goat_*persistence boundary. - Supabase secret and service-role keys must never be committed or exposed to the browser.
- Run
npm run check:privacybefore deployment to scan tracked source and the static export.
Ariadne is currently an owner-focused personal application with workflow-specific naming and data assumptions. It is open source, but it is not maintained as a general-purpose turnkey productivity product, SaaS, or stable public API.