Loading...
Definitions of key terms used in Context Mesh.
An executable specification that defines how AI should complete a specific task, including purpose, scope, execution steps, and completion criteria.
Example
context/agents/agent-auth.md
A documented example of what NOT to do, including why it's problematic and what to do instead.
Example
context/knowledge/anti-patterns/prop-drilling.md
Specific, measurable conditions that define when a goal has been achieved.
The collection of intent, decisions, knowledge, and agents that define your project. The primary artifact in Context Mesh.
Example
context/
A methodology for AI-first development that treats context as the primary artifact, providing structure for intent, decisions, knowledge, and agents.
A document that captures an architectural decision, including context, the decision itself, rationale, and consequences.
Example
context/decisions/001-tech-stack.md
A checklist of criteria that must be met for a task or feature to be considered complete.
The process of updating and improving your context over time based on learnings and changes.
Example
context/evolution/changelog.md
A document that defines what a specific feature should do, why it's needed, and criteria for success.
Example
context/intent/feature-auth.md
A document or set of documents that define what you're building and why, before how.
Example
context/intent/project-intent.md
Documented patterns, anti-patterns, and best practices that guide implementation.
Example
context/knowledge/patterns/
A documented solution to a recurring problem, including when to use it, how to implement it, and examples.
Example
context/knowledge/patterns/api-handler.md
The root intent document that defines the overall project goals, scope, and acceptance criteria.
Example
context/intent/project-intent.md
The boundaries of what an agent or feature should and should not do. Helps prevent scope creep.
Now that you know the terminology, see how Context Mesh compares to other methodologies.