i4F Team Onboarding
Every new i4F team member walks the same onboarding spine — access, environment, a guided domain walk, and a first verified change. Each operational node runs its own checklist instance below. A node's headline verdict is the worst of its steps: one blocked step turns the node red, and a fully-checked node reads green.
Checklists by Node
Ashkelon, Ahmedabad, and Miami each track the same four steps. The pill on each row is that step's traffic light; the pill on each header is the node's rollup.
Validation-engine and keystone-gate ownership.
- Provision accessDone
SSO, repo read/write, and node VPN granted.
- Bootstrap local environmentDone
Monorepo installs and the dev-admin cockpit boots clean.
- Walk the validation-engine domainDone
Pair through the keystone gate and fixture set with a mentor.
- Land a first verified changeIn Progress
Open, review, and merge one small PR end to end.
Worker pipeline and migration tooling.
- Provision accessDone
SSO, repo read/write, and node VPN granted.
- Bootstrap local environmentDone
Monorepo installs and the worker test suite runs green.
- Walk the worker + migrations domainIn Progress
Trace a job from enqueue to completion with a mentor.
- Land a first verified changeTo Do
Open, review, and merge one small PR end to end.
Web app, design system, and observability surface.
- Provision accessBlocked
SSO, repo read/write, and node VPN granted.
- Bootstrap local environmentTo Do
Monorepo installs and the web app renders locally.
- Walk the web + design-system domainTo Do
Tour the UI kit and the cockpit routes with a mentor.
- Land a first verified changeTo Do
Open, review, and merge one small PR end to end.
Node checklists are illustrative cockpit project-tracking state authored in src/data/onboarding-steps, not product data. A node reads blocked when any step is blocked, done when every step is checked, and in-progress otherwise.