Documents are rectangular and readable.
Start with stacked rectangles, even spacing, and horizontal line groupings before adding any decorative treatment.
Text analysis identity
A structured product language for inspection and evidence.
ScriptLens extends its document-and-lens mark into a calm visual system for transcript review, pattern detection, script comparison, clustering, and anomaly analysis. The visual grammar stays flat, geometric, and evidence-led.
Document rectangles
Inspection rings
Node clusters
Red detection lines
The logo defines the system.
The document, horizontal text lines, red highlight stroke, and blue magnifying handle become the core building blocks for every illustration and UI accent.
Document frame
Text structure
Lens focus
Detection line
Knowledge nodes
Foundation
Six rules keep the system consistent.
Every asset should read as structured analysis, not as a startup vignette or a generic corporate illustration. The composition should feel precise, quiet, and useful.
Inspection uses rings, not drama.
Focus is shown with lens circles, ring overlays, and measured outlines instead of exaggerated motion or oversized shapes.
Red marks evidence, not branding.
Use the red accent only for flagged lines, anomaly nodes, or comparison differences so it keeps semantic weight.
Characters stay out of the way.
Scenes should mainly use documents, panels, lines, rings, and nodes. If a figure appears, keep it minimal and still.
Composition stays gridded.
Use aligned cards, clear gutters, and balanced whitespace. Avoid floating startup scenes or decorative chaos.
UI and illustration share shapes.
The same document blocks, lines, rounded frames, and highlight strokes should appear in marketing, product, and support surfaces.
Palette
Neutral structure with one detection accent.
The palette is intentionally restrained. Blue and gray carry structure, navy carries text and outlines, and red only appears when the system wants the user to notice evidence.
Off white
#F4F1EB
Navy ink
#24354D
Muted blue
#8FA5BF
Gray surface
#EEF2F5
Detection red
#D45A5C
Scene library
Six reusable scenes cover the product narrative.
These scenes can be used in onboarding, empty states, product marketing, documentation, and UI explainer modules without breaking the identity system.
Hero or first-run state for core transcript review.
Use when explaining flagged lines or repeated structures.
Use for side-by-side transcript and revision views.
Use for grouped findings, themes, or evidence maps.
Use for summaries, takeaways, and downstream actions.
Use when the product calls out irregular phrasing or suspicious spikes.
UI language
Product components should feel like analysis instruments.
Use rounded panels, evidence rows, restrained chips, and document-derived modules. The UI should support judgment instead of trying to entertain the user.
Mixed / possibly assisted
Verdict cards should foreground the score, the language of confidence, and the evidence summary before any secondary details.
Repeated sentence cadence
Highlighted transition cluster
Low lexical variation
Transcript evidence
Source quality
Hosted transcript recovery
Knowledge cluster
Grouped writing signals
Motion motifs
Animations should reinforce inspection, not add spectacle.
Keep motion short, quiet, and utilitarian. The product should feel active enough to explain what it is doing without turning analysis into theater.
A narrow scan passes across text or document rows.
Inspection rings grow once, then settle.
Flagged strokes should animate as a short reveal.
Cluster links can draw in to show grouping.
Panels can stack or fan slightly to imply a change of state.
Usage rules
Keep the product credible.
This system should make ScriptLens feel like a thoughtful analysis tool. It should not slide into noisy startup marketing or speculative AI imagery.
Use documents, lines, rings, and nodes.
Those motifs are enough to cover inspection, review, comparison, and synthesis without inventing a second visual language.
Skip dramatic blobs, neon gradients, or social scenes.
The system should feel editorial and structured. Avoid hype imagery, chaotic shapes, or highly emotive characters.
Let red keep semantic meaning.
If red appears everywhere, it stops functioning as evidence. Use it only when the product needs to call out a pattern or anomaly.