01_READ_ME_FIRST.txt
Start here: scope, status and file map.
01 · WHAT YOU ACTUALLY RECEIVE · FICTIONAL CUSTOMER PACKAGE
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.
Fictional package · No client or performance results · Direction is not full production.

02 · PACKAGE MAP
The public ZIP contains the exact customer-facing structure below - no build scripts, debug files, private notes or internal QA scratchpads.
Start here: scope, status and file map.
Strategy, Five Brand Codes and governance.
Valid functional color roles and usage notes.
Existing NOVALEDGER palette board.
Existing strategic logo-direction board.
Headline, subline, CTA and claim guard.
Six curated ChatGPT image prompts with explicit locks and variation axes.
Six curated Midjourney prompts with current parameter syntax and explicit controls.
Six launch and content directions.
Visual, copy and AI-production boundaries.
Reviewed items, open work and proof status.
The downloadable package is in US English because that is the defined TAC delivery language.
03 · FIVE BRAND CODES
The files are connected by one system: meaning, recognition, behavior, generation and governance.
Trust is earned through visible evidence and bounded uncertainty.
Obsidian architecture, measured cyan provenance and functional gold approval.
Evidence gathered, review required, output ready and human approved.
Prompt rules preserve the dominant subject, color roles, material world and no-go boundaries.
Experimental, Direction, Selected, Approved and Rejected remain visibly distinct states.
04 · HUMAN-READABLE HANDOFF
The guide, copy, social ideas, boundaries and QA summary explain the direction in language a founder can review directly.
HUMAN-READABLE
VISIBLE BOUNDARIES
05 · STRUCTURED / TOOL-READY HANDOFF
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
TOKEN EXCERPT
{
"cta": {"value": "#D8C173", "role": "Human approval"},
"signal": {"value": "#4AC7D9", "role": "Evidence"}
}06 · PROMPT DIRECTION SYSTEM
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.
16:9 · Trust and provenance with headline-safe space.
Dominant subject changes; approval meaning stays stable.4:3 · Evidence, warning and approval as distinct states.
Direction demonstration, not a finished UI.16:9 · Stable architecture supporting proof points.
No fake charts or growth figures.4:5 · Mobile-first vertical provenance narrative.
Strong hook space, no hype metaphors.4:3 · Bounded uncertainty without panic.
Approval intentionally withheld.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
No unqualified PASS wall. Every status names its basis or boundary.
Core truth, trust need and visual tension are consistent inside the fictional sample.
Six genuinely different contexts preserve the same non-negotiable codes.
No real client, testimonial, performance or market-outcome claim.
Vector finalization and separate trademark review remain required.
Direction modules do not represent a finished build.
Generation never replaces selection, risk review or final approval.
08 · DOWNLOAD & INSPECT
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.
