welcome.md markdown
31 lines 1.3 KB
Raw
sha256:c2dbf04d56308f3bbf2d06e6d2eb022b8948b1e827195fe525a44e5e18d5f9c0 feat(auth): Phase B Connect cloud agent (RFC 8628) + Hermes… Human minor ⚠ breaking 11 days ago

title: Welcome — business ops vault project: business-ops-template tags:

  • onboarding
  • operations
  • knowtation date: 2026-04-07

Welcome — business ops vault

This is the team’s shared memory for how we run the business: who decided what, how we handle incidents, and what each customer cares about.

Day-one checklist

  1. Confirm access to chat, calendar, CRM, and the document drive (link internally—do not paste secrets here).
  2. Read the latest kickoff or QBR note for your squad in meetings/.
  3. Skim playbooks/incident-response.md even if you are not on call—you may need it during an outage.

Conventions

  • Customers: one brief per key account under customers/; update after every major call.
  • Decisions: when we change stack, pricing, or process, add an ADR under decisions/ instead of debating twice in Slack.
  • Competitive: quarterly snapshots in competitive/; tag by segment (b2b-saas, agency, etc.).

What not to store here

Passwords, API keys, or unredacted personal data. Link to secure vaults and CRM instead; keep this vault for narrative context and decisions.

Questions? Ask your manager or ops lead and then capture the answer in the right folder so the next hire finds it.

File History 1 commit
sha256:93bcf8f9bd56d8c5b9339f4ec73b9ebd66571398d56262d38eedc2cfa9db9882 fix(test): align Band B landing assertion with desktop MCP … Human 11 days ago