The structured human interface to your context.
LatticeExplorer is the exploration surface that gives humans interactive access to context objects. Navigate an Explorer > Collections hierarchy, browse and query context atoms, get source-grounded answers, generate artifacts, and export context packs.
Your context layer is only as useful as your ability to navigate it.
Organizations invest in capturing and structuring context, but without a dedicated exploration interface, the resulting knowledge graph remains opaque. Teams cannot browse what exists, query across collections, or verify whether context atoms actually answer their questions. Context packs stay locked inside APIs, inaccessible to the humans who curated them.
LatticeExplorer solves this by providing a structured, hierarchical interface to the entire context layer. Humans can navigate collections, interactively query context atoms, receive source-grounded answers with citations, generate artifacts from context, and export context packs for downstream use — all without writing API calls.
From context layer to human understanding.
Browse the Explorer > Collections hierarchy. Collections organize context atoms by domain, team, workflow, or any organizational dimension that makes context findable.
Interactively browse and query context atoms within collections. Search by keyword, filter by maturity state, scope by role, or ask natural-language questions.
Receive source-grounded answers with citations back to the original context atoms, documents, and contributions. Every answer is traceable to its origin.
Create artifacts from context — summaries, reports, playbooks, onboarding guides, and reference materials assembled from governed context atoms.
Package context into exportable context packs for downstream use by agents, teams, or external systems. Export in JSON, MDX, or Markdown formats.
See, query, and use everything in your context layer.
LatticeExplorer reads from LatticeCore's three-tier memory system and surfaces context assembled by ContextCurator. It serves as the human verification layer — teams can browse, validate, and approve context before it reaches agents through LatticeEngine.