py10x-core 0.1.12__tar.gz

py10x_core-0.1.12/.coveragerc

@@ -0,0 +1,6 @@
+[run]
+omit =
+	*/manual_tests/*
+	*/examples/*
+
+

py10x_core-0.1.12/.github/workflows/build.yml

@@ -0,0 +1,32 @@
+name: Publish py10x-core to PyPI (uv)
+on:
+  push:
+    tags:
+      - "v*"
+  workflow_dispatch:
+
+jobs:
+  publish:
+    name: Build and publish
+    runs-on: ubuntu-latest
+    permissions:
+      id-token: write
+      contents: read
+
+    steps:
+    - uses: actions/checkout@v4
+
+    - name: Set up uv
+      uses: astral-sh/setup-uv@v5
+      with:
+        enable-cache: true
+        cache-dependency-glob: "**/pyproject.toml"
+
+    - name: Set up Python
+      run: uv python install 3.12
+
+    - name: Build distributions
+      run: uv build
+
+    - name: Publish to PyPI
+      run: uv publish

py10x_core-0.1.12/.gitignore

@@ -0,0 +1,6 @@
+__pycache__
+.DS_Store
+.coverage
+htmlcov
+.venv
+uv.lock

py10x_core-0.1.12/.idea/.gitignore

@@ -0,0 +1,4 @@
+# Default ignored files
+/shelf/
+/workspace.xml
+/copilot.data.migration.*

py10x_core-0.1.12/.idea/inspectionProfiles/profiles_settings.xml

@@ -0,0 +1,7 @@
+<component name="InspectionProjectProfileManager">
+  <settings>
+    <option name="PROJECT_PROFILE" value="Default" />
+    <option name="USE_PROJECT_PROFILE" value="false" />
+    <version value="1.0" />
+  </settings>
+</component>

py10x_core-0.1.12/.idea/misc.xml

@@ -0,0 +1,10 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<project version="4">
+  <component name="Black">
+    <option name="sdkName" value="Python 3.13 (py10x)" />
+  </component>
+  <component name="ProjectRootManager" version="2" project-jdk-name="Python 3.11 (py10x)" project-jdk-type="Python SDK" />
+  <component name="PythonCompatibilityInspectionAdvertiser">
+    <option name="version" value="3" />
+  </component>
+</project>

py10x_core-0.1.12/.idea/modules.xml

@@ -0,0 +1,8 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<project version="4">
+  <component name="ProjectModuleManager">
+    <modules>
+      <module fileurl="file://$PROJECT_DIR$/.idea/py10x.iml" filepath="$PROJECT_DIR$/.idea/py10x.iml" />
+    </modules>
+  </component>
+</project>

py10x_core-0.1.12/.idea/py10x.iml

@@ -0,0 +1,18 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<module type="PYTHON_MODULE" version="4">
+  <component name="NewModuleRootManager">
+    <content url="file://$MODULE_DIR$/../cxx10x/core_10x/cmake-build-debug" />
+    <content url="file://$MODULE_DIR$/../cxx10x/infra_10x/cmake-build-debug" />
+    <content url="file://$MODULE_DIR$">
+      <excludeFolder url="file://$MODULE_DIR$/.venv" />
+    </content>
+    <content url="file://$MODULE_DIR$/../rio">
+      <excludeFolder url="file://$MODULE_DIR$/../rio/.venv" />
+    </content>
+    <orderEntry type="jdk" jdkName="Python 3.11 (py10x)" jdkType="Python SDK" />
+    <orderEntry type="sourceFolder" forTests="false" />
+  </component>
+  <component name="TestRunnerService">
+    <option name="PROJECT_TEST_RUNNER" value="py.test" />
+  </component>
+</module>

py10x_core-0.1.12/.idea/ruff.xml

@@ -0,0 +1,7 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<project version="4">
+  <component name="RuffConfigService">
+    <option name="runRuffOnSave" value="true" />
+    <option name="useRuffServer" value="true" />
+  </component>
+</project>

