WHAT SPEAR OF LIFE ACTUALLY IS

This page exists because SPEAR OF LIFE (SOL) is a game architecture designed to change how you observe your own life and how you act on what you observe. It uses streaks, identity roles, scorecards, and daily reflection loops to produce that change. If a tool is doing something to you, you deserve to know exactly what and how. This is that document.

If any of it stops serving you: take your data and go. The door is always open. That is structural, not a favor.

1 · What this is

SOL is a personal + team operating system built around a daily observation loop. You log three Vital Planck actions per day, score them (HIT · MISS · ADJUST), and the system composes that into longer-horizon signals — weekly Big 3, quarterly SMART goals, annual targets, and four "creature" roles (Lion, Ox, Wise Heart, Eagle) that represent different functions of your judgment.

At the architecture level, it is trying to do three things:

• Make observation reflexive — daily scorecards, explicit HIT/MISS/ADJUST prompts, streak counters.
• Reduce decision friction — creature roles collapse thousands of daily micro-choices into four archetypal questions.
• Compound small signals — the daily Planck log is the data substrate for every higher-altitude report.

2 · Who built it, and why

SOL was designed and is maintained by Caleb LL Davis. The architecture draws direct lineage from Darren Hardy's compound-effect work, Napoleon Hill's definite-chief-aim framing, and Hardy's High Performance Forum scorecard discipline. Caleb has publicly attributed Hardy as having "saved his life" and the product explicitly carries that lineage forward rather than hiding it.

Why Caleb builds anti-cult rails into a product he also makes charismatic: he self-identifies as charismatic by nature. He knows charisma without structural rails produces capture. The disclosure you are reading, the one-click export, the frictionless account delete, the celebrate-the-miss framing — those are the rails. They are intentional, not PR. If the product succeeds, the rails are what keep it from becoming a cult.

3 · The game mechanics, named

Streaks

The dashboard shows CONSECUTIVE DAYS of Planck-log completion. This is a deliberate behavioral lever — streaks trigger loss-aversion and status-maintenance circuits and make showing up more likely. What the streak counts is showing up. It is NOT a measure of winning. Winning is confirmed by Guardians (below) and real-world outcomes. If a streak number is making you anxious rather than engaged, the system is failing you — pause and re-read section 8.

HIT · MISS · ADJUST

Daily reflection asks three things. All three are treated as equal data:

A MISS is information, not failure. The entire color palette and copy layer has been rebuilt to celebrate misses because Caleb's personal commitment is to "celebrate my failures, not shame myself for them." If any surface in the app still shames a miss, it is a bug.

Creature roles

Four archetypal identities (Lion · Ox · Wise Heart · Eagle) that map to four functions of judgment (hunt, build, discern, scout). They are vocabulary for your own decisions, not external authorities. You are the sovereign. The creatures serve you.

Scorecards + Vital Planck cascade

3 annual SMART goals → 3 quarterly goals → 6 Vital Planck Frequencies (or 3 for executor roles) → 3 daily Planck actions. Small observations compound into larger signals. The data is yours, scoped to your user_id, and exportable as plain JSON at any time.

4 · What data is collected

Every user-scoped table in the SOL database is exportable via GET /api/account/export (signed in). It includes at minimum:

• planck_log — your daily 3-action log, hours spent, done/not-done, HIT/MISS/ADJUST notes.
• board_data — your scorecard instruments (identity, mission, goals, trinity of telemetry).
• big3_log — weekly priorities + status.
• scribe_log — if you use Scribe, your chat exchanges classified C1/C2/C3.
• sentry_log — signals you logged (inbound threats, outbound commitments, follow-ups).
• Creature-gate logs — 17 gate-specific tables (lion_log, ox_log, etc.) for agent interactions.
• Biometrics — sleep hours, HRV, cognitive capacity modifier, if you logged them.

Enterprise-shared data (other operators, shared formation instruments) is not part of your personal export — it belongs to the enterprise you operate within, not to you individually.

5 · What this does to you

This section is intentionally uncomfortable. A system designed to change behavior changes behavior. Some of what SOL does:

• Streaks shift your attention economy. You start thinking about logging before you think about sleeping. That can be useful or it can be compulsive.
• Identity framing is sticky. Adopting "Lion" / "Ox" / "Sovereign" language changes how you describe yourself to others and how you read your own impulses. Carry it lightly.
• Observation pressure. Once you know you'll score HIT/MISS/ADJUST at day-end, you behave differently during the day. This is the mechanism — and it's worth knowing that's the mechanism.
• Sunk-cost accumulation. 100+ day streaks make it feel expensive to miss a day. That is loss aversion, not proof of the system's value.

6 · Guardian-in-the-loop (in development)

The architecture specifies a Guardian for each sphere — a human who verifies real-world outcomes and provides reality checks the system cannot provide for itself. Guardians will be vetted on evidence of proven outcomes in the domain they guard, not title or charisma. This infrastructure is still being built. Until it ships, the dashboard explicitly says "Guardian-confirmed wins: system in development" rather than pretending verification is happening. You can see this on your sovereign dashboard.

This matters because a system that self-scores without external verification is a system that produces delusion. The honest label is part of the rail.

7 · How to leave

There is no retention funnel. There are no dark patterns between you and the exit.

Deleting your account hard-deletes every row scoped to your user_id inside a single database transaction, plus all active sessions. Enterprise-shared data is untouched (it does not belong to you individually). There is no recovery. The door was always open.

8 · Limitations and systems still in development

• Guardian infrastructure is specified but not yet built. Until it ships, winning is not externally verified.
• Outcomes-logging (real-world results separate from Planck hours) is not yet instrumented.
• The disclosure you are reading is v1. It will be updated as the architecture changes. Date-stamped at the top.
• No third-party data sharing. No ads. No sale of user data. (If this ever changes, this document changes with it before the change ships.)