Dev

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,81 @@
+name: Bug report
+description: A computation is wrong, a build breaks, or something panics where it shouldn't
+labels: [bug]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Before filing:
+        - `cargo test` is the source of truth. If you can reproduce with a failing
+          test (or a short `#[test]`), that's the strongest possible report.
+        - A *wrong number* is a bug. An *unimplemented theorem* usually isn't —
+          check `docs/OPEN.md` and the per-pillar `AGENTS.md` for documented scope
+          boundaries first (e.g. `Ordinal` nim-multiplication panics by design
+          past the verified Kummer boundary; `Nimber` is `F_{2^128}`, not
+          algebraically closed).
+
+  - type: dropdown
+    id: surface
+    attributes:
+      label: Which surface?
+      options:
+        - Rust core (cargo)
+        - Python bindings (the abi3 extension)
+        - examples/ or demo.py
+        - docs (rustdoc / README / AGENTS.md)
+        - not sure
+    validations:
+      required: true
+
+  - type: dropdown
+    id: pillar
+    attributes:
+      label: Which pillar (if known)?
+      options:
+        - "scalar/ (coefficient worlds: Nimber, Surreal, Fp/Fpn, Zp/Qp/..., Ordinal, ...)"
+        - "clifford/ (the multivector engine + GA layer)"
+        - "forms/ (quadratic forms, Arf/Brauer-Wall, local-global, integral)"
+        - "games/ (combinatorial game theory)"
+        - "py/ (PyO3 bindings)"
+        - "linalg/ (shared linear algebra)"
+        - not sure
+
+  - type: input
+    id: backend
+    attributes:
+      label: Scalar backend
+      description: If the bug is backend-specific, which one? (e.g. `Nimber`, `Surreal`, `Fpn<2,8>`, `Qp`, `Ordinal`)
+      placeholder: Nimber
+
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: What happened?
+      description: What did you compute, what did you expect, and what did you get? Cite the math fact you're checking against if there is one.
+    validations:
+      required: true
+
+  - type: textarea
+    id: repro
+    attributes:
+      label: Minimal reproduction
+      description: The shortest Rust snippet / `cargo test` / Python call that reproduces it.
+      render: rust
+    validations:
+      required: true
+
+  - type: input
+    id: version
+    attributes:
+      label: ogdoad version
+      description: "`cargo pkgid` (Rust) or `pip show ogdoad` (Python), or the commit SHA."
+      placeholder: 1.0.0
+    validations:
+      required: true
+
+  - type: input
+    id: toolchain
+    attributes:
+      label: Toolchain
+      description: Output of `rustc --version` (and `python --version` if it's the bindings).
+      placeholder: rustc 1.85.0

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Open research problems
+    url: https://github.com/a9lim/ogdoad/blob/main/docs/OPEN.md
+    about: The natural Gold-quadric play rule, a game-native quadratic deformation, transfinite nim beyond the verified Kummer boundary, and friends are KNOWN-open — not bugs. See docs/OPEN.md before filing.
+  - name: Security vulnerability
+    url: https://github.com/a9lim/ogdoad/security/policy
+    about: Please report security issues privately (see SECURITY.md).

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,59 @@
+name: Feature request
+description: Suggest a new backend, invariant, bridge, or ergonomic improvement
+labels: [enhancement]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        A few scope boundaries this project deliberately keeps (see AGENTS.md and
+        the "Claim levels and non-claims" section):
+
+        - It is **not** a Clifford algebra over arbitrary partizan games — a
+          Clifford algebra needs a commutative scalar *ring*, and the full game
+          group is only an abelian group. New scalar worlds must be commutative
+          rings.
+        - The genuine open problems (a natural Gold-quadric play rule, a
+          game-native quadratic deformation of `GameExterior`, transfinite nim
+          past the verified Kummer boundary) live in `docs/OPEN.md`. Those are research
+          questions, not feature requests — open a discussion instead.
+
+        New backends, invariants, cross-pillar bridges, and binding/docs
+        ergonomics are all in scope and welcome.
+
+  - type: textarea
+    id: problem
+    attributes:
+      label: Problem
+      description: What are you trying to do that ogdoad doesn't support today?
+    validations:
+      required: true
+
+  - type: textarea
+    id: proposal
+    attributes:
+      label: Proposed solution
+      description: How would it work? A type sketch, an API shape, or the math being implemented is welcome.
+    validations:
+      required: true
+
+  - type: dropdown
+    id: surface
+    attributes:
+      label: Which surface does this touch?
+      options:
+        - New scalar backend (must be a commutative ring)
+        - Clifford engine / GA layer
+        - Forms layer (a new invariant or classification)
+        - Games layer
+        - A cross-pillar bridge (ROADMAP.md)
+        - Python bindings / ergonomics
+        - docs only
+        - other
+    validations:
+      required: true
+
+  - type: textarea
+    id: prior-art
+    attributes:
+      label: Reference / prior art
+      description: A theorem, paper, or standard construction this implements. Helps pin the claim level (standard math vs. interpretation vs. open).

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,29 @@
+## What
+
+<!-- One or two sentences on what changed -->
+
+## Why
+
+<!-- What problem does this solve? Link issues with "Fixes #N" if applicable -->
+
+## Test plan
+
+- [ ] `cargo test` passes
+- [ ] `cargo clippy --all-targets` is warning-clean
+- [ ] `cargo fmt --check` is clean
+- [ ] If this touched `src/py/` or any core API the bindings call: `cargo check --features python` **and** `cargo clippy --features python --all-targets`
+- [ ] If this touched `clifford/` or `scalar/big/surreal/`: rebuilt (`maturin develop`) and ran `demo.py` — Display changes don't surface in `cargo test`
+- [ ] If this touched any doc comment (`//!` / `///`): ran `cargo doc --no-deps` **cold** (`RUSTDOCFLAGS="-D warnings"`) and it's link-clean
+- [ ] If this added a new operation: there's a test pinning it to an independent oracle (the `associativity_*` / `general_product_reproduces_*` style)
+
+## Claim level
+
+<!-- If this changes prose / comments / examples, label the claims per AGENTS.md:
+     standard math · implemented and tested · interpretation · open. New "X is
+     true" math statements should be backed by a test or cited, not asserted. -->
+
+## Notes
+
+<!-- Anything reviewers should know. If this touches the metric/product, confirm
+     q and b stay independent and signs go through the scalar's neg() — the two
+     load-bearing char-2 invariants (see Hard rules in AGENTS.md). -->

.github/dependabot.yml

@@ -0,0 +1,23 @@
+version: 2
+updates:
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    open-pull-requests-limit: 5
+    commit-message:
+      prefix: "ci"
+
+  # The only runtime/dev crates are PyO3 (optional, `python` feature) and
+  # proptest (dev). Watch them, but keep PyO3 on a short leash: its abi3 / ABI
+  # coupling means a major bump is a deliberate decision, not a weekly automerge.
+  - package-ecosystem: "cargo"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    open-pull-requests-limit: 5
+    commit-message:
+      prefix: "deps"
+    ignore:
+      - dependency-name: "pyo3"
+        update-types: ["version-update:semver-major"]

.github/workflows/ci.yml

@@ -0,0 +1,101 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+concurrency:
+  group: ci-${{ github.ref }}
+  cancel-in-progress: true
+
+permissions:
+  contents: read
+
+jobs:
+  fmt:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v6
+      - uses: dtolnay/rust-toolchain@stable
+        with:
+          components: rustfmt
+      - run: cargo fmt --all --check
+
+  clippy:
+    # Lint the whole workspace (ogdoad + the unpublished grundy crate) and,
+    # separately, ogdoad under the `python` feature (what the PyO3 bindings
+    # compile under — the feature only exists on ogdoad, so it is scoped -p).
+    # The tree is kept warning-clean, so a warning in either is a failure.
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v6
+      - uses: dtolnay/rust-toolchain@stable
+        with:
+          components: clippy
+      - uses: Swatinem/rust-cache@v2
+      - run: cargo clippy --workspace --all-targets -- -D warnings
+      - run: cargo clippy -p ogdoad --features python --all-targets -- -D warnings
+
+  test:
+    # The math core is pure Rust and the source of truth (AGENTS.md): no Python
+    # in the loop. Run it on both platforms ogdoad is developed on. The property
+    # suites (scalar_axioms / clifford_axioms) fuzz the ring + geometric-product
+    # axioms here too.
+    strategy:
+      fail-fast: false
+      matrix:
+        os: [ubuntu-latest, macos-latest]
+    runs-on: ${{ matrix.os }}
+    steps:
+      - uses: actions/checkout@v6
+      - uses: dtolnay/rust-toolchain@stable
+      - uses: Swatinem/rust-cache@v2
+      - run: cargo test --workspace
+
+  doc:
+    # Rustdoc must run COLD with -D warnings. An incremental `cargo doc` only
+    # re-checks what it recompiles, so it silently under-reports stale intra-doc
+    # links in untouched modules (AGENTS.md). A fresh checkout is cold by
+    # construction.
+    runs-on: ubuntu-latest
+    env:
+      RUSTDOCFLAGS: -D warnings
+    steps:
+      - uses: actions/checkout@v6
+      - uses: dtolnay/rust-toolchain@stable
+      - uses: Swatinem/rust-cache@v2
+      - run: cargo doc --no-deps --workspace
+
+  python:
+    # Build the abi3 extension with maturin, install the wheel, and run the demo
+    # tour. Display paths (blade / nimber / surreal rendering) don't surface in
+    # `cargo test`, so the tour is the smoke test for the binding + Display
+    # layer. If this is green the release workflow's wheel build can publish
+    # blind.
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v6
+      - uses: dtolnay/rust-toolchain@stable
+      - uses: Swatinem/rust-cache@v2
+      - uses: actions/setup-python@v6
+        with:
+          python-version: "3.9"
+      - name: Build the abi3 wheel
+        uses: PyO3/maturin-action@v1
+        with:
+          command: build
+          args: --release --out dist
+          sccache: true
+          manylinux: auto
+      - name: Install the wheel and run the demo tour
+        run: |
+          pip install --find-links dist --no-index ogdoad
+          python demo.py
+      - name: Check the committed type stubs are up to date
+        # ogdoad.pyi is @generated from the built module by scripts/generate_stubs.py.
+        # If a binding was added/renamed without regenerating, the committed stub is
+        # stale — fail here rather than ship a wrong .pyi. The generator output is
+        # fully sorted, so it is byte-stable across Python versions.
+        run: python scripts/generate_stubs.py --check