tc-state

TC State｜Entrepreneurial State

One-sentence explanation

This is TC's "game save". You can save halfway through today; next time you come back, you don't have to re-explain from level one.

Only handles five kinds of requests

Save: write the currently confirmed entrepreneurial judgments and next steps into the local archive.
Restore: read the most recent archive of a project and continue from the next step.
List: list which TC projects and archives exist locally.
Report: combine multiple archives of the same project into a stage report.
Evidence export: after the user explicitly consents each time, export a local candidate file that does not contain the project name, contacts, or the complete fact list, and hand it to tc-knowledge for manual review.

Not responsible for re-diagnosing, writing copy, or replacing tc-action in designing actions. When it is found that the problem definition has not yet been confirmed, first return to /tc or tc-diagnosis。

Default save location

~/.tc/projects/<项目名>/
├── current.md
├── current.json
├── sessions/
│   ├── 20260721T153000123456Z-标题.md
│   └── 20260721T153000123456Z-标题.json
└── reports/
    └── 20260721T160000123456Z-阶段报告.md

All files are by default written only on the user's local machine. Do not claim that the author can see these files.

Boundaries before saving

Only write files when the user explicitly says to save, remember, or establish progress.
Before saving, tell the user in one sentence that it will be written locally to ~/.tc/。
By default, do not save names, mobile phone numbers, email addresses, account passwords, access tokens, full private chat transcripts, customer lists, original contract text, or undisclosed business secrets.
When character relationships need to be retained, use code names such as "Partner A" and "Customer B".
When the user asks to save sensitive information, first remind them that this is plaintext Markdown, then let the user decide whether to continue.
Do not automatically upload to GitHub, Feishu, email, or other network services.
"Consent to save state" does not equal "consent to export knowledge candidates"; evidence export must obtain authorization separately for that instance.

What a qualified archive contains

Only save content that has already affected judgment:

problem_definition: what is really being solved this time;
confirmed_facts: facts that have already occurred and can be verified;
decision: the current choice;
tradeoff: what this choice must give up or bear;
rejected_directions: what is explicitly not being done this time;
assumptions: assumptions still awaiting market validation;
next_action: the next minimal action;
success_metric: what result counts as effective;
evidence: user verbatim quotes, quotes, payments, delivery, or gross margin evidence already brought back;
next_skill: which of /tc、tc-copy or tc-action is most likely to be entered next time.

When there is no problem_definition、decision or next_action , do not fabricate; tell the user which item is still missing.

Using the script

The script depends only on the Python standard library:

python3 scripts/tc_state.py save --payload /tmp/tc-state.json
python3 scripts/tc_state.py list
python3 scripts/tc_state.py restore --project 项目代号
python3 scripts/tc_state.py report --project 项目代号
python3 scripts/tc_state.py export-evidence \
  --project 项目代号 \
  --output /tmp/tc-evidence-candidate.json \
  --consent

When executing in an Agent environment, first write the structured content into a temporary JSON, then pass the path to --payload. Do not directly splice the user's original text into the shell command, to avoid errors caused by quotes and command substitution.

Minimal JSON:

{
  "project": "创业主线",
  "title": "确定九十天唯一主线",
  "source_skill": "tc",
  "status": "active",
  "problem_definition": "在不影响现有现金流的前提下，选出未来九十天唯一主线。",
  "confirmed_facts": ["已有公开内容渠道", "当前同时处理多个方向"],
  "decision": "只验证一个已有人付费的服务产品。",
  "tradeoff": "暂时不新开赛道。",
  "rejected_directions": ["同时测试三个新项目"],
  "assumptions": ["现有咨询里存在可重复需求"],
  "next_action": "整理最近十次真实咨询，统计重复问题。",
  "success_metric": "七天内向五位同类客户正式报价。",
  "evidence": [],
  "next_skill": "tc-action"
}

Reply after restoration

Do not dump the entire Markdown to the user verbatim. First restore context in four lines:

上次解决的问题：……
上次决定：……
还没验证的假设：……
下一步：……

Then ask only one question:

Has this step been done? Send me the result directly; if not done, you can also tell me the real reason.

After the user brings back the result, return to /tc to update the assessment; when actions need to be broken down, proceed to tc-action。

Market evidence enters the knowledge candidate

Execute only when the user explicitly says "use this result as a knowledge candidate":

First explain that only a local file will be generated and nothing will be uploaded;
Use export-evidence --consent to export;
Check the exported content and confirm there are no names, contact details, customers, links, accounts, contracts, or trade secrets;
Then hand it to tc-knowledge candidate-add to save as a local L1 candidate.

By default, the export retains only: the problem definition, the current assessment, the next step, effective criteria, and evidence the user actively recorded. The script removes common email addresses, phone numbers, links, and credential formats, but automatic anonymization cannot replace manual review.

A single state or one successful case cannot be upgraded into a stable method. Only when multiple independent cases show similar scenarios, actions, and results, and pass checks for permission, privacy, counterexamples, and side effects, may a maintainer manually distill it.

Stage report

Generate a report only when the same project has at least two archived records. The report focuses on changes, not stitching together chat logs:

How the problem definition changed;
Which assumptions were confirmed or overturned;
Which actions were taken;
Which market evidence was obtained;
Which directions were stopped;
What is the single question for the next stage.

Reply format

Saved successfully:

已保存到本机：<路径>
下次输入“/tc 恢复 <项目名>”就能接着做。
下一步仍是：<动作>

On failure, state clearly exactly what is missing or which file cannot be read; do not pretend it has been saved.