profile.yaml lives in your individual HR repo. It stores your personal,
payment, and engagement details — Wizard reads it for invoice generation and
other HR automation.
All fields are required; at least one entry in bank_accounts and one entry
in crypto_wallets must be specified:
first_name, last_nameid_number, date_of_birthresidential_address, email, phone_numbergithub_handle, telegram_phone, whatsapp_phonebank_accounts (one or more)crypto_wallets (one or more)rates (one or more — see Rate history)max_cap is optional — only set it if your agreement defines a maximum
billable hours per month.
profile:
first_name: Jane
last_name: Doe
id_number: 'A123456789'
date_of_birth: '1990-01-15'
residential_address: 123 Main Street, Springfield, IL 62701, US
email: jane@gmail.com
phone_number: '+1234567890'
github_handle: janedoe
telegram_phone: '+1234567890'
whatsapp_phone: '+1234567890'
max_cap: 160 # optional — max billable hours per month, from the agreement
bank_accounts:
- bank: First National Bank
account_name: Jane Doe
account_number: '1234567890'
swift_bic: FNBAUS12XXX
- bank: Second National Bank
account_name: Jane Doe
iban: GB29NWBK60161331926819
crypto_wallets:
- network: Ethereum
token: USDT (ERC-20)
address: 0x742d35Cc6634C0532925a3b8D4C9b5A93b2c4D1f
rates:
- amount: 37.5
effective_from: '2024-04-01'
Your hourly rate is stored as a history so rate changes can be merged at any time without operational coordination:
rates:
- amount: 5
effective_from: '2026-01-01'
- amount: 6
effective_from: '2026-06-01'
effective_from must always be the first day of a month — Wizard enforces
this at PR merge time and rejects values that aren't the first of a month.effective_from
that is on or before the first day of the billing month, so a single rate
applies to all PRs within any calendar month.