Advanced consult, image, and video contracts

Transferable contracts from the published Oracle resource family: premise coverage, bounded escalation, attachment proof, multimodal continuity, and honest completion.

Transferable contracts from the published Oracle resource family: premise coverage, bounded escalation, attachment proof, multimodal continuity, and honest completion.

Keep the original premise stronger than the latest plan

The execution-oriented consult pattern preserves the original request and derives measurable outcomes, constraints, and falsifiable completion checks. Every premise clause maps to a plan step. Exhausting a plan that omitted part of the request is not completion.

This is distinct from a simple independent second opinion. The execution pattern labels a step execute when local evidence and the existing plan suffice, and think when a genuine architectural choice, unresolved ambiguity, or difficult diagnosis requires frontier reasoning. Size or tedium alone does not justify another consult. Batch independent adjacent think decisions. The intended ratio is few think steps, not a consult for every implementation step.

The named consultation points are planning, think decisions, escalation after two distinct failed verification attempts, and a final whole-premise audit. Every consultation asks for the maximum actionable batch: exact file/function/test targets, alternatives, tradeoffs, intended commit boundaries, and enough detail for substantial local execution—not merely “what next?”

Execution is implement → falsifiable verification → scoped commit → advance. Preserve unrelated dirty work. Mechanical, evidence-backed plan corrections can be local; new decisions become explicit think steps. An escalation includes the actual failing commands, outputs, receipts, and attempted diff. A step that still fails after its escalation is a genuine block rather than permission to consult indefinitely.

The final independent audit compares the actual result with the original premise. PASS requires final local proof against the same state. FAIL returns the complete remediation set, not just the first gap. Out-of-scope nice-to-haves do not silently expand the task. Missing authorization for credentials, destructive action, or broader scope is a stop boundary.

Rich context and compact evidence are alternatives, not dogmas

The Packx reference favors rich code context for broad architecture work, with a roughly 900k-token target in the demonstrated browser-consult setup. The boundary audit favors the smallest useful evidence packet. These answer different problems: a whole-system decision may need the complete relevant source, while a local decision should not carry an entire stale conversation.

When raw material is too large or unsafe, supply compact evidence explicitly: prior-state decisions, trustworthy receipts, failure observations, intentionally omitted sources, and a goal-coverage map. Do not replace raw evidence with an unlabelled confident summary. Avoid bundling credentials or private instructions simply because a large attachment is technically supported.

Video analysis: attachment proof before expensive extraction

Use the attached-video path itself as the readiness test. A signed-in browser UI is required, but a text-only cookie error does not prove that the video upload path is broken. Conversely, a text response is not evidence that a model watched a video.

A cheap probe asks the model to identify a concrete visible or audible event and end with an exact sentinel. Save the complete response and verify the sentinel before running long analyses. Use short clips directly when that is sufficient. For long recordings, preserve source-native segments, explicit segment boundaries, source metadata, and the relation between local segment time and recording time. Record unsupported claims rather than filling gaps from a transcript.

For each segment, request a dense timeline, concept inventory, demonstrations and screen activity, Q&A with answer status, links/tools/commands/resources, keyframes worth checking, exercises, and uncertainties. Run an omissions pass against the same evidence, reconcile cross-segment overlaps, and retain partial or unanswered questions as such. A successful parse is not a complete account.

The resource family distinguishes routine multimodal analysis from explicitly requested deeper reasoning. Model-selector labels and product limits must be verified against the installed version; ChatGPT’s Instant/Pro Extended labels are not Gemini video readiness signals.

When a single shard fails while neighboring shards succeed, classify the input separately from the transport. The demonstrated remedy was re-encoding the failing shard, rerunning the cheap proof, then preserving the working media recipe. That is an empirical fix, not proof of the underlying cause. Keep an unresolved run from being duplicated just because a local wait returned. After successful artifact capture, close only the browser tab owned by that run.

For research batches, filter using actual source metadata rather than titles or remembered dates; exclude topic-name collisions and irrelevant material. Keep a durable queue with source identity, title, author, duration, and public URL. Make prompts specific to the research topic. Batching, cadence, and quota boundaries must be explicit, not hidden retries.

Image generation: requested count is not captured count

