aether-quant 4.12.3__tar.gz → 5.4.8__tar.gz

aether_quant-5.4.8/.devcontainer/README.md

@@ -0,0 +1,12 @@
+# .devcontainer
+
+GitHub Codespaces / VS Code Dev Container definition for Aether Quant
+(`devcontainer.json`), plus a `dind-v1-test/` variant used to test
+Docker-in-Docker setups.
+
+The container is the `mcr.microsoft.com/devcontainers/python:3.11` image with
+an sshd feature (Codespaces training access) and a post-create command that
+installs the CPU PyTorch build plus both requirements files. This is the
+environment behind this project's own "train in the cloud" convention — see
+[`RUNBOOK.md`](../RUNBOOK.md) and
+[`development/infrastructure.md`](../development/infrastructure.md).

aether_quant-5.4.8/.githooks/README.md

@@ -0,0 +1,14 @@
+# .githooks
+
+Optional git hooks, opt-in per clone (never auto-installed on a fresh
+checkout):
+
+```powershell
+git config core.hooksPath .githooks
+```
+
+Currently one hook: `pre-commit`, which invokes `aq secrets-check`
+(`execution/secret_scan.py`) and blocks the commit if a populated secret
+field is about to land in the tracked `lean.json` or a real `.env` file is
+tracked by git. This is what actually stops a secret from being committed —
+see [`SECURITY.md`](../SECURITY.md) for the reporting policy.

aether_quant-5.4.8/.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,50 @@
+---
+name: Bug report
+about: Something is broken, wrong, or behaves differently than documented.
+title: "[bug] "
+labels: ["bug"]
+---
+
+## What happened
+
+<!-- One or two sentences. Lead with the observable failure. -->
+
+## Where
+
+<!-- File(s)/module(s)/CLI command(s) involved, e.g. `aq evaluate --rank-book`, portfolio/book_construction.py -->
+
+## Expected vs actual
+
+- **Expected:**
+- **Actual:**
+
+## Reproduction
+
+<!--
+  Minimal steps from a clean clone. Include the exact command(s) and any
+  config.json keys involved (`aq config get <dotted.key>` output helps).
+-->
+
+```text
+<commands / steps>
+```
+
+## Evidence
+
+<!-- Test output, log excerpt, or backtest artifact reference. Paste the
+smallest relevant slice; link large files instead of pasting them. -->
+
+```text
+<output>
+```
+
+## Environment
+
+- OS:
+- Python version:
+- Commit / tag:
+
+## Checklist
+
+- [ ] I ran `aq test` and can name the failing/passing state
+- [ ] I checked `development/Problems.md` for a known entry covering this

aether_quant-5.4.8/.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Question / usage help
+    url: https://github.com/leon1706-lol/Aether-quant/discussions
+    about: Ask here before opening an issue — most setup questions are answered in README.md, development/infrastructure.md, or CONTRIBUTING.md.
+  - name: Security vulnerability
+    url: https://github.com/leon1706-lol/Aether-quant/security/advisories/new
+    about: Report privately via GitHub Security Advisories — do NOT open a public issue (see SECURITY.md).

