Legal employer
Rafael and the approved employee population
The customer identifies the employing entity, buyer, data controller, and employees included in this journey.
In scopeWeb3 employee onboarding software
The protocol docs cannot onboard Rafael.
For 120 to 500 employee protocol companies adding specialist cohorts, coordinate People and Product to a manager-confirmed first contribution.
Rafael NascimentoProtocol Product Manager. Starts in 10 days.HireOnboardGrow
Assigned to Protocol sponsorDue FridayApprove Rafael’s first 30-day contribution goal
- Every dependency has a human owner
- Living protocol sources stay authoritative
- The route leads to a first bounded contribution
The links arrived. Rafael’s route still has six human owners.
Living sources explain the protocol. They do not assign Security, the Protocol sponsor, the manager, the buddy, or People to act.
Rafael NascimentoProtocol Product Manager, starts in 10 days
Owned role ramp
- Candidate continuityCarry Rafael’s employer, role, and interview context into preboardingPeople owns thisComplete
- EquipmentPrepare Rafael’s equipmentIT owns thisComplete
- Access dependencyConfirm Rafael’s access request in the customer-controlled systemSecurity owns this2 days late
- Company modelLead Rafael’s company, protocol, foundation, and community reviewProtocol sponsor owns thisScheduled
- Human supportHold the first introduction in a compatible working windowBuddy owns thisScheduled
- Blocker questionRoute Rafael’s access question to Security and track the responsePeople owns thisAfter Rafael’s journey questionWaiting
- First contributionApprove Rafael’s first bounded product contribution goalManager owns thisAfter the company-model review and access confirmationWaiting
People sees the complete route. Security, the sponsor, the manager, the buddy, and Rafael remain responsible for their own part.
Name the employer before you map the journey.
A company, protocol, foundation, and community can be related without sharing one employer, authority model, or employee population.
- Technical context
Protocol or network
Approved protocol context informs Rafael’s role while protocol operation, governance, and technical control remain elsewhere.
Company context - Related entity
Foundation
A foundation can have separate authority, employees, data responsibilities, and internal processes.
Separate responsibility - Wider population
Community and ecosystem
Token holders, grantees, delegates, validators, and independent contributors are not silently treated as employees.
Out of scope
CapoFine does not determine worker status. The customer’s People and Legal owners define every in-scope population and process.
One company model. Different routes through the same protocol.
Reuse the approved foundation, then target the people, context, practice, and first goals each specialist role actually needs.
The company context every specialist employee should receive.
- The employer, product, protocol, foundation, and community relationship
- Company language, responsibility boundaries, and escalation paths
- The people and living sources employees should use
- The company-approved security and safe-working foundation
Build once. Reuse across specialist teams.
Then target what changes
Protocol Product Manager
Add Protocol and Engineering introductions, decision context, source ownership, stakeholder boundaries, and a manager-approved first contribution goal.
Developer Relations Engineer
Add developer audiences, documentation ownership, Protocol and Community handoffs, approved external language, and a supervised first content contribution.
Solutions Engineer
Add product boundaries, customer context, Security and Protocol introductions, and guided preparation for a first customer-facing contribution.
Start with the role ramp. Add the full ATS and LMS where the next gap is real.
Lead with Onboard for one recurring employee role. Connect Hire or Grow when recruitment or ongoing learning has its own measurable problem.
01
Full applicant tracking system
Hire
Run specialist recruitment in one complete ATS.Publish precise vacancies, centralise candidate communication, coordinate distributed interview panels, move applicants through stages, collect post-interview feedback, and hand the accepted candidate into Onboard.
Explore Hire02
Employee journey orchestration
Onboard
Give every journey owner one timed responsibility.Coordinate Rafael’s access dependency, Protocol introduction, interactive company story, buddy meeting, questions, files, communication, first goal, and visible progress from day -30 through day 90.
Explore Onboard03
Full learning management system
Grow
Turn one approved change into role-specific learning.Give Product, DevRel, Solutions, Support, or Security the company-approved scenario relevant to their role, with scheduled learning windows, reminders, progress, and formal assessment only where deliberately required.
Explore GrowKeep protocol truth live. Keep employee scope precise.
CapoFine coordinates the employee route around approved sources and named owners. Technical systems and qualified human decisions remain authoritative.
What CapoFine coordinates
- Accepted-candidate context, meetings, tasks, communication, files, questions, buddies, goals, and progress
- Role-specific stories that connect approved sources to company responsibility
- Named owners, due dates, reminders, and visible blockers
- Company-approved learning targeted by role, team, department, or location
- Human escalation when AI Buddy cannot answer safely
What remains elsewhere
- Protocol, node, wallet, smart-contract, treasury, governance, and community operations
- Repository, account, permission, key, or production-access approval and provisioning
- Private keys, seed phrases, credentials, secrets, vulnerabilities, and production-sensitive data
- Worker classification, legal interpretation, regulatory scope, and compliance decisions
- Technical readiness, secure-coding competence, and approval of a first contribution
Measure the route to a first contribution, not course completion.
Run one employee journey with a named People Ops owner and Protocol or Product sponsor. Measure only the coordination signals CapoFine can make visible.
Map accepted candidate through a manager-approved first contribution with People, Security, the Protocol sponsor, the manager, a buddy, and Rafael in scope.
Owner action on-time
Internal actions completed by the responsible owner on the agreed date.
Unresolved blockers
Open employee dependencies still waiting at planned journey checkpoints.
Manual People follow-up
Reminders and status checks still performed outside the journey.
Expert repeat time
Foundation explanations repeated by Protocol, Product, Engineering, or Security.
First-contribution timing
Days until the manager confirms the first bounded employee contribution.
These signals measure coordination and employee-journey execution. They do not certify technical competence, protocol readiness, security, productivity, or compliance.
Questions from People, Protocol, Product, and Security.
Can our protocol and product documentation remain the source of truth?
Yes. Keep volatile technical material in its living source. CapoFine coordinates stable company context, source links, role-specific stories, human conversations, review ownership, goals, and targeted follow-up around it.
Can we start with employees in one legal entity?
Yes. The recommended pilot uses one defined employer, one recurring employee role, and one customer-approved population. Contractors, grantees, token holders, community members, and independent contributors remain out of scope unless the customer deliberately approves a suitable process.
Is Hire a complete ATS for distributed specialist recruitment?
Yes. Hire covers career pages, vacancies, application forms, applicant pipelines, candidate CRM, communication, interview scheduling, post-interview scorecards, documents, talent pools, automations, reporting, privacy workflows, and accepted-candidate handoff.
Is Grow a complete LMS for role-specific company learning?
Yes. Grow supports course and pathway creation, interactive learning, audience assignment, scheduled windows, progress, formal assessments, retries, results, certificates, reporting, and gamification.
Where do access approval and technical-readiness decisions remain?
With the customer’s Security, IT, Engineering, Protocol, and management owners. CapoFine can assign and track the dependency, but it does not grant access, handle secrets, approve production work, or certify technical competence.
How does CapoFine fit around our HRIS, documentation, chat, and access systems?
Keep them in place. Your HRIS remains the employee record, living documentation remains authoritative, and customer-controlled systems approve and fulfil access. CapoFine coordinates the people, timing, activities, learning, and follow-up across them.
Map one protocol-to-role journey.
Bring one repeat-hire role, one recent start, the People Ops owner, and the Protocol or Product sponsor.
Bring the current vacancy, employee journey, living sources, human owners, access dependencies, and one recent blocker.
What you leave with
- Legal-employer and employee-population scope
- Current employee journey and owner map
- Living-source and journey-content split
- Late dependencies and repeated expert sessions
- One-role pilot and measurement plan