py10x_core-0.1.12/.idea/runConfigurations/collection_editor__rio_.xml

@@ -0,0 +1,25 @@
+<component name="ProjectRunConfigurationManager">
+  <configuration default="false" name="collection_editor (rio)" type="PythonConfigurationType" factoryName="Python">
+    <module name="py10x" />
+    <option name="ENV_FILES" value="" />
+    <option name="INTERPRETER_OPTIONS" value="" />
+    <option name="PARENT_ENVS" value="true" />
+    <envs>
+      <env name="UI_PLATFORM" value="Qt6" />
+    </envs>
+    <option name="SDK_HOME" value="" />
+    <option name="WORKING_DIRECTORY" value="$PROJECT_DIR$/ui_10x/examples" />
+    <option name="IS_MODULE_SDK" value="true" />
+    <option name="ADD_CONTENT_ROOTS" value="true" />
+    <option name="ADD_SOURCE_ROOTS" value="true" />
+    <EXTENSION ID="PythonCoverageRunConfigurationExtension" runner="coverage.py" />
+    <option name="SCRIPT_NAME" value="$PROJECT_DIR$/ui_10x/examples/collection_editor.py" />
+    <option name="PARAMETERS" value="" />
+    <option name="SHOW_COMMAND_LINE" value="false" />
+    <option name="EMULATE_TERMINAL" value="false" />
+    <option name="MODULE_MODE" value="false" />
+    <option name="REDIRECT_INPUT" value="false" />
+    <option name="INPUT_FILE" value="" />
+    <method v="2" />
+  </configuration>
+</component>

py10x_core-0.1.12/.idea/ryecharm-overrides.xml

@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<project version="4">
+  <component name="insyncwithfoo.ryecharm.configurations.ruff.Override">
+    <option name="names">
+      <map>
+        <entry key="crossPlatformExecutableResolution" value="true" />
+        <entry key="executable" value="true" />
+      </map>
+    </option>
+  </component>
+</project>

py10x_core-0.1.12/.idea/ryecharm.xml

@@ -0,0 +1,6 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<project version="4">
+  <component name="insyncwithfoo.ryecharm.configurations.ruff.Local">
+    <option name="executable" value="ruff" />
+  </component>
+</project>

py10x_core-0.1.12/.idea/vcs.xml

@@ -0,0 +1,6 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<project version="4">
+  <component name="VcsDirectoryMappings">
+    <mapping directory="" vcs="Git" />
+  </component>
+</project>

py10x_core-0.1.12/AGENTS.md

