Does this reproduce a reference identity design?

The workflow develops a new fictional profile artifact, brief and visual system. It excludes copied platform branding, watermarks, protected identities and unlicensed reference expression. Actual results and source permissions still need inspection; a prompt does not establish rights clearance.

How are unknown profile facts or permissions handled?

They remain visibly pending in the source ledger, separate from creative assumptions. The agent must not invent a qualification, owner, evidence item or permission and present it as approved. Codes and labels remain clearly nonfunctional.

Three distinct 16:9 WebP review images of the concept, not issued credentials or packaging production files. The paid FAL wrapper first returns three PNG variants at 1536×864; exact labels/disclaimers, nonfunctional-code review and WebP conversion are later steps. FAL_KEY and Node.js 20+ are required.

Industrial Identity Artifact

Previews from the publisher

Present an approved fictional professional profile as a tactile industrial archive object. Industrial Identity Artifact translates selected skills, tools, projects and evidence into three visual directions, with labels and codes clearly nonfunctional. It is a communication concept for review, not an actual credential, access document or manufactured object.

What you get

Three distinct 16:9 review previews of an industrial archive-style identity artifact, guided by the approved fictional profile and intended use. Material, packaging, palette and display choices support the profile story rather than inventing qualifications or evidence.
A source ledger keeping supplied information, assumptions, rights/privacy requirements and unresolved questions separate. The production brief specifies composition, continuity, exact exclusions, barcode/identity/disclaimer rules and clean zones for labels added later.
Clearly nonfunctional labels and codes, with exact approved wording applied through a deterministic overlay. Functional annotation icons use labelled inline SVG; source-platform branding, watermarks, protected identities and unlicensed assets are excluded.
Exactly three final 16:9 WebP previews with open issues recorded. The included FAL script requests three high-quality 1536×864 PNG variants from one shared prompt; it does not typeset exact codes, enforce nonfunctionality or convert to WebP. Those checks and final formatting remain part of production.
Workflow instructions, an image-brief contract, an SVG icon reference and a persistent-request generation wrapper. The delivery is raster concept artwork, not print-production packaging files, a functioning barcode system or an evidence-verification service.

Before you choose

Read the object as someone unfamiliar with the brief: can they distinguish the fictional profile, supported evidence and decorative archive treatment? Revise any label or code that could suggest a real qualification, access right or verification the concept does not provide.

Good fit

A consultant wants an evidence-bounded client visual around an explicitly fictional profile or professional concept.
An analyst needs to organize approved skills, tools, projects and evidence into a tangible visual artifact.
An executive or review team wants to discuss the concept’s assumptions, risks and intended actions before using it.

Not for

Inventing professional facts, measurements, citations, owners, permissions or guarantees.
Reusing source branding, watermarks, protected identities or unlicensed assets, or making decorative codes appear operational.
Replacing subject, rights, privacy, accessibility or final human review, or treating an illustration as an issued credential.

How to use

You say

/industrial-identity-artifact Turn the fictional professional profile I provide into a tactile industrial archive object with clearly nonfunctional labels and codes.

Provide the approved fictional profile, intended use and the skills, tools, projects and evidence that may appear. Define material/packaging, palette, ratio, display constraints, privacy/identity/barcode/trademark rules and disclaimers. Identify the audience and final review owner.
Build a ledger of supplied facts, creative assumptions, rights and pending questions. Review a fresh English brief that makes the industrial-object metaphor clear while keeping labels/codes explicitly nonfunctional. Reserve clean copy zones and prohibit unsupported qualifications or implied permissions before payment.
Use Node.js 20 or newer, a FAL account and FAL_KEY in the environment. One paid task requests three 1536×864 high-quality PNG variants. The dimensions are fixed; a requested alternative ratio or exact functional code behavior is not implemented by the wrapper.
Keep provider-task.json and the approved prompt. With a saved request ID and unchanged prompt/output directory, resume that request rather than automatically replacing a recorded failure. Persistence happens after the submission response, so inspect provider history before retrying an uncertain response or failed write. Preserve approved images separately because resumed downloads can overwrite matching paths.
Inspect all three directions for profile meaning, material/display coherence, unwanted identity/branding and any code that could be mistaken for functional access or verification. Check actual ratio, visual distinctness and the source-led evidence boundaries. Three returned images do not verify facts, permissions or code behavior.
Add exact labels, explanatory notes and disclaimers in a deterministic layout tool, then convert and verify the three final WebP previews. Record unresolved issues and route the artifact for subject, rights, privacy, accessibility and delivery review. Do not present it as a real identity credential or a manufactured product.

Requirements and costs

You bring: Approved fictional professional profile and intended use · Skills, tools, projects, and evidence that may be visualized · Material, packaging, palette, ratio, and display constraints · Privacy, identity, barcode, trademark, and disclaimer requirements
Dependencies: FAL account — required · Node.js 20 or newer — required
Outside costs: Image generation uses one paid FAL task for three directions. Review the brief before submission; a failed task is never retried automatically.
Publisher testing: v1.0.0 — Claude Code / Claude Desktop / Cowork / Codex / ChatGPT