knowledge-frames

name	knowledge-frames
description	Minsky frames, Drescher schemas, interchange registry, and MOOLLM K-lines — distinct layers.
allowed-tools	["read","grep","glob"]

Knowledge Frames — Layers

Several ideas get called “schema” or “frame” in the wild. This skill keeps them separate so MOOLLM skills can point at the right layer.

Part of MOOLLM

See skills/README.md and the repo README.

1. Minsky frames (situation shape)

What: A frame is a structured expectation about a kind of situation: named slots, default fillers, hooks for exceptions. Restaurant, birthday party, debugging session.

Job: Answer “what kind of situation is this?” and “what pieces usually belong?”

Not: A causal learning unit (that’s Drescher). Not a protocol activation symbol (that’s K-lines).

In MOOLLM: Use frame when you mean slot structure or default script for a situation. YAML Jazz directory listings and CARD layouts often act as lightweight frames (“what’s here?”).

2. Drescher schemas (causal units)

What: Context → Action → Result — a learned causal unit. See schema-mechanism.

Job: Answer “what tends to happen when I do X in context Y?”

Not: Interchange validation (JSON Schema, XSD, RELAX NG, …). Not Minsky’s frame slots.

3. Interchange schema registry (wire shapes)

A for valid serialized data: JSON Schema, Zod, RELAX NG, W3C XML Schema (XSD), and others registered under . Nomenclature, docs, libraries, and between mechanisms live there.