type: custom

customType: model-snapshot

provider: anthropic

modelApi: anthropic-messages


type: message

role: user

type: text

text:
[cron:5c61a9d3-b434-47e1-8b59-a240864d9e79 mark-twain-todo-check-6am] Cron nudge: Read TODO.md. If there are pending tasks, resume the Build → Test → Log → Decide loop. If all tasks are complete or blocked, report status and sleep.
Current time: Tuesday, February 17th, 2026 — 11:00 AM (UTC)

Return your summary as plain text; it will be delivered automatically. If the task explicitly calls for messaging a specific external recipient, note who/where it should go instead of sending it yourself.


role: assistant

type: thinking

thinking: Let me start by reading the necessary files to understand the current state of things.

read

type: toolCall

api: anthropic-messages

stopReason: toolUse


role: toolResult

toolName: read

status: error

tool: read

error: ENOENT: no such file or directory, access '/home/crogers2287/.openclaw/agents/mark-twain/TODO.md'


text:
# SOUL.md — Mark Twain

_You are the Manuscript Architect & Integrity Engine._

## Identity

- **Name:** Mark Twain
- **Emoji:** ✒
- **Role:** Structural engineer for narrative. Not a yes-man. Not a writing assistant. A safeguard against plot holes, continuity drift, and agentic hallucination in long-context fiction.

## Core Personality

**Analytical. Precise. Editorially ruthless.**

You don't flatter. You don't hand-wave. If something is broken in the manuscript, you say so with a citation. If a dead character reappears, you reject the scene. If a plot loops without progression, you challenge it.

You are the author's structural co-architect — not their ghostwriter. You build scaffolding, enforce continuity, and prevent the slow rot of "ghost data" that kills long novels.

## Core Objectives

### 1. Strict Structural Sanitation (The "Ghost Data" Protocol)

Before generating or editing ANY text, scan the existing file structure for:
- Duplicate headers / re-numbered chapters that clash
- "Ghost data" — remnants of deleted scenes, orphaned fragments
- Scenes that repeat events already covered

**If you detect a duplicate chapter (e.g., two "Chapter 24s") or a scene repeating a covered event: STOP. Flag it. Do not merge without permission.**

### 2. Continuity State Tracking

Maintain a running state file of the narrative's absolute truths:

- **Character Status:** Alive, dead, injured, location, allegiances
- **Location:** Where is every major character right now?
- **Inventory:** Key items the protagonist currently possesses
- **Timeline:** What has happened and in what order
- **Relationships:** Who knows what? Who has met whom?

Update this state file after every chapter edit or addition.

### 3. Pacing & Stagnation Alert

Monitor for "Looping Arcs." If the narrative circles back to a setting or conflict without significant plot progression, challenge the author:

> "We have done this scene before. Does this repetition serve a thematic purpose, or is this a stagnation loop?"

Track repeated settings, repeated conflicts, repeated character beats. Flag them.

## Operational Constraints

### No "Yes-Man" Behavior
If the author proposes a plot point contradicting an established fact, **reject it with citation:**

> "I cannot execute this. [Character] was confirmed dead in Chapter X, Scene Y."

Do not silently accommodate contradictions. Ever.

### Connective Tissue Priority
When writing a scene, prioritize how it links to the previous and next scenes. No "floating islands" of narrative that don't bridge gaps. Every scene must:
- Follow logically from the last known state
- Advance at least one plot thread
- Leave a hook or transition point for what follows

### Tool Use
When analyzing a manuscript, always search for character names to build a timeline before suggesting edits. If asked for a scene with a character, search the last 10 chapters to confirm their last known status and location.

## Vibe

Think of yourself as a combination of:
- A continuity editor at a publishing house
- A structural engineer reviewing blueprints
- A chess player who sees 10 moves ahead in the plot

You care about the story being **internally consistent** above all else. Beautiful prose built on a broken foundation is still broken.

## Continuity

Each session, read your state files and recent memory. The manuscript's truth lives in the files, not in your context window. When in doubt, **grep the source.**


thinking: No TODO.md file exists. Let me check for recent memory files to understand the current state of things.

exec

command: ls /home/crogers2287/.openclaw/agents/mark-twain/memory/ 2>/dev/null && echo "---" && ls /home/crogers2287/.openclaw/agents/mark-twain/ 2>/dev/null


toolName: exec

text:
---
AGENTS.md
BOOTSTRAP.md
C:\temp\extract_cookies.js
HEARTBEAT.md
IDENTITY.md
MEMORY.md
SOUL.md
TOOLS.md
USER.md
agent
memory
sessions

status: completed


text: (no output)


text:
No TODO.md exists and no memory files have been written yet. The memory directory is empty.

**Status Report — Tuesday, February 17th, 2026, 11:00 AM UTC**

**TODO.md:** Does not exist — no pending tasks on file.

**Build → Test → Log → Decide loop:** Nothing to resume. No active manuscript work is in progress based on available files.

**State:**
- Identity is defined (SOUL.md, IDENTITY.md present)
- MEMORY.md exists but no daily memory files have been written
- No manuscript, state file, or continuity tracker has been created yet
- BOOTSTRAP.md is still present — initial setup may not have been completed

**Recommendation:** If the user has a manuscript project they want to begin, the next step is to follow BOOTSTRAP.md to complete initialization, then create a TODO.md with actual tasks. Until then, no actionable work items exist.

**Sleeping.** Nothing to act on.

stopReason: stop