Kantext Playground — Guided Experience

The Language

Kantext Code —

Points:—

Boundaries:—

Traces:—

Time:—

This entire scenario was composed by Claude Opus 4.6 in a single session via Kantext MCP — proof that AI can compose Kantext.

Syntax Reference

⛩️ Boundary

Declares vocabulary, shapes, and constraints.

⛩️:
    Meaning@name
    Space@shape

Meaning Declaration

Semantic label with gradient mapping.

Meaning@trust:
    Mapping:
        -1.0: Anonymous
        1.0: Attested

Space & Values

Structural containers with typed fields.

Space@Principal:
    id
    trust
    reason

Context

Real instances composing against vocabulary.

Alice@Principal:
    id: alice@example.com
    trust: 0.5

The Holograph

The fully resolved, navigable composition. Click any point to inspect.

⛩️

Edit the .kant content above — composition runs automatically as you type

Query with HQL

🔍

Run a query to see results

HQL Syntax

/Name

Exact path to a point

/A/B/C

Nested path traversal

/A/B/*

Direct children of B

/**

All descendants

/**[Type]

Type-filtered descendants
(Boundary, SpaceBond, ValueBond, Meaning)

Render with Templates

Select a template or write Jinja2 to see output

Why Templates? This is how Kantext MCP lets models explore large compositions without flooding context windows. Models write Jinja templates in a language they already know.