Logo & Mark
- Set the wordmark in Satoshi, 600 weight, API in signal green.
- Keep clearspace of one mark-height on all sides.
- Use on void or reversed on bone. Nothing else.
- Recolor the mark or gradient the green.
- Letterspace, condense, or re-weight the wordmark.
- Reference the closed-source server internals in public marks.
Color
- Default to void and bone. Green marks action and live state.
- Hold AA contrast on all text against the void.
- Use gold only for seals or internal marks.
- Flood backgrounds with green.
- Introduce new hues. The palette is closed.
- Use crimson (that is Meridian) or blush (that is Snow).
Typography
Voice & Tone
Exact, not vague.
Name the endpoint, the scope, the limit. Precision is the product.
Terse, not chatty.
Say it once, plainly. No filler, no hype, no adjectives the spec cannot back.
Institutional, not solo.
Kinetic is infrastructure, not a founder. We describe the machine, not the person.
Opaque by design.
The server is the moat. We document the contract, never the internals.
- Lead with the endpoint, the scope, or the integration step.
- Quote real request and response shapes.
- Keep claims provable against the spec.
- Expose closed-source server internals or the brain seam in public copy.
- Overpromise capability the spec does not back.
- Use startup growth language or urgency.
Elements
Hairline squares
Single-weight square frames, no fills. Structure is shown, never decorated.
The prompt
Endpoints, keys, and status set in Geist Mono. The record looks like a console.
Signal nodes
A green node marks a live or active state. Used sparingly, never as fill.
Strict measure
Content holds a 1140px measure. Generous void around dense blocks.
Two weights
Bone 2px opens a document, green 2px marks a section. Hairlines split rows.
Show the contract
If it does not clarify the protocol, cut it. The brand earns trust by being exact.
House Guides
API Reference & Docs
PublicThe public developer surface: endpoints, scopes, the OpenAPI explorer, and SDK quickstarts.
Open guide →Marketing Site
PublicThe product front door: positioning, plans, and the path from sandbox to operator.
Open guide →Spec & Conformance
Standing upThe canonical contract: resource model, scope map, idempotency rules, and the conformance standard.
In preparation →Brand & Voice Standard
Standing upThe writing system: how to name endpoints, describe capability, and hold the line on opacity.
In preparation →