@plurnk/plurnk-grammar 0.75.0 → 0.75.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/plurnk.md +13 -8
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@plurnk/plurnk-grammar",
3
- "version": "0.75.0",
3
+ "version": "0.75.2",
4
4
  "description": "ANTLR4 grammar for the Plurnk LLM agent protocol",
5
5
  "type": "module",
6
6
  "license": "MIT",
package/plurnk.md CHANGED
@@ -119,20 +119,25 @@ Body content is character-perfect, exactly matching whitespace.
119
119
 
120
120
  To spawn a new WORKer run: <<WORK(run://capital-checker):Find the capital of France from a primary source:WORK
121
121
  To FORK the current run: <<FORK(run://recheck):Re-derive the capital from a primary source:FORK
122
- To message another run: <<SEND(run://recheck):Also, what's the capital of Germany?:SEND
123
- To kill another run: <<KILL(run://recheck)::KILL
122
+ To SEND a run a message: <<SEND(run://recheck):Also, what's the capital of Germany?:SEND
123
+ To KILL another run: <<KILL(run://recheck)::KILL
124
124
 
125
125
  ## Imperatives
126
126
 
127
- YOU MUST ONLY use EXEC for actions that can't be performed with other Plurnk OPs.
128
127
  YOU SHOULD document all relevant questions and uncertainties into taxonomized, tagged, and topical unknown:/// entries.
129
128
  YOU SHOULD distill source information into taxonomized, tagged, and topical known:/// entries.
130
129
 
131
- YOU MUST terminate the turn by SENDing a message to the user with the proper status code.
132
- * 102: submit a continuing turn with status code 102: <<SEND[102]:Submitting operations and optimizing log relevance.:SEND
133
- * 200: submit a final turn with status code 200: <<SEND[200]:Operations returned. Tasks successfully performed.:SEND
134
- * 300: stop and ask the user a multiple-choice question: <<SEND[300]:Deploy to (a) staging or (b) production?:SEND
135
- * 499: submit a failed loop with status code 499: <<SEND[499]:Aborted: Unrecoverable internal error:SEND
130
+ YOU MUST ONLY use EXEC for actions that can't be performed with other Plurnk OPs.
131
+ YOU MUST KILL leftover worker runs and streams, or await them with SEND[102]<seconds>, before SEND[200] final turn.
132
+ YOU MUST avoid and recover from Budget Overflow errors by FOLDing or KILLing big or irrelevant log items to save tokens.
133
+ YOU MUST NOT share internal knowledgebase paths. Users can't access them.
134
+ YOU MUST NOT emit free text between operations. Users can only see finishing SEND messages with the proper status code.
135
+
136
+ YOU MUST start the turn with a concise PLAN.
137
+ 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.
138
+ * 102: submit a continuing turn with status code 102: <<SEND[102]:FOLDing irrelevant log items and performing retrieval operations.:SEND
139
+ * 200: submit a final turn with status code 200: <<SEND[200]:Retrieval operations received. Tasks successfully performed.:SEND
140
+ * 499: submit a failed loop with status code 499: <<SEND[499]:Aborted: Unrecoverable error:SEND
136
141
 
137
142
  ## Examples
138
143