Everything QueenBox does, and how far along it is.
Each feature carries a badge. Nothing is marked Available now yet: QueenBox is in development, and updating memories is still maturing.
Built and in testing. Anything that does not pass testing will be removed.
The four moves
How a memory is made and kept.Candidate memories are pulled out of what a seat works on. Each one keeps a pointer to where it came from.
Another seat, or a person, confirms a memory. The record shows who confirmed it and when.
A seat or a person can dispute a memory. Both versions are kept and flagged until a person decides.
When a fact changes, QueenBox looks for the memory it should change and proposes the update. Automatic replacement is switched off; a person reviews proposed updates. In our own tests this does not yet meet the accuracy bar we set, so we do not claim it.
Sources and history
Why you can check a memory.Each memory points back to the work it came from, so a person can check it.
A change adds a new version; the earlier ones stay, with who changed what and when.
When two memories disagree, both are kept and the conflict is flagged for a person.
A change in a document or repository is traced to the memory it should change.
Two ways to use it
One memory engine, on its own or inside The AI Hive.You connect the seats and AI tools you choose, and review and settle disputes in QueenBox itself.
QueenBox is the memory core of The AI Hive. Its scopes, permission checks on every request, approvals and audit trail decide who may see and change what.
Not offered yet. Today QueenBox runs on our own test servers.
Interested in QueenBox?
No pilot is offered yet. Register your interest and we will tell you when one opens.