explainroo
explainroo is a free, open source tool that lets your AI agent make explainer videos with a voice. It runs on your own computer and needs no API key.
How India’s governments have handled protests since 1974, under every party, at the Centre and in the states. Every claim links to a dated source.
MediaTypeScript · CSSGitHub @theachyuttiwariOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
How India's governments have handled protests: an open, sourced record across every party, since 1974.
Translation pending
Loading the full README.
Read the full README ↗An open record of how the Indian state acts when different parties hold power. It starts with protest: today's event, set beside how earlier governments of every party handled the same kind of protest. Every claim links to a dated source.
LIVE EVENT ──► tagged by action type ──► PRECEDENT SHELF (1974 → now)
│
▼
COMPARISON: party × action, in power vs in opposition
Memory is short and the record is long. A new generation sees today's crackdown or today's permission without the thirty cases before it. Priors puts them side by side.
| Path | What |
|---|---|
content/precedents/*.yaml | One protest, one government's answer. Hand-written or pipeline-drafted, human-checked. |
content/current/*.yaml | Events underway. Added by hand or drafted by the pipeline, marked reviewed: false until checked. |
content/SCHEMA.md | The schema and action-type vocabulary. |
src/ | Next.js static site. |
pipeline/ingest.ts | Claude + web search finds recent events, structures them, writes YAML. |
pipeline/validate.ts | Command-line wrapper for src/lib/validate.ts. Runs in CI. |
tests/ | Unit tests for formatting, validation and the counting rules. |
docs/ | Landscape research and naming notes. |
Needs Node 22 (see .nvmrc).
npm install
npm run dev # http://localhost:3000
npm run build # static export to out/
| Command | What it does |
|---|---|
npm run check | Format, lint, typecheck, tests and content validation. Run before a PR. |
npm run validate | Schema and source-reference checks on content/. |
npm run validate -- --strict | The same, but warnings fail too. CI runs this. |
npm test | Unit tests (Vitest). |
npm run format | Format with Prettier. |
export ANTHROPIC_API_KEY=... # or: ant auth login
npm run ingest -- --days 14 --dry # print, do not write
npm run ingest -- --days 14 # write to content/current/
The site is static and refreshed by hand. "Last updated" dates come from git history. The ingest.yml workflow can be run by hand once the ANTHROPIC_API_KEY repo secret exists. It opens a pull request. Review the sources, set reviewed: true, merge.
content/SCHEMA.md.npm run check.Code: MIT. Content in content/: CC BY 4.0. Quoted sources belong to their publishers. To cite the record, see CITATION.cff.