One production record for every AI tool your studio uses
Studios do not use one generation tool - they use six, plus whatever a client demands next month. Here is how each capture channel wires into Archibal, what evidence each one actually provides, and how unrouted captures get triaged without breaking client boundaries.
In one sentence: Archibal gives every AI tool a studio uses - ComfyUI, Claude, fal, ElevenLabs, Runway, Higgsfield, or anything webhook-capable - one shared production record, with each capture graded by the evidence its channel can honestly provide.
Ask a studio which AI tool they use and you will get a list, not an answer. Comfy for controllable image work. A video model behind fal or Higgsfield. ElevenLabs for voice. Runway for a specific look one director likes. Claude orchestrating half of it from a chat. And next quarter, whatever the new client's brand team has already fallen in love with.
That heterogeneity is normal - and it is exactly why AI production records rot. Each tool keeps its own partial history in its own place, none of them talk, and the person who knows how the final was assembled eventually goes on holiday. The fix is not standardizing on one tool. It is giving every tool the same place to report to.
The channels, and what each one is worth
Archibal's capture layer takes eight roads in, and - this matters more than the count - it grades what each road can honestly prove:
ComfyUI, local or Cloud. The strongest channel. The Archibal node pushes renders straight from the graph, and the workflow itself - models, seed, references, every node - travels inside the file's metadata. That is verifiable capture evidence: a record you can re-open on a Comfy canvas, not a claim about one. Renders arriving this way carry the highest evidence grade.
fal, ElevenLabs, Runway, Higgsfield. Vendor webhooks, each verified the way that vendor supports (cryptographic signatures where offered, verified secrets elsewhere). The tool reports its own metadata over a trusted machine-to-machine channel at generation time. Strong evidence - honestly labeled as vendor-reported rather than independently verifiable.
Claude. The MCP connector turns chat-orchestrated sessions into logged, file-attached records automatically - covered in depth in its own post.
A plain webhook. For anything that can POST a file. Mint a capture URL once, paste it into the tool, done. This is the road for tools Archibal has never heard of - which, in this industry, is always next month's tool.
Orchestration-log import. Render farms and pipeline tools produce logs; importing one records the jobs as studio-logged evidence, matched to files by name or fetched from result URLs.
And for work that predates all of this: uploading a file runs the same scanner every capture gets. Embedded ComfyUI workflows, generator metadata, and signed Content Credentials are recovered from the file itself, so even a folder of last year's renders arrives with as much of its story as the files still carry.
The workspace-webhook reality, and the Inbox
Here is an operational truth vendors do not advertise: you get one webhook per workspace, not per project. So a naive integration dumps every team member's renders into one bucket, and someone becomes the person who sorts it.
Archibal's answer is the Inbox. Captures that arrive without a project route land there, and lineage matching suggests where each one belongs - this render fingerprints as a variant of a file in the Resort project, so the Resort project is suggested. A person confirms. That last part is doctrine, not laziness: nothing is ever auto-filed across client boundaries. A machine guess that lands a confidential render in the wrong client's workspace is not a time-saver, it is an incident. The machine suggests; you confirm; filing forty captures takes a minute.
What the studio gets out of it
Once the tools report to one place, three things change shape:
The library becomes institutional memory. Unlike each tool's own history panel - a Comfy queue, a vendor dashboard, a chat log - which ends at that tool's walls and often at its retention policy, the record is cross-tool and yours. Every render from every tool, searchable by prompt, model, project, and source - with the recipe attached where the channel provided one. "Find the take we almost shipped in March" stops being an archaeology project. (More on the library.)
Attribution stops being a meeting. Which models touched this deliverable is a fact the record holds, per file, with the evidence grade stated. When a model's terms change or a client asks what their campaign was made with, the answer is a query.
Deliveries inherit the whole chain. When work ships, the delivery freezes what the capture layer recorded - models, lineage, evidence grades - into a signed certificate with a public verify link. The record your tools built while you worked is the same record your client's procurement team checks.
None of this asked anyone to change how they create. That is the design constraint the whole capture layer is built around: the best production record is the one nobody has to keep.