guarantee-based-coding 0.2.0__py3-none-any.whl

gbc/assets/i18n/texts/setup.en.md

@@ -0,0 +1,74 @@
+# Wiring GBC into your agent
+
+GBC is installed. This is the wiring guide: it tells you **where the endpoints and
+files are** so your agent can reach them. It does **not** dictate *how* to wire them —
+that depends on how your particular agent framework loads MCP servers and skills.
+GBC only hands you the coordinates; you (or your agent) do the connecting.
+
+There are two independent ways to give an agent GBC's abilities. Use whichever your
+agent supports; you may use both.
+
+---
+
+## Option A — MCP (recommended when your agent speaks MCP)
+
+GBC ships a stdio MCP server exposing both subsystems: the guarantee engine
+(guarantee / dep / verify / refactor / tree / consistency / executor) **and** the
+intent documents (doc show / check / set-* / sync / migrate).
+
+**The endpoint** — start the server with:
+
+```
+gbc mcp up <ABSOLUTE_PATH_TO_YOUR_PROJECT>
+```
+
+Register that command as an MCP server wherever your framework keeps its MCP config.
+A typical stdio entry looks like (adapt to your framework's schema):
+
+```
+{{
+  "command": "gbc",
+  "args": ["mcp", "up", "/abs/path/to/your/project"]
+}}
+```
+
+Notes:
+- The project root is passed as that argument; the server keeps all mutable state
+  under your project's `.gbc/` (created on first write — you do not need to pre-make it).
+- If `gbc` is not on PATH for your launcher, use the interpreter form:
+  `<python> -m gbc.entry mcp up <project-root>`.
+- After registering, reload / reconnect MCP so your agent picks up the tools.
+
+---
+
+## Option B — Skills (for agents that don't use MCP, or where MCP is inconvenient)
+
+Because every GBC ability is also a plain `gbc ...` command, an agent that can run
+shell commands can use GBC through a set of **pre-authored skills** that teach it
+which commands to run. This is the CLI-side equivalent of MCP tool descriptions.
+
+**The files** — the bundled skills live here:
+
+```
+{skills_dir}
+```
+
+Copy (or symlink) those skill files into wherever your agent discovers skills. GBC
+does not place them for you, because every framework reads skills from a different
+location — materializing the files is ours, placing them is yours.
+
+---
+
+## Verify it works
+
+Once wired, have your agent run a read-only call — e.g. the `tree` tool over MCP, or
+`gbc tree` on the CLI. If it returns your project's dependency tree (or an empty one
+for a fresh project), GBC is reachable.
+
+## One thing GBC does NOT do for you
+
+GBC gives abilities, not restraint. The safety rules (who may edit `.gbc/`, when
+intent changes need human sign-off) are printed by `gbc rules`, and their
+**enforcement** must come from your agent framework (e.g. a pre-tool-use hook) — the
+same hook applies whether the ability arrived via MCP or CLI. Installing GBC does not
+make you automatically safe; read `gbc rules` and wire the enforcement yourself.

gbc/assets/i18n/texts/setup.zh.md

