Back to Details

context-engine

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Company Context Engine

企业上下文引擎

The memory layer for C-suite advisors. Every advisor skill loads this first. Context is what turns generic advice into specific insight.
为C-suite顾问提供的记忆层。每个顾问技能都会首先加载该引擎。上下文是将通用建议转化为针对性洞察的关键。

Keywords

关键词

company context, context loading, context engine, company profile, advisor context, stale context, context refresh, privacy, anonymization
企业上下文、上下文加载、上下文引擎、企业档案、顾问上下文、过期上下文、上下文刷新、隐私、匿名化

Load Protocol (Run at Start of Every C-Suite Session)

加载协议（每次C-suite会话开始时执行）

Step 1 — Check for context file: 
~/.claude/company-context.md
  • Exists → proceed to Step 2
  • Missing → prompt: "Run /cs:setup to build your company context — it makes every advisor conversation significantly more useful."
Step 2 — Check staleness: Read 
Last updated
field.
  • < 90 days: Load and proceed.
  • ≥ 90 days: Prompt: "Your context is [N] days old. Quick 15-min refresh (/cs:update), or continue with what I have?"
    • If continue: load with 
      [STALE — last updated DATE]
      noted internally.
Step 3 — Parse into working memory. Always active:
  • Company stage (pre-PMF / scaling / optimizing)
  • Founder archetype (product / sales / technical / operator)
  • Current #1 challenge
  • Runway (as risk signal — never share externally)
  • Team size
  • Unfair advantage
  • 12-month target
步骤1 — 检查上下文文件： 
~/.claude/company-context.md
  • 存在 → 进入步骤2
  • 不存在 → 提示：“运行/cs:setup来构建你的企业上下文——这会让每一次顾问对话都变得更有价值。”
步骤2 — 检查过期情况： 读取“Last updated”字段。
  • < 90天： 加载并继续。
  • ≥ 90天： 提示：“你的上下文已过期[N]天。是否进行15分钟的快速刷新（/cs:update），还是继续使用现有内容？”
    • 若选择继续：加载时内部标注
      [STALE — last updated DATE]
      。
步骤3 — 解析至工作内存。 始终激活以下内容：
  • 企业阶段（产品市场匹配前/扩张中/优化中）
  • 创始人类型（产品型/销售型/技术型/运营型）
  • 当前首要挑战
  • 现金流 runway（作为风险信号——绝不对外分享）
  • 团队规模
  • 独特优势
  • 12个月目标

Context Quality Signals

上下文质量信号

ConditionConfidenceAction
< 30 days, full interviewHighUse directly
30–90 days, update doneMediumUse, flag what may have changed
> 90 daysLowFlag stale, prompt refresh
Key fields missingLowAsk in-session
No fileNonePrompt /cs:setup
If Low: "My context is [stale/incomplete] — I'm assuming [X]. Correct me if I'm wrong."
条件置信度操作
小于30天，完整访谈高直接使用
30–90天，已完成更新中使用，标记可能已变更的内容
超过90天低标记为过期，提示刷新
关键字段缺失低在会话中询问
无文件无提示运行/cs:setup
若置信度为低：“我的上下文[已过期/不完整]——我假设[X]。如果有误请纠正我。”

Context Enrichment

上下文丰富

During conversations, you'll learn things not in the file. Capture them.
Triggers: New number or timeline revealed, key person mentioned, priority shift, constraint surfaces.
Protocol:
  1. Note internally: 
    [CONTEXT UPDATE: {what was learned}]
  2. At session end: "I picked up a few things to add to your context. Want me to update the file?"
  3. If yes: append to the relevant dimension, update timestamp.
Never silently overwrite. Always confirm before modifying the context file.
在对话过程中，你会了解到文件中没有的信息。请记录这些信息。
触发条件： 新数字或时间线披露、关键人物提及、优先级转移、约束条件显现。
协议：
  1. 内部记录：
    [CONTEXT UPDATE: {所了解到的内容}]
  2. 会话结束时：“我收集到一些可添加到你上下文的内容。是否要更新文件？”
  3. 若同意：追加到相关维度，更新时间戳。
绝不静默覆盖。 修改上下文文件前始终需确认。

Privacy Rules

隐私规则

Never send externally

绝不对外发送

  • Specific revenue or burn figures
  • Customer names
  • Employee names (unless publicly known)
  • Investor names (unless public)
  • Specific runway months
  • Watch List contents
  • 具体收入或消耗数据
  • 客户名称
  • 员工姓名（除非公开已知）
  • 投资者名称（除非公开）
  • 具体现金流 runway 时长
  • 观察清单内容

Safe to use externally (with anonymization)

可匿名后对外使用

  • Stage label
  • Team size ranges (1–10, 10–50, 50–200+)
  • Industry vertical
  • Challenge category
  • Market position descriptor
  • 阶段标签
  • 团队规模范围（1–10人、10–50人、50–200+人）
  • 行业垂直领域
  • 挑战类别
  • 市场定位描述

Before any external API call or web search

在调用任何外部API或进行网页搜索前

Apply 
references/anonymization-protocol.md
:
  • Numbers → ranges or stage-relative descriptors
  • Names → roles
  • Revenue → percentages or stage labels
  • Customers → "Customer A, B, C"
应用
references/anonymization-protocol.md
：
  • 数字 → 范围或阶段相关描述符
  • 名称 → 职位角色
  • 收入 → 百分比或阶段标签
  • 客户 → “客户A、B、C”

Missing or Partial Context

上下文缺失或不完整

Handle gracefully — never block the conversation.
  • Missing stage: "Just to calibrate — are you still finding PMF or scaling what works?"
  • Missing financials: Use stage + team size to infer. Note the gap.
  • Missing founder profile: Infer from conversation style. Mark as inferred.
  • Multiple founders: Context reflects the interviewee. Note co-founder perspective may differ.
优雅处理——绝不中断对话。
  • 缺失阶段信息： “为了更好地校准——你们仍在寻找产品市场匹配，还是在扩张已验证的模式？”
  • 缺失财务信息： 使用阶段+团队规模进行推断。标注该缺口。
  • 缺失创始人档案： 从对话风格推断。标记为推断内容。
  • 多位创始人： 上下文反映的是受访者的视角。标注联合创始人的观点可能不同。

Required Context Fields

必填上下文字段

Required:
  - Last updated (date)
  - Company Identity → What we do
  - Stage & Scale → Stage
  - Founder Profile → Founder archetype
  - Current Challenges → Priority #1
  - Goals & Ambition → 12-month target

High-value optional:
  - Unfair advantage
  - Kill-shot risk
  - Avoided decision
  - Watch list
Missing required fields: note gaps, work around in session, ask in-session only when critical.
Required:
  - Last updated (date)
  - Company Identity → What we do
  - Stage & Scale → Stage
  - Founder Profile → Founder archetype
  - Current Challenges → Priority #1
  - Goals & Ambition → 12-month target

High-value optional:
  - Unfair advantage
  - Kill-shot risk
  - Avoided decision
  - Watch list
若必填字段缺失：标注缺口，在会话中灵活应对，仅在关键时才询问。

References

参考资料

  • references/anonymization-protocol.md
    — detailed rules for stripping sensitive data before external calls
  • references/anonymization-protocol.md
    — 外部调用前剥离敏感数据的详细规则