---
schema_version: 1
revision: "22ce5d34dbcb5a78"
id: "factory-reasoning-and-video-worked-example"
title: "Independent reasoning and video evidence — worked example"
---

# Independent reasoning and video evidence — worked example

Detailed worked example with concrete prompts, observable outcomes, and the limits of the example.

## Before the session: the only beat a human owns

You

Sign into chatgpt.com and gemini.google.com in your normal Chrome — then hand the keys over:

``` text
oracle --engine browser -p "HI"
```

Agent

Oracle copies the session cookies from that logged-in profile into a temporary automation profile, opens ChatGPT in an automated Chrome, sends the prompt, and records the reply as a session. Any reply proves the cookie path works.

Cookies are the entire auth story. No API keys — the browser authenticates as *you* and gets everything the subscription gives you: the model picker, extended thinking, and the upload widget the video pipeline depends on.

## The session, beat by beat

You

`$oracle-video https://www.youtube.com/watch?v=uC6slhCTXlA` — Built this up into an extensive `$here-now` workshop wiki with extensive resources/pull quotes/and ai prompts to copy/paste

That is the whole human contribution to the run — one prompt naming a public 93:49 YouTube workshop ("Building Durable Autonomous Agents", the Loopcraft project). Everything below is the agent working.

Agent

Sized up the source: 93 minutes and 49 seconds of screen-heavy workshop footage. No text model can watch that — only Gemini genuinely watches video, and only through the page's own upload widget. Plan: cut the recording into source-native shards Gemini can watch one at a time.

The first decision is a routing decision: text questions go to GPT-5.6 Pro, footage goes to Gemini — both through the same browser hands.

Agent

Before touching video, asked the strongest text model to review the plan. Session `loopcraft-segmentation-review` (gpt-5.6-pro, completed): GPT-5.6 Pro reviewed how to shard a 93:49 recording so Gemini gets watchable, source-native chunks.

Planning the pipeline with the pipeline: maximum intelligence supervises the video intelligence before a single expensive run starts.

Agent

Probed before spending. A battery of cheap sentinel runs on gemini-3-pro, each asking for exactly one line back:

``` text
loopcraft-video-smoke-probe      error
loopcraft-video-probe-retry      error
loopcraft-video-probe-rebuilt    completed
loopcraft-submit-proof-probe     completed
loopcraft-awaited-upload-probe   completed
  └─ reply: ATTACHED_VIDEO_OK loopcraft-awaited-upload-probe
```

Two failures cost seconds each. Only after the sentinel came back byte-exact — from the real MP4 — did the long runs start. The generalized probe, liftable:

``` text
[video-upload-smoke-probe]

This is an attached-video readiness probe for a longer video analysis run.

Confirm that you can inspect the attached video. Return exactly three short bullets:
- whether video frames are visible;
- whether audio is detectable;
- one strictly observed visual detail, without guessing.

End with this exact sentinel on its own line:
END_OF_VIDEO_ANALYSIS video-upload-smoke-probe probe
```

``` text
oracle --engine browser --model gemini-3-pro --browser-attachments always \
  -p "$(cat probe-prompt.md)" --file "/absolute/path/to/probe-clip.mp4" \
  --slug "video-upload-smoke-probe"
```

Probes before spends: a falsifiable one-line sentinel proves the fragile path (upload, submit, encoding) before an hour-long analysis bets on it. A paraphrase or silence means the path is broken.

Agent

Watched the shards. Sessions `loopcraft-workshop-shard-001…004` (gemini-3-pro): each shard analyzed for the wiki, each analysis required to end in its exact sentinel. The results prove Gemini genuinely watched the footage — it heard "we are going to talk about Loopcraft…" and identified the GitHub workshop page with the presenter's picture-in-picture at the 00:30 mark.

Timestamped screen evidence — slides, terminal output, picture-in-picture — is the thing a transcript summarizer cannot produce.

Agent

Shard 004 errored — twice — while its three siblings sailed through. That pattern rules out "the pipeline is down" and points at the input. Diagnosis: a media-encoding problem. An exact re-encode fixed it completely: the analysis finished in 73 seconds with the exact sentinel, and the re-encode settings were kept as the durable media recipe for future runs.

Failure handled like engineering, not vibes: classify the error, change one variable, re-run the cheap proof, keep the fix.

Agent

Verified, then published. Pull quotes were source-checked against the analyses, the site build passed its checks with zero errors, and after publishing the agent curled the *live* URLs rather than trusting the publish receipt. The result is public and permanent: the [Loop Craft workshop wiki](https://silken-ferry-63mw.here.now/) and its [video companion](https://silken-ferry-63mw.here.now/video-companion/).

One working session: a 93-minute recording became a quotable artifact anyone in the room can open right now — not a chat log.

## Where it landed: the shard prompt, verbatim

This exact prompt produced shard 001 of the wiki — it is the money artifact of the run. Swap the metadata block and the sentinel for your own video; keep the evidence rules, because they are what stop Gemini from inventing commands, URLs, and speakers.

``` text
[loopcraft-workshop-shard-001-source-native]

Analyze the attached source-native video shard for an extensive public workshop wiki.

Metadata:
- run_key: loopcraft-agent-workshop
- shard_id: 001
- original recording range: 00:00:00–00:04:00
- publication chapter: Workshop Setup and the Looping Resolver

Evidence rules:
1. Use original workshop timestamps from 00:00:00 through 00:04:00.
2. Separate spoken evidence, visible screen evidence, and inference.
3. Listen to the audio; do not rely on automatic captions.
4. Do not invent commands, URLs, files, tools, speakers, or UI labels.
5. Pull quotes must be brief (under 20 words), audio-verified, attributed to Joel Hooks, and timestamped.
6. Exclude credentials, account details, local paths/usernames, private URLs, signed URLs, notifications, or incidental personal data.
7. Treat opinions and live-demo observations as such, not universal facts.
8. Derived prompts must use placeholders, be clearly labeled as inspired by the workshop, and require confirmation for destructive or externally visible actions.

Return dense Markdown with these sections:
# Shard 001 — 00:00:00–00:04:00
## Executive Takeaway
## Dense Timeline
## Concepts and Mental Models
## Visible Demo Evidence
## Architecture and Workflow Patterns
## Tools, Commands, and References
## Pull Quote Candidates
## Copy/Paste AI Prompt Candidates
## Student Exercises and Reflection Questions
## Keyframes to Capture
## Uncertainties and Publication Review
## Machine JSON

The fenced JSON object must contain: shard_id, original_range, summary, timeline, concepts, workflows, demos, resources, quotes, prompts, exercises, keyframes, warnings, unanswered_questions.

End with this exact sentinel on its own line:
END_OF_VIDEO_ANALYSIS loopcraft-agent-workshop shard-001
```

For the text-consult side of this section — the maximum-batch consult prompt and the full agent setup — go back to the [section guide](https://shiny-rosette-m6zy.here.now/index.html), or hear the skeptical version in the [dialogue](https://shiny-rosette-m6zy.here.now/dialogue.html). The full Oracle skill family behind this run is [attached on the index](https://shiny-rosette-m6zy.here.now/index.html#attachments-the-oracle-skill-family), downloadable and installable.

## Original references

- [Independent reasoning and video evidence — worked example](https://shiny-rosette-m6zy.here.now/replay.html)
