Overview

contox_explain_schemakey provides a comprehensive deep-dive into a specific brain node identified by its schemaKey. It returns schema metadata, a content preview, runtime links (incoming and outgoing), recent entries, and related contracts.

Use this to understand any part of the brain in detail before making modifications.

Parameters

Name	Type	Required	Default	Description
`schemaKey`	string	Yes	—	The schemaKey to explain (e.g., `"root/contracts/auth"`, `"root/bugs"`)

Return value

Returns a formatted markdown report including:

Section	Description
Schema metadata	Tier, contextType, writePolicy, and other schema-level properties
Content preview	Truncated preview of the context content
Runtime links	Incoming and outgoing links to other contexts
Recent entries	Latest journal entries (if applicable)
Related contracts	Associated contracts or agreements

Usage examples

Understanding the architecture node

User: Tell me about the architecture context in the brain

Claude calls: contox_explain_schemakey({ schemaKey: "root/architecture" })

Response:
## root/architecture

### Schema Metadata
- Tier: 1 (always loaded)
- Context Type: memory
- State: approved

### Content Preview
Next.js 14 App Router with TypeScript strict mode. Tailwind CSS v4 for styling.
Appwrite Cloud for backend services...

### Links
#### Outgoing (1)
- -> root/conventions [see-also] — Architecture decisions inform conventions

#### Incoming (2)
- <- root/scan/routes [related] — Route structure reflects architecture
- <- root/implementation [depends-on] — Implementation follows architecture patterns

Investigating a specific subsystem

Claude calls: contox_explain_schemakey({ schemaKey: "root/scan/api-routes" })

Notes

The content preview is truncated for large contexts. Use contox_get_context to read the full content.
This tool combines data from multiple API calls (context metadata, links, entries) into a single readable report.
If the schemaKey does not exist, the tool returns an error.

contox_oncall_view

contox_scan