RACI Model

RACI assigns four roles to every kind of work: Responsible (does the work), Accountable (one person, signs off and answers for the outcome), Consulted (gives input before the work is done), Informed (told after the work is done). Every activity has exactly one Accountable. Multiple Responsibles is normal; multiple Accountables is the same as no Accountable.

The model is here to make ownership unambiguous when something goes wrong, and equally to make it unambiguous who has standing to make a decision before something starts. "It fell between teams" is a RACI failure, not a personal failure.

Named individuals (May 2026)

Hiring for the three open roles uses hr/resource-profiles, hr/candidate-tests, and hr/interview-templates end-to-end.

RACI by activity type

Requirement specification

• Responsible: Whoever drafted it (often Mikkel Nygaard with AI assistance).
• Accountable: Mikkel Nygaard (PA).
• Consulted: Assigned developer, QA Lead, any legal/compliance owner the spec flags.
• Informed: CEO (for customer-visible features), the rest of the team via the weekly digest.

Implementation of a Castline feature

• Responsible: Assigned developer (Ahmed Mahmood Khan for full-stack; Frontend/Backend hires for split work).
• Accountable: Ahmed Mahmood Khan as Lead Developer.
• Consulted: Designer, QA Lead, Security Lead for security-sensitive work.
• Informed: Project Manager, QA Testers (so they can prepare functional test cases).

Functional testing

• Responsible: QA Testers (Earl Elvin Badua, Loïc Joubert, Niran Phongphan, Renata Gomes — rotating).
• Accountable: QA Lead.
• Consulted: Developer who built the feature.
• Informed: Project Manager (failures); CEO (S1/S2 failures blocking a release).

Release

• Responsible: Lead Developer (Ahmed Mahmood Khan) executes the deploy.
• Accountable: Head of Compliance (release notes), Lead Developer (deploy).
• Consulted: QA Lead, Project Manager.
• Informed: CEO, Customer Success.

Security incident

• Responsible: First Responder (on-call engineer).
• Accountable: Incident Commander.
• Consulted: Lead Developer, Head of Compliance, Head of Legal.
• Informed: CEO immediately; affected individuals and supervisory authority per compliance/incident-response.

Hiring

• Responsible: Hiring manager for the role.
• Accountable: CEO for any role; Project Manager owns the candidate pipeline operationally.
• Consulted: People Operations on contract terms; existing team member on technical evaluation.
• Informed: Whole team when an offer is accepted.

Investor and stakeholder updates

• Responsible: CEO (drafts), Project Manager (compiles supporting materials).
• Accountable: CEO.
• Consulted: Head of Finance for numbers, Head of Compliance for posture statements.
• Informed: Board, investors.

What the model does not do

The RACI is not a job description. Ahmed Mahmood Khan is "Main Developer" by role; whether Ahmed Mahmood Khan is Responsible for a given activity depends on the activity. Likewise the QA Testers are individuals, but their accountability rolls up to the QA Lead.

The RACI is also not a delegation veto. The Accountable person can — and often should — delegate the work. They cannot delegate the accountability.

Owned by

People Operations, with the Project Manager as the day-to-day curator. Audited by the Master skill on a 60-day cadence.