i am absolutely blown away by the data we're getting from testers so far.
we have absolutely surpassed expectations and then some. and the plugin is not even public yet.
at this point i am confident saying a few things:
-the plugin can retrieve with ~97-98% accuracy under heavy load and handle complex requests with no trouble
-the plugin has essentially 0 hallucinations if accurate data is in it's memory. it refrains rather than return false data
-in a scenario where a user would need to retain full project context in his context/memory files for any length of time, the plugin saves the users 98.7% in tokens. (yes i'm serious.)
all of these things are reproducible, and i encourage anyone to join the discord, install the plugin, and try to break things.
a few other things about operations and our growth: we're in the process of officializing a few new team members and automating some workflows.
this week i set up:
-automated plugin patch maintenance workflow (bugs extracted from report surfaces discord chats, triaged, fixed, tested, prepped for deployment and sent to me for approval)
-automated marketing graphic creation using a similar workflow where marketable pieces of beta testing conversations and testing data is extracted from the chats and placed into well designed marketing materials like the ones you see SIBYL posting recently.
and i haven't even told you guys about the hackathon yet.
independent testers have been running adversarial suites against the memory plugin.
the attacks that matter held: injection, path traversal, prompt injection, archive leakage, tenant isolation.
10/10 on the migration suite. 8/8 runtime hardening checks.
the findings they did surface are already fixed and shipped: error responses no longer echo submitted values, path isolation is hardened, and a forged local cache can't lift the tier cap.