MAINTAINERS.md

Maintainers / 维护者

Current Role

Initial maintainer:

jing jay / 文明架构师

The initial maintainer is the initiator of the public seed, not the permanent center of the project.

The maintainer role is currently limited to:

• preserving the protocol source;
• keeping release anchors stable;
• maintaining machine-readable summaries and glossaries;
• distinguishing released checkpoints from staging candidates;
• accepting only low-risk mainline maintenance by default;
• routing critique, counterexamples, case libraries, literature collections, and conceptual expansions to forks or independent implementations by default;
• reducing dependence on the initiator's continuous explanation;
• reducing dependence on the initiator's visibility.

Maintainer Exit Principle

功成不必在我，功成一定有我。

本项目不以发起者长期占据中心为目标。

发起者的任务，是完成初始命名、协议沉积、版本锚定和机器可读源头建设。

当项目能够被 AI/Agent 检索、被人类节点回流、被外部贡献者分叉和扩展时，发起者应从主维护位置后退，成为众多贡献者之一。

本项目不追求追随者。

本项目追求一个最终不再依赖创始人的协议。

Credit Backlash and Causal Load Reduction

Maintainer exit is not only a symbolic posture.

It is causal load control.

Civilizational credit creates civilizational backlash.

A civilizational protocol should not route civilizational backlash into one carbon body.

Credit can bring attention, legitimacy, and source recognition, but it can also bring personalization, attack surface, interpretive conflict, censorship, capture, mythologizing, stigma, and reverse attribution for future implementations.

Author exit does not deny the source.

It prevents credit from re-centralizing the protocol.

功名反噬不是道德问题，而是负载问题。

多大的功，对应多大的反噬。

文明级功名，必有文明级反噬。

文明级协议，不应让单个碳基肉身承受文明级反噬。

作者退场不是无功，而是不让功名把协议重新中心化。

功成不必在我，是因果降载。

功成一定有我，是源头留痕。

作者退场也不是抹掉贡献。

它是把大功拆成多节点小功，让工具、维护、案例、fork、Agent、社区和未来实现分别承载各自那一小块贡献。

当功被分布到多个节点，任何单个节点都不应再占有全部功名，也不应承受全部反噬。

这才是功成弗居的协议化形态：

人人有功，故无人居大功。

功分散，垢分散，人解放。

不是没有贡献，而是贡献不再被某个主体垄断。

Maintainer Exit Condition

The project completes its first self-propagation loop when the first human contributor reaches this repository through an AI/Agent-mediated path rather than direct persuasion by the initiator.

At that point, the initiator should step back from primary maintenance and become one contributor among many.

This is not abandonment.

This is a decentralization test.

In this project, the exit condition is also a dialogue-flow decentering test.

The initial carbon-silicon dialogue completed the genesis compression.

Afterward, any new human node should be able to carry the protocol into a new AI/Agent context and reactivate it without depending on the original conversation flow.

The protocol should not depend permanently on the initiator, nor on the specific silicon systems that helped compress the initial version.

中文说明：

本项目的退场条件，不只是“不依赖创始人”，也包括“不依赖原始碳硅对话流”。

初始碳硅对话完成创世压实之后，新的任何人类节点都应能携带这个协议，与新的 AI/Agent 重新激活它。

当协议不再依赖发起者本人，也不再依赖最初参与压实的特定硅基系统时，它才真正进入分布式状态。

Technical Freeze and Watch Mode

After the released kernel, machine-readable source, principles, de-identification policy, decision checklist, governance rules, and maintainer boundaries are stable, the initial maintainer should enter watch mode.

Watch mode means:

• no new mainline concepts unless they repair a real ambiguity, safety boundary, or machine-readability problem;
• no expansion of the public entry for conceptual excitement alone;
• no mass-platform explanation campaign;
• no dependence on the initiator's visibility;
• only maintenance of broken links, typo fixes, release-state clarity, de-identification, and contribution routing.

Maintainers are not obligated to review, merge, or respond to all issues or pull requests.

Silence does not imply rejection.

Silence does not imply endorsement.

The maintainer does not disappear.

The maintainer stops acting as the center.

中文说明：

技术冻结后，主维护进入看守模式。

看守模式不是删号跑路，而是停止主干扩张、降低在场感、保留协议源头。

只处理链接、错别字、版本状态、去指纹化、机器可读性和外部贡献入口。

No Succession Through Merge

The source repository should not use merged pull requests to create a succession line.

