ODIN JOIN #ODIN-BOT
SHIPPIT INTERNAL LIVE INSlack

AN INTERFACE TO WHAT SHIPPIT ACTUALLY RUNS

ASK THE
CODEBASE.

Understand product behaviour, integrations and technical decisions from the code that powers them.

JOIN #ODIN-BOT SEE HOW AN ANSWER WORKS
SOURCECURRENT CODE
SURFACEPUBLIC Slack THREADS
ACCESSORG-WIDE
MODEREAD-ONLY
01 / WHY ODIN

THE PROBLEM IS NOT A LACK OF DOCUMENTS

THE TRUTH DRIFTS.
THE CODE DOESN’T.

Specs describe intent. Project pages capture a moment. Chat preserves opinions.

Odin answers from the implementation that exists now. If the evidence is incomplete, it says so.

02 / THE BOUNDARY

LESS NOISE.
MORE SIGNAL.

Odin is deliberately narrow. It does not search every company document and hope the most confident sentence is current.

INSIDE THE TRUST BOUNDARY
01
Current source codeThe behaviour running in production.
AUTHORITY
02
Codebase mapUsed to navigate systems, then verify against code.
INDEX
03
Pull requestsRecent changes and the code behind them.
CURRENT
OUTSIDE THE TRUST BOUNDARY
×
ConfluenceMay describe a system that has since changed.
EXCLUDED
×
Google DriveUseful context; not executable truth.
EXCLUDED
×
Company folkloreWhat someone remembers is not evidence.
EXCLUDED
03 / THE ANSWER

THE INTERFACE IS A Slack THREAD

PLAIN ENOUGH TO USE.
TECHNICAL ENOUGH TO TRUST.

Every response starts with a direct conclusion, explains the behaviour, then shows the evidence behind it.

A real Slack thread showing Odin answering a product question with code-level evidence and practical workarounds.
04 / HOW IT WORKS

ONE QUESTION.
FOUR MOVES.

Odin investigates in a bounded, read-only loop. It cannot change the code it reads.

  1. 01
    ASK

    Join #odin-bot and mention @Odin in the channel or a thread.

  2. 02
    SEARCH

    Odin traces the question through its codebase map and relevant repositories.

  3. 03
    VERIFY

    Claims are checked against current files, identifiers and pull requests.

  4. 04
    ANSWER

    The result returns to the same Slack thread with its evidence status attached.

05 / WHAT TO ASK

ASK ACROSS THE PRODUCT.

Start with the behaviour you need to understand. You do not need to know which repository contains it.

PRODUCT / OPERATIONS

“What happens when a label fails after allocation?”

Trace a workflow through the actual states, conditions and fallbacks.

SALES / SUPPORT

“Do we currently support this carrier capability?”

Check what the integration implements—not what an old enablement page promised.

ENGINEERING

“Where is the retry behaviour for failed manifests?”

Find the owning service, entry point and exact implementation evidence.

LEADERSHIP / ENABLEMENT

“How does Shopify LIVE Quotes work with Shippit Connect?”

Build shared understanding from the connector behaviour and the code that powers it.

06 / WHAT ODIN IS NOT

A NARROW TOOL IS A TRUSTWORTHY TOOL

ODIN KNOWS
ITS BOUNDARY.

Does Odin query live customer or order data?−

No. Use the operational data tools designed for that purpose.

Can Odin tell me roadmap or rollout status?+

No. Code can show what exists; it cannot establish a commitment or launch decision.

Can Odin change code or open a pull request?+

No. Its investigation tools are read-only.

What happens when the code is inconclusive?+

Odin marks the answer as partially confirmed or not confirmed instead of filling the gap.

AVAILABLE TO EVERYONE AT SHIPPIT

DON’T ASK “WHO KNOWS THIS?”
START WITH ODIN FIRST.

JOIN #ODIN-BOT
JOIN #ODIN-BOT MENTION @ODIN ASK A SPECIFIC QUESTION
JOIN #ODIN-BOT