This Code of Conduct defines safe, respectful, and responsible behavior within the SIRIUS LOCAL AI GAMA project.
GAMA follows the SIRIUS ecosystem principles of privacy, safety, determinism, modularity, and offline‑first design, extended with hybrid‑safe rules introduced in the 3.x architecture and strengthened in 3.2.0.
Version 3.2.0 reinforces hybrid‑safe boundaries, SUL compliance, module isolation, deterministic behavior, and full compatibility with the Mobile Runtime 3.2.0 event and vision pipeline.
All contributors and users agree to uphold:
- Respect – professional, dignified communication
- Safety – no harmful, abusive, or dangerous behavior
- Privacy – no collection or sharing of personal data
- Integrity – honest, transparent collaboration
- Inclusivity – zero discrimination
- Family‑safe environment – content appropriate for all ages
- Offline‑first mindset – no cloud, no telemetry, no remote dependencies
- Determinism – predictable, reproducible behavior across all modules
- Modularity – isolated, replaceable components
- Hybrid‑safe architecture – strict separation of offline and online data
- SUL Compliance – respect for the SIRIUS Unified License (SUL 3.x)
- 3.2 Runtime Integrity – all modules must follow the unified event lifecycle v3.2
Contributors and users should:
- communicate respectfully
- collaborate constructively
- provide clear, actionable feedback
- follow project architecture and guidelines
- protect user privacy
- avoid unsafe or unpredictable behavior
- maintain deterministic execution
- ensure all contributions remain 100% offline unless explicitly hybrid‑safe
- follow SECURITY FAMILY rules
- document changes clearly
- test modules in restricted, offline, and hybrid‑safe environments
- respect SUL 3.x license boundaries
- ensure compatibility with Runtime 3.2.0 and the unified event schema
- ensure outputs follow Result Schema v3.2
Strictly prohibited:
- harassment, insults, personal attacks
- discrimination of any kind
- sharing private or sensitive data
- adding cloud services, telemetry, or tracking
- bypassing SECURITY FAMILY rules
- weakening offline or hybrid‑safe guarantees
- malicious code or backdoors
- harmful, violent, or adult content
- remote code execution, dynamic imports, or unsafe eval
- attempts to circumvent restricted mode or identity rules
- injecting untrusted data into offline modules
- attempts to bypass the Quarantine Pipeline
- attempts to extract, reuse, or repackage runtime components (SUL violation)
- attempts to bypass 3.2 event lifecycle, routing, or module isolation rules
- attempts to interfere with VisionEngineV3 or hybrid routing safety
Violations may result in contribution removal, access restrictions, or license enforcement.
Contributors must:
- follow the SIRIUS architecture (runtime, modules, safety layers)
- ensure deterministic, offline‑safe and hybrid‑safe behavior
- test modules in restricted environments
- respect OWNER / FAMILY / STRANGER identity rules
- maintain compatibility with GAMA 3.2.x
- avoid unnecessary complexity
- ensure hybrid‑input safety
- include diagnostics logging where required
- validate knowledge packs and metadata
- follow event architecture standards (3.2.x)
- comply with SUL 3.x licensing rules
- ensure module outputs follow unified Result Schema v3.2
- ensure compatibility with VisionEngineV3 and the hybrid router
Maintainers will:
- enforce this Code of Conduct
- review contributions fairly
- ensure safety, privacy, and hybrid‑safe standards
- protect the integrity of the SIRIUS ecosystem
- reject unsafe or non‑offline features
- guide contributors toward best practices
- ensure module isolation and deterministic behavior
- verify SECURITY FAMILY and SUL compliance
- maintain architectural consistency across the 3.2.x ecosystem
- ensure all modules follow the 3.2 Runtime Pipeline
- ensure compatibility with VisionEngineV3 and Event Engine 3.2
This Code of Conduct applies to:
- GitHub repositories
- issues and pull requests
- discussions
- documentation
- community interactions
- all official SIRIUS LOCAL AI GAMA channels
- LAN Offline Bridge interactions
- Knowledge Pack contributions
- Vision, Schoolwork, Health, and Diagnostics modules
- hybrid‑safe envoy interactions
- all components covered by SUL 3.x
- all modules participating in the 3.2.x event lifecycle
- all modules interacting with VisionEngineV3
To report violations:
- open a private GitHub issue
- describe the problem clearly
- provide context if needed
Maintainers will review reports confidentially and take appropriate action.
GAMA 3.2.x enforces strict hybrid‑safe rules:
- all online data is low‑trust
- envoy output must pass through the Quarantine Pipeline
- offline core must remain air‑gapped
- no untrusted data may reach reasoning, packs, or vision modules
- hybrid modules must use deterministic, sandboxed execution
- no direct online → offline data flow is allowed
- all hybrid‑safe modules must follow Hybrid Safety Layer v3.2
- all cross‑module communication must follow Event Schema v3.2
- all vision events must follow VisionEngineV3 safety constraints
Any attempt to bypass hybrid‑safe rules is prohibited.
By contributing to SIRIUS LOCAL AI GAMA, you agree to:
- uphold this Code of Conduct
- protect the offline, safe, deterministic nature of the project
- respect hybrid‑safe boundaries
- support a respectful and inclusive environment
- follow all architecture, safety, privacy, and SUL licensing rules
- maintain compatibility with the 3.2.x runtime architecture
- ensure all modules behave deterministically and safely
SIRIUS LOCAL AI GAMA exists to provide safe, private, offline AI for everyone —
and this Code of Conduct ensures it stays that way.