Signals Corps brand book
Logos, color, type, imagery, and language for anyone who builds with the Signals Corps brand: our team, our partners, and the AI agents that write and design with us.
Who we are
Signals Corps helps organizations adopt AI agents with visibility, governance, and control. We give IT and Security the means to reduce agent risk, so the rest of the business can keep using AI.
Let every team use AI. Keep agent risk under control.
Engineers, platform teams, and employees using Claude Code, Codex, Cursor, Windsurf, and whatever comes next. They need to hear that their work keeps moving and that any interruption comes with a reason.
They need to see what agents are doing, decide what is allowed, and show what happened. They need to hear that they stay in control, with evidence they can defend.
Use these as written. To shorten, drop whole sentences.
Signals Corps gives IT and Security control over the AI agents their teams use.
Give IT and Security the visibility, governance, and control to reduce agent risk before release, during action, and after an incident.
Signals Corps helps organizations adopt AI agents with visibility, governance, and control. Supply Chain Security keeps unsafe agent components out of production. Runtime Protection stops high-risk actions before they execute. Hunt searches AI activity so teams can investigate incidents faster. Together they let every team use AI while IT and Security keep agent risk under control.
Signals Corps is a dogesec company (do only good everyday security).
The platform
An agent can create risk before a team trusts a component, while it acts, and after the activity is logged. Each product owns one moment and one color. They always appear in this order.
Know what your agents trust. Before they use it.
Inspect skills, MCP servers, agent instructions, plugins, and packages across repositories, pull requests, pipelines, and local workflows.
Control risky agent actions. Before they execute.
Evaluate tool calls, shell commands, file access, and network activity in the flow of work, then allow, warn, request approval, or block.
Find the signal in your AI logs. Follow every action.
Search agent sessions, tool calls, policy decisions, and logs from agents, gateways, and model providers to reconstruct incidents and investigate suspicious behavior.
Logo
The logo is a sonar mark and the Signals Corps wordmark, both on the same lime plaque with an ink outline and a hard ink shadow. Sharing the plaque is what makes them one family. Every file has outlined lettering, so none needs fonts installed.
The plaque carries its own background, so the logo works on canvas, paper, blue, and ink. On ink the shadow disappears into the background, which is expected.
CanvasPaperBlueInkRecolor the plaque or the rings
Stretch or squash it
Rotate it
Add a soft shadow or effects
Put the glyph on another fill
Imagery and meaning
Signals Corps listens for what agents are doing and turns it into something IT and Security can act on. The visual language carries that idea from the mark to the page.
1
2
3
The thing being observed: an agent, a session, a single action.
A sonar ping spreading outward, the way coverage reaches the three moments of risk: before trust, while agents act, and after activity.
The rings never close into a wall. We watch and control without fencing teams in.
A ping goes out, meets something, and comes back as a signal you can act on. That is the job.
A label stamped on a piece of kit: high visibility and impossible to mistake. Lime is reserved for the brand, so seeing it means Signals Corps.
Solid offsets with no blur make components feel like objects with clear edges, which suits a product built on clear decisions and evidence you can point to. Pressing a control removes its shadow.
The mark at page scale, as if the ping from the logo is still traveling. Faint, decorative, tucked into the top corner. Text never crosses them.
Yellow for inspection before trust, sky for live activity, soft pink for investigation afterwards. Blue holds the platform that connects them.
Recreated product UI in ink-outlined windows: pull request checks, blocked commands, Hunt timelines. Invented data is always labeled "Illustrative data".
Photography is for real people, such as blog authors: circular crop, ink outline, small hard shadow. No hooded hackers, padlocks, glowing shields, or binary rain.
Color
Repeat a color only when the repetition means something: the same product, state, or category. Never cycle colors across unrelated cards for decoration. Select a swatch to copy its hex value.
Typography
Manrope carries almost everything, from 800-weight headlines with tight tracking to body copy. DM Mono is only for genuinely technical content. Space Grotesk Bold is reserved for the wordmark.
letter-spacing: -0.058em; line-height: 1Stop high-risk actions. Before they execute.
letter-spacing: 0.08emWorks with your agent stack
line-height: 1.65; about 65 charactersApply the right control through native hooks, MCP, extensions, repositories, pipelines, and gateways without forcing teams onto one tool.
code, commands, paths, timestamps, log dataletter-spacing: -0.045emSignals Corps
Shape and components
Solid ink outlines, modest corner radii, and hard offset shadows. Interactive elements move toward their shadow on hover and lose it when pressed. Try the buttons.
Solid fill, ink outline, ink shadow, 800-weight label. Hover turns yellow. Focus is a pink ring. No pill shapes for text.
Classification and status labels use a 7px rectangle. Circles are only for dots, avatars, and sequence markers.
Voice and language
We write for builders and for IT and Security at the same time. Security is how an organization says yes to agents with confidence, so we never use it as a reason to slow down or stop.
"Stop high-risk actions before they execute" comes before "a hook evaluates each tool call".
Name the control point, evidence, or workflow once the reader knows what it protects.
A user, a risk, an action, or an outcome. Verify, control, investigate, stop, approve, reconstruct.
State what a check covers and what evidence it rests on. "Browser results are an advisory preview" is on-brand.
Direct verbs, plain words. Cut anything that does not change the meaning.
Specific and practical. We never scold the reader or sell with fear.
Two short sentences. A lead that states the benefit, then an accent in a contrasting color that adds timing or proof.
Let every team use AI. Keep agent risk under control.
Know what your agents trust. Before they use it.
Find the signal in your AI logs. Follow every action.
| Use | Avoid |
|---|---|
| Signals Corps | Signal Corps, SignalsCorps, SC |
| Supply Chain Security, then Supply Chain | SCS, supply-chain module |
| Runtime Protection, then Runtime | RTP, runtime guard |
| Hunt | Signals Hunt |
| the Signals Corps platform | the suite, the solution |
| AI agents, then agents | bots |
Organization, behavior, analyze, color, center, catalog, program.
Headings, labels, and buttons. Buttons start with a verb.
Use commas, colons, parentheses, or full stops.
Invented numbers in mockups carry "Illustrative data".
For agents
The brand kit ships as a Claude Code plugin with two skills. Agents load them automatically when they write copy or design anything with the Signals Corps name on it.
The voice skill covers positioning, approved descriptions, naming, vocabulary, and a review checklist. The visual skill covers logo choice, color roles, type, shape, and what the imagery means. Both are rebuilt from the brand kit's guidelines on every release, so they match this book.
skills/signals-corps-voice/How Signals Corps talks about itselfskills/signals-corps-visual/How Signals Corps looksdist/tokens.jsonMachine-readable color, type, radius, and shadow valuesdist/brand.jsonAsset manifest with paths, uses, and minimum sizes# Add the brand kit as a plugin marketplace /plugin marketplace add signalscorps/brand-kit # Install the brand skills /plugin install signals-corps-brand@signalscorps-brand-kit