aether_quant-5.4.8/.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,32 @@
+---
+name: Feature request
+about: A new subsystem, module, CLI capability, or behavioral improvement.
+title: "[feature] "
+labels: ["enhancement"]
+---
+
+## Problem to solve
+
+<!-- What can't you do today? Describe the user-facing need, not the implementation. -->
+
+## Proposed behavior
+
+<!-- What should exist after this ships? Include the intended CLI/config surface if any:
+     new `aq` command/flag? new `phase_v2.*` config block (remember: flags ship `false`
+     until verified)? new output artifact? -->
+
+## Scope guardrails
+
+<!-- This repo's conventions shape every feature. Confirm how yours fits: -->
+
+- [ ] Ships backward-compatible: additive `None`-default parameters / default-off config keys; an unmodified `config.json` reproduces today's behavior exactly.
+- [ ] Testable without Lean: pure logic lives in a package module, not `main.py`; tests planned/attached.
+- [ ] Docs plan: README/sub-readmes + `development/Changelog.md` entry (and `development/architecture.md` when it changes system structure).
+
+## Alternatives considered
+
+<!-- What did you rule out and why? -->
+
+## Extra context
+
+<!-- Related Problems.md entries (#N), prior Changelog rounds, or backtest evidence. -->

aether_quant-5.4.8/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,37 @@
+<!-- Title style: `V<version> <short what-and-why>` for release-bound PRs,
+     matching the repo's commit history; otherwise a plain descriptive title. -->
+
+## What & why
+
+<!-- One paragraph: what changed and the problem/round it belongs to.
+     Reference development/Problems.md entries (#N) where applicable. -->
+
+## Changes
+
+-
+-
+
+## Behavior contract
+
+<!-- This repo's hard rule: prove what changed and for whom. -->
+
+- [ ] Default behavior is byte-identical when new flags/params are absent (`None`-default / default-off convention), **or** the behavior change is intentional and listed below:
+  - <!-- intentional changes here -->
+- New config keys: <!-- `phase_v2.*` keys + defaults, or "none" -->
+
+## Verification
+
+<!-- How was this confirmed? The suite must be green before review. -->
+
+- [ ] `aq test` green (N passed): <!-- paste count -->
+- New tests: <!-- files + what they pin down -->
+- Manual checks: <!-- CLI dry-runs, real-data spot checks -->
+- Real Lean backtest: <!-- not run in PRs by convention; note if one is required before merge -->
+
+## Docs updated
+
+- [ ] README / sub-package README
+- [ ] `development/Changelog.md` (append-only entry)
+- [ ] `development/Problems.md` (if a bug was found/fixed)
+- [ ] `development/architecture.md` / `development/infrastructure.md` (if structure/services changed)
+- [ ] Obsidian vault regenerated (`generate_code_graph.py` → `regenerate_vault.py --append-handoff`)

aether_quant-5.4.8/.github/workflows/ci.yml

@@ -0,0 +1,158 @@
+name: CI
+
+# V5.3.9 - deep CI suite: windows+ubuntu pytest matrix with a calibrated
+# coverage fail-under gate (82% measured - 2), ruff lint, the full webui
+# vitest suite, an offline CLI smoke battery, and workflow self-validation.
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+# V5.4.2 - cancel superseded runs on rapid-fire pushes (ported from Aether-Vault)
+concurrency:
+  group: ci-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  python-tests:
+    runs-on: ${{ matrix.os }}
+    timeout-minutes: 30
+    strategy:
+      fail-fast: false
+      matrix:
+        os: [ubuntu-latest, windows-latest]
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.11"
+          cache: "pip"
+
+      - name: Syntax-check main.py (no Lean runtime available in CI - see development/Problems.md #69)
+        run: python -m py_compile main.py
+
+      - name: Install dependencies
+        run: |
+          pip install -r requirements/requirements.txt -r requirements/requirements-dev.txt
+          pip install pytest-cov
+
+      - name: Run full test suite with coverage gate
+        run: >
+          pytest -m "not lean_backtest" -ra
+          --cov --cov-report=term-missing --cov-report=xml
+          --cov-fail-under=80
+
+      - name: Upload coverage artifact
+        if: matrix.os == 'ubuntu-latest'
+        uses: actions/upload-artifact@v4
+        with:
+          name: coverage-xml
+          path: coverage.xml
+
+  python-lint:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.11"
+
+      # V5.3.11 FIX: bare `ruff check .` — NOT `aq test --ruff` (which
+      # requires importing aq_cli → pandas via the full package chain, but
+      # this job intentionally has a minimal environment). Local devs use
+      # `aq test --ruff`; CI uses bare ruff for speed.
+      # V5.4.7: ruff is PINNED - the previous unbounded range let new ruff
+      # releases add rules and break CI independently of any repo change.
+      - name: Install ruff
+        run: pip install "ruff==0.16.4"
+
+      - name: Ruff check (E/F ruleset calibrated in pyproject.toml)
+        run: ruff check .
+
+      - name: Syntax-check main.py
+        run: python -m py_compile main.py
+
+  dependency-audit:
+    runs-on: ubuntu-latest
+    timeout-minutes: 15
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.11"
+
+      - name: Install pip-audit
+        run: pip install pip-audit
+
+      - name: Audit runtime dependencies for known CVEs
+        run: |
+          pip install -r requirements/requirements.txt
+          pip-audit --requirement requirements/requirements.txt --desc
+
+      - name: Audit dev dependencies for known CVEs
+        run: |
+          pip-audit --requirement requirements/requirements-dev.txt --desc
+
+  webui-tests:
+    runs-on: ubuntu-latest
+    timeout-minutes: 20
+    defaults:
+      run:
+        working-directory: webui
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-node@v4
+        with:
+          node-version: "20"
+          cache: "npm"
+          cache-dependency-path: webui/package-lock.json
+
+      - run: npm ci
+      - run: npx tsc -b
+      - run: npx oxlint
+      # V5.3.9 - the full frontend suite finally runs in CI too.
+      - run: npx vitest run --pool=threads
+      - run: npm run build
+
+  cli-smoke:
+    runs-on: ubuntu-latest
+    timeout-minutes: 15
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.11"
+
+      - name: Install package editable
+        run: |
+          pip install -r requirements/requirements.txt
+          pip install -e .
+
+      - name: CLI smoke battery (offline, deterministic)
+        run: |
+          aq --help > /dev/null
+          aq evaluate --help > /dev/null
+          aq config get phase1.universe.name
+          aq secrets-check
+
+  workflows-lint:
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    steps:
+      - uses: actions/checkout@v4
+
+      # V5.3.10 - single-step pinned install + validate: the previous two-step
+      # pattern (PATH append, then bare `actionlint`) failed with
+      # "command not found" on the runner. Pinned to v1.7.7 for
+      # reproducibility (meta-tested in tests/test_ci_workflows.py).
+      - name: Validate workflow files (actionlint v1.7.7)
+        run: |
+          curl -sSL -o actionlint.tar.gz \
+            https://github.com/rhysd/actionlint/releases/download/v1.7.7/actionlint_1.7.7_linux_amd64.tar.gz
+          tar -xzf actionlint.tar.gz actionlint
+          ./actionlint -no-color -verbose

{aether_quant-4.12.3 → aether_quant-5.4.8}/.github/workflows/release.yml

@@ -9,6 +9,28 @@ on:
     tags: ["v*.*.*"]
 
 jobs:
+  # V5.3.9 - NON-BLOCKING visibility job: runs the full offline suite on the
+  # tagged commit so release-time gaps are visible right next to the
+  # artifacts. Deliberately NOT wired into `needs:` of the publish jobs
+  # (user decision): releases proceed regardless; read this job's result to
+  # see where the gaps are.
+  tag-tests:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.11"
+          cache: "pip"
+
+      - name: Install dependencies
+        run: |
+          pip install -r requirements/requirements.txt -r requirements/requirements-dev.txt
+
+      - name: Run full offline suite (visibility only - does not gate the release)
+        run: pytest -m "not lean_backtest" -ra
+
   publish-pypi:
     runs-on: ubuntu-latest
     environment: pypi # must match the Environment name configured in PyPI's Trusted Publisher setup
@@ -78,3 +100,26 @@ jobs:
           # image, so the npm ci/pip install layers survive between runs.
           cache-from: type=gha
           cache-to: type=gha,mode=max
+
+  # Creates the GitHub Release itself, once per tag. Notes are auto-generated
+  # (commit list since the previous tag); the body additionally points at the
+  # matching development/Changelog.md entry, which is this repo's canonical
+  # per-version record (see CONTRIBUTING.md's versioning section).
+  github-release:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Create GitHub Release with changelog link
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: |
+          TAG="${GITHUB_REF_NAME}"
+          VERSION="${TAG#v}"
+          BODY="See [development/Changelog.md](https://github.com/${GITHUB_REPOSITORY}/blob/main/development/Changelog.md) for the full entry for \`V${VERSION}\` and every prior release."
+          gh release create "$TAG" \
+            --title "Aether Quant ${TAG}" \
+            --notes "$BODY" \
+            --generate-notes

{aether_quant-4.12.3 → aether_quant-5.4.8}/.gitignore

@@ -73,6 +73,14 @@ ml/versions/
 # rank-pivot roadmap work, development/Problems.md#43) - a local backup,
 # never meant to be committed.
 ml/_backup_pre_rank_pivot/
+# Manual pre-smoke-test snapshot (rollback point before the V5.2.8
+# gate_aware_ranking_weights Codespace smoke test, development/Problems.md#94)
+# - a local backup, never meant to be committed.
+ml/_backup_pre_v528_gate_aware_smoke_test/
+# Manual pre-full-retrain snapshot (rollback point before the V5.2.9
+# full production retrain with gate_aware_ranking_weights enabled) - a
+# local backup, never meant to be committed.
+ml/_backup_pre_v529_full_retrain/
 ml/model.pt
 ml/scaler.pkl
 ml/*.pkl
@@ -119,6 +127,24 @@ visualization/state.json
 visualization/scene.json
 visualization/topology_state.json
 visualization/grafana/
+# V5.2.2 book-history diagnostic log - per-date live book selections
+# (roles/raw scores/weights) from a real backtest. Off by default
+# (phase_v2.diagnostics.book_history.enabled), but gitignored regardless
+# so an accidental enable+commit can't leak it - same rationale as the
+# ml/evaluation/ reports below. Wildcarded (not just the exact filename) so
+# the per-run isolated extracts used for reconciliation (e.g.
+# book_history_v524_only.jsonl, book_history_v525_only.jsonl - see
+# development/Problems.md #91) are covered too; book_history_v524_only.jsonl
+# was committed in V5.2.4's commit before this gap was caught, untracked
+# alongside this fix (V5.2.5).
+visualization/book_history*.jsonl
+
+# Generated evaluation reports (aq evaluate --...) - reveal historical
+# model selections/scores (book composition by date, rank scores,
+# calibrated thresholds), effectively derived model IP, not source - same
+# rationale as the ml/*_model.json weight-artifact rules above.
+# Regenerable by re-running the command that wrote them.
+ml/evaluation/
 
 # Logs and temporary files
 .coverage
@@ -142,6 +168,9 @@ webui/dist/
 # scripts/profile_inference.py's pstats dump - regenerable output, not source
 scripts/profile_inference_output*.txt
 scripts/profile_subsystems_output*.txt
+# scripts/order_events_audit.py's output dump (V5.3.1) - regenerable
+# diagnostic output, not source.
+scripts/order_events_audit_output*.txt
 
 # cpp_inference_ext/'s compiled build artifacts - regenerable via
 # `pip install -e cpp_inference_ext/`, never source. The .pyd itself is

aether_quant-5.4.8/AGENTS.md

@@ -0,0 +1,144 @@
+# Aether Quant — Agent Instructions
+
+## What this project is
+
+Aether Quant is a dynamic, self-adapting algorithmic trading system built on
+QuantConnect Lean and PyTorch. An ensemble of neural models predicts direction,
+return magnitude, volatility, and cross-sectional rank for every asset every
+day, driving a market-neutral long/short book validated end-to-end inside Lean,
+with a kill switch, position reconciliation, and controlled retraining in front
+of live trading.
+
+## Essential commands
+
+```powershell
+pip install -e .          # register `aq` CLI from source (pyproject.toml)
+aq test                   # full pytest suite (~2929 tests), refreshes badge
+aq test --risk            # risk subsystem only (subsystem filtered)
+aq evaluate               # offline rank evaluation
+aq backtest               # real Lean backtest (requires Docker, ~1hr+)
+ruff check .              # linter (must pass before commit)
+```
+
+## File layout
+
+| Path | What lives here |
+|---|---|
+| `main.py` | Lean algorithm entry point — **zero unit test coverage by design**, only runs inside Lean |
+| `risk/` | Position sizing, portfolio slicing, kill switch, correlation |
+| `portfolio/` | Book construction, book neutrality, HRP, risk parity, options strategies |
+| `execution/` | Order gate, cost model, reconciliation |
+| `features/` | Pure feature functions (technical, macro, alt data, options greeks) |
+| `inference/` | Model loading, exported model reader, batch inference |
+| `moe/` | Mixture-of-experts gating and routing |
+| `train.py` | Core training loop (dataset, ranking losses, walk-forward, export) |
+| `train_*.py` | Specialized trainers (multitask, sequence, gating, topology, strategy selector) |
+| `evaluation/` | Offline evaluation: rank book simulator, Monte Carlo, calibration tools |
+| `retraining/` | Candidate promotion: validation gate, backtest gate, artifact versioning |
+| `experience/` | Experience pipeline: Redis queue, Postgres worker, session summaries |
+| `audit/` | Tamper-evident audit log (hash-chained) |
+| `monitoring/` | FastAPI server, neural network state, evaluation state, Grafana dashboards |
+| `notifications/` | Telegram alerts (pure/format/worker split) |
+| `data_pipeline/` | Yahoo backfill, FRED backfill, bar synthesis, fetching |
+| `regime/` | Market regime detection |
+| `topology/` | Market topology overlay |
+| `json_safety.py` | Shared JSON-safety helpers (finite-safe, atomic writes) |
+| `aq_cli.py` | CLI entry point: all `aq` subcommands, subsystem test routing |
+| `tests/` | pytest suite — one file per module, round files for cross-module regressions |
+| `development/` | Architecture docs, Changelog, Problems.md, backups |
+| `webui/` | React dashboard (TypeScript) |
+
+## Code conventions
+
+- **Pure, testable modules over `main.py` logic.** Anything needing tests must
+  be a pure function importable by both `main.py` and `tests/`.
+- **One test file per source module.** Cross-module regressions go in round
+  files: `test_v543_new_features.py`, `test_rl_sizing_v541.py`, etc.
+- **Register every new test file** in `aq_cli.py`'s `_SUBSYSTEM_TEST_FILES`
+  dict immediately when you create it — otherwise it is silently skipped by
+  subsystem-filtered runs (`aq test --risk`, `--portfolio`, etc.).
+- **Never commit changes that break the full test suite.** Run `aq test` after
+  every code change; ruff must also be clean.
+- **Round files at the same commit as their fixes.** Test + fix together, never
+  separately.
+- **`aq test` only, never bare `pytest` from root** — see `development/Problems.md`
+  #8 and `tests/README.md`.
+
+## Code context
+
+- **README + sub-readmes:** every folder has a short sub-readme for introduction
+  and overview. Always read the relevant sub-readme before editing a module.
+- **`development/` folder:** read every `.md` file — they hold important context
+  for project structure, plan, and known problems.
+- **Obsidian vault** (`Aether-quant-Obsidian-Vault`): generated graph of all
+  dependencies and functions. Use for general overview, but always verify
+  against source — it can be outdated.
+
+## Verification tasks
+
+After every code change, complete ALL of the following:
+
+1. **Add tests** for everything you added/changed.
+2. **Run them** (`aq test` — no Lean backtest in the test suite) and debug if
+   needed. Also do manual debugging where unit tests don't cover.
+3. **Update documentation:**
+   - README.md + sub-readmes (if module docs changed)
+   - Test suite badge (`aq test` auto-refreshes)
+   - `development/` folder: Problems.md, Changelog.md, architecture.md,
+     infrastructure.md
+   - `aq --help` surfaces if new/changed flags
+4. **AQ Vault:** run `generate_code_graph.py` + `regenerate_vault.py
+   --append-handoff` (see Vault section below).
+5. **Report to user:** say whether Docker image should be updated and/or git
+   commit saved. Say if `aq backtest` is needed — user runs backtests
+   themselves, never run them in the agent session.
+
+## Model training
+
+- **Always train models on the Codespace**, not locally. Use the CLI.
+- **Sync codespace with local project** including all gitignored and normal
+  files before training.
+- **Training codespace:** `aq-Training-Ground-Fixed` — keep it OFF when not in
+  active use to reduce costs.
+- **After training finishes:** bring the entire model, data, and any extra files
+  back to the local machine for testing.
+
+## Problems.md status markers
+
+Every entry in `development/Problems.md` uses the established color scheme:
+
+| Marker | Meaning |
+|--------|---------|
+| 🟢 `fixed` | Code changed + verified, nothing pending |
+| 🟡 `partial` | Fix shipped but verification incomplete (needs backtest, live deploy, or user confirmation) |
+| 🔴 `closed` | No code fix: declined/won't-fix/moot/superseded |
+
+Always update the status marker when closing a problem entry.
+
+## CI (`.github/workflows/ci.yml`)
+
+Single job: checkout → setup-python 3.10 → install → ruff → `aq test` → badge refresh.
+No Docker/Lean backtests in CI. Docker rebuild is required before any paper/live
+deploy whenever material code changes land.
+
+## Vault (Aether-quant-Obsidian-Vault)
+
+The Obsidian vault tracks code graphs and agent handoffs:
+
+```powershell
+cd Aether-quant-Obsidian-Vault
+python scripts/generate_code_graph.py --repo-root .. --vault .
+python scripts/regenerate_vault.py --repo-root .. --vault . --append-handoff \
+  --agent ox-alpha --action completed --summary "..." --files file1.py file2.py
+```
+
+## Don'ts
+
+- Never commit secrets, API keys, or credentials
+- Never run `aq backtest` as part of an automated PR gate
+- Never add new top-level `.py` modules without updating `pyproject.toml`
+  `py-modules` and re-installing with `pip install -e .`
+- Never let NaN / inf / None silently pass through feature pipelines — use
+  `json_safety` helpers and explicit guards
+- Never assume a Redis / Postgres / IB connection is available — always
+  degrade gracefully (the test suite runs without any of them)

aether_quant-5.4.8/CODE_OF_CONDUCT.md

@@ -0,0 +1,56 @@
+# Code of Conduct
+
+## Our standard
+
+This project is a research codebase worked on by people with very different
+backgrounds. Participate in good faith: be respectful, be direct without
+being hostile, and assume competence in others. Harassment, personal
+attacks, and demeaning conduct are not acceptable anywhere in this
+project's spaces.
+
+## Expected behavior
+
+- Critique code, data, and claims — not people.
+- Keep discussions technical; this repo's tone is direct and evidence-first.
+- Accept that backtest results, signal quality, and design choices get
+  challenged, sometimes bluntly. Disagreement about the work is normal and
+  welcome.
+
+## Unacceptable behavior
+
+- Harassment, discrimination, or personal attacks of any kind.
+- Trolling, insulting or derogatory comments, and deliberate intimidation.
+- Publishing others' private information (doxxing) without consent.
+- Sexualized language or imagery, unwelcome attention of any kind.
+- Sustained disruption of discussions after being asked to stop.
+
+## Scope
+
+This policy applies within the repository (issues, PRs, code review,
+commit messages) and in all project community spaces: the GitHub
+organization, discussions, chat channels, and any event or space claiming
+to represent the project. It also applies when representing the project
+externally.
+
+## Enforcement
+
+Maintainers enforce this policy and may edit or remove comments, commits,
+code, issues, and PRs that violate it, up to and including temporarily or
+permanently banning a contributor.
+
+Report violations privately to the maintainers via
+[GitHub report/flag mechanisms](https://docs.github.com/en/communities/moderating-comments-and-conversations/reporting-abuse-or-spam)
+or a direct message to a maintainer. Do not escalate harassment in public
+threads.
+
+Reports are handled confidentially to the extent possible; information is
+shared only with maintainers who need it to investigate and act. Retaliation
+against anyone reporting in good faith is itself a violation.
+
+Maintainers respond on a best-effort basis and will state an outcome to the
+reporter where appropriate. Repeated or severe violations lead to permanent
+removal from all project spaces.
+
+## Attribution
+
+Adapted for this project; not bound to any single template.