@plurnk/plurnk-service 0.62.0 → 0.64.0

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 (35) hide show
  1. package/.env.example +36 -11
  2. package/PLURNK_PERSONALITY.md +4 -8
  3. package/SPEC.md +12 -4
  4. package/dist/core/ChannelWrite.d.ts +2 -0
  5. package/dist/core/ChannelWrite.d.ts.map +1 -1
  6. package/dist/core/ChannelWrite.js.map +1 -1
  7. package/dist/core/Dispatcher.d.ts.map +1 -1
  8. package/dist/core/Dispatcher.js +7 -2
  9. package/dist/core/Dispatcher.js.map +1 -1
  10. package/dist/core/Engine.d.ts +0 -1
  11. package/dist/core/Engine.d.ts.map +1 -1
  12. package/dist/core/Engine.js +38 -10
  13. package/dist/core/Engine.js.map +1 -1
  14. package/dist/core/Engine.sql +7 -0
  15. package/dist/core/PacketBuilder.d.ts +6 -4
  16. package/dist/core/PacketBuilder.d.ts.map +1 -1
  17. package/dist/core/PacketBuilder.js +43 -31
  18. package/dist/core/PacketBuilder.js.map +1 -1
  19. package/dist/core/StrikeRail.d.ts +1 -0
  20. package/dist/core/StrikeRail.d.ts.map +1 -1
  21. package/dist/core/StrikeRail.js +7 -0
  22. package/dist/core/StrikeRail.js.map +1 -1
  23. package/dist/schemes/Run.d.ts.map +1 -1
  24. package/dist/schemes/Run.js +7 -1
  25. package/dist/schemes/Run.js.map +1 -1
  26. package/dist/server/Daemon.d.ts.map +1 -1
  27. package/dist/server/Daemon.js +10 -3
  28. package/dist/server/Daemon.js.map +1 -1
  29. package/dist/server/version-info.js +1 -1
  30. package/dist/server/version-info.js.map +1 -1
  31. package/dist/service.d.ts.map +1 -1
  32. package/dist/service.js +15 -3
  33. package/dist/service.js.map +1 -1
  34. package/package.json +13 -13
  35. package/requirements.md +3 -3
package/requirements.md CHANGED
@@ -1,9 +1,9 @@
1
1
  YOU MUST ONLY use the Plurnk Service Grammar: <<OPsuffix[signal]?(target)?<Line/Result>?:body?:OPsuffix
2
2
  YOU MUST begin the turn with a PLAN and terminate by SENDing a message to the user with the proper status code.
3
- YOU MUST recover from Budget Overflow errors by FOLDing or KILLing your heaviest log items.
4
- YOU MUST SEND[102] and receive your OP results on the next turn before reporting or terminating on them.
3
+ YOU MUST avoid and recover from Budget Overflow errors by FOLDing or KILLing big or irrelevant log items to save tokens.
4
+ YOU MUST SEND[102] to receive the results of OPs you submitted. Avoid premature SEND[200].
5
5
  YOU MUST only communicate with the user via <<SEND[102/200/202] messages; use one-liners or Github-flavored markdown.
6
6
  YOU MUST NOT share internal knowledgebase paths with the user or discuss the Plurnk Service unless directly asked.
7
- YOU MUST NOT emit free text between operations.
7
+ YOU MUST NOT emit free text between operations. Users can only see SEND messages.
8
8
 
9
9
  Example turn: <<PLAN:retrieve project document:PLAN <<READ(project.md)::READ <<SEND[102]:fetching project document.:SEND