Knowledge objects
Extracted knowledge
2,847 objects across 6 sources — browse, search, and inspect
Production deployment process
All deploys to production require a PR approved by at least one senior engineer. Deploys happen via the deploy command in #deploys. Feature flags must be used for any change affecting >10% of users.
Sev1 escalation path
Page on-call engineer first. If unresponsive after 5 minutes, notify #incidents and tag the engineering lead. CEO notification required for downtime exceeding 30 minutes.
Support tier definitions
Tier 1: billing and account questions handled by support team. Tier 2: product bugs escalated to product+eng Slack. Tier 3: data loss or security issues, immediate eng escalation required.
API naming conventions
REST endpoints use kebab-case plural nouns. All new endpoints require an OpenAPI spec before implementation. Breaking changes require a deprecation notice of at least 30 days.
Pricing tier decision — Q2 2026
Decided to move from seat-based to usage-based pricing for the Growth tier. Rationale: aligns cost to value for high-volume low-seat customers. Effective July 1, 2026.
New hire onboarding checklist
Day 1: laptop setup, system access, intro to tech lead. Week 1: shadow support, read architecture doc, set up local dev. Week 2: first PR. First 30 days: paired on-call rotation.
Customer refund policy
Full refund within 14 days of billing, no questions asked. Partial refund (pro-rata) for annual plans cancelled mid-cycle. Escalate enterprise refunds to account manager.
Code review standards
Reviews should be completed within 1 business day. Nit comments prefixed with 'nit:' are non-blocking. Security-affecting changes require two approvals.