Category
9 articles
I want analysis context to narrow at decision points, not only at capacity limits. Preserve accepted definitions, unresolved questions, and evidence locations without turning tentative work into verified conclusions.
Read article →A Skill can record the last analysis correctly and still apply it in the wrong project. How I separate reusable methods, shared rules, project knowledge, and decisions for one analysis.
Read article →Prompt engineering is not obsolete, but agents must also manage tools, data, state, history, and memory. Context engineering determines what the model actually sees on each turn.
Read article →A larger context window can hold more tokens, but that does not mean a model uses every passage equally reliably. Long tasks need compaction, structured artifacts, and on-demand loading to control context rot.
Read article →Long-term agent memory affects analysis across conversations, so enterprise knowledge needs provenance, scope, approval, and retirement. This article provides a practical Memory governance framework and Queued Knowledge approval flow.
Read article →MCP connects AI applications, data, and tools through a standardized client-server protocol. This article explains its core components, security boundaries, and Lantide's two-way MCP integration.
Read article →MCP standardizes connections but does not guarantee least privilege. Use host, credential, scope, capability, approval, and audit controls to review agent data access.
Read article →AI Agent governance starts by defining capability boundaries among users, agents, tools, and data, then adding approval, monitoring, and recovery. Use this six-part capability map to assign owners and create testable controls.
Read article →Table names and field types describe the shape of data, not the definitions of valid customers, revenue, conversion, or time windows. Learn which business semantics AI analysis needs and how to turn definitions into a reviewable contract.
Read article →