Skip to main content
THE AESTHETIC CONSULTANTAI Startup Brand Sprint · 72h

01 · WHAT YOU ACTUALLY RECEIVE · FICTIONAL CUSTOMER PACKAGE

Inspect the handoff, not just the marketing.

A complete eleven-file NOVALEDGER fictional sample package shows how strategy, brand codes, generator rules and human QA are handed over. No client data, outcomes or invented proof.

Exactly 11 filesUS English deliveryFictional method proof

Fictional package · No client or performance results · Direction is not full production.

NOVALEDGER fictional website hero direction
Existing NOVALEDGER asset, reused unchanged.

02 · PACKAGE MAP

What you actually receive

The public ZIP contains the exact customer-facing structure below - no build scripts, debug files, private notes or internal QA scratchpads.

01_READ_ME_FIRST.txt

Start here: scope, status and file map.

Human-readable

02_MINI_BRAND_GUIDE.pdf

Strategy, Five Brand Codes and governance.

Human-readable

03_COLOR_TOKENS.json

Valid functional color roles and usage notes.

Machine-readable

04_COLOR_PALETTE.png

Existing NOVALEDGER palette board.

Visual asset

05_LOGO_DIRECTION.png

Existing strategic logo-direction board.

Visual asset

06_HERO_COPY.txt

Headline, subline, CTA and claim guard.

Human-readable

07_IMAGE_PROMPTS_CHATGPT.txt

Six curated ChatGPT image prompts with explicit locks and variation axes.

AI-tool-ready

08_IMAGE_PROMPTS_MIDJOURNEY.txt

Six curated Midjourney prompts with current parameter syntax and explicit controls.

AI-tool-ready

09_SOCIAL_POST_IDEAS.txt

Six launch and content directions.

Human-readable

10_DO_DONT_GUIDE.pdf

Visual, copy and AI-production boundaries.

Human-readable

11_QA_SUMMARY.txt

Reviewed items, open work and proof status.

Governance

The downloadable package is in US English because that is the defined TAC delivery language.

03 · FIVE BRAND CODES

Strategy becomes five usable brand codes.

The files are connected by one system: meaning, recognition, behavior, generation and governance.

01

Meaning Code

Trust is earned through visible evidence and bounded uncertainty.

02

Recognition Code

Obsidian architecture, measured cyan provenance and functional gold approval.

03

Behavior Code

Evidence gathered, review required, output ready and human approved.

04

Generation Code

Prompt rules preserve the dominant subject, color roles, material world and no-go boundaries.

05

Governance Code

Experimental, Direction, Selected, Approved and Rejected remain visibly distinct states.

04 · HUMAN-READABLE HANDOFF

Readable without specialist tools.

The guide, copy, social ideas, boundaries and QA summary explain the direction in language a founder can review directly.

HUMAN-READABLE

Files a founder can read directly

  • Mini Brand Guide
  • Hero Copy
  • Social Ideas
  • Do / Don’t Guide
  • QA Summary

VISIBLE BOUNDARIES

What the handoff does not pretend to replace

  • Final vector identity and trademark review
  • Production website or application UI
  • Verified client or market outcomes
  • Human approval and implementation QA

05 · STRUCTURED / TOOL-READY HANDOFF

Different files carry different levels of structure.

Color Tokens are machine-readable JSON. Prompt files are generator-ready natural-language instructions for controlled reuse, not a formal executable schema, runtime generator or enterprise brand API.

STRUCTURED HANDOFF

Reusable without overstating automation

  • Machine-readable Color Tokens
  • Curated ChatGPT prompt file
  • Curated Midjourney prompt file
  • Asset and approval status
  • Human review rules

TOKEN EXCERPT

Functional roles, not decorative swatches

{
  "cta": {"value": "#D8C173", "role": "Human approval"},
  "signal": {"value": "#4AC7D9", "role": "Evidence"}
}

06 · PROMPT DIRECTION SYSTEM

Six curated directions, not six paraphrases.

Each prompt changes at least three adaptive axes while keeping the same hard constraints and brand locks. The set is manually reviewed; it is not presented as an automatic infinite-output generator.

01 · Hero

Evidence Architecture

16:9 · Trust and provenance with headline-safe space.

Dominant subject changes; approval meaning stays stable.
02 · Product

Human Approval State

4:3 · Evidence, warning and approval as distinct states.

Direction demonstration, not a finished UI.
03 · Pitch

Explainability Infrastructure

16:9 · Stable architecture supporting proof points.

No fake charts or growth figures.
04 · Social

Signal to Approval

4:5 · Mobile-first vertical provenance narrative.

Strong hook space, no hype metaphors.
05 · Warning

Review Required

4:3 · Bounded uncertainty without panic.

Approval intentionally withheld.
06 · Detail

Recognition Macro

1:1 · Material, signal and approval junction.

No logo, letters or numbers.

The prompt is not the brand. It executes the brand rules.

07 · QA & REMAINING WORK

Reviewed with explicit remaining work.

No unqualified PASS wall. Every status names its basis or boundary.

StrategyReviewed

Core truth, trust need and visual tension are consistent inside the fictional sample.

Prompt systemDemonstrated

Six genuinely different contexts preserve the same non-negotiable codes.

Client evidenceNot claimed

No real client, testimonial, performance or market-outcome claim.

LogoSeparate production

Vector finalization and separate trademark review remain required.

Website / UISeparate production

Direction modules do not represent a finished build.

Human approvalRequired

Generation never replaces selection, risk review or final approval.

08 · DOWNLOAD & INSPECT

Open the guide. Download the package. Inspect every file.

The ZIP is intentionally customer-clean: eleven documented files only.

SHA-256 and internal build records remain in the release package, not inside the customer sample ZIP.

NOVALEDGER fictional color-role board