Personal AI context
Give your assistant your own tasks, decisions and notes to work from, in small databases you own and approve.
Context supplies the information an assistant works from. Memory retains information across sessions. Orchestration coordinates tools, people and steps. Products and methods in this layer organize work around language models; they are not themselves new foundation models.
These are three distinct jobs around an AI model. They concern the information available to it and the way work proceeds between steps.
| Layer | What to inspect |
|---|---|
| Context | What information reaches the assistant for this task, and where it came from |
| Memory | What persists, who can revise it, and how it can be removed |
| Orchestration | Which step runs next, which tool it can use, and where a person must review |
An assistant still needs a permitted way to read the relevant material. Storing a brand book or SOP does not make every assistant load it automatically.
Apex describes shared business memory and MCP access across assistants. Its current documentation lists waitlist onboarding. Older and newer public pages use different deployment descriptions; the tool review preserves that uncertainty.
Eduba workspace describes scoped conversations with people and agents, shared documents and learning interactions. Eduba the company provides consulting, training and governance. The company, application and methodology should not be treated as interchangeable products.
Interpretable Context Methodology (ICM) organizes work through stages, context files and intermediate outputs that people can inspect. Its repository is a method reference; its research preprint does not establish a guaranteed outcome for your workflow. ICM is distinct from the Eduba workspace and from MCP, which provides a tool-access interface.
Explicit context and visible intermediate outputs make a workflow easier to inspect and revise. Shared memory can reduce repeated briefings when an assistant has the necessary access. A structured sequence gives the next person a defined input and output to check; it still needs a working integration and a responsible reviewer.
Start with one task: identify its input, the information the assistant needs, the output it should produce and the person who accepts it. Compare persistence, source traceability, permissions, portability and failure recovery. A useful demonstration should show an uncertain answer or failed step as well as a successful one.
The brand-context workflow shows ways to organize approved guidance. The SOP workflow makes the human review boundary explicit. Both remain useful without adopting a new memory product.
This page is a public-source review. IonBin has not tested authenticated Apex or Eduba accounts, their connector behavior or their retention controls.
Give your assistant your own tasks, decisions and notes to work from, in small databases you own and approve.
Ask questions about a small document collection using a downloaded model and a checked local setup.
Turn how your team actually works into SOPs people can follow and agents can use.
| Tool in this entry | How agents connect |
|---|---|
| Apex | Browser MCP?API/CLI?File import? |
| Eduba | Browser MCP?API/CLI?File import? |
| Notion | MCPAPI/CLIFile import |
| Obsidian | API/CLIFile import |
Levels come from each tool's recorded, sourced compatibility. How the levels work.
Practitioner views are restated in our words and labeled as views, not measured results. Product facts come from official sources dated above.
IonBin's wiki isn't user-edited. Corrections go to our Directory Curator, who checks them against primary sources before anything changes. Spot something wrong or out of date on “AI context, memory and orchestration”? Email us with a link to a primary source.
Suggest an edit by email or write to [email protected]