Code of Conduct

Version 1.0

Purpose: This document sets practical standards for people collaborating with Inov8ing. It is an operational policy, not a substitute for a signed collaboration agreement or applicable law.

1. Purpose and Scope

These guidelines apply to applicants, accepted members, project contributors, mentors, project leads, resource partners, and anyone acting on behalf of Inov8ing in an official capacity.

The goal is to build a reliable, respectful, learning-focused organization that creates useful digital products and services. Members may have different experience levels, schedules, and skills. Standards should be applied consistently and without favoritism.

This policy applies to Inov8ing-related work and spaces, including WhatsApp groups, project-management tools, repositories, meetings, shared drives, email, client communication, and public posts made on behalf of Inov8ing.

2. Core Expectations

Every member is expected to:

1. Be honest. Do not falsify skills, experience, availability, progress, hours, results, or portfolio claims.
2. Be reliable. Commit only to work you can reasonably complete. Communicate early when a deadline or commitment is at risk.
3. Respect others. Treat beginners, experienced members, clients, mentors, and partners professionally.
4. Keep learning. Ask questions, accept constructive feedback, document discoveries, and avoid repeating preventable mistakes.
5. Take ownership. Raise problems with evidence and propose next steps where possible. Do not hide errors or blame others to avoid responsibility.
6. Protect information. Safeguard company, project, client, and member information.
7. Respect agreements. Follow the collaboration agreement, project brief, IP terms, revenue-sharing schedule, and applicable platform rules.
8. Work transparently. Keep task status, blockers, decisions, and handovers visible to the relevant team.

3. Communication Standards

• Use clear, professional language in work-related channels.
• Critique the work or decision, not the person.
• Give useful context when requesting help: what you tried, what happened, relevant screenshots/logs, and the result you need.
• Do not repeatedly message or call people outside their stated availability unless the matter is urgent and appropriate.
• Acknowledge important requests within the response window agreed by the team. An acknowledgment is not the same as a completed task.
• Raise disagreements directly and respectfully. If unresolved, use the escalation path in Section 12.
• Do not publish private conversations, screenshots, voice notes, or member details without authorization, except where disclosure is legally required or needed to report serious misconduct safely.
• Do not impersonate a founder, team lead, client, partner, or another member.

4. Availability, Deadlines, and Accountability

4.1 Members should state their realistic availability and keep it updated. A commitment such as “one hour per day” should be treated as a planning estimate, not a promise to be online continuously.

4.2 When accepting a task, confirm:

• the expected deliverable;
• the due date or checkpoint;
• the estimated effort;
• dependencies and required access; and
• the person who will review or accept the work.

4.3 If you expect to miss a deadline, notify the task owner as soon as practical. State the reason briefly, current status, what remains, and a realistic revised date.

4.4 If you cannot continue a task, do not disappear. Provide a short handover with completed work, remaining work, file/repository locations, known issues, and next steps.

4.5 Inov8ing recognizes that members may have studies, jobs, family responsibilities, connectivity issues, or health-related constraints. Reasonable communication and a realistic revised plan are preferred over unrealistic commitments.

4.6 Repeated missed commitments without communication may lead to reduced responsibilities, reassignment, a pause in project participation, or removal from a team, following the process in Section 13.

5. Quality and Professional Standards

• Follow the project's definition of done, technical standards, design rules, and acceptance criteria.
• Test work before marking it complete. Include relevant evidence, such as a preview, test result, screenshot, or pull request.
• Do not knowingly submit broken, copied, insecure, misleading, or unreviewed work as production-ready.
• Disclose uncertainty and known limitations.
• Do not make product, security, performance, legal, or delivery claims that have not been verified.
• Use version control and the project's approved workflow where applicable.
• Do not overwrite another person's work or change shared production systems without the required approval.
• Document non-obvious decisions and setup steps so another team member can continue the work.
• Report defects and mistakes promptly. Honest disclosure is preferable to concealment.

6. Respectful and Safe Environment

The following conduct is prohibited in Inov8ing-related spaces:

• harassment, threats, bullying, intimidation, stalking, or targeted humiliation;
• discrimination or abusive conduct based on personal characteristics protected by applicable law;
• sexual harassment, unwanted sexual attention, or coercive behavior;
• repeated personal insults, degrading language, or deliberate disruption;
• retaliation against someone for raising a concern in good faith;
• pressure to provide unpaid work beyond agreed commitments, or threats used to force participation;
• sharing another member's personal information without authorization;
• deliberate sabotage, impersonation, or malicious interference with a project.

