Back to Details

bootstrap

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

bootstrap — create the brain

bootstrap — 创建大脑

Interview the operator and create the minimum brain. Do not ask about scope: the building layer is activated per initiative, not per user.
向操作者提问并创建最小化大脑。无需询问范围：构建层会针对每个任务启动，而非针对单个用户。

Step 0 — install the OS if it is missing

步骤0 — 若系统缺失则安装OS

Everything below assumes the product is hooked into the brain (
.os/core
resolves). If it does not — you were installed standalone, e.g. from skills.sh — install it first:
  1. Clone 
    github.com/pedroromeroluna/ai-first-os
    to a fixed local folder outside the brain (the operator will need it to update later).
  2. Run 
    <clone>/core/install.sh <brain-path>
    — idempotent; it hooks the session contract, the resolvers, the subagents and all sixteen skills by symlink.
  3. Continue with the interview below.
If 
.os/core
already resolves, skip this step entirely.
以下所有操作均假设产品已连接至大脑（
.os/core
可解析）。若未连接——例如你是从skills.sh单独安装的——请先执行安装：
  1. 将
    github.com/pedroromeroluna/ai-first-os
    克隆至大脑外部的固定本地文件夹（操作者后续需要此文件夹进行更新）。
  2. 运行
    <clone>/core/install.sh <brain-path>
    ——此操作具有幂等性；它会通过符号链接关联会话契约、解析器、子Agent以及全部16项技能。
  3. 继续进行下方的提问环节。
若
.os/core
已可解析，请直接跳过此步骤。

The interview

提问环节

Five questions. One at a time, and do not move on until you have the answer.
  1. What is your name?
  2. Profile: what you do, what you are on today, what you decide.
  3. Voice: how you write when you write well — language, register, words you do not use.
  4. How you want to be answered: what you expect from an agent. Length, order, what annoys you.
  5. Your organizations: where you work. For the typical case —one person, one employer— that is one. For each one ask what it does and what you do there; the role is written by the system.
Return the answers summarized and wait for approval before writing anything.
共五个问题。每次仅提问一个，得到答案后再继续下一个。
  1. 你的名字是什么？
  2. 个人简介：你的工作内容、当前状态、职责权限。
  3. 语气风格：你写作时的理想风格——语言类型、语体级别、禁用词汇。
  4. 期望回复方式：你对Agent的回复要求。包括长度、结构、反感点。
  5. 所属组织：你的工作单位。对于典型情况——一人就职于一家雇主——只需回答一个。针对每个组织，需询问组织业务和你的职位；角色信息将由系统写入。
汇总答案并等待操作者确认后，再进行后续写入操作。

What it writes

写入内容

Build an answers file and run the deterministic part:
.os/core/lib/bootstrap.sh --brain . --answers <file>
Format of the answers file, one key per line:
name: <name>
profile: <one item>
voice: <one item>
reply: <one item>
org: <Name> | <role> | <owner> | <identity file>
profile
, 
voice
, 
reply
and 
org
repeat. In 
org
, the owner and the identity file are optional: with no owner the operator is used, and with no identity a placeholder text is left.
The result is 
operator.md
, 
voice.md
, 
resolver.md
, 
tree.md
and one folder per organization. 
voice.md
is the operator's voice — it used to live in a section of 
operator.md
, and from now on it is its own file: one identity, two questions, never the same sentence in both. Nothing else: the inbox, the root's own work (initiatives, backlog, decisions, learnings) and the environment table are born with their first piece of data, like any node.
It runs once per brain. If the root pieces already exist, the script stops instead of rewriting them. Adding an organization to a brain that already exists is 
new-org
's job.
创建答案文件并执行确定性部分：
.os/core/lib/bootstrap.sh --brain . --answers <file>
答案文件格式，每行一个键值对：
name: <姓名>
profile: <一项内容>
voice: <一项内容>
reply: <一项内容>
org: <名称> | <角色> | <所有者> | <身份文件>
profile
、
voice
、
reply
和
org
可重复填写。在
org
中，所有者和身份文件为可选项：若未指定所有者，则默认使用操作者；若未指定身份文件，则留占位文本。
执行后将生成
operator.md
、
voice.md
、
resolver.md
、
tree.md
以及每个组织对应的一个文件夹。
voice.md
记录操作者的语气风格——它曾是
operator.md
中的一个章节，现在成为独立文件：一个身份信息，两个问题，两份文件中不会出现相同语句。除此之外：收件箱、根节点自身的工作内容（任务、待办事项、决策、学习记录）以及环境表会在首次加入数据时生成，与其他节点一致。
每个大脑仅执行一次此操作。若根节点文件已存在，脚本将停止运行，不会覆盖重写。向已存在的大脑添加组织是
new-org
的职责。

When it finishes

完成后操作

  • Show the tree created and what each file answers, in outcomes and not in canonical names.
  • If the identity cap warning appears, pass it through as is: the operator chooses the way out.
  • If the script reports 
    sin dato:
    or 
    sin crear:
    , pass it through whole and ask again for what is missing. A gap nobody names is a gap nobody fills.
  • Handoff: if the operator wants to add another organization, the add an organization capability is needed. If it is not available, say so and continue.
  • 展示创建的路径树，以及每个文件对应的用途，用成果描述而非标准名称。
  • 若出现身份上限警告，直接原样告知操作者：由操作者选择解决方式。
  • 若脚本提示
    sin dato:
    或
    sin crear:
    ，完整传达该信息并再次询问缺失内容。无人提及的缺口将永远无法填补。
  • 交接：若操作者想要添加另一个组织，需使用添加组织功能。若该功能不可用，需告知操作者并继续后续流程。