Pulse mark
The custom SVG mark combines curved signal paths and stable nodes to represent semantic movement across surfaces while keeping the site clearly public-facing.
Visual Identity
Visual Identity Guide
A public-facing Neurokinetic visual identity guide covering logo and wordmark usage, color tokens, typography notes, dark-card styling, favicon guidance, and route-level visual consistency.
Static brand guidance
A stronger Neurokinetic identity for semantic review surfaces.
The v4.0.0 visual identity guide gives Neurokinetic.com a clearer public identity for the standalone custom theme: pulse logo mark, refined wordmark treatment, consistent color tokens, route-level visual rhythm, dark-card styling notes, and evidence-packet card cohesion.
This page is static reviewer guidance only. It does not execute endpoints, crawl remote sites, validate credentials, train models, or imply control over other domains.
Neurokinetic AISemantic nervous-system interface layer
Logo and wordmark usage
The pulse mark should signal semantic continuity, not clinical authority.
Wordmark
The wordmark uses a compact high-weight treatment for header clarity across phone, tablet, laptop, and desktop widths.
Favicon
The favicon mirrors the SVG logo mark so tabs, bookmarks, and evidence pages share one recognizable visual anchor.
Color tokens
Color is used as semantic signal, not decoration.
Signal cyan
Used for semantic continuity, safe handoffs, and highlight states.
Protocol blue
Used for links, evidence routing, and structured protocol references.
Boundary coral
Used for warnings, card tags, and namespace-boundary emphasis.
Review gold
Used for reviewer focus, callouts, and manual decision prompts.
Deep field
Used for hero, footer, and dark evidence-card surfaces.
Paper field
Used for readable public documentation and long-form reviewer pages.
Route consistency checklist
Each public route should feel related without implying operational control.
Homepage hero
Use the brand lockup, pulse mark, and direct ecosystem role statement to clarify the site lane immediately.
Domain cards
Keep domain cards rhythmically consistent with accent bars, readable headings, strong contrast, and wrapped long names.
Evidence packets
Keep JSON, Markdown, and HTML evidence cards visually grouped and obviously static/manual-review oriented.
Hard boundaries
Continue using public-safe language: no runtime authority, no clinical claims, no certification claim, and no control claim over other domains.
Boundary confirmation
Brand polish does not widen the claim surface.
This visual identity guide is static, public-safe, and reviewer-facing. It does not add runtime AI behavior, model training, live crawling, telemetry loops, agent execution, endpoint execution, credential validation, private-network probing, remote-site writes, webhooks, tunnel opening, screenshot automation, rollback automation, correction automation, safety certification, consciousness claims, biological-equivalence claims, medical/therapy claims, or command-and-control claims over other domains.