@@ -0,0 +1,69 @@
+# 把 GBC 接入你的 agent
+
+GBC 已经装好了。这是一份**接线指南**：它告诉你**端点和文件在哪**，好让你的 agent
+够得着它们。它**不**规定*具体怎么接*——那取决于你所用的 agent 框架如何加载 MCP
+server 和 skill。GBC 只给你坐标，接线由你（或你的 agent）来做。
+
+给 agent 赋予 GBC 能力有两条彼此独立的路。你的 agent 支持哪条就用哪条，也可以都用。
+
+---
+
+## 方案 A —— MCP（你的 agent 会说 MCP 时推荐）
+
+GBC 自带一个 stdio MCP server，暴露两个子系统：保证引擎（guarantee / dep / verify /
+refactor / tree / consistency / executor）**以及**意图文档（doc show / check / set-* /
+sync / migrate）。
+
+**端点** —— 用下面的命令启动 server：
+
+```
+gbc mcp up <你项目根的绝对路径>
+```
+
+把这条命令注册为 MCP server，注册位置在你框架存放 MCP 配置的地方。一个典型的 stdio
+条目形如（按你框架的 schema 调整）：
+
+```
+{{
+  "command": "gbc",
+  "args": ["mcp", "up", "/abs/path/to/your/project"]
+}}
+```
+
+说明：
+- 项目根作为那个参数传入；server 把一切可变状态放在你项目的 `.gbc/` 下（首次写入时
+  自动创建——你不必预先建它）。
+- 如果启动器的 PATH 上没有 `gbc`，改用解释器形式：
+  `<python> -m gbc.entry mcp up <项目根>`。
+- 注册后重新加载 / 重连 MCP，让你的 agent 拉到这些工具。
+
+---
+
+## 方案 B —— Skills（给不用 MCP、或 MCP 不方便的 agent）
+
+因为 GBC 的每一项能力同时也是一条普通的 `gbc ...` 命令，一个能跑 shell 的 agent 可以
+通过一套**预组 skill** 来使用 GBC——这些 skill 教它该敲哪些命令，等价于 CLI 侧的 MCP
+工具描述。
+
+**文件** —— 随包分发的 skill 在这里：
+
+```
+{skills_dir}
+```
+
+把这些 skill 文件拷贝（或软链）到你的 agent 发现 skill 的位置。GBC 不替你放置它们，
+因为每个框架读 skill 的位置都不同——把文件准备好是我们的事，放到哪由你决定。
+
+---
+
+## 验证是否接通
+
+接好后，让你的 agent 跑一次只读调用——比如经 MCP 调 `tree` 工具，或在 CLI 敲
+`gbc tree`。如果它返回了你项目的依赖树（新项目则是一棵空树），说明 GBC 已经够得着了。
+
+## 有一件事 GBC 不替你做
+
+GBC 给的是能力，不是约束。安全规则（谁能改 `.gbc/`、意图变更何时需人类签字）由
+`gbc rules` 打印，而它们的**强制执行**必须来自你的 agent 框架（例如 pre-tool-use
+hook）——无论能力是经 MCP 还是 CLI 到达，同一个 hook 都适用。装了 GBC 并不会让你自动
+安全；请读 `gbc rules`，并自己把强制执行接上。

gbc/assets/skills/README.md

@@ -0,0 +1,16 @@
+# GBC pre-authored skills (for CLI-only agents)
+
+This directory ships **pre-authored skills** that teach an agent how to drive GBC
+through its plain `gbc ...` commands — the CLI-side equivalent of the MCP tool
+descriptions. They exist for agents that don't speak MCP, or where MCP is
+inconvenient.
+
+`gbc setup` points users here by absolute path; copying the skill files into
+wherever their agent discovers skills is up to them (every framework reads skills
+from a different place — GBC materializes the files, the user places them).
+
+## What's here
+
+- **`gbc-cli/`** — teaches an agent to drive GBC through its `gbc ...` commands
+  (the CLI-side equivalent of the MCP tool descriptions). Point your agent at
+  `gbc-cli/SKILL.md`.

gbc/assets/skills/gbc-cli/SKILL.md

