> For the complete documentation index, see [llms.txt](https://zh.chanyuan8.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://zh.chanyuan8.org/xue-feng-wen-ji-chan-yuan-pian/te-feng-cang-hai-cao-wei-sheng-ming-chan-yuan-hu-fa-da-jin-gang.md).

# 特封沧海草为生命禅院护法大金刚

特封沧海草为“禅院护法大金刚”。

沧海草对生命禅院理念从理论上理解和掌握的比较到位，在这禅院理念越来越被广泛传播越来越多人认识越来越多人成为禅院草的时刻，雪峰由于时间和精力有限，无法对有悖禅院理念的错误认识和观点及时给予指正，故特封沧海草为“禅院护法大金刚”，来维护禅院理念不被一点一点地侵蚀。

沧海草头脑很清醒，逻辑性很强，看问题透彻，不怕权威，有大无畏精神，常常对错误理念和禅院草的错误做法一针见血，一剑封喉，且又不怕打击、不怕讽刺挖苦，不怕被孤立，从这点上讲，他已进入无私无我境界，这是一朵奇葩，属奇花异草，凤毛麟角人物。

沧海草虽然显得凶神恶煞，但人们无论如何恨他，他内心里对人毫无恨意，也谈不上爱意，有时候他显得汹涌澎湃，但实际上他内心的海洋很宁静，心态很好。

沧海草很诚实、很正直、很坦荡，信守诺言。

今封沧海草为“禅院护法大金刚”，目的是想告诉大家，沧海草有资格和品德对我们所有人违背禅院理念的做法和说法进行鞭挞和指正。不论他采取什么方式，我们当谨记，他全是为了生命禅院，而不是为了凸显自己。他烈火般的方式刚好让我们进入无我无相境界。

“禅院护法大金刚”必须“从心所欲不逾矩”，你只在理念这个“法”理上进行护法，但对家园的实践不能干涉，对每个人所从事的工作不能干扰。

浑沌元初

2011/3/20


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://zh.chanyuan8.org/xue-feng-wen-ji-chan-yuan-pian/te-feng-cang-hai-cao-wei-sheng-ming-chan-yuan-hu-fa-da-jin-gang.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.