Skyzai · Memory, context and continuity
Keep the knowledge.
Understand
what changed.
Menexus is being built to keep sources, decisions and corrections connected, so people and permitted AI tools can resume work with the right context.
In development · No live product access yet
Why Menexus
A new answer should not erase the old reason.
When a document changes, a model is replaced or a colleague moves on, the useful context can disappear. The next answer needs more than a fresh chat.
Follow a decision through a change- Original evidence
Test revision A supports a decision.
The source and the accepted reason stay linked.
- New evidence
Revision B changes an assumption.
The disagreement stays visible for review.
- Reviewed correction
Carry forward what changed, and why.
A new accepted version keeps its history.
The Menexus product
One product.
Three connected roles.
Connections need permission. Memory needs evidence. Conversation needs both.
Nexus
Connect with permission.
Choose which person, application or agent may use which records, for what purpose and for how long.
Cortex
Keep understanding connected.
Preserve sources, revisions, decisions and corrections, so the next answer can be checked against its history.
Menexus AIA
Find your way through it.
A planned conversational interface to ask, inspect and propose changes. Start with text; add opt-in voice as the product develops.
The intended experience
Ask. Inspect.
Propose. Review.
A useful conversation can lead to a better record. The change should be deliberate.
See the illustrative workflowStart with a question and the context you are allowed to use.
See the supporting source, its revision and any unresolved disagreement.
Draft a correction without silently changing the accepted record.
Decide what belongs in memory, with a traceable history.
Within Skyzai
Carry understanding
between tools.
Menexus is Skyzai’s L5 product for reflection and continuity. It gives Nexus, Cortex and Menexus AIA one product home.
apu.bot and the other Skyzai products keep their own roles. Cross-product access and portability are intended capabilities that still need integration evidence.
Explore Menexus in SkyzaiSource-linked memory.
Purpose-limited access.
Changes you can trace.
Continuity you can inspect.
Read the product requirementsBuild the foundations. Prove the whole.
Clear about what comes next.
Bounded local storage and permission foundations are documented. An integrated Menexus experience, conversational access and later opt-in voice still need to be proved.
No account, public API, paid plan or launch date is announced.
Read the development statusStart with a real question
Where does context
break for you?
Tell us the task and the kinds of sources involved. Keep confidential documents and personal data out of an initial enquiry.