@@ -0,0 +1,143 @@
+---
+name: gbc-cli
+description: Drive GBC (Guarantee-Based Coding) through its `gbc` command-line interface. Use this whenever you need to register/verify/inspect guarantees, dependencies, or intent docs and MCP is not available to you (or you prefer the CLI). This is the CLI-side equivalent of GBC's MCP tools — every ability is a `gbc ...` subcommand. Assumes the `gbc` command is already installed and on PATH.
+---
+
+# gbc-cli: using GBC from the command line
+
+GBC turns implicit inter-module dependencies into **named, executable guarantees**: a guarantee
+is a named behavior a file promises, backed by a test. Change code → re-run the affected
+guarantees → green means every dependent's promise still holds. This skill tells you which `gbc`
+commands realize those abilities, so you can use GBC without an MCP connection.
+
+Everything here is a plain shell command. If `gbc` is not on PATH, substitute
+`python -m gbc.entry` for `gbc` (same subcommands).
+
+> **Which project am I acting on?** Commands act on the current GBC target project, which
+> defaults to the directory you run `gbc` from (its cwd) — no environment variable needed. Just
+> `cd` into the project root before running commands. All paths you pass to commands are
+> **project-relative** (e.g. `app/core/config.py`).
+
+---
+
+## The core loop (register once, verify forever)
+
+1. **Register an executor** (how tests run) — once per project, by name.
+2. **Create a guarantee** on a provider file — born-green: the test runs immediately, and
+   creation is refused if it fails.
+3. **Register dependencies** — record that a consumer relies on a provider's symbol/guarantee.
+4. **Verify** after changes — run a provider's guarantees; green iff nothing failed.
+
+---
+
+## Guarantees — `gbc guarantee`
+
+| Command | What it does |
+|---------|--------------|
+| `gbc guarantee create <provider> <id> <test> <executor> <desc>` | Create a named guarantee. **Born-green**: runs the test now, refuses if it fails. Add `--heavy N` (cost rank; `>=1` is skipped in batch verify), `--timeout S`, or `--disabled` (placeholder that skips born-green — only to break a circular dependency; enable it later). |
+| `gbc guarantee update <provider> <id>` | Change fields: `--desc`, `--test`, `--executor`, `--heavy`, `--timeout`. Changing the test/executor re-runs born-green. |
+| `gbc guarantee retire <provider> <id>` | Delete a guarantee. **Refused if it still has dependents** — migrate them first. |
+| `gbc guarantee disable <provider> <id>` | Suspend born-green/batch verify for it while keeping its id and all edges. Escape hatch for refactors; **not** a delete. |
+| `gbc guarantee enable <provider> <id>` | Re-run born-green now; clears disabled only if the test passes. |
+| `gbc guarantee list <provider>` | List every guarantee a provider offers, with state and dependent count. |
+
+**Id convention**: `<symbol>.<behavior>`, e.g. `get_config.never_none`. Do **not** encode the
+provider path in the id — the path is carried by the `<provider>` argument. Ids need only be
+unique per provider.
+
+---
+
+## Dependencies — `gbc dep`
+
+| Command | What it does |
+|---------|--------------|
+| `gbc dep add <consumer> <provider> <symbol>` | Register a **free** symbol-level dependency (depends on the symbol existing, not on a specific behavior; no test, no reverse edge). |
+| `gbc dep add <consumer> <provider> <symbol> -g <guarantee_id>` | Register a **behavior** dependency on an existing guarantee. The reverse edge (provider's dependents) is written automatically. Multiple consumers may share one guarantee. |
+| `gbc dep remove <consumer> <provider> <symbol> [-g <id>]` | Remove one guarantee from the edge (`-g`), or the whole symbol edge (no `-g`). |
+| `gbc dep of <consumer>` | List every dependency edge a file declares. |
+| `gbc dep who <provider> [-s <symbol>] [-g <id>]` | Reverse lookup: who depends on this provider. Replaces ad-hoc grep. |
+
+---
+
+## Verify — `gbc verify`
+
+| Command | What it does |
+|---------|--------------|
+| `gbc verify provider <provider>` | Run all of a provider's guarantees. Heavy guarantees above the threshold are skipped and reported (not failed). Add `--max-heavy N` to run heavier ones. **GREEN iff nothing failed.** |
+| `gbc verify single <provider> <id>` | Run one guarantee by id — always runs, ignoring the heavy threshold. Add `-v` for full stdout/stderr. |
+
+**Gate semantics**: a test that ran is either pass or fail; a test that was *skipped* (heavy) is
+reported loudly but does **not** turn the gate red. Green = no failures.
+
+---
+
+## Inspect — `gbc tree` / `gbc doctor`
+
+| Command | What it does |
+|---------|--------------|
+| `gbc tree` | Render the whole `.gbc` tree as one AI-readable dependency document (intent backbone + dependency edges + provided guarantees). Add `--detail` for guarantee desc/test/heavy, `--gaps` for registration gaps. **Start here for a whole-project overview.** |
+| `gbc doctor check` | Global consistency lint: dangling references, two-way edge drift, and disabled guarantees (reported loudly, not as errors). |
+
+---
+
+## Executors — `gbc executor`
+
+An executor is a named recipe for running tests, stored per project. Register it once, then
+guarantees reference it by name.
+
+```bash
+gbc executor upsert <name> --json '{"command": ["pytest", "{file}", "-x", "-q"], "cwd": "/abs/project", "timeout": 30, "env_ops": [{"key": "PYTHONPATH", "action": "prepend", "value": "/abs/project"}]}'
+```
+
+- `command`: argv parts; `{file}` is substituted with the test selector.
+- Or pass a JSON file with `--file <path>` instead of `--json`.
+- Give it a **project-scoped name** (e.g. `pytest-<project>`) so it won't collide with another
+  project's executor.
+
+---
+
+## Move / rename — `gbc refactor` (never hand-fix the graph)
+
+Relocating a file or renaming a symbol desyncs every path-addressed reference. Use these instead
+of editing `.gbc` by hand:
+
+| Command | What it does |
+|---------|--------------|
+| `gbc refactor file <old> <new>` | Move a file/dir + its `.gbc` metadata, rewrite all references graph-wide, auto-disable the moved file's guarantees (their tests break until you fix imports). Ids are unchanged (path-free). Idempotent. |
+| `gbc refactor func <provider> <old_symbol> <new_symbol>` | Rename a symbol: rewrite consumers' edges + the guarantee ids under that symbol, auto-disable them. You rename `def`/call sites in source, then `enable`. |
+| `gbc refactor rename-id <provider> <old_id> <new_id>` | Rename a guarantee id, keeping both directions consistent. |
+
+After any refactor: fix imports, move the test files and `gbc guarantee update <p> <id> --test ...`,
+then `gbc guarantee enable <p> <id>` for each disabled id.
+
+---
+
+## Intent docs — `gbc doc`
+
+`gbc.md` files hold the project's architectural intent. `gbc doc` is the compliant read/write
+entry — it keeps each doc's three-section structure and parent/child consistency for you.
+
+| Command | What it does |
+|---------|--------------|
+| `gbc doc show <folder>` | View a folder's intent / constraints / entries. Root folder is `""` or `.`. |
+| `gbc doc check` | Whole-tree intent consistency lint (DRIFT/ORPHAN are errors, STUB is a note). |
+| `gbc doc set-intent <folder> "<text>"` | Set a folder's intent (auto-projected into the parent entry). |
+| `gbc doc set-constraints <folder> "<text>"` | Set internal constraints (local only). |
+| `gbc doc set-file <folder> <name> "<desc>"` | Add/update a file entry (name without `/`). |
+| `gbc doc rm-entry <folder> <name>` | Remove a doc entry (does not delete the file on disk). |
+| `gbc doc sync` | Deterministically repair parent/child drift. |
+
+> If a `<text>` argument begins with `-`, put `--` before it so it isn't parsed as an option:
+> `gbc doc set-intent app -- "- a line starting with a dash"`.
+
+**Writing intent is changing human-held architecture truth.** Whether it needs your human's
+sign-off is set by your agent framework's rules/hooks, not by this tool. Never hand-edit `gbc.md`.
+
+---
+
+## The boundary (read `gbc rules`)
+
+GBC gives abilities, not restraint. Who may edit `.gbc/`, when intent needs human sign-off — those
+rules are printed by `gbc rules`, and their **enforcement** must come from your agent framework
+(e.g. a pre-tool-use hook). The same enforcement applies whether you reach GBC via CLI or MCP.
+Run `gbc rules` and follow what your human has adopted.

gbc/entry.py

@@ -0,0 +1,126 @@
+# Copyright 2026 Jesse-x86
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+#     http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+"""`gbc` 的唯一入口 —— 纯分发器。
+
+不实现任何业务:只把两个子系统的表面**组合**成一棵命令树,再挂上跨子系统的
+服务/初始化命令。各表面自己是薄的、只调各自的 base。
+
+  gbc guarantee|dep|verify|doctor|executor|refactor|tree   → 保证引擎(interface.cli)
+  gbc doc <...>                                            → 意图文档(intent.cli)
+  gbc mcp up [root]                                        → 保证引擎的 MCP 表面(interface.mcp)
+  gbc editor up                                            → 意图文档的 web 表面(intent.editor)
+  gbc rules / setup                                        → 跨子系统的辅助命令
+
+[project.scripts] 的 `gbc` 指向本模块的 app。
+"""
+from typing import Optional
+
+import typer
+
+from gbc.app.interface.cli import app as guarantee_cli
+from gbc.app.intent.cli import doc_app
+
+# 顶层命令树 = 保证引擎的 cli(含 guarantee/dep/verify/doctor/executor/refactor/tree
+# 与全局 --lang callback),再往上挂 doc 子树与服务/辅助命令。
+app = guarantee_cli
+app.add_typer(doc_app, name="doc")
+
+mcp_app = typer.Typer(help="cli.mcp.help")
+editor_app = typer.Typer(help="cli.editor.help")
+app.add_typer(mcp_app, name="mcp")
+app.add_typer(editor_app, name="editor")
+
+
+@mcp_app.command("up")
+def mcp_up(
+    project_root: Optional[str] = typer.Argument(None, help="cli.mcp_up.arg.project_root"),
+):
+    """启动 GBC 的 stdio MCP server（常驻）。由 MCP 表面自己的启动器承载。"""
+    from gbc.app.interface.mcp import run_server
+    run_server(project_root)
+
+
+@editor_app.command("up")
+def editor_up(
+    root: Optional[str] = typer.Option(None, "--root", "-r", help="默认项目路径，前端预填并自动加载"),
+    host: str = typer.Option("127.0.0.1", "--host", help="监听地址"),
+    port: int = typer.Option(8765, "--port", "-p", help="监听端口"),
+    lang: Optional[str] = typer.Option(None, "--lang", help="界面语言 zh/en"),
+):
+    """启动意图编辑器 web 服务（常驻）。"""
+    from gbc.app.i18n import set_lang, resolve_lang, t
+    from gbc.app.intent.editor import run_editor
+    set_lang(resolve_lang(lang))
+    typer.echo(t("editor.starting", host=host, port=port))
+    run_editor(host=host, port=port, root=root or "")
+
+
+@app.command("rules", help="cli.rules.help")
+def rules_cmd(
+    lang: Optional[str] = typer.Option(None, "--lang", help="cli.option.lang.help"),
+):
+    """打印作者推荐的围栏规则集到 stdout（推荐默认，非强制沙箱）。"""
+    from gbc.app.i18n import set_lang, resolve_lang, load_text
+    set_lang(resolve_lang(lang))
+    # 纯文本发射器：用 print 而非 rich，便于管道/复制。
+    print(load_text("rules"))
+
+
+@app.command("setup", help="cli.setup.help")
+def setup_cmd(
+    lang: Optional[str] = typer.Option(None, "--lang", help="cli.option.lang.help"),
+):
+    """打印本地化的接线指南到 stdout：怎么把 MCP / skills 接入你的 agent。"""
+    from gbc.app.i18n import set_lang, resolve_lang, load_text
+    from gbc.app.assets import SKILLS_DIR
+    set_lang(resolve_lang(lang))
+    # 与 rules 同构：纯文本发射器。只给坐标(skills 目录/MCP 入口)，
+    # 具体怎么接入取决于用户 agent——{skills_dir} 填入随包 skills 的真实路径。
+    print(load_text("setup").format(skills_dir=str(SKILLS_DIR)))
+
+
+def get_wrapped_app():
+    """返回经 i18n 完整包装的 Click Group（供 main_cli/main + CliRunner 共用）。
+
+    GBC 不在 typer.main.get_group 上做全局 monkey-patch——只在 GBC 自己的
+    命令树上做局部包装，不污染同一进程内其他 Typer 应用。
+    """
+    from gbc.app.interface.cli import i18n_wrap_click_tree
+    root = typer.main.get_command(app)
+    i18n_wrap_click_tree(root)
+    return root
+
+
+def main_cli() -> None:
+    """GBC console_scripts 入口：i18n 包装后交给 Click（含 sys.exit）。
+
+    这是 pyproject.toml [project.scripts] gbc 指向的入口。
+    pipx 安装后 PATH 上的 `gbc` 命令经此路径执行，与 main() 共用 get_wrapped_app()。
+    """
+    get_wrapped_app()(standalone_mode=True)
+
+
+def main() -> None:
+    """GBC 唯一入口（python -m）：组合命令树 → i18n 包裹 → 交给 Click 执行。
+
+    与 main_cli 共用 get_wrapped_app()，差异只在 standalone_mode：
+    - main_cli(standalone_mode=True)  → sys.exit，给 pipx/setuptools console_scripts
+    - main(standalone_mode=False)     → 返 exit code，给 python -m 调用链
+    """
+    get_wrapped_app()(standalone_mode=False)
+
+
+if __name__ == "__main__":
+    main()

guarantee_based_coding-0.2.0.dist-info/METADATA

@@ -0,0 +1,108 @@
+Metadata-Version: 2.4
+Name: guarantee-based-coding
+Version: 0.2.0
+Summary: Make code safely modifiable even when not fully understood — turn implicit inter-module dependencies into explicit, executable, verifiable guarantees.
+Author: Jesse-x86
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/Jesse-x86/guarantee-based-coding
+Project-URL: Repository, https://github.com/Jesse-x86/guarantee-based-coding
+Keywords: guarantee,testing,ai-coding,mcp,code-safety
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Software Development :: Testing
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: typer[all]
+Requires-Dist: pydantic
+Requires-Dist: mcp<2.0,>=1.0
+Dynamic: license-file
+
+# Guarantee-Based Coding (GBC)
+
+**与其指望 AI 更聪明，不如让再笨的 agent 也改不坏你的代码。**
+
+**English version: [docs/en/README.md](docs/en/README.md)**
+
+GBC 把「这次改动会不会悄悄碰坏别处」从一种担心，变成可以当场验证的事实：你在意的行为被登记成
+一条条带测试的**保证（guarantee）**，每次改完一跑——全绿就安心，有红就精确告诉你碰坏了谁、谁在
+依赖它。
+
+---
+
+## 🚀 快速开始
+
+```bash
+pipx install guarantee-based-coding
+gbc setup        # 打印本地化接线指南：怎么把 MCP / skills 接入你的 agent
+```
+
+装好后 `gbc` 命令即在 PATH 上。完整上手（安装 → 接入 agent → 冒烟验证）见
+**[docs/zh/quick-start.md](./docs/zh/quick-start.md)**。
+
+想让 agent 替你接入？把 **[docs/zh/onboarding-agent.md](./docs/zh/onboarding-agent.md)** 交给它。
+
+---
+
+> 🚧 **交互式 demo 施工中**：旧的演示套件已废弃，新的交互式演示正在筹备。目前请直接读文档上手。
+
+---
+
+## 📚 文档
+
+| 你想 | 看这里 |
+|------|--------|
+| 装好并跑起来 | [快速开始](./docs/zh/quick-start.md) |
+| 懂 GBC 在保护什么 | [核心概念](./docs/zh/concepts.md) |
+| 在 GBC 下安全改代码 | [工作流](./docs/zh/workflow.md) |
+| 查命令 / 工具 / executor | [参考手册](./docs/zh/reference.md) |
+| 你是 agent，被要求接入 GBC | [Agent 上手](./docs/zh/onboarding-agent.md) |
+
+English docs: [docs/en/](./docs/en/)。
+
+---
+
+## 核心想法
+
+代码之间的依赖本质上是一组**保证**。模块 A 依赖模块 B，不是依赖它的实现细节，而是依赖它的某些
+行为承诺——返回值的类型、格式、语义。把这些保证从隐含变成**显式、可执行、可验证**，正确性的判定
+就从「AI 觉得自己改对了」变成「所有被依赖的保证仍通过」——一个可机械验证的布尔条件。
+
+![无 GBC vs 有 GBC](docs/assets/workflow-comparison.svg)
+
+GBC **不是**另一个要挑战 Cursor / Aider 的 AI 编程助手，而是填补它们在大型项目里缺的一环：
+**机器可判定的变更边界**。它与那些 agent 配合——改前查依赖树，改后必须跑通所有相关保证；也区别
+于 CI——CI 是事后的，GBC 是准入制的门禁，错误在落地前就被拦在 agent 的上下文里。
+
+完整概念、架构图、与已有概念（Design by Contract / 测试）的区别，见
+[核心概念](./docs/zh/concepts.md)。
+
+---
+
+## 当前状态
+
+GBC 目前是一个可用的 Python 分发包（`pipx install guarantee-based-coding`），自身用 GBC 管理自己的
+`.gbc/`（dogfooding）：
+
+- ✅ 核心保证机制（具名 id、多对一、出生即绿、退休保护、反查）
+- ✅ 多语言 executor 配置
+- ✅ CLI + MCP 双接口（含意图文档 `gbc doc` 全进 MCP）
+- ✅ 意图文档子系统（`gbc doc` / web 编辑器）
+- ✅ 随包分发的接线指南（`gbc setup`）与 CLI-only agent 的 skill 包
+- ✅ 原子文件写入 + 备份
+
+
+**诚实的局限**：保护能力上限 = 测试质量（测试只走 happy path 就是虚假安全感）；依赖需主动登记，
+覆盖率随项目增长需持续投入；每次验证真实跑测试，有一定延迟。详见
+[核心概念 · 局限性](./docs/zh/concepts.md#局限性诚实地说)。
+
+---
+
+## 许可
+
+本项目采用 [Apache-2.0](./LICENSE) 许可证。
+
+## 联系
+
+如果你对这个方向感兴趣，欢迎 star、issue 或者直接联系我。

guarantee_based_coding-0.2.0.dist-info/RECORD

@@ -0,0 +1,48 @@
+gbc/__init__.py,sha256=IWieHkgW4RyX8FMHea6qZ35p3uOSQhu2M8CltlZ_V-Q,843
+gbc/entry.py,sha256=B0-xUnLWBEVgayHvwIazvh-k6aOywlXTS1Yv-zxiO8s,5218
+gbc/app/__init__.py,sha256=I4xqrxoGB8PldKRIqY5lMGQzPhiZOqpJRa0PtjBVagI,574
+gbc/app/assets.py,sha256=GHD-AhfRPXqKhNYS9aH93J6kUnKkXBDVrLm5nLDGTAQ,1730
+gbc/app/config/__init__.py,sha256=I4xqrxoGB8PldKRIqY5lMGQzPhiZOqpJRa0PtjBVagI,574
+gbc/app/config/backups.py,sha256=rNM-Fal4PuARasNKTUYUjVt3JCd9uXoAgAeGlVA9li4,868
+gbc/app/config/base.py,sha256=6qcjh4xQ36uLCX_rod5QvNwDgHfBr51AVxPNbaqL7Zk,993
+gbc/app/config/executor.py,sha256=STfgDhA48-KL9hEyImHVZ5yIEJUtTHfOltRFtB7ipww,5186
+gbc/app/config/project.py,sha256=CWuAo4tvwWO39uBlfBpwoHx5TAyFbbydwle1Q2anr5w,1265
+gbc/app/core/__init__.py,sha256=I4xqrxoGB8PldKRIqY5lMGQzPhiZOqpJRa0PtjBVagI,574
+gbc/app/core/env.py,sha256=9ixnfXGDSzoI7gMK5F3n-DHqVr--wc0n0PF5qmG8iR0,1917
+gbc/app/core/executor.py,sha256=eFfxVcOkvtKy9Tg1TPLfh403NHYxS5-63CiYM3F8tZU,3334
+gbc/app/core/guarantee.py,sha256=hDoltUPQleNXMxyAfx13G-tctTLGBP9jf_EWRjBv7Kw,13226
+gbc/app/i18n/__init__.py,sha256=5vrC6Z2wuCBTmKP11PafV6fY2C7SxN4HW9ZK63z_Ku0,1447
+gbc/app/i18n/lang.py,sha256=NZucZuA3Hh3DSiTJSQw32mpzV8LlT8hgwqmfaAM1dDU,2985
+gbc/app/i18n/translate.py,sha256=NA-vBEQ3Pc2YeRsA_xX-kFeZT6fHfXonlkDqNkTVwy4,2957
+gbc/app/intent/__init__.py,sha256=v96XUU2CyukyXD_W526-13Fjqt83UtExblMxMX6MZXY,868
+gbc/app/intent/base.py,sha256=0HtFih8o_hT4Ml9txMUZ_kr9vBI1iTx8PORdVwxWKfE,12706
+gbc/app/intent/cli.py,sha256=nH8K_ug0kkJnTi8gaWv8y38icCxfpwRWiOUGK_y-B0E,4436
+gbc/app/intent/editor.py,sha256=kjWzvXNMsQDTMf5GfyPxfB-6pE_g_lXhnwRzA3NAlm8,4183
+gbc/app/interface/__init__.py,sha256=I4xqrxoGB8PldKRIqY5lMGQzPhiZOqpJRa0PtjBVagI,574
+gbc/app/interface/base.py,sha256=aaNSZls0DP67Eh9Ishgqgo-mWCTEWAg5fGuqNya7eeE,36648
+gbc/app/interface/cli.py,sha256=bF56LuONiUk049Zz2G7bQkY3FrG_BQJvlv6asSpl_MI,24057
+gbc/app/interface/mcp.py,sha256=gWBZDfhgbQETREC_-a5GzCx-lXm81Q9n1n83yOkrwCk,23077
+gbc/app/models/__init__.py,sha256=I4xqrxoGB8PldKRIqY5lMGQzPhiZOqpJRa0PtjBVagI,574
+gbc/app/models/errors.py,sha256=ZATZC0fK5RBCSkE3Jf-SMBdtBrgLV_qoeg-Sm3hWkXo,5734
+gbc/app/models/meta.py,sha256=edRIt5JVRBNKHiqplE8r5ex8_-U2iFEuY6BxgRp54Cc,4753
+gbc/app/models/verify.py,sha256=2i6hBRymYyU8bntxdcCJ-r-wT0uUR0yfy0iZc0JO_k4,2439
+gbc/app/utils/__init__.py,sha256=I4xqrxoGB8PldKRIqY5lMGQzPhiZOqpJRa0PtjBVagI,574
+gbc/app/utils/file_utils.py,sha256=njUkbhPELGDmSTbwjMnbLsGggDOcT-3C6DI2fieP8Gw,925
+gbc/app/utils/gbc_md.py,sha256=G-tVcFxl0YGXzjwT_PqQ0G6qr5-3XKkm27DWq4EnCwQ,4370
+gbc/app/utils/json_model_operator.py,sha256=xVv1WLfytLRT98G_JGHT_hB_orVXvifgWz6PPHROxXw,2501
+gbc/app/utils/safe_file_writer.py,sha256=57_5sUa6dhEyE_wOkJFfPwmMm6gypS04xPw-zAC3qJE,6944
+gbc/assets/editor/index.html,sha256=sqiwu6Gx4ShQBcJpegBVfaXzWC8ET4xTaOLHfEPohfA,13441
+gbc/assets/i18n/catalog/en.json,sha256=u2Ium5ZNzZu4sfrrb6ia5iq_0MHHB8A65mqy3YTPYRY,3608
+gbc/assets/i18n/catalog/zh.json,sha256=iVjfJ3b7gLtWFFD7UKJzn4utFq69FRtRhHR5fEZ1LvM,3651
+gbc/assets/i18n/texts/rules.en.md,sha256=ZF8z_yirFkH2gsRmhNfHP6LVDHGKwtb7T21MEU2qFbc,1656
+gbc/assets/i18n/texts/rules.zh.md,sha256=LdV225wwelzLYckAU6bskU3ePGLrahpbtDSE1Lav-Us,1377
+gbc/assets/i18n/texts/setup.en.md,sha256=_bl3jnulNaWOOKcDhv7pwXphDAL_690TCredRcjYjq0,2817
+gbc/assets/i18n/texts/setup.zh.md,sha256=FMAxeKUXPh-UuMMdW5gq8Bp-YF_TAFf4E0u8KLI-Kyg,2775
+gbc/assets/skills/README.md,sha256=R0D3Uub-QIt6AfygbL5dgdZoVidrtr5Nb4x228zxWZA,737
+gbc/assets/skills/gbc-cli/SKILL.md,sha256=fyXIM-ZefWQ1fH1l1iJurAHAsgTl9PXfYesRIrqEcSs,8355
+guarantee_based_coding-0.2.0.dist-info/licenses/LICENSE,sha256=yVuuHRzgI17MzTVgt3LsHvuX80innw--CmNPDCzO_iw,11358
+guarantee_based_coding-0.2.0.dist-info/METADATA,sha256=dt4vycGpi3LJQ4wUUE6Q-GFNaRIe3wHnKU7LVXiKxqU,4385
+guarantee_based_coding-0.2.0.dist-info/WHEEL,sha256=K260EYznzXsJYBQGqmI8VTxEdiZYNvDZwW9cBh9-_MA,91
+guarantee_based_coding-0.2.0.dist-info/entry_points.txt,sha256=f2j8lLb4FYNVhs8sWlZiH5B81fTmnjhN_aC06E2gxtk,43
+guarantee_based_coding-0.2.0.dist-info/top_level.txt,sha256=oxAntW6an4vJFFPhygPs75vQlezyyttPbBDS_5W3Ltg,4
+guarantee_based_coding-0.2.0.dist-info/RECORD,,

guarantee_based_coding-0.2.0.dist-info/WHEEL

@@ -0,0 +1,5 @@
+Wheel-Version: 1.0
+Generator: setuptools (83.0.0)
+Root-Is-Purelib: true
+Tag: py3-none-any
+

guarantee_based_coding-0.2.0.dist-info/entry_points.txt

@@ -0,0 +1,2 @@
+[console_scripts]
+gbc = gbc.entry:main_cli