Usage log per piece
Feature, model, summarized prompt, chosen variation, expected credential and who approved it, filled in from the generation history.
Deliverable: registro_uso_ia.csvOcto for generative AI in Illustrator
Illustrator generates icons, patterns and scenes from text, recolors artwork, fills in bleed and turns sketches into vectors, with models from Adobe and partners. Octo generates nothing by script: it organizes the request queue and the usage log, checks color against the palette, inspects the generated vector and reads the Content Credentials before delivery. Generating, choosing, approving and disclosing stay with people.
Six possible deliverables, drawn from the assessment. All of them happen before or after generation, none calls a generative feature, none changes Content Credentials, and all go to review by whoever is accountable for the piece.
Feature, model, summarized prompt, chosen variation, expected credential and who approved it, filled in from the generation history.
Deliverable: registro_uso_ia.csvApproved colors, forbidden colors and ΔE tolerance, approved by the brand owner and read by the check.
Deliverable: versioned paleta_marca.jsonEach color in the recolored SVG, the nearest brand color and the ΔE. An "almost the same" color becomes a number, not a debate.
Deliverable: conferir_paleta.py and checkIcon requests in a queue worked by a person, one at a time; a request with someone else's brand or character is blocked.
Deliverable: pedidos_icones.csvAnchor points, colors, size, hidden raster images and live text in each generated SVG, against the library's limits.
Deliverable: inspecionar_svg_gerado.pyc2patool in read mode on every delivery file, cross-checked with the log. Nothing is signed, removed or rewritten.
Deliverable: conferir_credenciais.sh and reportThe same Octo cycle, applied to generative AI in Illustrator. Each arm has a narrow role; generating, choosing, approving and disclosing are people's decisions.
Which generative features, on which version, with which models, and what each contract says about AI.
Brand palette, request queue and usage log in versioned files.
Terms of use read, MCP server key kept out of the repository, personal data kept out of prompts.
Automation before and after generation; generating and choosing stay with the designer.
Palette, vector inspection and credential reading, with the source of each rule noted.
Color against palette, anchor points against limit, credential against log. "Looks on-brand" is not a check.
Delivery folder with the checks; delivery and disclosure approved by people.
Version, feature, model and who approved each piece.
Octo does not generate artwork by script, remove credentials or disclose AI use on anyone's behalf. It measures, logs and points out what diverges.
The documented feature for each task and what gets checked afterward, with each one's limit.
| Task | Feature | Check and limit |
|---|---|---|
| Color variations of the same artwork | Generative Recolor | Up to 5 guide colors; ΔE against the palette |
| Icon, scene or subject from text | Text to Vector Graphic | Up to 4 variations (1 with a partner); inspect anchor points and colors |
| Pattern for a background or print | Text to Pattern | Comes in as a swatch; color against palette |
| Fill in the bleed | Generative Expand (bleed) | 3 variations and "Combine"; the printer checks the proof |
| Sketch that becomes an outline | Concept to Vector | Up to 8 presets; optional raster output, flagged by the inspection |
| Text-based adjustment to generated artwork | Prompt to Edit | Only artwork from Text to Vector Graphic or Turntable |
| Know what was made with AI | Generation history and log | Deleting from history is permanent |
| Many pieces per request in batch | None by script | Terms forbid unauthorized automation |
Three steps. Each one only makes sense after the previous one has shown results on your team.
A proposal, not a promise
Octo builds the usage log from the generation history of pieces in production, without changing how you generate.
Palette in a file, color checked, vector inspected before it enters the library.
Credentials read and cross-checked with the log on every delivery, with the disclosure made by a person.
Each point below has a source published by the vendor, the project or the responsible body. The sources are in the next section.
8
points with a published source, each with its reference shown alongside.
--info and a tree with --tree; it reads SVG, PNG, JPEG and PDF.Source: c2patool documentation (Content Authenticity Initiative)Octo prepares everything, but it does not sign. The document of record stays with whoever is accountable for it.
Surveys, calculates, organizes and generates the documents: files, artboards, proofs and reports.
Deliverable: material ready to checkThe client or the art director checks what Octo delivered before approving. If something doesn't add up, it goes back to Octo with the correction.
Step: review by the approverOcto does not approve the artwork. Artwork carries no legal signature: approval of the artwork and the proof stays with the client or the art director.
Approval: client or art directorIllustrator Help pages on generative AI, partner models, AI Assistant and the MCP server, credits pages, Adobe's generative AI user guidelines and the c2patool documentation, consulted on Oct 31, 2026.
The assessment starts with the usage log of a delivery that has already gone out and a color check of a recolored piece. You get what was made with AI, what diverged from the palette and the questions only your team can answer, and you decide with that in hand.