Installation — Ecosystem Animation

Where everything lives and how to install it. Three homes: the GitHub repo (canonical), Google Drive (sharing), and the design project (editing).

1. What's in this package

github-commit/                          ← the package folder (unzipped from `Animation specs needed.zip`, at `export/github-commit/`)
└── docs/design/console/animation/
    ├── ecosystem-animation-standalone.html   ← playable, self-contained (open in any browser)
    ├── README.md                             ← contents + provenance
    ├── vo/
    │   └── VO-SCRIPT.md                      ← timecoded narration (40s)
    └── src/
        ├── ecosystem-animation.dc.html       ← authoring entrypoint (scenes, playback, tweaks)
        ├── ecosystem-scene.jsx               ← all motion, layout, timing
        ├── animations-v3.jsx                 ← animation engine (runtime)
        └── tweaks-panel.jsx                  ← tweaks panel (runtime)

2. Install into the repo (MIZOKICloudRun)

The source archive is the design-project export Animation specs needed.zip; the package folder inside it is export/github-commit/ (there is no github-commit.zip). Unzip it anywhere, then copy its docs/ subtree over the repo's — nothing else in the export is needed.

cd MIZOKICloudRun
git checkout -b design/ecosystem-animation
PKG=../github-commit   # set to the unzipped export/github-commit/ folder before running the chain
test -d "$PKG/docs/design/console/animation" \
  && mkdir -p docs/design/console/animation \
  && cp -R "$PKG/docs/design/console/animation/." docs/design/console/animation/ \
  && git add docs/design/console/animation \
  && git commit -m "docs(design): ecosystem animation — standalone player, scene source, VO script" \
  && git push -u origin design/ecosystem-animation

The chain is &&-joined on purpose: if PKG does not point at the package, the first test fails and nothing after it runs.

Result: everything lands under docs/design/console/animation/ — the console design home; this folder's README.md carries the contents and provenance. No build step, no dependencies, nothing touches app code or cells. As of 2026-09-02 the package is already on main (player and src/ via #877, vo/ via #890), so these steps are the record of how it got there and the path for a re-export.

3. View it (no install needed)

Open ecosystem-animation-standalone.html directly — double-click, any modern browser, works offline. This is the file to share, demo, or attach. Do not edit it (it's compiled).

4. Edit it

The src/ files are authoring sources from the design environment; they need its runtime (support.js, design-system bundle) which is not in this package — they will NOT run standalone. To change motion, timing, copy, or colors: edit in the design project ("Animation specs needed" — files Ecosystem Animation.dc.html + ecosystem-scene.jsx at the project root), then re-export the standalone and replace it here. Timeline edits (trim/re-speed scenes) and video export: Share → Export → Video in the design project.

5. Google Drive (already installed)

Folder: MIZ OKI — Ecosystem Animation https://drive.google.com/drive/folders/1S-oT4MNl1Rqe98hhqtDajLti0cPX6Zzd

Contains the source .dc.html, ecosystem-scene.jsx, and the VO script. The standalone HTML exceeds the connector limit — drag ecosystem-animation-standalone.html (the file in this folder; the design tool's own download of it is titled Ecosystem Animation - standalone.html, same bytes) into that folder to complete it.

6. Where it does NOT go

Not into app/, not into the command-center UI, not served by any cell. It's a docs/design artifact only — a communication asset, not shipped product code.