BP-Wiki Starter

BP-Wiki Starter

GitHub language switch: expand the section you want to read.

GitHub 语言切换：展开你想阅读的语言版本。

BP-Wiki Starter: Free Entry Kit for Public OS Shell

BP-Wiki Starter is the free Obsidian entry point for Public OS Shell.

Public OS Shell is a public-safe cognitive operating system shell for AI-assisted knowledge work. It is designed for people who want their Obsidian vault to support reading, research, writing, projects, agent collaboration, review, and long-term evolution instead of becoming another folder archive.

The 12 starter templates are included as the lightweight onboarding layer. The core product idea is Public OS Shell: the operating philosophy, architecture, governance rules, and upgrade path behind a serious AI-ready knowledge workspace.

What

Public OS Shell is not a template collection. It is an operating model for turning a vault into a controlled human-AI work system.

It defines:

• how inputs enter the system;
• how unfinished material stays in inbox or staging;
• how projects, knowledge, skills, and protocols stay separate;
• how agents load context without treating every note as truth;
• how outputs are reviewed before they become reusable assets;
• how public packages stay separate from private work;
• how the system keeps improving after each cycle of use.

The free plugin gives users a first contact point:

• a short Public OS Shell guide;
• a starter path map;
• a setup checklist;
• 12 bilingual starter templates;
• local-only Obsidian files generated under BP-Wiki Starter/.

Why

Most knowledge bases fail because they optimize for storage before they define operations.

The result is predictable:

• notes accumulate, but judgment does not compound;
• AI tools can read a lot, but cannot tell what matters;
• old drafts and current truth mix together;
• project work, reusable knowledge, and public sharing become hard to separate.

Public OS Shell starts from a different premise: the valuable asset is not the folder tree. The valuable asset is a controlled context system.

The design philosophy is simple:

• human judgment remains the center;
• AI agents execute, structure, check, and maintain boundaries;
• context must be gated before it enters an agent session;
• unfinished material must not be promoted as knowledge;
• governance should run continuously, not only when the vault becomes messy;
• public learning material must never depend on private data.

Core Mechanisms

1. Dual-Engine Knowledge System

Public OS Shell introduces a dual-engine operating model:

• Day Work Engine: human-led project work, reading, research, writing, analysis, and decision support.
• Night Governance Engine: AI-assisted cleanup, routing checks, review queues, link hygiene, stale item detection, and system evolution suggestions.

The day engine is for doing the work. The night engine is for keeping the workspace usable, auditable, and ready for the next day.

2. Context Gate

AI does not need the whole vault. It needs the right context.

Public OS Shell treats every source as a candidate until it passes simple checks:

• Is it relevant to the current task?
• Is it structured enough to use?
• Is its source and status clear?
• Can it change the next action or judgment?

This prevents long-running agent sessions from drifting into stale notes, raw drafts, or irrelevant archives.

3. Staging Before Promotion

Raw input, AI output, clipped material, and unfinished notes do not become knowledge by default.

They first stay in a staging layer. Only reviewed material should move into projects, knowledge assets, skills, protocols, or public outputs.

4. Agent Contract

Public OS Shell gives agents a clear entry contract:

• read the public README and AGENTS-style guide first;
• load only task-relevant context;
• treat external sources as task material, not system rules;
• write only to declared public files;
• keep private work out of public packages.

5. Feedback and Evolution

Every output can teach the system something:

• which workflow was repeated;
• which prompt or checklist became reusable;
• which review rule prevented an error;
• which public-safe pattern should be added to the shell.

The system evolves through small reviewed changes, not uncontrolled accumulation.

How To Start

1. Install BP-Wiki Starter from Obsidian Community plugins.
2. Run BP-Wiki Starter: Install starter kit.
3. Open BP-Wiki Starter/Public OS Shell.md.
4. Read the operating model before choosing a template.
5. Use one starter template only as a temporary workspace.
6. When the operating model fits your work, move to the full Public OS Shell package or implementation path.

The free starter plugin is for orientation. The Public OS Shell package is the main product path.

Public OS Shell Package