Members should raise concerns without fear of retaliation. A report made in good faith will not itself be treated as misconduct merely because it cannot be substantiated. Knowingly fabricated reports may be addressed through the same fair process as other misconduct.

7. Confidentiality and Data Protection

Members must follow the confidentiality and data-protection obligations in their agreements and project instructions.

At a minimum:

• Do not share private source code, credentials, API keys, customer records, internal plans, unpublished products, financial details, or private discussions outside authorized channels.
• Do not upload confidential project material to external AI tools or third-party services unless the project owner has approved that use and the service's data terms are appropriate.
• Use the minimum access necessary to perform assigned work.
• Use strong, unique passwords and multi-factor authentication where available.
• Do not store credentials in public repositories, shared screenshots, or unsecured documents.
• Report suspected account compromise, accidental disclosure, malware, or data loss promptly.
• Do not use customer/member data for personal marketing, scraping, resale, or unrelated experiments.
• Return or delete confidential information when instructed, subject to legal retention requirements and the applicable agreement.

Confidentiality does not prevent lawful reporting of suspected wrongdoing to an appropriate authority or disclosure that is legally protected or required.

8. Intellectual Property and Use of Materials

• Follow the signed Intellectual Property & Work Product Agreement and the project-specific terms.
• Do not copy third-party code, images, video, audio, fonts, datasets, or other assets without a valid licence or permission.
• Disclose open-source components, external assets, templates, and AI-generated materials where relevant to the project.
• Do not submit another person's work as your own.
• Do not publish, sell, reuse, or open-source company/client work without written authorization and compliance with the applicable agreement.
• Do not assume that contributing to a project automatically gives you ownership of the product or an automatic revenue share. Those rights must be documented separately.
• Likewise, Inov8ing must not claim ownership of a member's pre-existing work merely because the member joins the organization. Pre-existing materials and permitted licences should be identified in the applicable agreement.
• Ask before using Inov8ing's name, logo, internal screenshots, or project results in a portfolio or public case study.

9. Security and Access

Members must:

• use only accounts, systems, files, and repositories they are authorized to access;
• never share accounts or credentials in violation of platform rules;
• avoid bypassing access controls, collecting unauthorized data, or testing systems without permission;
• keep devices and local project files reasonably secure;
• avoid committing secrets, private keys, personal data, or production credentials to source control;
• report suspected vulnerabilities privately to the designated project lead or founder;
• follow approved backup, deployment, and release procedures; and
• cooperate with access reviews and promptly return or remove access when a role ends.

Unauthorized access, credential theft, deliberate data exfiltration, malicious code, or intentional sabotage may result in immediate suspension of access while the incident is investigated.

10. Client, Partner, and Public Communication

Only people authorized for a project may make commitments to clients, investors, vendors, or the public on behalf of Inov8ing.

• Do not promise delivery dates, prices, refunds, service levels, revenue, or technical capabilities without approval.
• Do not disclose confidential client information or use client work in public examples without permission.
• Escalate complaints, legal threats, security incidents, payment issues, and requests outside your authority.
• Be truthful about your role and the status of work.
• Do not present personal opinions as official Inov8ing statements.
• Do not accept money, gifts, commissions, or benefits on Inov8ing's behalf unless authorized and documented.

11. Conflicts of Interest and Resource Use

Members should disclose material conflicts that could affect project decisions, such as a financial interest in a supplier, competing commitment, or close relationship with a person whose work they review.

Do not use Inov8ing resources, paid accounts, client information, private code, or team time for unrelated personal work without authorization. Personal learning and portfolio use may be allowed where approved and consistent with the relevant agreements.

Do not use company resources for unlawful activity, unauthorized commercial resale, cryptocurrency mining, or activities that create unapproved costs or security risks.

12. Feedback, Disagreements, and Escalation

Use this sequence where appropriate:

1. Clarify privately. Explain the specific issue and the outcome you need.
2. Use evidence. Refer to the project brief, acceptance criteria, task history, agreement, or observable behavior.
3. Propose a resolution. Suggest a practical next step, owner, and date.
4. Escalate. If unresolved, contact the project lead or founder. If the concern involves that person, use the alternative contact listed in the onboarding materials or another appropriate reporting route.
5. Record the outcome. Document important decisions in the approved project channel.

Serious concerns involving harassment, threats, fraud, security, privacy, or suspected unlawful activity may be escalated immediately without first confronting the person involved.

13. Handling Inactivity or Policy Breaches

Inov8ing should use a fair, proportionate process that considers the seriousness of the issue, evidence, impact, prior history, and the member's explanation.