@@ -0,0 +1,99 @@
+## py10x-core – Guide for AI Agents
+
+This file is a **meta-guide** for tools and AI agents working in this repo.  
+It points to canonical docs and records only the minimal, project-specific rules that agents must obey.
+
+---
+
+## 1. Where canonical knowledge lives
+
+- **High-level overview**: see `README.md`.
+- **Installation / environment details**: see `INSTALLATION.md`.
+- **Concepts, traitables, getters/setters, storage, execution modes**: see `GETTING_STARTED.md`.
+- **Contribution workflow, code style, test layout**: see `CONTRIBUTING.md`.
+- **Security, changelog, community**: see `SECURITY.md`, `CHANGELOG.md`, `CODE_OF_CONDUCT.md`.
+- **Low-level traitable implementation details**: see `core_10x/traitable.py` and existing tests in `core_10x/unit_tests/`.
+
+Agents should **link to and rely on those files**, not duplicate them here.
+
+---
+
+## 2. Environment & tooling rules for agents
+
+- **Use UV and the project venv**
+  - Assume development happens via `uv` and a local `.venv`.
+  - When suggesting or running commands, prefer:
+    - `uv sync --all-extras` for dependency setup.
+    - `uv run ...` for Python tooling (`pytest`, `ruff`, etc.).
+
+- **Respect C++ / cxx10x backend**
+  - Treat `py10x-kernel` / `py10x-infra` (from `cxx10x`) as **opaque C++ backends**.
+  - Do **not** try to reimplement or bypass them in Python; use the public Python APIs.
+
+- **MongoDB & UI assumptions**
+  - Some tests require a local passwordless MongoDB on port 27017.
+  - UI work should assume Rio/Qt backends as configured in `INSTALLATION.md` / `pyproject.toml`.
+
+For any environment ambiguity, favor the patterns and instructions in `INSTALLATION.md` and `CONTRIBUTING.md`.
+
+---
+
+## 3. Traitable invariants agents must preserve
+
+Most important invariants are around `core_10x.traitable.Traitable` and are documented in `GETTING_STARTED.md` and `core_10x/traitable.py`.  
+Agents must **not** violate the following:
+
+- **Construction & initialization**
+  - **Never override `__init__`** on subclasses of `Traitable`; use `__post_init__` instead.
+  - Only use `_replace=True` in constructors when you intentionally want to update non-ID traits of an existing entity with the same ID.
+
+- **Trait definitions**
+  - Always provide a **type annotation** for each trait, and use `T(...)` / `RT(...)` / `M(...)` as in the existing code.
+  - Do not change the meaning of ID vs ID_LIKE vs regular vs runtime traits; follow the patterns and explanations in `GETTING_STARTED.md` (“Core Concepts”, “Object Identification System”).
+
+- **Getters / setters / converters**
+  - Follow the existing naming contracts (`*_get`, `*_set`, `*_from_str`, `*_from_any_xstr`).
+  - Keep getters side-effect free; put validation / cross-field updates into setters.
+
+- **Storage & identity**
+  - Maintain the shared-by-ID semantics: instances with the same ID share trait values.
+  - Respect storage contexts (`CACHE_ONLY`, `MongoStore.instance(...)`) and do not introduce ad-hoc persistence mechanisms.
+
+Before changing anything under `core_10x/traitable.py` or traitable-heavy code, agents should:
+- Read the relevant sections of `GETTING_STARTED.md`.
+- Scan the corresponding tests in `core_10x/unit_tests/` to mirror existing patterns.
+
+---
+
+## 4. Testing & layout expectations
+
+- **Test placement**
+  - Core logic tests belong in `core_10x/unit_tests/`.
+  - UI tests belong in `ui_10x/unit_tests/` or backend-specific test folders.
+  - Infra/storage tests belong in `infra_10x/unit_tests/`.
+
+- **How to run tests / lints**
+  - Prefer:
+    - `uv run pytest` (or narrower paths) for tests.
+    - `uv run ruff check .` and `uv run ruff format .` for linting/formatting.
+
+When adding new functionality, agents should **add or update tests** in the appropriate suite following nearby examples, rather than inventing new test patterns.
+
+---
+
+## 5. Default agent behavior in this repo
+
+- **Prefer existing patterns over new abstractions**
+  - When in doubt, copy the style and structure from nearby code and tests instead of inventing a new mini-framework.
+
+- **Minimize duplication**
+  - If some behavior is already described in `README.md`, `GETTING_STARTED.md`, or tests, link or reference it rather than restating it.
+
+- **Be conservative with Traitable changes**
+  - Any changes in this package are potentially high impact.
+  - Such changes should:
+    - Be as small/local as possible.
+    - Include focused tests.
+    - Keep public semantics consistent with existing docs unless the change is explicitly a breaking redesign.
+
+

py10x_core-0.1.12/CHANGELOG.md

