When you want AI to understand your material in depth
Mekra Method keeps the reasons and conditions alongside your knowledge, so an agent can find the background it needs when you start a conversation.
When you want different kinds of material understood as one context
Bring together meeting notes and customer commitments, research and experiment logs, study notes and weekly routines, or recipes and a weekly menu. Give AI the context to use them together.
02
Get started
Apply to your folder
Ask an AI agent that can read and edit the folder containing your material:
Read the application guide in the release at https://github.com/mekra-lab/mekra-method/releases/tag/mekra-1.1 and apply it to this folder.
The agent decides how to organize and maintain knowledge from your material. After applying Mekra, you can ask it to incorporate new material into the existing Mekra.
Once setup is complete, ask the question you wanted these materials to help answer.
Not sure what to ask first?
Use the Mekra bundle in this folder as your starting point to understand these materials together, taking their context and relationships into account, and create the result that is most important and useful right now.
Consider what emerges from the materials as a whole, and use your own judgment to decide what matters and how to use and present it.
Create the result as a single HTML file that is easy to explore at a glance.
With the context in place, you can spend less time explaining and more time working together.
What to keep in your folder and what to ask, by field. The more your material keeps its reasons and conditions, the more an agent can find and use that context from a short request.
Keep in your folder
Study notesWhat you've learned, where you got stuck, courses finished
Weekly logWhen study kept going and when it stopped, and why
Education budgetHow much you can spend, and when
Course notesCandidate courses and why you chose them
Try asking
Make me a three-month study plan based on my notes.
Find in my records why my study stopped last month.
Pick the course that fits me now from my candidates, and tell me why.
Keep it going
When the plan changes, ask the agent to record what changed and why. Your next check-in starts there.
Keep in your folder
Launch planSchedule and who it reaches
Customer commitmentsConditions agreed with each customer
Meeting notesWhat was decided, and why
Support notesRecurring questions and how they were handled
Try asking
Draft a customer-by-customer transition plan for this launch.
Find where the announcement draft conflicts with our customer commitments.
If the launch date moves, list the commitments and schedules it affects.
Keep it going
When you agree on a new condition, ask the agent to add it to the customer commitments, not just the meeting notes. It becomes the basis for the next decision.
Keep in your folder
Research questionWhat you want to find out, and its scope
Experiment logConditions and results
Review notesOpen questions and counterexamples
DraftThe current conclusion of your paper or report
Try asking
Write a follow-up experiment plan from what we have so far.
Point out where the draft's conclusions lack support.
Put the differences between the two experiments' conditions in a table.
Keep it going
When a new result comes in, ask the agent to keep the earlier result and its conditions alongside it. You can follow how the interpretation changed.
Keep in your folder
RequirementsGoals and constraints
Design recordsThe approach chosen, and why
Operations and access rulesTime limits, who can reach what
Performance and incident logsMeasurements and the situation at the time
Try asking
Draft a design and task plan for implementing this requirement.
If we change this feature, find the design decisions and code to review with it.
Check whether the current implementation still fits the reasons in the design records.
Keep it going
When the design changes, ask the agent to update the design records with the reason, keeping the earlier decision.
Your material doesn't need particular names or formats. When you apply the method, the agent organizes it to fit.
AI understands what matters and why.Now it’s ready to work with you.
04
Mekra Method
Mekra Method lets agents decide how to organize and maintain knowledge, then use that context in actual work. It provides application guides, templates, and operating knowledge to put the method into practice.
Keep the reference clear. Give each fact a clear place to be defined and updated. Sources of truth
Connect the context. Keep reasons, conditions, and relationships where they help understanding. Review related knowledge when something changes. Context propagation
Let the agent decide how to organize, maintain, and work. It uses the material, purpose, and evidence to choose what knowledge to retain and how to connect and update it. That context also informs how it helps, within the authority you grant. Agent autonomy
Fewer instructions. Let agents find their own way.
A harness shapes how agents work through instructions, tools, and workflows.
Mekra provides context for judging what matters and why, and which conditions and relationships to consider.
Together, you can provide the structure agents need to act while leaving specific working methods to their judgment.
Mekra vs Ontology
An ontology explicitly represents concepts and relationships.
Mekra lets agents judge what knowledge to keep, which reasons and conditions to connect, and what to update together when something changes.
Together, they can connect concepts and relationships expressed in an ontology with the reasons for that structure, the conditions where it applies, and the context of change.
06
Why Mekra
Keep sources of truth clear, share context where it is needed, and delegate judgment.
Finding a fact is only part of understanding it. An agent also needs to know why it matters, when it applies, and what else changes with it.
Mekra keeps that context available where the agent needs it, and maintains the connections as your knowledge changes.