Teaching surface · canonical grammar v0.1

Csound Teatro — Speaking Sound in Space

Csound Teatro gives humans and machines one inspectable language for saying what exists, how things relate, when relations apply, how values map, what Ear observes, and what a Scenario is allowed to execute.

Governance Chapter 151 → · Open Teatro →

One contract

Meaning first, engines second.

The canonical Scenario is semantic authority. Physics supplies events, Csound realizes sound, WebGL projects state, Ear measures, MIDI2 carries governed lifecycle, and FountainStore keeps evidence. None of those adapters may silently invent semantic meaning.

Canonical Csound Teatro grammar flowing from human request through Scenario to physics, Csound, WebGL, Ear, MIDI2 and Store evidence
Governance projection of the architecture. It is not live runtime evidence.
Ten steps

Learn the same grammar the runtime validates.

  1. 01 · ThingsIdentify canonical entities such as Ball.01, Plate.01 and Ear.01.
  2. 02 · PropertiesInspect typed values and units, for example Ball.01.velocity in m/s.
  3. 03 · RelationsState admitted predicates such as EXCITES and LISTENS_TO.
  4. 04 · EventsSay when a relation applies: collision(Ball.01, Plate.01).
  5. 05 · MappingsMap a declared input domain to a declared target port with explicit policy.
  6. 06 · SpaceProject canonical state without turning geometry into semantic authority.
  7. 07 · EarAttach a typed observing instrument and a measurable assertion.
  8. 08 · ScenarioCollect GIVEN, TRANSFORM, CONSTRAINTS, EXPECT and VERIFY into one executable contract.
  9. 09 · Model collaborationUse local or remote models only as optional interpreters; the guaranteed path remains provider-independent.
  10. 10 · Implementation inspectionFollow the admitted Scenario into physics, Csound, WebGL, MIDI2, Store and verification.
Grammar reference

Finite vocabulary, explicit mapping.

Grammar v0.1 admits the predicates below. Unknown predicates are rejected before execution.

PRODUCES · RECEIVES · EXCITES · CONTROLS · MODULATES · MAPS_TO · TRIGGERS · FOLLOWS · CONTAINS · OBSERVES · LISTENS_TO · AFFECTS · ABOVE · BELOW · NEAR · INSIDE · OUTSIDE · TOUCHING · MOVING_TOWARD · MOVING_AWAY

Entity kinds

BODY, INSTRUMENT, EAR, FIELD.

Scenario schema

GIVEN, TRANSFORM, CONSTRAINTS, EXPECT, VERIFY, plus grammar and schema version.

Mapping policy

Source property, target port, domains, units, transfer, clamp, interpolation and update mode are explicit.

Example Scenario

Ball excites Plate when they collide.

WHEN collision(Ball.01, Plate.01)
    Ball.01 EXCITES Plate.01

Ball.01.velocity 0..7 m/s
    MAPS_TO
Plate.01.excitation 0..1 normalized

Ear.01 LISTENS_TO Plate.01

AFTER collision(Ball.01, Plate.01)
EXPECT Ear.01.onset == true WITHIN 50 ms

The 50 ms value belongs to this admitted fixture. A different Scenario must declare and justify its own assertion boundary.

Provider independence

A model may interpret. It may not own the system.

The built-in path works without network inference, API keys or provider credits. Supported human requests resolve through authoritative selection and discovered capabilities. Unsupported language is refused rather than guessed. Apple on-device models, Linux-local models, Codex or other providers can collaborate behind the same narrow intent contract.

Evidence boundary

What the initial fixture establishes.

The accepted Ball/Plate/Ear fixture establishes provider-independent interpretation, native pre-effect admission, physics collision, declared mapping, Csound-backed excitation, measured Ear onset, native verification, Store evidence and terminal MIDI2 lifecycle for that fixture. It does not establish universal grammar coverage, human hearing, arbitrary natural-language understanding or public release.