Standard employment engagement governed by a formal Employment Agreement between an organization and an employee, outlining the full terms of the working relationship.
Role and responsibilities: Full-time commitment to the organization, performing duties diligently and competently as assigned by the Board or management, while acting in the organization's best interests and protecting its reputation.
Compensation and benefits: Fixed annual gross remuneration, paid per the organization's standard payroll cycle, along with statutory benefits and paid leave (vacation, personal, and sick days) as per company policy. Unused leave doesn't carry forward or get encashed unless specifically approved.
Exclusivity: The employee is expected to avoid other business, occupation, or employment during the term without prior organizational approval, ensuring full focus on the role.
Termination: The organization may terminate the agreement immediately for cause including negligence, serious or repeated breach of duties, or unauthorized absence with notice in writing.
This structure reflects a clear, professional employment framework built around defined duties, fixed compensation, and specific grounds for termination, giving both parties clarity on expectations and protections throughout the engagement.
I’ve been razzmatazzing and flibbertigibbeting with Claude Code and somehow ended up with a new yels.dev.
It finally feels like me: simple on the surface, slightly complicated underneath, and very much alive.
You can see who I am, what I do, the work behind Herodot, RaptorLabs, CyberLink Security and Solmint, plus a selection of projects I’ve built across AI, cybersecurity, Web3, product systems, education, archives, and experimental digital spaces.
The simple-on-the-surface, layered-underneath idea comes through so clearly in the presentation. I especially like how the project archive turns the site into something to explore rather than just a résumé of links.
I designed this 9-page Client Welcome Guide in Canva with a clean, professional and welcoming visual style. The project focuses on organizing client information into clear, easy-to-follow sections while maintaining consistent typography, spacing and layout throughout the guide.
The goal was to create a practical digital document that businesses can use to introduce their process, communicate important information and create a polished first impression for new clients.
Nine pages feels like the interesting constraint — most onboarding docs either stop at two and leave people guessing or run to twenty and get skimmed. Did any section earn its page by killing a question that kept coming back over email?