Creative workflow experiment
A multi-surface creative workflow prototype
A multi-surface creative-workflow prototype with web, API, gateway, worker, mobile, and document-add-in packages. The repository shows routing and workflow structure; provider availability and output quality are configuration-dependent.
Business ↔ technology bridge · Creative workflow experiment
Explores persistent brand context and provider-neutral orchestration across creative workflows.
This is a portfolio and source interpretation—not a customer, deployment, certification, or outcome claim.
Creative teams move between provider tools while project context, brand constraints, approvals, licensing, and asset lineage fragment.
Keep client, campaign, and brand context outside individual model requests and separate the user workflow from provider routing and background work.
Web, API, gateway, worker, mobile, presentation-add-in, project-context, provider-adapter, export, and selected test surfaces.
Provider availability, asset quality, cost, licensing, and reviewer decisions return to workflow, model choice, and campaign governance.
Source evidence
A multi-surface creative-workflow prototype with web, API, gateway, worker, mobile, and document-add-in packages. The repository shows routing and workflow structure; provider availability and output quality are configuration-dependent.
Repository evidence is not client, deployment, certification, or outcome evidence.
Architecture
Three source boundaries: campaign organisation, medium-specific workflow surfaces, and a CreativeRouter abstraction over operator-configured provider adapters.
Source map only: a layer can represent implemented code, an adapter boundary, or documented design. It does not assert a configured production service.
Agency-native data model: Clients hold brand profiles + visual guidelines + voice rules; Campaigns roll up Phases; Phases roll up Assets. Multi-tenant, multi-seat, role-aware.
The source represents Copy, Image, Video, Music, Voice, 3D and the Deck Builder. The proposed inspectors, prompt templates and export targets vary by medium (PPTX, DOCX, video files, asset packages).
Routes tasks through configured provider adapters and carries project and brand context between workflow steps. Catalogue entries do not prove provider availability or output quality.
The Problem
Why creative AI is fragmented
Agencies juggle Midjourney, Runway, ElevenLabs, Suno, and dozens more — each with its own interface and pricing.
Every tool starts from scratch. No persistent brand voice, visual guidelines, or campaign history across platforms.
Choosing the right AI model for each task requires expertise. Creative teams waste time on tool selection, not creation.
Copy, image, video, and audio live in separate tools. No unified project view, no cross-asset intelligence.
Features
Source surfaces for coordinating creative AI workflows
Source scope only: an entry can describe implemented code, a documented adapter, or a configured workflow. It is not a statement that a production service is active.
01
A routing abstraction selects among configured model adapters using task metadata. Selection quality and provider availability require separate evaluation.
02
Persistent client profiles storing brand voice, visual guidelines, colour palettes, and full campaign history.
03
Hierarchical organisation: Clients > Campaigns > Phases > Assets. Full creative workflow management.
04
Dedicated workspaces for Copy, Image, Video, Music, Voice, 3D, and the Deck Builder (PPTX-native), each designed for its medium, plus Social Media Optimiser, Document Generator (DOCX), and Utilities surfaces.
05
Source paths represent PPTX, DOCX, media, and asset-package exports. Generated files still require licensing, quality, and brand review.
06
The separate venture repository contains provider and model catalogue entries plus explicit development mocks. Catalogue presence does not prove that an adapter is live, licensed, regionally available, or quality-validated.
Seven specialised studios
Generic AI playgrounds force creatives to fight the UI before they fight the work. The Techne source represents purpose-built studios per medium, each with the right inspector, the right prompts, the right export targets. Brand Memory threads through all of them.
Repository surface only: availability, completeness, performance, and operational fitness require separate validation.
STUDIORepresents long-form posts, taglines, ad copy, email sequences, and SEO briefs, with a brand-voice profile, versioning, side-by-side comparison, and tone shifting (formal ↔ punchy). Output quality is not asserted.
STUDIORepresents hero images, social cards, paid-creative variants, and in-app illustrations, with style references tied to brand visual guidelines and multi-aspect output for omnichannel campaigns.
STUDIOProposed video workflow: Shorts, vertical ads, explainers, brand films. Storyboard → shot list → renders → cut. Voice + music tracks are designed to coordinate via the brand profile.
STUDIORepresents soundtrack, jingle, audio-logo, ambience, and export controls in the workflow. Provider licensing and royalty status must be verified outside the generated output.
STUDIORepresents narration, character voices, and multilingual voice-over, with a per-brand voice library, SSML controls for pacing, emphasis, and intonation, and side-by-side multilingual rendering.
STUDIORepresents hero assets, product mockups, and environment shots through text-to-3D and image-to-3D paths with brand-locked materials and lighting.
BUILDERRepresents an outline → slides → pitch flow that draws visuals from Image Studio, copy from Copy Studio, and charts from supplied data, with a deck template tied to the client's brand. PPTX export is represented in source.
Tech Stack
Named technologies identify repository dependencies or adapter surfaces; they do not assert a live integration or deployment.
Source Code
The Techne AI Studio prototype — monorepo with web, API, AI gateway, and workers — is available upon request.
To access the source code, please sign the Non-Disclosure Agreement. This is a standard legal formality.
Need help building production AI systems or deploying intelligent agents? Explore the related consulting services.
Partnership
This prototype is for creative agencies, brand studios, and AI partners looking to unify creative workflows.
From demo to dependable operation. Subscribe for new Physical AI reading.
Unsubscribe anytime. No spam, ever.