Professional operating code
Protect the decision, the data, and the handoff.
IT Modality professionals are expected to make their contribution, evidence, authority, risks, corrections, and transfer legible. The written engagement sets the actual role; this code establishes the conduct around it.
ForExperienced independent professionals
FocusAssessment, readiness, engagement operations, and support
Relationship boundary: This code applies within the independent-contractor model. It is not an employment policy, does not expand a professional's authority, and does not create guaranteed work.
Eight commitments govern the work.
1. Represent yourself and your contribution precisely.
Claim only qualifications, credentials, experience, role, availability, authorship, decisions, and outcomes that can be supported. Distinguish team output from personal contribution and prior-role experience from IT Modality engagement history.
2. Work from a bounded scope.
Confirm the intended outcome, role, deliverables, exclusions, dependencies, decision owners, acceptance evidence, client contacts, data and access boundary, and escalation path before consequential work.
An informal request does not silently expand the scope, commercial terms, or authority.
3. Separate fact, assumption, recommendation, and decision.
Make the evidence and uncertainty behind a recommendation visible. Record who owns the decision, which conditions could change it, and what remains unresolved. Do not describe unreviewed, untested, or unaccepted work as approved.
4. Protect information and access.
Use only approved identities, devices, environments, data, tools, providers, transfers, and storage. Do not place patient information, credentials, client secrets, privileged material, private source code, production records, or confidential work into public forms, unapproved AI systems, ordinary personal accounts, or unauthorized repositories.
Access is the minimum approved for the task and changes or ends when the role or scope changes.
5. Keep consequential authority with its owner.
Clinical, legal, accounting, privacy, security, regulatory, contractual, and client executive decisions remain with the qualified assigned owners. A professional can frame evidence and recommend action without pretending to hold authority that the engagement did not assign.
6. Declare material assistance and conflicts.
Disclose material use of AI, templates, code, collaborators, subcontractors, or other assistance under the applicable instructions. Declare personal, financial, organizational, assessment, or client conflicts before they distort the record.
Academy enrollment, payment, scholarship, performance, completion, and certificates never influence Rigors, network, rate, or client-selection decisions.
7. Surface and correct defects.
Use the required checks, reviews, versioning, acceptance gates, and correction process. Report material errors promptly, preserve the original record, contain affected work where appropriate, and support an attributable correction. Do not conceal a defect, delete an exception history, or shift blame through an inaccurate record.
8. Leave the work transferable.
Keep decision, review, exception, change, access, acceptance, operating, and handoff records usable by the next owner. Close with accepted artifacts, open decisions, unresolved risk, access changes, continuity notes, and one receiving owner.
Stop and escalate when authority ends.
A professional should pause or refuse work that is:
unsafe, unlawful, deceptive, or incompatible with a professional duty;
materially outside the written scope or beyond assigned authority;
dependent on missing required evidence, approval, access, or qualified review;
based on an unapproved data, tool, provider, environment, transfer, or identity path;
designed to conceal a defect, evade an agreed control, or misattribute work; or
inconsistent with the confidentiality, security, privacy, integrity, or client boundaries of the engagement.
The escalation records the condition, evidence, consequence, actions already taken, available options, recommendation, decision owner, and timing impact. Good-faith escalation is a delivery control, not an admission of failure.
Cooperate with review without dissolving boundaries.
Professionals provide the evidence and explanation required by the agreed review, acceptance, incident, grievance, or audit process. Cooperation does not authorize disclosure outside approved channels or surrender of unrelated personal or client information.
Questions about scope, payment, conduct, attribution, access, retaliation, deactivation, or another engagement-process issue follow the professional grievance path.