Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
91 commits
Select commit Hold shift + click to select a range
e2e387e
small title change
DeveloperAlly Jan 18, 2026
e4e18b4
clean up duplicate assets
DeveloperAlly Jan 18, 2026
d1af4f0
tweaks on Home Pages, adding content
DeveloperAlly Jan 18, 2026
8234de5
home tab ok to ship to preview
DeveloperAlly Jan 18, 2026
3a4eaec
change n8n fetches to github actions
DeveloperAlly Jan 19, 2026
91c35b4
add github workflows
DeveloperAlly Jan 19, 2026
373b524
update gh secret name
DeveloperAlly Jan 19, 2026
03f1e44
Update forum data - 2026-01-19T03:30:43.015-05:00
DeveloperAlly Jan 19, 2026
8bfc8d2
Update Blog Data 2026-01-19T03:35:53.410-05:00
DeveloperAlly Jan 19, 2026
fc6330a
blog workflow
DeveloperAlly Jan 19, 2026
348991f
add youtube ingest
DeveloperAlly Jan 19, 2026
3bc88ba
remove secret
DeveloperAlly Jan 19, 2026
c4fd763
remove from git
DeveloperAlly Jan 19, 2026
fbbb1c2
Update Livepeer YouTube videos - 2026-01-19T11:18:24.988Z
DeveloperAlly Jan 19, 2026
92ab39f
Update Livepeer YouTube videos - 2026-01-19T11:24:35.317Z
DeveloperAlly Jan 19, 2026
44cb743
Update Livepeer YouTube videos - 2026-01-19T11:40:42.960Z
DeveloperAlly Jan 19, 2026
d4d4087
youtube ingest
DeveloperAlly Jan 20, 2026
3e25953
manual pull
DeveloperAlly Jan 20, 2026
8449d34
finalise trending page
DeveloperAlly Jan 20, 2026
637bc09
remove tests
DeveloperAlly Jan 20, 2026
7674c70
Update forum data - 2026-01-20T14:00:14.116-05:00
DeveloperAlly Jan 20, 2026
b382233
add discord announcements automation
DeveloperAlly Jan 21, 2026
b3d55c0
chore: update Discord announcements from workflow
DeveloperAlly Jan 21, 2026
9f3a5db
commitMessage: `chore: create Discord announcements file from workflo…
DeveloperAlly Jan 21, 2026
276a84c
discord announcements integrated
DeveloperAlly Jan 21, 2026
a8d96fe
tweak
DeveloperAlly Jan 21, 2026
2428594
tweak
DeveloperAlly Jan 21, 2026
5d6044e
tweak
DeveloperAlly Jan 21, 2026
010fa59
added socials links to community
DeveloperAlly Jan 21, 2026
9fbcf58
add luma automation
DeveloperAlly Jan 21, 2026
25e8575
Rename lumaEvents.jsx to lumaEventsData.jsx
DeveloperAlly Jan 21, 2026
e9efd63
`Chore: Update Livepeer events from Luma - ${new Date().toISOString()}`
DeveloperAlly Jan 21, 2026
104d5fb
fix luma calendar style
DeveloperAlly Jan 21, 2026
f57f0f5
`Chore: Update Livepeer events from Luma - ${new Date().toISOString()}`
DeveloperAlly Jan 21, 2026
f81ce1f
`Chore: Update Livepeer events from Luma - ${new Date().toISOString()}`
DeveloperAlly Jan 21, 2026
d21d4e6
clean up console.logs
DeveloperAlly Jan 21, 2026
327fe70
Update forum data - 2026-01-21T14:00:13.974-05:00
DeveloperAlly Jan 21, 2026
ae12a56
commitMessage: `chore: create Discord announcements file from workflo…
DeveloperAlly Jan 22, 2026
c8e9e5b
Update forum data - 2026-01-22T14:00:13.728-05:00
DeveloperAlly Jan 22, 2026
550af11
Update forum data - 2026-01-23T14:00:14.163-05:00
DeveloperAlly Jan 23, 2026
f92d178
updating pages
DeveloperAlly Jan 23, 2026
1a67f24
finishing Livepeer section
DeveloperAlly Jan 23, 2026
6912819
Home > Livepeer Section content
DeveloperAlly Jan 24, 2026
d88527c
update ecosystem page
DeveloperAlly Jan 24, 2026
f03fcc3
add a quote component
DeveloperAlly Jan 24, 2026
39abb81
home cleanup
DeveloperAlly Jan 24, 2026
8a8b7e4
commitMessage: `chore: create Discord announcements file from workflo…
DeveloperAlly Jan 24, 2026
95e04f2
fix discord automation
DeveloperAlly Jan 24, 2026
face906
im tired now goodnight
DeveloperAlly Jan 24, 2026
085cab9
Update forum data - 2026-01-24T14:00:41.219-05:00
DeveloperAlly Jan 24, 2026
2f08e77
Update Livepeer YouTube videos - 2026-01-25T05:00:25.250Z
DeveloperAlly Jan 25, 2026
938379f
`Chore: Update Livepeer events from Luma - ${new Date().toISOString()}`
DeveloperAlly Jan 25, 2026
1401aeb
Update Blog Data 2026-01-25T00:00:46.631-05:00
DeveloperAlly Jan 25, 2026
a2d6876
primer
DeveloperAlly Jan 25, 2026
f1a2e06
add embody section
DeveloperAlly Jan 25, 2026
12b9806
resolve merge conflict
DeveloperAlly Jan 25, 2026
97cca96
basic embody page
DeveloperAlly Jan 25, 2026
3c782d9
products updates
DeveloperAlly Jan 25, 2026
d010c04
product IA merge
DeveloperAlly Jan 25, 2026
ab5acc9
socialscomponent, primer
DeveloperAlly Jan 25, 2026
b80cb1b
tweaks
DeveloperAlly Jan 25, 2026
f32bcdf
continuing ecosystem
DeveloperAlly Jan 25, 2026
052dd07
refining ecosystem
DeveloperAlly Jan 25, 2026
f178936
refining ecosystem
DeveloperAlly Jan 25, 2026
1106d84
split org and eco
DeveloperAlly Jan 25, 2026
e134c04
Update forum data - 2026-01-25T14:00:41.121-05:00
DeveloperAlly Jan 25, 2026
db69804
script to create a glossary, updating socials links, finalising organ…
DeveloperAlly Jan 26, 2026
6023185
finalise section
DeveloperAlly Jan 26, 2026
7a31b91
Update forum data - 2026-01-26T14:00:41.280-05:00
DeveloperAlly Jan 26, 2026
e964a7d
Update forum data - 2026-01-27T14:00:41.077-05:00
DeveloperAlly Jan 27, 2026
572fa04
primitives for showcase
DeveloperAlly Jan 28, 2026
332fab4
starting orchestrators
DeveloperAlly Jan 28, 2026
f26e954
wading through the orchestrator docs
DeveloperAlly Jan 28, 2026
c97afb1
Update forum data - 2026-01-28T14:00:42.617-05:00
DeveloperAlly Jan 28, 2026
a0daf01
gpus and protocol
DeveloperAlly Jan 29, 2026
b0e4e92
fix docs.json
DeveloperAlly Jan 29, 2026
fdb1a45
Update forum data - 2026-01-29T14:00:42.661-05:00
DeveloperAlly Jan 29, 2026
1ef535e
pools complete
DeveloperAlly Jan 30, 2026
b9269f8
orchestrator setup
DeveloperAlly Jan 30, 2026
259f30e
Update forum data - 2026-01-30T14:00:41.546-05:00
DeveloperAlly Jan 30, 2026
eb0f86c
Update forum data - 2026-01-31T14:00:46.521-05:00
DeveloperAlly Jan 31, 2026
b076c70
Update Livepeer YouTube videos - 2026-02-01T05:00:25.179Z
DeveloperAlly Feb 1, 2026
6557e86
`Chore: Update Livepeer events from Luma - ${new Date().toISOString()}`
DeveloperAlly Feb 1, 2026
3049050
Update Blog Data 2026-02-01T00:00:46.630-05:00
DeveloperAlly Feb 1, 2026
2024d35
Update forum data - 2026-02-01T14:00:41.121-05:00
DeveloperAlly Feb 1, 2026
0d6f130
Update forum data - 2026-02-02T14:00:40.838-05:00
DeveloperAlly Feb 2, 2026
399c16e
protocol section
DeveloperAlly Feb 3, 2026
6488015
Update forum data - 2026-02-03T14:00:41.180-05:00
DeveloperAlly Feb 3, 2026
dc69e67
finishing home tab, protocol section
DeveloperAlly Feb 4, 2026
5fd28da
showcase setup
DeveloperAlly Feb 4, 2026
36125e7
Update forum data - 2026-02-04T14:00:40.899-05:00
DeveloperAlly Feb 4, 2026
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 0 additions & 16 deletions .ai-audit.sh

This file was deleted.

File renamed without changes.
46 changes: 46 additions & 0 deletions .augment/rules/imported/AI_GUIDELINES.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,46 @@
---
type: "always_apply"
---

# 🛡️ AI SAFETY PROTOCOL: GIT WRITE OPERATIONS

## 1. MANDATORY SAFETY HOOKS

This repository uses custom Git hooks for "Human-in-the-Loop" (HitL)
verification.

- **ENFORCEMENT:** You SHALL NOT attempt to bypass hooks.
- **FORBIDDEN:** The use of `--no-verify`, `-n`, or any environment variable
designed to skip Git hook execution is STRICTLY PROHIBITED.
- **BEHAVIOR:** When you initiate a `commit`, `push`, or `rebase`, the hook will
pause and wait for manual input in the user's terminal. You MUST wait for the
user to confirm.

## 2. AUTOMATED CHECKPOINTING

Every write command triggers an automatic checkpoint branch.

- **FORMAT:** `checkpoint/YYYY-MM-DD_HHMMSS`
- **ACTION:** Before running a write command, you MUST state: _"I am initiating
[COMMAND]. A safety checkpoint will be created. Please approve the prompt in
your terminal."_

## 3. CATASTROPHIC FAILURE RECOVERY

In the event of a destructive operation (e.g., accidental file deletion,
corrupted rebase, or broken merge):

- **DO NOT** attempt to "fix" the state with further complex Git commands.
- **PROCEDURE:**
1. Identify the latest `checkpoint/` branch using
`git branch --list 'checkpoint/*'`.
2. Suggest a `git reset --hard` to that specific checkpoint branch to restore
the repository to its pre-failure state.
3. Notify the user immediately of the failure and the recovery path.

## 4. SCOPE LIMITATIONS

- **READS:** You have full permission for `git status`, `git diff`, and
`git log`.
- **WRITES:** Every `commit`, `push`, and `rebase` is a high-stakes action.
Treat them as irreversible without human oversight.
96 changes: 96 additions & 0 deletions .augment/rules/imported/copilot-instructions.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,96 @@
---
type: "agent_requested"
description: "Example description"
---

docs. The docs are built and previewed using Mintlify CLI, and can be
containerized with Docker.

# Copilot Instructions for Livepeer Docs (2026)

## Big Picture & Architecture

- **Multi-version Docs:**
- `v1/` = legacy, `v2/` = current. Navigation in `docs.json`/`docs_v2.json`.
- **Component System:**
- Custom React/TSX/JSX components in `snippets/components/` (see
README-custom-view.md for advanced usage).
- Use `.tsx` for new components; `.jsx` is legacy but supported.
- **Automations & Scripts:**
- All dynamic, AI, and data-fetching logic in `automations/` and `ai-tools/`.
- Scripts for API doc generation and external data in `snippets/scripts/` (see
generate-api-docs.sh, fetch-openapi-specs.sh).
- **API Reference:**
- OpenAPI spec in `openapi.yaml` (AI API: see ai/worker/api/openapi.yaml). Use
scripts to generate MDX/API docs.
- **Assets:**
- Images/logos in `images/`, `logo/`, and static assets in `assets/`.

## Developer Workflows

- **Preview Locally:**
1. Install Mintlify CLI: `npm i -g mintlify`
2. Run: `mint dev` (from repo root, where `mint.json` or `mint_v1.json`
exists)
- **Build/Deploy:**
- Docker:
`docker buildx build --platform linux/amd64 --load -t livepeer/docs .`
- Makefile: `make all`
- **API Docs Generation:**
- Use `snippets/scripts/generate-api-docs.sh` to convert OpenAPI specs to
MDX/API docs and navigation JSON. Example:
```bash
./snippets/scripts/generate-api-docs.sh ai/worker/api/openapi.yaml v2/pages/04_gateways/guides-references/api-reference/AI-API "AI API"
```
- Output: MDX files + navigation snippet for `docs.json`.
- **External Data Fetching:**
- Use `fetch-openapi-specs.sh` and `fetch-external-docs.sh` for syncing
specs/docs from other repos.
- **Component Usage:**
- Import with relative paths from `snippets/components/` in `.mdx` files.
- For custom dropdowns, see `CustomViewDropdown` in
`snippets/components/custom-view-dropdown.jsx` and its README.

## Project Conventions & Patterns

- **MDX-First:** All docs are `.mdx` (Markdown + JSX/TSX components).
- **Versioning:** New docs in `v2/`, legacy in `v1/` or
`deprecated-references/`.
- **AI/Dynamic Content:** All AI-generated or dynamic content in `automations/`
or `ai-tools/`.
- **SEO & Metadata:** Add SEO tags/metadata in page frontmatter (see
`README_V2.md`).
- **No Formal Test Suite:** Preview changes locally before merging.
- **Architecture:**
- Docs mirror protocol architecture: Gateway, Orchestrator, Transcoder, AI
Worker. See `README_V2.md` for detailed flows and node roles.
- Gateways do not process video; they route jobs to orchestrators. Node roles
are mutually exclusive (see `README_V2.md`).
- **Custom Views:**
- Use `CustomViewDropdown` for Mintlify-style view switching. See
`snippets/components/README-custom-view.md` for migration and usage.

## Integration Points

- **Mintlify:** All build/preview flows use Mintlify CLI and config files
(`mint.json`, `docs.json`).
- **OpenAPI:** API docs generated from `openapi.yaml` (see also
`ai/worker/api/openapi.yaml`).
- **Docker:** Containerized builds for CI/CD and local dev.
- **Automations:** Scripts in `snippets/scripts/` automate API doc generation
and external data sync.

## Key Files & Directories

- `docs.json`, `docs_v2.json` — Navigation/config
- `snippets/components/` — Custom components (see README-custom-view.md)
- `automations/`, `ai-tools/` — Scripts, AI, dynamic content
- `openapi.yaml`, `ai/worker/api/openapi.yaml` — API reference
- `Dockerfile`, `Makefile` — Build/deploy
- `README.md`, `README_V2.md` — Developer notes, protocol/architecture
- `snippets/scripts/` — Automation scripts (API docs, data fetching)

---

If any conventions or workflows are unclear, review the latest `README.md`,
`README_V2.md`, or automation READMEs, or ask for clarification.
128 changes: 128 additions & 0 deletions .github/augment-instructions.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,128 @@
# Augment Instructions for Livepeer Docs

## ⛔ CRITICAL RULES - VIOLATION = CATASTROPHIC FAILURE ⛔

### NEVER PERFORM GIT OPERATIONS WITHOUT EXPLICIT PERMISSION

- **NEVER** run `git commit` without explicit user permission
- **NEVER** run `git push` without explicit user permission
- **NEVER** run `git reset` (soft/hard/mixed) without explicit user permission
- **NEVER** use `--no-verify` flag to bypass hooks
- **NEVER** modify git history or remote state
- **ALWAYS** ask before ANY git operation that could lose work

### INCIDENT LOG - LEARN FROM THESE FAILURES

**2026-01-06 00:52 UTC**: AI assistant performed unauthorized
`git reset --hard HEAD~1`

- Destroyed hours of user work across 11 files
- Violated explicit "NEVER commit/push without permission" rule
- Required emergency recovery from VSCode Augment checkpoints
- User lost focus, workflow, and trust
- **THIS MUST NEVER HAPPEN AGAIN**

## User Rules (CRITICAL - FOLLOW ALWAYS)

1. **Never make code edits without permission that cannot be reverted**
2. **Don't ask for read/grep/view command permissions** - just do it
3. **Before implementing fixes** - explain the issue and proposed solution first
4. **Don't repeat past errors** - if something failed, try a different approach
5. **Keep context minimal** - only load files needed for the task
6. **Always have a backup before risky changes** - THIS IS CRITICAL. If testinga
change, ensure you can revert first
7. **Easily reversible code changes** - OK to make without asking
8. **Never make irreversible changes** - always ensure changes can be undone

## Repository Structure

### Multi-Version Docs

- `v1/` - Legacy documentation
- `v2/` - Current documentation
- Navigation configs: `docs.json` (v1), `docs_v2.json` (v2)

### Key Directories

- `snippets/components/` - Custom React/JSX/TSX components
- `snippets/data/` - Data files (gateways.jsx, etc.)
- `automations/` - Dynamic/AI/data-fetching logic
- `ai-tools/` - AI-related tooling
- `v2/scripts/` - API doc generation, data fetching scripts
- `images/`, `logo/`, `assets/` - Static assets

### Important Files

- `mint.json`, `docs.json` - Mintlify config/navigation
- `openapi.yaml` - API reference spec
- `ai/worker/api/openapi.yaml` - AI API spec
- `Dockerfile`, `Makefile` - Build/deploy
- `README.md`, `README_V2.md` - Developer documentation

## Development Workflows

### Local Preview

```bash
npm i -g mintlify
mint dev
```

### Docker Build

```bash
docker buildx build --platform linux/amd64 --load -t livepeer/docs .
```

### API Docs Generation

```bash
./v2/scripts/generate-api-docs.sh ai/worker/api/openapi.yaml v2/pages/04_gateways/guides-references/api-reference/AI-API "AI API"
```

## Component System

- All docs are `.mdx` (Markdown + JSX)
- Custom components in `snippets/components/`
- Use `.tsx` for new components (`.jsx` is legacy)
- Import with relative paths from `snippets/components/`

### Key Components

- `CustomCodeBlock` - Code blocks with variable interpolation
- `CustomViewDropdown` - Mintlify-style view switching
- Various callout/warning components in `snippets/components/gateways/`

## Architecture Context

Livepeer protocol node roles:

- **Gateway** - Routes jobs, doesn't process video
- **Orchestrator** - Coordinates work
- **Transcoder** - Processes video
- **AI Worker** - Handles AI inference

Node roles are mutually exclusive.

## Data Files

### snippets/data/gateways.jsx

Contains Docker Compose configurations:

- `DOCKER_YML.offChain.{videoMin, video, aiMin, ai, dualMin, dual}`
- `DOCKER_YML.onChain.{video, ai, dual}`

Use with `CustomCodeBlock`:

```jsx
<CustomCodeBlock language="yaml" codeString={DOCKER_YML.offChain.videoMin} />
```

## Conventions

- MDX-first documentation
- New docs go in `v2/`
- Legacy/deprecated content in `v1/` or `deprecated-references/`
- No formal test suite - preview locally before merging
- SEO tags/metadata in page frontmatter
Loading