Brand guide
The Kawung mark, the palette, the typefaces and the Cak mascot — with the rules that keep them recognisable when someone else applies them.
Titen is quiet infrastructure that helps agents remember, verify and coordinate. The identity should read as precise, dependable, culturally grounded and lightweight — not as a generic glowing AI product. Everything below exists to keep that impression intact when the mark is applied by someone who did not draw it.
The repository SVGs are canonical for the current mark geometry. Where this page and a file disagree, the file wins.
descriptor Collaborative memory for AI agents.
supporting Evidence-grounded context. Safe parallel work.
Use lowercase titen in the wordmark and ordinary title case in prose.
The Kawung mark
The primary mark is a four-petal Kawung construction. The petals are
tenant · subject · agent · run — the four scopes every record is filed under —
meeting at one evidence core. They touch at the centre and do not overlap.
Lead with the Kawung mark for repository, product, avatar and favicon use.
Keep its orientation fixed and preserve the exact petal geometry and tangent centre.
Use one colour, or Ink and Gading with a single Soga accent.
Keep clear space of at least 20% of the mark's width on every side.
Below 24 px, remove the inner core ring and use solid petals. Minimum rendered size is 16 px.
No gradients, bevels, glow, drop shadows, gaps between petals, or overlapping petals.
Do not recreate the mark from a font, and do not substitute a flower icon. Canonical files: the square mark and the README hero.
Wordmark
Lowercase titen in Bricolage Grotesque, weight 600, with the Kawung mark to its left
for the primary horizontal lockup. The descriptor sets in Instrument Sans; small
technical labels set in JetBrains Mono.
Do not stretch, outline, italicise, or typeset the wordmark in all caps.
Cak, the mascot
Cak is a house gecko: small, observant, and present at the edge rather than the centre.
Cak belongs on documentation headers, empty-memory states, page-edge moments, 404 and error illustrations, stickers and community material. Cak never appears inside the primary logo lockup, the avatar or the favicon. No mascot artwork exists in the repository yet; when it is added, reuse the approved watching, climbing, resting or peeking poses and do not invent a new mascot style per surface.
Colour
| Token | Hex | Role |
|---|---|---|
| Ink | #171310 |
primary text, dark surfaces, logo base |
| Soga | #A9552A |
attention, status, links, mascot detail |
| Soga light | #C97A44 |
accent on Ink backgrounds |
| Wedel | #223A57 |
runtime and infrastructure information |
| Gading | #F7F2E9 |
paper background and light mark |
| Warm gray | #8A7F72 |
secondary labels |
| Border | #CFC4B2 |
light-surface boundaries |
Soga and Wedel are distinct semantic accents: attention versus runtime fact. Do not apply both to one element. Use colour sparingly and keep text contrast accessible.
Typography
| Use | Typeface | Weight |
|---|---|---|
| display and wordmark | Bricolage Grotesque | 600–800 |
| body and interface | Instrument Sans | 400–600 |
| code, badges, labels | JetBrains Mono | 400–700 |
| Javanese accent | Noto Sans Javanese | 600 |
For GitHub-hosted SVGs, or anywhere the brand fonts cannot load, fall back to a stable system sans-serif or monospace. Never convert long body text to outlines.
Layout and imagery
Prefer Ink or Gading surfaces, thin rules, clear grids and generous negative space.
One strong idea per composition.
A tiled Kawung pattern may appear at 6–14% opacity on dark hero surfaces only, never behind body text.
Show believable context, provenance, runtime or agent coordination — not humanoid robots, floating node clouds, neon gradients or invented dense dashboards.
Keep README and social graphics honest: status and runtime labels must reflect implemented, verified state.
Badges
Badges are flat, compact and monospace. Neutral Ink labels; Soga for status that needs attention; Wedel for verified runtime information.
Do not publish badges for version, MCP readiness, dependency count, bundle size, coverage or runtime support until the corresponding artifact or measurement exists. A badge is a claim, and the identity is only worth as much as the claims made under it.
Voice
Explain evidence and limits before aspiration.
Distinguish implemented behaviour from target design, every time.
Prefer concrete verbs: observe, verify, compile, hand off, restore.
Avoid "revolutionary", "magical", "human-like memory" and benchmark hype.
Say "agent" for a software identity and "human" for a person. Do not use "user" for both when authority matters.
Changing an asset
Logo geometry, primary colours and the mascot’s role are durable decisions. A change updates docs/BRAND.md, the canonical SVGs, the README application and any generated social assets in one pull request — not one surface at a time.