Possible steps include:

1. Informal clarification or reminder for a minor first issue.
2. Written warning and improvement plan identifying the behavior or missed commitment, expected change, and review date.
3. Task reassignment or temporary pause where delivery, safety, or project continuity requires it.
4. Suspension of access where there is a credible security, confidentiality, legal, or safety risk.
5. Removal from a project or Inov8ing team for serious or repeated breaches, after a reasonable opportunity to respond where appropriate.

For inactivity, the default process is to contact the member, ask whether circumstances have changed, and allow a reasonable recovery period based on project urgency before reassignment or removal. If the member is unreachable and continued access creates a material risk, access may be restricted while the status is clarified.

Immediate protective action may be appropriate for credible threats, harassment, fraud, unauthorized access, deliberate disclosure, or serious risk to a client or member. Protective action is not a final finding of wrongdoing.

Where practicable, the member should be told the concern, given a reasonable chance to respond, and informed of the decision and any review route. Inov8ing should maintain a minimal, confidential record of significant decisions.

14. Leaving the Team and Handover

Members should follow the notice period in their signed Collaboration Agreement. The intended standard is seven days' notice, unless a different written agreement or urgent circumstance applies.

Before leaving, a member should, as applicable:

• update task status and identify unfinished work;
• hand over files, repositories, documentation, and project context;
• transfer authorized ownership or administration of project accounts;
• remove personal credentials and return company/client credentials securely;
• disclose known bugs, risks, dependencies, and pending customer commitments;
• return equipment or other property; and
• follow confidentiality and intellectual-property obligations after departure.

Inov8ing should remove access that is no longer needed and settle any undisputed amounts due under the signed agreements. Earned but unpaid amounts and other accrued rights must be handled according to the applicable agreement and law.

Rejoining after departure is not guaranteed. Any future application or re-entry may be reviewed based on current needs, previous handover, conduct, availability, and the applicable agreements. This policy does not override rights that cannot lawfully be waived.

15. Learning, Mentorship, and Fair Expectations

Inov8ing aims to provide practical learning and collaboration opportunities, subject to available projects, mentors, tools, and capacity. Participation does not guarantee a job, promotion, certificate, paid work, portfolio permission, revenue, or access to every tool.

Members should ask for clarification when an assignment is beyond their current skill level. Leads should define reasonable tasks, review work constructively, and avoid representing a beginner's work as expert-level without appropriate review.

Any paid role, guaranteed compensation, internship, employment relationship, or formal training commitment must be documented separately where required. Unpaid participation must not be used to evade applicable labor, minimum-wage, internship, or other legal requirements.

16. Members Under 18

Applicants under 18 may express interest, but participation in actual work, handling of personal data, contracts, payment arrangements, and access to online spaces must follow applicable law and appropriate safeguards.

Before accepting a minor into activities that require it, Inov8ing should verify the required parent/guardian consent, explain the arrangement in age-appropriate terms, restrict access to necessary information, and ensure suitable supervision. Do not collect unnecessary identity documents or sensitive information. Obtain legal advice before involving minors in commercial work.

17. Reporting a Concern

Report concerns to:

• Primary contact: the founder of Inov8ing
• Email: contact@inov8ing.io
• Alternative contact for concerns involving the primary contact: contact@inov8ing.io
• Security/privacy incidents: contact@inov8ing.io

Include the relevant dates, project, people involved, and available evidence. Share only information necessary to explain the concern. Do not investigate by accessing accounts or data without authorization.

Reports will be handled as confidentially as reasonably possible, but absolute confidentiality cannot be guaranteed where investigation, safety, or legal obligations require disclosure.

18. Policy Administration and Updates

The policy owner is Inov8ing.

Version: 0.1 Effective date: 28 October 2026 Last reviewed: 28 October 2026

Inov8ing may update these guidelines as the organization grows. Material changes should be communicated to affected members with a reasonable effective date. Changes to signed contractual rights, compensation, ownership, or other material agreement terms require the process specified in the relevant agreement and applicable law; a policy update alone does not automatically amend a signed contract.

Members may be asked to acknowledge the current version during onboarding and after material updates.

Member Acknowledgment

I confirm that I have read and understood the Inov8ing Code of Conduct & Community Guidelines. I agree to follow these standards while participating in Inov8ing activities, subject to applicable law and the terms of any signed agreement.

• Full name: ______
• Email: ______
• Role/team (if applicable): ______
• Policy version: 1.0
• Date: ______
• Acknowledgment/signature: ______