# Contents

- `drivers/` – fixed Blender and CadQuery native adapters and portable boundary checks.
- `education/` – the fixed Manim adapter, pure lesson/timing validation, original presenter toolkit and native qualification source.
- `assets/` – supported provider asset acquisition, retained provenance and bounded immutable files.

# Guidelines

- Preserve native source authority and exact declared dependencies. Import, inspect and pure planning never execute authored source.
- Execute only through fixed host-selected adapters and an explicit current-user trust envelope. Native Python and installed runtime plugins are not sandboxed; keep the profile nonhermetic.
- Keep source, output, scratch and diagnostics separate. Reverify hashes, dimensions, clocks, media profiles and exact output coverage before successful publication.
- Probes describe observed installed capabilities; native fixtures qualify actual behavior. Do not infer GPU rendering, rig deformation, solver completion, cache reuse or correct units from configuration flags.
- Keep downloaded assets inert. Bound origins, redirects, bytes, files and paths; retain provider credit, license and original file identity.
- Embed required driver/template bytes in the copied CLI and include owned source in application identity. Do not depend on a development checkout or an implicit Python helper.
- Keep actual media, installed engines, caches, provider state and native qualification outputs under ignored artifacts. Portable tests require no paid service or native engine installation.