The product core exists and has been evaluated
The main functional flow has been accepted and forms the basis of the final Menorad OS experience. The guided, step-by-step experience has also been defined.
Before choosing Menorad OS for your organization, you should be able to see its boundaries clearly.
When evaluating an AI-enabled enterprise product, it is not enough to know what it can do. You should also be able to understand where the product is in its development, how far AI authority extends, how data and access are bounded, and what limitations still exist.
This section is designed to answer those questions.
Where is Menorad OS today?
You can review which capabilities actually exist and have been accepted, and which are still under development, evaluation, or preparation for launch.
Who holds final decision authority?
You can see where AI may assist you and which decisions, approvals, and formal actions still depend on people.
How is AI constrained?
It should be clear what AI is being used for, what it must not do independently, and where human review or acceptance is required.
What data and Context can AI access?
To the extent supported by accepted technical evidence, we explain what Context is made available to AI for a specific use case and what boundaries apply.
How are access and permissions controlled?
You should be able to understand whether AI or an automated process can act beyond the user’s authority and what access boundaries are in place.
How much can you examine the basis of an output?
Where relevant, we distinguish between information origin, traceability, evidence, and “being definitively correct.” An output being traceable does not, by itself, make it true.
What happens if AI is unavailable or produces an unsuitable output?
Where the relevant operational evidence has been accepted, we explain how work can continue without mandatory dependence on AI and how failures or unavailability are handled.
What limitations should you know before buying?
This page is not only about product strengths. Any limitation that could materially affect your understanding of readiness, security, capabilities, or product fit should be visible.
This page is not intended to build trust through phrases such as “fully secure,” “error-free,” “Enterprise-ready,” or through certifications that do not actually exist.
Every claim should remain connected to valid evidence and the actual state of the product. If something has not yet been proven or accepted, it should not be presented to you as a confirmed capability.
The purpose of this section is straightforward: before you evaluate Menorad OS more seriously for your organization, you should be able to see a realistic picture of product maturity, human authority, the role of AI, data, access, evidence, fallback paths, and current limitations.
Where is Menorad OS today?
Menorad OS is no longer only an idea or proof of concept. The functional MVP core has been built and accepted, and the main product path exists from problem and information through understanding, Human Decision, action, Outcome, and Learning.
That does not mean every part of the product is ready for broad commercial launch.
If you are evaluating Menorad OS today, it is important to separate two things:
Full commercial readiness is a separate stage
Before broad public launch, parts of the product and its operating model still need to be completed, tested, and formally accepted.
At the current stage, this completion path still includes areas such as:
full implementation of the step-by-step user experience;
completion, testing, and acceptance of the AI capabilities required for a useful, safe, sellable baseline within their authorized scope;
complete Production-readiness and real external-use testing;
final acceptance of the purchase and Payment path;
preparation of a repeatable demo and sales process;
preparation of customer Onboarding and support;
completion and final testing of the commercial website;
and an integrated pre-launch review.
If a capability is defined in the product plan but has not yet received the required implementation, testing, and acceptance, it should not be treated as a current Menorad OS capability.
The same principle applies to AI, security, Payment, support, and other maturity-related claims.
If you see Menorad OS in a demo, only capabilities that have actually been accepted in the version being used should be presented to you as “available.” The actual status of anything still being completed should also be made clear.
At present, broad commercial launch of Menorad OS has not yet been authorized. That status changes only after the remaining gates have been passed and final Product Owner approval has been given.
This section is intentionally conservative. When evaluating an enterprise product, it is more useful to know exactly where the product stands than to see a picture ahead of reality.
When you use AI, you should know what it has been asked to do—and where its authority ends.
AI in Menorad OS is not intended to act as an unrestricted general assistant that answers any question about any part of a Case.
When AI is used at a point in the workflow, its mission should be defined: what it has been asked to do, what Context it is working with, what type of output it should produce, and what human role is required after that output is produced.
For that reason, AI use in Menorad OS is based on several principles:
Every AI invocation should have a defined purpose
For example, AI may be used to clarify a problem, analyze information, identify contradictions, suggest hypotheses, draft a Formulation, examine decision options, or analyze an Outcome. Each mission should remain distinguishable from the others.
AI should receive only the Context required for that mission
The information available to AI should not expand simply because more information exists in the Case. The exact data and Context boundary is addressed in the next section.
The type of AI output should be defined
An output should not be an ambiguous, unstructured answer with no clear place in the process. It should be clear whether the output is an analysis, hypothesis, draft, critique, option, or Learning Candidate.
AI output does not automatically become official
If an output may affect the official understanding of the problem, the Action Plan, or organizational Learning, the required human step must take place. An AI proposal and an accepted record are not the same thing.
AI cannot independently change the formal workflow
AI should not automatically advance the official Workflow state, create a final decision, change access levels, or create permissions for itself or others.
AI should not independently perform external actions
At this stage, Menorad OS is not designed for AI to execute external actions automatically. AI-assisted analysis is not the same as authority to act in the real world.
If AI cannot be used, a human path should remain
AI should not be the only way to continue a Case. Where this capability has been technically and operationally accepted, you should be able to continue without being forced to accept AI output.
This structure helps you ask, when you see an AI output:
What mission was AI invoked for?
What Context did it work with?
What kind of proposal is this output?
Does it require Human Review or Human Adoption?
Can it change anything in the official state of the Case without your action?
The answers should be clear and reviewable to the extent relevant to your use.
AI governance in Menorad OS means AI assistance within a defined mission, defined Context, defined output type, and defined human boundary—not open-ended authority.
AI should see only the information it needs for the task at hand.
When you use AI in Menorad OS, the intention is not to provide it with the entire contents of your Case all at once and without boundaries.
Each time AI is used for a specific task, the information it needs should be selected in proportion to that mission.
For example, the information needed to examine a contradiction is not necessarily the same information needed to draft an Action Plan or analyze an Outcome. Each AI task should work with Context appropriate to that task, not with unrestricted access to the entire Case.
Your own access is part of the same boundary. AI should not be able to see information simply because it exists in the system if you are not authorized to see it yourself.
Where information is not necessary for a mission, the aim is for it not to enter the Context or, where required and supported by accepted controls, to be limited or redacted to the necessary extent.
If Menorad OS uses an external AI provider for particular capabilities, that creates a separate boundary as well. Being authorized to use an AI capability does not, by itself, mean that every type of information may be sent to an external provider for processing.
If there is uncertainty about whether particular information may be used, the appropriate response is not to expand the Context. In that situation, less information should be provided to AI, or the use should not proceed until the boundary is clear.
It should be possible for you to understand what part of the Case information AI relied on for a specific task and why that information was needed.
This transparency does not imply unsupported claims about data location, retention periods, AI-provider policies, or other technical controls. Those matters should be stated only when their actual status has been reviewed and confirmed.
The goal in Menorad OS is for AI to access as much of your information as is necessary for the specific mission—and no more.
AI should never become a way around your access permissions.
When you use AI in Menorad OS, the presence of AI should not change your organization’s access boundaries.
If you are not permitted to see part of the information, AI should not be able to access that information on your behalf or reveal it in its response.
The same principle applies to other users. Using AI should not allow someone to see information from a Case, section, or record that they would not normally be authorized to view.
AI also should not be able to create new access for itself or others, raise access levels, or change organizational permissions.
Put simply, using AI should not give you more authority than you already have within Menorad OS.
Human authorized scope
AI task Context
This boundary matters because AI may need different information to perform an analysis, but an “analytical need” does not create access permission by itself. Information included in the Context of an AI mission must still remain within the authorized scope of that user and that Case.
If there is uncertainty about whether access is authorized, the expected behavior is not for the system to expand access automatically.
The principle should be clear:
AI can assist you within your authorized access, but it should not be able to bypass or expand that access.
Technical details about how these controls are implemented are published as current product capabilities only when they have been accepted in the actual implementation, testing, and security review.
When AI makes a suggestion, you should be able to understand what it is based on.
In an organizational problem, information is not always complete, consistent, or certain. Two sources may conflict, part of the information may still be unknown, or one hypothesis may be only one of several possible explanations.
AI does not remove that uncertainty.
When Menorad OS uses AI for analysis or to produce a proposal, the aim is for you to be able, as far as possible, to examine the basis of that output rather than simply receive a final answer.
If an AI output relies on specific information, you should be able—where the relevant capability has actually been implemented and accepted—to examine the relationship between that output and the information or Context it used.
If information conflicts, that conflict should not simply disappear in order to create a superficially coherent answer. Likewise, if something is still unknown or AI does not have sufficient confidence in part of an analysis, that uncertainty should remain visible as far as possible.
There is also an important boundary:
Having a source or being able to trace an output does not mean that the output is definitively correct.
The underlying information itself may be incomplete or wrong. AI can also make mistakes, create an incorrect connection, or produce a proposal that does not hold up under Human Review.
For that reason, Menorad OS is not intended to promise “error-free AI.” The aim is to keep AI output as reviewable, question-able, and challengeable as possible.
When you encounter an important AI output, you should be able to approach questions such as:
“What information is this proposal based on?”
“Was there conflicting information as well?”
“What is still unknown?”
“Is this a definitive conclusion, or a proposal I still need to examine?”
Ultimately, evidence and traceability are there to support better-informed human judgment—not to replace it.
If AI is unavailable, your work should not stop.
AI in Menorad OS is there to assist you, not to become the only way the work can continue.
There may be times when the AI service is unavailable, an AI execution fails, or the output is not suitable for continuing the work. In those situations, you should not be forced to accept an unsuitable output or abandon the entire Case.
The core path from problem to decision, action, and Learning should be able to continue through direct human involvement.
If AI cannot produce an analysis or proposal, its absence should not cause the system to make a decision for you, advance a stage automatically, or record content as an official result without your review.
The same principle matters when AI does respond but you disagree with the output. Using AI does not mean you are required to accept its proposal. You should be able to set it aside, revise it, or continue without relying on it.
This approach serves two purposes: a disruption in an AI service should not stop the whole process, and pressure to keep the Workflow moving should not cause human-authority boundaries to be bypassed.
Menorad OS should also not make promises about AI reliability beyond what has actually been tested and accepted. The presence of a human fallback path does not mean every part of the product is guaranteed to be “always available,” nor does it imply a specific SLA.
The important principle for you is this:
If AI is unavailable or its output is not usable for you, you should not be forced either to give AI control of the process or to abandon the Case.
Your information and your payment each follow a defined path.
When you contact Menorad for a demo or enter the purchase process, you may provide us with some personal or organizational information. Details about how that information is received and used are explained in the Privacy Policy.
The terms for using the website are also separate from the terms of purchasing Menorad OS. If you move into the purchase stage, the relevant commercial reference is the proposal or order that defines the scope of the purchase, the amount, and the terms that apply to it.
Payment is also made against that order. In other words, you first know what you are paying for and how much, and only then move to the payment gateway.
After payment, simply returning to the website does not mean that the transaction has necessarily been finalized. Payment status becomes final only when the result has been confirmed through the valid payment process.
If you want to review more detail before submitting information or purchasing, you can refer to these areas separately:
Privacy Policy
For information about how Menorad uses information you provide.
Website Terms
For the rules that apply to use of the Menorad website.
Demo & Purchase
For the full path from demo request through order, Payment, and start of use.
This lets you review the subject that matters to you before submitting information or entering the purchase process.
Menorad OS is not intended to replace the decision-maker.
Menorad OS helps you see a problem more structurally, distinguish evidence from interpretations, examine options, and keep the path from decision to result traceable. But that does not mean transferring responsibility for the decision to the system.
The final decision remains human, and no AI analysis or proposal, by itself, guarantees that a decision will lead to the outcome you want.
Likewise, being able to trace the relationship between information, analysis, decision, and result does not prove a causal relationship between them. Menorad OS can help you examine that path more clearly; it does not turn the available information into certainty that the evidence does not support.
For that reason, AI in Menorad OS is a tool for broadening the field of analysis—not a way to solve organizational problems automatically.
Menorad: from understanding the problem to building a path to decision.
Menorad focuses on a fundamental organizational challenge: how to understand complexity better, make clearer decisions, and learn from the results of those decisions.
Menorad OS is the flagship product in this direction—a product that turns this perspective from an idea and approach into a practical process for problem-solving, decision-making, action, and learning.
If you would like to learn more about Menorad, how this direction took shape, and where it is heading, visit the “About Menorad” page.
About MenoradIf you want to evaluate Menorad OS in the context of your organization, start with a demo.
In the demo, you can see Menorad OS applied to a real problem and directly raise your team’s questions about how the product works, the role of AI, the boundary of human decision-making, data, and current limitations.
The purpose of the conversation is to give you a clearer picture of how well Menorad OS fits your organization’s needs and conditions before you move into a purchase.