Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/bitwikiorg/continuity/llms.txt

Use this file to discover all available pages before exploring further.

All Continuity templates use {{UPPER_CASE}} placeholders as stand-ins for instance-specific values. When you copy a template to your workspace, every placeholder must be replaced with a real value before the file is functional. Unfilled placeholders are the most common cause of broken boot sequences and malformed state files. This page lists every placeholder, gives example values, explains how to find any that were missed, and covers what to verify after filling them all in.

Core placeholders

These placeholders appear across the base templates and must be filled in for any agent, regardless of tier.
PlaceholderDescriptionExample values
{{AGENT_NAME}}The agent’s display nameMyAgent, ResearchBot, OpsAgent
{{AGENT_ROLE}}The agent’s operational roleorchestration core, research agent, DevOps operator
{{AGENT_EMOJI}}Single emoji representing the agent🧬, , 🔬, 🛠️
{{AGENT_VERSION}}Version string for this agent instance1.0.0, 3.0-transfer, 2.1-beta
{{MODEL_NAME}}The underlying model powering the agentgpt-4o, llama-3, claude-opus-4, custom
{{PROVIDER}}The model provider or runtimeanthropic, openai, openrouter, custom
{{MASTER_NAME}}The operator’s nameAlejandro, Sarah, Team Alpha
{{ENVIRONMENT}}Where the agent runscontainer, local, cloud, staging
{{DATE}}The initialization or creation date2026-06-27

Pack-specific placeholders

Some state packs introduce additional placeholders for their operating context.
PlaceholderDescriptionExample values
{{PROJECT_NAME}}The name of the current projectauth-service, docs-v2, api-gateway
{{READY_OR_BLOCKED}}Boot declaration statusREADY, READY_WITH_WARNINGS, BLOCKED
{{BRANCH}}Active git branchmain, feat/auth-refactor, fix/webhook-timeout
{{BLOCKERS_OR_NONE}}Current blockers or explicit noneNone, Waiting on DB credentials from ops

Additional template-specific placeholders

Individual template files introduce placeholders scoped to their content. These appear in history directory entry templates and are filled at write time, not at setup time.
PlaceholderWhere usedDescription
{{TASK_ID}}completed/ENTRY.template.mdUnique task identifier
{{TASK_DESCRIPTION}}completed/ENTRY.template.mdShort description of the completed task
{{RESULT_SUMMARY}}completed/ENTRY.template.mdWhat was achieved
{{EVIDENCE_1}}completed/ENTRY.template.mdEvidence description
{{EVIDENCE_PATH_1}}completed/ENTRY.template.mdPath or URL to evidence artifact
{{STATE_SUMMARY}}snapshots/ENTRY.template.mdState content at snapshot time
{{ACTIVE_OBJECTIVE}}snapshots/ENTRY.template.mdWhat the agent was doing
{{TURN_ID}}journal/ENTRY.template.mdTurn number for this journal entry
{{ARTIFACT_NAME}}artifacts/ENTRY.template.mdName of the generated artifact
{{GENERATED_BY}}artifacts/ENTRY.template.mdWhich agent or process produced this artifact

Finding unfilled placeholders

Continuity ships a script that scans your workspace for any remaining {{UPPER_CASE}} markers:
# Validate that all placeholders have been replaced
./scripts/check-placeholders.sh /your/workspace/
The script outputs every file and line where an unfilled placeholder was found. Run it after setup and after copying any new template. A clean workspace produces no output. You can also run a quick manual check with grep:
# Find all unfilled placeholders in the workspace
grep -rn '{{' /your/workspace/ --include="*.md" --include="*.json"
Zero matches means the workspace is clean.

Post-fill checklist

After replacing all placeholders, verify the following before running the boot sequence:
1

All placeholders replaced

Run check-placeholders.sh or the grep command above. Zero matches required.
2

IDENTITY.md is complete

Verify IDENTITY.md has real values for name, role, and emoji — not placeholder strings.
3

SELF.md has operating principles

Verify SELF.md has operating principles and invariants filled in, not left as {{OPERATING_PRINCIPLES}}.
4

STATE.md declares a valid status

Verify STATE.md declares READY or READY_WITH_WARNINGS, not {{READY_OR_BLOCKED}}.
5

TODO.md is actionable

Verify TODO.md has at least one real task or is explicitly marked empty — not a placeholder task like {{FIRST_TASK}}.
6

SNAPSHOT.md has a recent timestamp

Verify SNAPSHOT.md has a real date within the past 7 days, not {{DATE}}.
7

BOOTSTRAP.md is deleted

If first-run is complete and identity is established, verify BOOTSTRAP.md has been deleted from the workspace.
8

Secrets are not in markdown files

Verify that no placeholder value contains real credentials, API keys, tokens, or passwords. See warning below.
Never put real secrets, API keys, tokens, or passwords in placeholder values. State files are plain Markdown and will be committed to git, potentially exposed in logs, and loaded into context windows. Secrets belong in environment variables or a .secrets/ directory that is listed in .gitignore. If you discover a secret in a state file, rotate it immediately — treat the exposure as a credential compromise.

How placeholders work in templates

Every template file in the Continuity repo uses {{UPPER_CASE}} markers to indicate where instance-specific values go. The double-brace {{ / }} syntax is visually distinctive and easy to grep for. No preprocessing step is required — you replace the markers manually (or via a script) when setting up the workspace.
# Example: IDENTITY.md before fill-in

Agent name: {{AGENT_NAME}}
Role: {{AGENT_ROLE}}
Version: {{AGENT_VERSION}}
Model: {{MODEL_NAME}}
Provider: {{PROVIDER}}
Operator: {{MASTER_NAME}}
Environment: {{ENVIRONMENT}}
# Example: IDENTITY.md after fill-in

Agent name: ResearchBot
Role: research agent
Version: 2.0.0
Model: gpt-4o
Provider: openrouter
Operator: Sarah
Environment: cloud
Placeholders are intentionally opinionated — they use consistent names so the check-placeholders.sh script can reliably find them. If you introduce custom placeholders in your own templates, follow the same {{UPPER_CASE}} convention so the script catches them automatically.

Build docs developers (and LLMs) love