rock/poimen-memory
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Deploy Poimen Memory K8s cluster with ArgoCD tracking (M2.2, M3.5-M3.7)
ci / markdown (push) Waiting to run
Details

Browse Source
This commit is contained in:
Story Crater Bot
2026-08-22 23:13:42 -07:00
parent 9c723fe66f
commit d3be7f6fd4
105 changed files with 10973 additions and 113 deletions
Download Patch File Download Diff File Expand all files Collapse all files
fixtures/expected/prompt-t1.txt
+11
View File
@@ -0,0 +1,11 @@
You are presented with a problem, a section of an article that may contain the answer to the problem, and a previous memory. Please read the provided section carefully. You should reason about whether the new section contains useful information about the problem, and then update the memory with the new information that helps to answer the problem.
Be sure to retain all relevant details from the previous memory while adding any new, useful information. You should also carefully judge whether you have collected enough information to answer the problem.
You should reason about whether the new section contains useful information, what to update, and what to do next first between <think> and </think>.
If the new section contains useful information about the problem, you should first generate <check>yes</check>. After that, update the new memory between <update> and </update>.
If the new section does not contain useful information about the problem, you should first generate <check>no</check>. After that, you should keep the previous memory unchanged between <update> and </update>.
In the end, if you haven't collected enough information for the problem, return <next>continue</next>. ONLY when enough information is collected, return <next>end</next>.
<problem> What architectural decisions were made? </problem>
<memory> No previous memory </memory>
<section> [User] Tell me about the architecture
[Assistant] We use a microservices design </section>
fixtures/expected/prompt-tn.txt
+11
View File
@@ -0,0 +1,11 @@
You are presented with a problem, a section of an article that may contain the answer to the problem, and a previous memory. Please read the provided section carefully. You should reason about whether the new section contains useful information about the problem, and then update the memory with the new information that helps to answer the problem.
Be sure to retain all relevant details from the previous memory while adding any new, useful information. You should also carefully judge whether you have collected enough information to answer the problem.
You should reason about whether the new section contains useful information, what to update, and what to do next first between <think> and </think>.
If the new section contains useful information about the problem, you should first generate <check>yes</check>. After that, update the new memory between <update> and </update>.
If the new section does not contain useful information about the problem, you should first generate <check>no</check>. After that, you should keep the previous memory unchanged between <update> and </update>.
In the end, if you haven't collected enough information for the problem, return <next>continue</next>. ONLY when enough information is collected, return <next>end</next>.
<problem> What architectural decisions were made? </problem>
<memory> We use a microservices design with REST APIs. </memory>
<section> [User] What about the database?
[Assistant] We chose PostgreSQL for primary storage. </section>