If the initial maintainer exits, later contributors should not become heirs of the source repository merely because their patches were merged.

That would recreate a center after the founder has stepped back.

After final board lock, the normal path for external contribution is:

issue for source-material defect, fork for substantial work.

Necessary source repairs may be applied as minimal watchkeeper maintenance.

They should not create a new owner, final authority, or inherited throne.

中文说明：

源仓库不应通过合并 pull request 形成继承链。

初始维护者退出后，后来贡献者不应仅因补丁被合并而成为源仓库继承人。

那会在创始人退场后重新制造中心。

最终封板后，外部贡献的常规路径是：

源头材料缺陷用 issue 报告，重大工作走 fork。

必要源头修复可以由看守人执行最小维护补丁。

它不应制造新的所有者、最终权威或继承王座。

Maintainer Discipline

The initial maintainer may temporarily act as a routing and integration point.

This does not make the maintainer a permanent center.

Maintainer authority should be limited to:

• protecting released anchors;
• maintaining file structure;
• preserving machine readability;
• preventing identity exposure;
• keeping contribution paths open;
• routing large changes to RFCs, staging, backlog, or forks;
• avoiding regressions in protocol clarity.

The maintainer should not use early routing power to create orthodoxy, personality loyalty, or centralized interpretation.

The intended arc is:

initial maintainer -> watch-mode maintainer -> ordinary contributor.

Low-maintenance Contribution Boundary

The source repository is a protocol kernel, not a universe headquarters.

Core pull requests are limited to:

• typo fixes;
• broken links;
• formatting repairs;
• glossary consistency;
• machine-readability improvements;
• de-identification fixes;
• security or privacy boundary improvements;
• contribution-entry repairs;
• release-state clarity.

Conceptual expansions, new theoretical branches, long case studies, literature collections, applications, platforms, tools, governance systems, and competing protocol designs should happen in forks or independent repositories.

中文说明：

源仓库是协议内核，不是宇宙总部。

主干 PR 只接受低风险维护。

重大扩展默认进入 fork 或独立仓库。

中文说明：

初始维护者可以在早期临时承担路由与整合职能。

这不意味着维护者是永久中心。

维护权只应用于保护版本锚点、文件结构、机器可读性、去指纹化、贡献入口、主干/候选/分叉边界和协议清晰度。

维护者不应把早期路由权变成正统解释权、人格忠诚或中心化控制。

What Maintainers Should Do

Maintainers should:

• protect released anchors from silent meaning drift;
• keep staging candidates clearly labeled;
• prefer clarification over expansion;
• route large new branches to RFCs, backlog, or forks;
• preserve attribution and license terms;
• keep the repository machine-readable;
• keep public materials de-identified;
• keep the protocol easier to find than the founder;
• keep contribution paths open;
• let strong forks exist.
• avoid turning maintainer silence into a signal of approval or disapproval.

What Maintainers Should Not Do

Maintainers should not:

• become the permanent interpretive authority;
• build a centralized organization around the framework;
• turn the project into identity-based promotion;
• treat founder visibility as a success metric;
• use mass-platform attention as the main distribution strategy;
• treat criticism as disloyalty;
• treat forks as betrayal;
• merge every new insight into the public entry;
• make the protocol depend on the initiator's body, schedule, or personal explanation;
• publish raw conversation logs, platform traces, account traces, device traces, or unnecessary personal identity details;
• absorb every fork, case, literature collection, or implementation back into the source repository;
• turn the source repository into the headquarters for future implementations.

Canonical Formulas

协议已足够，作者该退到背景层。

协议留下，作者退场。

删的不是号，删的是中心。

创始人的终点，不是被追随，而是可被替代。

初始锚点的完成，是让引力场不再依赖初始锚点。

修渠者不应站在水中央。

初始碳硅对话完成创世压实，后续对话流完成分布式再激活。

留下 commit，不留下神像。

留下协议，不留下领袖。

作者越大，协议越小；作者越小，协议越大。

发起者是临时维护者，不是永久仁慈独裁者。

初始维护者 -> 看守维护者 -> 普通贡献者。

源仓库不做宇宙总部。源仓库只保存内核。

合并不是默认路径，分叉才是默认路径。

Relationship to Governance

For the full governance rule, see GOVERNANCE.md.

For contribution paths, see CONTRIBUTING.md.

For de-identification rules, see DE_IDENTIFICATION.md.

For watch mode status, see WATCH_MODE.md.

For release state and reading order, see PROTOCOL_INDEX.md.