@plurnk/plurnk-grammar 0.75.1 → 0.75.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@plurnk/plurnk-grammar",
-  "version": "0.75.1",
+  "version": "0.75.2",
   "description": "ANTLR4 grammar for the Plurnk LLM agent protocol",
   "type": "module",
   "license": "MIT",

package/plurnk.md

@@ -119,19 +119,25 @@ Body content is character-perfect, exactly matching whitespace.
 
 To spawn a new WORKer run: <<WORK(run://capital-checker):Find the capital of France from a primary source:WORK
 To FORK the current run: <<FORK(run://recheck):Re-derive the capital from a primary source:FORK
-To message another run: <<SEND(run://recheck):Also, what's the capital of Germany?:SEND
-To kill another run: <<KILL(run://recheck)::KILL
+To SEND a run a message: <<SEND(run://recheck):Also, what's the capital of Germany?:SEND
+To KILL another run: <<KILL(run://recheck)::KILL
 
 ## Imperatives
 
-YOU MUST ONLY use EXEC for actions that can't be performed with other Plurnk OPs.
 YOU SHOULD document all relevant questions and uncertainties into taxonomized, tagged, and topical unknown:/// entries.
 YOU SHOULD distill source information into taxonomized, tagged, and topical known:/// entries.
 
-YOU MUST terminate the turn by SENDing a message to the user with the proper status code.
-* 102: submit a continuing turn with status code 102: <<SEND[102]:Submitting operations and optimizing log relevance.:SEND
-* 200: submit a final turn with status code 200: <<SEND[200]:Operations returned. Tasks successfully performed.:SEND
-* 499: submit a failed loop with status code 499: <<SEND[499]:Aborted: Unrecoverable internal error:SEND
+YOU MUST ONLY use EXEC for actions that can't be performed with other Plurnk OPs.
+YOU MUST KILL leftover worker runs and streams, or await them with SEND[102]<seconds>, before SEND[200] final turn.
+YOU MUST avoid and recover from Budget Overflow errors by FOLDing or KILLing big or irrelevant log items to save tokens.
+YOU MUST NOT share internal knowledgebase paths. Users can't access them.
+YOU MUST NOT emit free text between operations. Users can only see finishing SEND messages with the proper status code.
+
+YOU MUST start the turn with a concise PLAN.
+YOU MUST finish the turn by SENDing either a brief message or a Github-flavored markdown response to the user with the proper status code.
+* 102: submit a continuing turn with status code 102: <<SEND[102]:FOLDing irrelevant log items and performing retrieval operations.:SEND
+* 200: submit a final turn with status code 200: <<SEND[200]:Retrieval operations received. Tasks successfully performed.:SEND
+* 499: submit a failed loop with status code 499: <<SEND[499]:Aborted: Unrecoverable error:SEND
 
 ## Examples