implicit vs explicit context

2 articles · 11 co-occurring · 0 contradictions · 0 briefs

Code (implicit) vs descriptions (explicit) distinction shows why explicit context representation matters. Claude only sees what's explicitly represented.

Related concepts

tool interface design 1 tool integration patterns 1 token efficiency 1 session persistence context compounding 1 requirement specification completeness 1 prompt engineering 1 output validation refinement 1 model context protocol 1 mcp server architecture 1 code generation 1 agent constraint propagation 1

Evidence chain (2 articles, showing 2)

Every App Needs an MCP Server Now - YouTube supports

Code (implicit) vs descriptions (explicit) distinction shows why explicit context representation matters. Claude only sees what's explicitly represented.

@mitchellh: The problem with the "if it works who cares what the code looks like" mindset... extends

The article highlights the gap between implicit human knowledge (design intent, compatibility priorities, roadmap constraints) and explicit agent context. This is a taxonomy of what context must be ma

query this concept

$ db.articles("implicit-vs-explicit-context")

$ db.cooccurrence("implicit-vs-explicit-context")

$ db.contradictions("implicit-vs-explicit-context")