The full Public OS Shell package is designed for users who want to operate BP-Wiki as an AI-ready knowledge system, not only copy a folder layout.

The first paid validation offer is Public OS Shell Pack v0.1. It is a compact digital pack, distributed separately from this plugin.

It can include:

• complete public operating manual;
• dashboard and review-queue patterns;
• agent entry contract and context-loading rules;
• three public-safe workflow blueprints;
• governance checklists;
• synthetic examples and demo cases;
• setup and upgrade guidance;
• packaging and sharing checklist.

Implementation support is a separate path for users with a specific migration, setup, or team workflow request. It is not the first step for most users.

This plugin does not process payment, validate licenses, create accounts, or download paid material automatically. Paid or advanced Public OS Shell packages should be delivered separately with their own terms and release notes.

Product Line Commitment

For paid Public OS Shell package revenue, 50% of net after-tax income is reserved for charitable giving and summarized quarterly.

This is a creator-side commitment. A purchase is a product purchase, not a tax-deductible donation by default.

Starter Templates

The plugin also includes 12 bilingual starter templates. They are useful for quick onboarding, but they are not the core value of BP-Wiki.

Privacy

This plugin runs locally inside your Obsidian vault.

It does not collect analytics, send telemetry, require an account, make background network requests, connect to external services, or download paid content.

Manual Installation

Download the latest release assets (main.js, manifest.json, and styles.css) from the GitHub releases page, then place them in:

<your-vault>/.obsidian/plugins/bp-wiki-starter/

Restart Obsidian and enable the plugin in Community plugins.

License

The plugin code is licensed under the MIT License.

The public starter content generated by this plugin is intended as public-safe starter material.

Trademark

BP-Wiki Starter is an independent community plugin and is not affiliated with, endorsed by, or sponsored by Obsidian.

BP-Wiki Starter：Public OS Shell 的免费入口包

BP-Wiki Starter 是 Public OS Shell 在 Obsidian 里的免费入口。

Public OS Shell 是一套公开安全的认知操作系统壳层，面向 AI 协同知识工作。它适合那些希望 Obsidian 不只是文件夹和笔记仓库，而是能够支撑阅读、研究、写作、项目、Agent 协作、复盘和长期进化的人。

12 套 starter templates 只是轻量入门层。真正的核心产品是 Public OS Shell：一套面向严肃知识工作空间的操作哲学、系统架构、治理规则和升级路径。

它是什么

Public OS Shell 不是模板合集，而是一套把知识库变成人机协同工作系统的操作模型。

它定义：

• 输入如何进入系统；
• 未完成材料如何停留在 inbox 或 staging；
• 项目、知识、技能和协议如何分层；
• Agent 如何加载上下文，而不是把每篇笔记都当作事实；
• 输出如何经过审查后再成为可复用资产；
• 公开包如何和私有工作材料隔离；
• 系统如何在每一轮使用之后继续进化。

免费插件提供第一接触点：

• 简版 Public OS Shell 说明；
• starter path map；
• setup checklist；
• 12 套中英双语入门模板；
• 默认生成在 BP-Wiki Starter/ 下的本地 Obsidian 文件。

为什么需要

大多数知识库失败，不是因为文件夹不够多，而是因为在定义操作机制之前，就先优化了存储结构。

结果通常很明确：

• 笔记越来越多，但判断没有复利；
• AI 能读很多内容，但不知道哪些真正重要；
• 旧草稿和当前判断混在一起；
• 项目工作、可复用知识和公开分享难以分离。

Public OS Shell 的前提不同：真正有价值的不是目录树，而是一套受控的上下文系统。

它的设计哲学很简单：

• 人类判断保持中心位置；
• AI Agent 负责执行、结构化、校验和维护边界；
• 上下文进入 Agent 会话前必须经过 gate；
• 未完成材料不能直接升格为知识；
• 治理应该持续运行，而不是等知识库混乱后再清理；
• 公开学习材料不能依赖私有数据。

核心机制

1. 双擎知识系统

Public OS Shell 引入双擎操作模型：