@@ -0,0 +1,198 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [0.1.12] - 2026-02-12
+### Changed
+- **Package rename:** This package is now **py10x-core**. Updated throughout: `pyproject.toml`, README, NOTICE, docs, and code references.
+
+## [0.1.11] - 2026-02-11
+
+### Added
+- **uv-sync installable command**: `uv_sync` available as an installable CLI command when using dev_10x.
+
+### Changed
+- **C++ package rename**: The native C++ dependency is now **py10x-kernel**. Updated throughout: `pyproject.toml`, README, NOTICE, docs, and code references; license URL now `py10x_kernel`.
+- **dev_10x.uv_sync**: Reduced verbosity; avoids unnecessary rebuilds; re-exec on Windows for correct environment; improved behavior when locating `pyproject.toml` (checks current directory).
+- **dev_10x.uv_sync**: Fixed info message for user profile.
+- **Documentation**: README updates and merged redundant sections.
+
+## [0.1.10] - 2026-02-09
+
+### Added
+- **Dynamic versioning**: Version read from `dev_10x.version`; `core_10x`, `infra_10x`, and `ui_10x` expose `__version__` with fallback when `dev_10x` is not installed.
+- **dev_10x.uv_sync**: Profile-based `uv sync` helper (e.g. `user`, `domain-dev`, `py10x-dev`, `py10x-core-dev`) that injects `[tool.uv.sources]` for `py10x-core`, `py10x-kernel`, and `py10x-infra` from git or local paths.
+- **Version tests**: `core_10x/unit_tests/test_version.py` and `infra_10x/unit_tests/test_version.py` assert package versions are set (no `0.0.0` or `unknown`).
+
+### Changed
+- **Documentation links**: Git and doc references updated from `10X-LLC` to `10x-software`; GETTING_STARTED, INSTALLATION, README, and CONTRIBUTING use full GitHub URLs where appropriate.
+- **C++ dependency constraints**: Relaxed from exact (`==0.1.9`) to `>=0.1.9,<0.2.0` to allow minor non-breaking releases.
+- **Build**: `pyproject.toml` uses `dynamic = ["version"]` and version-file; dev dependencies include `tomlkit` and `licensecheck`; package list includes `dev_10x`.
+
+## [0.1.9] - 2026-02-08
+
+### Added
+- **Verifiers documentation**: GETTING_STARTED.md section “Verifiers (Validation on verify() and save())” describing `*_verify` methods, that they run only on `verify()` or `save()` (not on assignment), and examples.
+- **Verifier tests**: `test_verify_success`, `test_verify_fails_when_verifier_returns_error`, `test_verify_not_called_on_set`, and `test_serialize_runtime_endogenous_reference` in `core_10x/unit_tests/test_traitable.py`.
+
+### Changed
+- **Trait**: `Trait` now uses a custom metaclass and `__slots__`; default `fmt` uses `t_def.fmt or trait.s_fmt`; `s_ui_hint` and `s_fmt` moved to class-level defaults.
+- **pyproject**: Version set to 0.1.9; dependency pins for py10x c++ packages.
+
+## [0.1.8] - 2026-02-06
+
+### Added
+- **Traitable.verify()**: Implemented using `BTraitable.verify_value(trait)`; checks `NOT_EMPTY` and per-trait `f_verify`; error header via `RC.prepend_error_header()`.
+- **TsStore.populate()**: New method for server-side population of params (e.g. `_who`, `_at`) in serialized data; subclasses may override.
+
+### Changed
+- **Attic**: Unused code moved to `core_10x/attic/` (backbone, vault, data_domain, entity, package_manifest).
+- Package and documentation refer to the pip-installable package as **py10x-core** (hyphen); repo path remains **py10x**.
+- README: early-preview disclaimer; licensing/attribution and authors sections updated.
+- CHANGELOG: version order (newest first), 0.1.7 and 0.1.8 entries.
+
+## [0.1.7] - 2026-02-05
+
+### Changed
+- README image URL for PyPI compatibility
+- OS compatibility classifiers (Windows, Linux, MacOS)
+
+## [0.1.6] - 2026-02-05
+
+### Changed
+- OS compatibility tagging
+- Inclusion of NOTICE
+
+## [0.1.5] - 2026-02-05
+
+### Changed
+- README image URL for PyPI compatibility
+- Development status classifier set to Beta
+- CI: uv cache keyed by pyproject.toml; optional uv lock --upgrade step removed
+
+## [0.1.4] - 2026-02-04
+
+### Added
+- **Traitable lifecycle**: `__post_init__` hook for subclass customization; overriding `__init__` is no longer allowed (use `__post_init__` instead)
+- **Traitable updates**: `_replace` constructor parameter and `new_or_replace()` for updating non-ID traits of an existing entity by ID
+- **AsOf context**: Time-travel queries for traitables that keep history; generalized to subclasses and all history-keeping traitable classes; graceful handling for classes that do not keep history
+- **Per-class store association**: Different store (e.g. TsStore) per traitable class via ts-class association; `use_ts_store_per_class` and related configuration
+- **TsStore / TsCollection**: Abstract store API; `TsStore` resource type, `TsUnion`; `store_class()` registration; `TsDuplicateKeyError`; collection `copy_to`
+- **Backbone and vault**: `core_10x.backbone` (backbone_store, vault, namespace, bound_data_domain) and `core_10x.vault` (vault, vault_user, vault_traitable, sec_keys) for credentials and lightweight backbone
+- **TraitableHeir**: Traitable that delegates trait values from a grantor traitable (`_grantor`); heir getters and serialization that omit unset grantor traits
+- **Environment variables**: `core_10x.environment_variables` with typed env vars, classproperty getters, optional `*_apply` hooks, and `AssertVar` for required vars
+- **Rdate**: Business-day roll rules (preceding, following, modified preceding/following) and calendar-aware date utilities in `core_10x.rdate`
+- **NamedConstant**: `core_10x.named_constant` with `NamedConstant`, `NamedConstantTable`, and `cls.item(symbol_name)` lookup
+- **Testlib**: Shared test utilities in `core_10x.testlib` (test_store, traitable_history_tests, ts_tests)
+- **Trait modification**: Unset trait default in trait modification; support `None` as `flags_to_set` (clearer than `BFlags(0)`)
+- **UI**: TraitableView omits hints with `widget_type` NONE; `collection_editor_app` in `ui_10x.apps`
+- **AGENTS.md**: Meta-guide for AI agents and tools working in the repo (canonical docs, tooling, traitable invariants, test layout)
+
+### Changed
+- **Package and branding**: C++ packages renamed to `py10x_kernel` and `py10x_infra` (from core_10x_i / infra_10x_i); email domain updates
+- **Python**: Requires Python 3.11+ (up to <3.13) per pyproject.toml
+- **Rio UI**: Upgraded to Rio 0.12
+- **Dependencies**: Version bumps for numpy, cryptography, pymongo, etc.; keyring and requests added where needed
+- **Lint/format**: Ruff rules relaxed and applied consistently
+
+### Fixed
+- `existing_instance_by_id(_throw=False)` for runtime objects when instance does not exist (with C++ update)
+- AsOf context exception handling when AsOf threw on enter (invalid BCP left on stack)
+- Revision handling for immutable entities
+- Rejection of unstable class names containing `__main__` or `<locals>`
+- Filter serialization
+- Runtime anonymous traitable traits no longer required to be embedded
+- Runtime endogenous serialization and related checks (tests)
+- Improved C++ exception traces
+
+## [0.1.3] - (pre-release development)
+
+No separate changelog; see Version History below.
+
+## [0.1.2] - 2024-12-19
+
+### Added
+- Initial pre-release
+- Core data modeling with `Traitable` framework
+- Trait-based traitable definitions with type safety
+- Object identification system (endogenous/exogenous traitables)
+- Serialization and deserialization framework
+- Storage integration with MongoDB store
+- Cross-platform UI components focused on traitable editing (Rio and Qt6 backends)
+- MongoDB integration via `infra_10x`
+- Built-in caching system for trait values and entity state
+- Manual resource management using context managers
+- Comprehensive test suite
+
+### Core Features
+- **Traitable Framework**: Traitable modeling with traits, validation, and persistence
+- **Object Identification**: Endogenous traitables (with ID traits) share trait values globally by ID, exogenous traitables get auto-generated UUIDs
+- **Dependency Graph**: Automatic computation of trait values and dependency tracking
+- **Seamless UI Framework**: Cross-platform components with automatic framework selection
+- **Storage Integration**: MongoDB store with revision tracking and flexible data persistence
+- **Infrastructure**: Manual resource management (enterprise resource management planned for future release)
+
+### UI Components
+- Focused on traitable editing and management
+- CollectionEditor for traitable collections
+- TraitableEditor for individual traitable editing
+- LineEdit, TextEdit, PushButton, Label
+- Layout components (VBoxLayout, HBoxLayout, FormLayout)
+- Dialog, MessageBox, GroupBox
+- ListWidget, TreeWidget, CalendarWidget
+- ScrollArea, Splitter, Spacer
+- RadioButton, CheckBox, Separator
+
+### Infrastructure
+- Storage integration with MongoDB store
+- Collection operations (CRUD, querying, indexing)
+- Revision-based conflict resolution
+- Manual resource management using context managers
+
+### Dependencies
+- Python 3.11+ support
+- Core dependencies: numpy, python-dateutil, cryptography
+- C++ implementation: our core and infra packages
+- UI backends: Rio UI, PyQt6
+- Infrastructure: pymongo
+- Development: pytest, ruff, playwright
+
+---
+
+## Version History
+
+- **0.1.12**: This package rename to `py10x-universe` → `py10x-core`; docs updated
+- **0.1.11**: C++ package rename `py10x-core` → `py10x-kernel`; `uv-sync` installable command; uv_sync verbosity/rebuilds/Windows/doc fixes
+- **0.1.10**: Dynamic versioning (dev_10x), dev_10x.uv_sync, version tests; doc links to 10x-software; C++ deps relaxed to >=0.1.9,<0.2.0
+- **0.1.9**: Verifiers docs and tests; Trait metaclass/slots and fmt handling; pyproject 0.1.9
+- **0.1.8**: Traitable.verify(), TsStore.populate(), RC.prepend_error_header; attic move; entity_filter removed; naming (`py10x-universe`, `py10x-core`, `py10x-infra`); README disclaimer
+- **0.1.7**: OS classifiers, README image URL
+- **0.1.6**: NOTICE, OS tagging, README image
+- **0.1.5**: Beta classifier, CI cache
+- **0.1.4**: Pre-release; AsOf, per-class stores, backbone/vault, TraitableHeir, env vars, rdate, testlib, lifecycle and trait-modification improvements
+- **0.1.3**: Pre-release development version
+- **0.1.2**: Pre-release development version
+- **0.1.1**: Pre-release development version
+- **0.1.0**: Initial development version
+
+## Migration Guide
+
+### From Development Versions
+
+No migration from previous versions is necessary - package versions will automatically be updated when installing.
+
+### Breaking Changes
+
+- **0.1.12**: This package renamed: use **py10x-core** instead of `py10x-universe` in dependencies, CI, or local installs.
+- **0.1.11**: C++ dependency renamed: use **py10x-kernel** instead of `py10x-core` in dependencies, CI, or local installs.
+- **0.1.4**: Subclasses of `Traitable` must not override `__init__`; use `__post_init__` for customization. Python 3.10 no longer supported (3.11+ required). C++ packages are now `py10x-core` and `py10x-infra` (rename from core_10x_i / infra_10x_i if you referenced them directly).
+- **0.1.2 and earlier**: Initial pre-release; no breaking changes from previous versions.
+
+
+## Acknowledgments
+
+- Relies on py10x-kernel and py10x-infra packages containing the underlying C++ implementation
+- UI components based on Rio and Qt6 frameworks, focused on traitable editing and management

py10x_core-0.1.12/CODE_OF_CONDUCT.md

@@ -0,0 +1,93 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+## Reporting
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at [Discord](https://discord.gg/m7AQSXfFwf). All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at:
+
+- **Email**: conduct@10x-software.org
+
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at [https://www.contributor-covenant.org/faq][FAQ]. Translations are available at [https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations