Skip to content

Trim conversational preamble from POLICY_SEED canonical section #407

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mikemol wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Trim conversational preamble from POLICY_SEED canonical section #407

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 0 additions & 11 deletions POLICY_SEED.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -90,17 +90,6 @@ doc_owner: maintainer
---

<a id="policy_seed"></a>
Excellent. What you’re asking for is not “documentation” in the usual sense. You’re asking for a **self-stabilizing policy nucleus**: a document that is simultaneously

* **normative** (it constrains behavior),
* **meta-normative** (it constrains how the constraints themselves may change),
* **interpretable by LLMs as an active control**, and
* **embedded in a feedback loop** so it can resist both *decay* (staleness) and *attack* (malice).

Below is a **documentation seed** you can drop into the repo (e.g. `POLICY_SEED.md#policy_seed`). It is written deliberately as a *control object*, not as prose. Repo-native agents and LLMs should be instructed (elsewhere, e.g. in a system prompt or CONTRIBUTING.md#contributing_contract) to treat this file as **authoritative and executable guidance**.

---

# POLICY_SEED.md#policy_seed

**Title:** Self-Stabilizing Security & Execution Policy Seed
Expand Down
Loading