The Codex and Antigravity mockup recipes use one built-in image call per asset. The Oracle/ChatGPT image resource instead requests a clearly numbered batch through one browser call. Preserve that distinction; it is tool-specific advice, not a universal rule.

A batch contract makes the number and output granularity explicit:

Create exactly N separate images. Each is its own standalone image file.
Image 1: <complete scene description>.
Image 2: <complete scene description>.
...
Output all N as N separate images. No text, no captions, no typography.

Count returned files and inspect each one to identify its intended scene; return order need not match prompt order. A short capture can mean later images were still rendering, not that the model refused the batch. Inspect the existing conversation before requesting replacements. A recovery probe that does not generate again is:

Do not generate or create any images in this response. Reply with only the digit count of images above.

Deduplicate recovered files by checksum. A failure before generation starts differs from a timeout while generation is active; only the former supports a simple immediate retry without duplication risk. Use returned artifact locations rather than constructing paths from a slug that may have been truncated.

For long sets, maintain a queue of complete self-contained scene descriptions and per-call requested/received counts. Sequential execution, explicit pacing, and quota-aware stopping make interrupted work resumable. Character consistency needs both the reference image and a repeated textual description; verify the face, clothing, and style rather than assuming the attachment enforced them.

The browser image workflow uses its image-appropriate mode, while non-image deep consultations use extended reasoning. This is a distinction between tasks, not permission to carry one model’s mode labels into another product. Refusals are prompt outcomes, not infrastructure errors: report them, change the request to an original permitted concept where appropriate, and do not retry-loop the same refused prompt.

Generated video: continuous story, separately verified clips

The published generation example uses short clips rather than assuming that asking for a minute yields a minute. Its demonstrated output was approximately ten seconds per clip, 1280×720 H.264 video with AAC audio. Those are observed product limits, not guaranteed current limits. Longer stories use multiple clips, continuity references, and a local stitch.

Write every beat before starting. Group images into two or three sequential visual references per clip. Where supported, put the prior clip before the next images as a reference for camera language, grade, and tone. Generate sequentially, persist each returned artifact, inspect its duration/codec/dimensions/size, and only then use it as the next clip’s reference.

A stitch-safe visual prompt includes:

Use the attached images as sequential visual references. Generate a full 10 second cinematic video: <beat-by-beat action>.

Audio constraints: no music, no score, no singing, no lyrics, no dialogue, no voiceover, no spoken words, no mouth-synced speech. Prefer a silent clip; if audio is unavoidable, use only subtle non-musical ambient sound.

No text, no captions, no readable words.

The silent-first policy prevents repeated dialogue or discontinuous generated music from ruining the edit. Strip unwanted clip audio rather than treating a technically successful speech track as usable. Add narration, music, and sound design after picture is locked unless preserving the generated audio was explicitly requested.

Use real media inspection, not a download receipt:

ffprobe -v error -show_entries format=duration,size:stream=codec_type,codec_name,width,height,duration -of json clip.mp4
ffmpeg -hide_banner -y -f concat -safe 0 -i concat.txt -c copy story.mp4
ffmpeg -hide_banner -y -i story.mp4 -vf 'fps=1/5,scale=320:-1,tile=3x4' -frames:v 1 contact-sheet.jpg

A contact sheet must actually be inspected. Matching codecs and dimensions support stream-copy stitching; a paced edit requires re-encoding and checking audio timing. Report per-clip and final counts, durations, references, and any continuity seams.

A generated-video run can finish with a text refusal and no video. That is not a reason to wait indefinitely. Read the visible response and distinguish refusal, quota, unsubmitted prompt, DOM drift, transfer limit, and real generation-in-progress. A prompt still sitting in the composer without a submitted user turn is a send failure, not a slow model. Never silently truncate a video to satisfy a transfer limit.

If identity-continuity wording is refused, do not keep submitting the same request. Reframe only toward permitted fictional material; if necessary remove the prior-video identity reference and use loose storyboard references, non-identifiable framing, objects, setting, and grade for continuity. Record the change because it affects the final story. A cosmetic fictional label alone was not a reliable remedy in the example.

Scheduling is an explicit alternative

A schedule is justified only by an agreed recurring action, owner, stop condition, and durable status. The resource family includes a follow-up scheduling tool; the broader software-factory discussion cautions that scheduled curation and review can become noise. Do not turn the availability of a scheduler into a recommendation to schedule everything.

Source references