Adrien Murillo
From scope to handover.
A readable framework from the first conversation through handover: scope, decisions, implementation and verification.
Frame
Define scope, operating constraints, SSI requirements, risks and the expected outcome.
Design
Shape the target architecture, controls, delivery path and responsibilities with your teams.
Automate
Implement maintainable IaC, CI/CD, GitOps, scans and repeatable operational routines.
Prove
Consolidate tests, CVEs, logs, remediation and SSI evidence for the decision.
Before starting
Scoping shapes what follows.
We identify the system, what cannot be interrupted, the available stakeholders and the desired result. Success criteria must be understandable to everyone involved. The schedule is defined on that basis.
During and after
Transfer the means to act.
Each deliverable should support the team that takes ownership: decision, code, procedure, control or evidence. Remaining gaps, limitations and the next owner are made explicit during the handover.
One question is enough to start.
What needs to become more reliable, safer or easier to decide?
Describe your context ↗Before we talk
Practical questions.
Who will I work with?
With Adrien Murillo, an independent engineer and trainer. I am your point of contact for scoping the need, carrying out the work and handing over agreed deliverables.
Can an engagement cover several areas?
Yes. A platform may need risk work, technical controls and training. Scoping identifies priorities, dependencies and what belongs in the engagement.
What should I prepare for the first conversation?
The expected outcome, the system or team concerned and the main constraint. A few lines are enough. Sensitive documents and any access requirements are addressed later within an appropriate framework.
What deliverables can I expect?
Depending on the engagement: risk documentation, control evidence, code, procedures, tests or training material. Deliverables, verification criteria and handover responsibilities are agreed before the work begins.
Are GitHub projects client engagements?
No. Case studies describe my professional experience. The GitHub catalogue contains public tools and demonstrators, with provenance and limits. AI security is documented there without claiming client references.
How is training prepared?
Starting with the audience, prerequisites and situations the team needs to handle. The program defines objectives, exercises, a debrief and material. The proposed workshops are a starting point for scoping.
When can an engagement start?
Schedule and terms are confirmed after discussing scope. The form starts that conversation. It does not reserve a slot or initiate an engagement.