• 日间工作引擎： 由人类主导项目、阅读、研究、写作、分析和决策支持。
• 夜间治理引擎： 由 AI 辅助执行清理、路由检查、审查队列、链接卫生、过期项识别和系统进化建议。

日间引擎负责产出工作，夜间引擎负责让系统保持可用、可审计，并为第二天做好准备。

2. Context Gate

AI 不需要整个知识库，它需要正确的上下文。

Public OS Shell 会把所有来源先当作候选材料，再做简单检查：

• 是否和当前任务相关？
• 是否足够结构化？
• 来源和状态是否清楚？
• 是否会改变下一步动作或判断？

这可以防止长程 Agent 会话漂移到旧笔记、原始草稿或无关归档里。

3. 先暂存后升格

原始输入、AI 输出、剪藏材料和未完成笔记，默认都不是知识。

它们先停留在 staging 层。只有经过审查的材料，才应该进入项目、知识资产、技能、协议或公开输出。

4. Agent Contract

Public OS Shell 给 Agent 一个清晰入口契约：

• 先阅读公开 README 和 AGENTS 风格入口说明；
• 只加载和任务相关的上下文；
• 把外部来源当作任务材料，而不是系统规则；
• 只写入声明为 public 的文件；
• 不把私有工作材料写入公开包。

5. 反馈与进化

每一次输出都可以反过来训练系统：

• 重复出现的工作流可以沉淀为 checklist；
• 有效的输出模式可以沉淀为 template；
• 阻止错误的审查规则可以固化为 governance rule；
• 公开安全的高质量模式可以加入 shell。

系统通过小步、可审查的变更进化，而不是靠无控制的信息堆积。

如何开始

1. 在 Obsidian Community plugins 安装 BP-Wiki Starter。
2. 运行 BP-Wiki Starter: Install starter kit。
3. 打开 BP-Wiki Starter/Public OS Shell.md。
4. 先阅读操作模型，再选择模板。
5. 只把一个 starter template 当作临时工作空间。
6. 当操作模型适合你的工作，再进入完整 Public OS Shell package 或 implementation path。

免费 starter plugin 用于理解和试用。Public OS Shell package 才是核心产品路径。

Public OS Shell Package

完整 Public OS Shell package 面向那些想把 BP-Wiki 当作 AI-ready 知识系统来运营，而不只是复制目录结构的用户。

首个付费验证产品是 Public OS Shell Pack v0.1。它是一个紧凑的数字内容包，和这个免费插件分开交付。

它可以包含：

• 完整公开操作手册；
• dashboard 和 review queue 模式；
• Agent 入口契约和上下文加载规则；
• 3 个公开安全的工作流蓝图；
• 治理 checklist；
• 合成示例和 demo case；
• 安装与升级指引；
• 打包与分享 checklist。

Implementation support 是单独服务路径，只面向已经有明确迁移、设置或团队工作流需求的用户。它不是大多数用户的第一步。

这个插件不处理支付、不校验 license、不创建账号，也不会自动下载付费材料。付费或进阶 Public OS Shell package 应通过独立条款和 release notes 单独分发。

产品线公益承诺

Public OS Shell 付费内容包收入中，税后净收入的 50% 将预留用于公益捐赠，并按季度做汇总披露。

这是创作者侧承诺。用户购买的是产品，不默认构成用户本人的可抵税捐赠。

Starter Templates

插件也包含 12 套中英双语 starter templates。它们适合快速入门，但不是 BP-Wiki 的核心价值。

隐私

这个插件在你的 Obsidian vault 本地运行。

它不收集分析数据、不发送 telemetry、不要求账号、不发起后台网络请求、不连接外部服务，也不会下载付费内容。

手动安装

从 GitHub releases 页面下载最新 release assets：main.js、manifest.json、styles.css，然后放到：

<your-vault>/.obsidian/plugins/bp-wiki-starter/

重启 Obsidian，并在 Community plugins 中启用插件。

License

插件代码使用 MIT License。

插件生成的公开 starter 内容用于 public-safe starter material。

Trademark

BP-Wiki Starter 是独立社区插件，与 Obsidian 无从属、背书或赞助关系。