Team onboarding — first week
Purpose. This is the document every new joiner reads in their first week. It is intentionally short. It is required reading, which means you'll get an acknowledgement request, and the doc only counts as "read" if you open the editor and scroll to the end. That is by design — reading is not the same as skimming.
Day 1 — accounts and access
Before lunch you should have working access to: GitHub, the team's Orimora workspace, the company email, the calendar, and the password manager. If any of these are missing, message @lena directly — she is the only one who can unblock access on day one.
Day 2 — the library
On day two, @lena walks you through the team library. The library is a knowledge base that lives — every doc has a pulse, a small number that says how well-maintained it is. Don't try to read everything. Read team/handbook.md, product/principles.md, and the most recent month's team/retros/*.md. That is enough for week one.
backlinks panel is how you find it.
Day 3 — the editor
Orimora's editor is a Markdown editor with block focus. The "block" is the unit: a paragraph, a heading, a list, a code block, a callout. Every block has its own state — selection, comment thread, pulse, last edit. The active block gets a soft outline so you always know which one you're editing.
# Follow a backlink from anywhere $ orimora backlink follow team/handbook.md
Days 4–5 — first doc
By the end of week one, you should publish one doc. It can be anything: a daily review, a piece of feedback on the editor, a question you wish this document had answered. The point is to put something into the library, see how a doc's pulse changes, and feel how backlinks and the outline work in practice.
Suggested first docs, in order of difficulty:
journal/2026-W*.md)
@om · week 1
inbox/editor-feedback.md)
@om · week 1
Required reading
You don't have to read all of these in week one. They are listed in the order you'll need them.
team/handbook.md — the day-to-day
before day 3
product/principles.md — what we believe about the product
before day 5
team/rituals.md — what meetings exist and why
before day 5
product/architecture.md — only the first three sections
by end of week 2
legal/data-handling.md — read once, internalise
by end of week 2
Where to ask for help
Three channels, in order of how loud you should be:
backlinks panel)
team/help channel — anyone can answer
team/incidents — that's the on-call
Welcome to the team. The library grows because you put things in it.