tractum 0.5.0__tar.gz

tractum-0.5.0/.env.example

@@ -0,0 +1,39 @@
+# Tractum Environment Configuration
+
+# API Settings
+CLAUDWAY_API_HOST=0.0.0.0
+CLAUDWAY_API_PORT=8000
+CLAUDWAY_DEBUG=true
+
+# Database
+CLAUDWAY_DATABASE_URL=postgresql+asyncpg://tractum:tractum@localhost:5432/tractum
+
+# Redis
+CLAUDWAY_REDIS_URL=redis://localhost:6379/0
+
+# Claude-Flow
+CLAUDWAY_CLAUDE_FLOW_URL=http://localhost:8080
+CLAUDWAY_CLAUDE_FLOW_API_KEY=
+
+# NATS
+CLAUDWAY_NATS_URL=nats://localhost:4222
+CLAUDWAY_NATS_USER=
+CLAUDWAY_NATS_PASSWORD=
+
+# JWT / Auth
+CLAUDWAY_SECRET_KEY=change-this-to-a-random-string-in-production
+CLAUDWAY_ALGORITHM=HS256
+CLAUDWAY_ACCESS_TOKEN_EXPIRE_MINUTES=30
+
+# Stripe (Billing)
+CLAUDWAY_STRIPE_API_KEY=sk_test_your_stripe_key_here
+CLAUDWAY_STRIPE_WEBHOOK_SECRET=whsec_your_webhook_secret_here
+CLAUDWAY_STRIPE_PRICE_ID_PRO=price_your_pro_price_id
+CLAUDWAY_STRIPE_PRICE_ID_ENTERPRISE=price_your_enterprise_price_id
+
+# Rate Limiting
+CLAUDWAY_RATE_LIMIT_REQUESTS=100
+CLAUDWAY_RATE_LIMIT_PERIOD=60
+
+# Anthropic
+CLAUDWAY_ANTHROPIC_API_KEY=sk-ant-your-anthropic-key-here

tractum-0.5.0/.gitattributes

@@ -0,0 +1,39 @@
+# Normalize line endings: LF in repo, LF in working copy.
+# Ends the "LF will be replaced by CRLF" warnings.
+* text=auto eol=lf
+
+# Explicit text types
+*.md   text eol=lf
+*.json text eol=lf
+*.js   text eol=lf
+*.ts   text eol=lf
+*.tsx  text eol=lf
+*.jsx  text eol=lf
+*.css  text eol=lf
+*.html text eol=lf
+*.yml  text eol=lf
+*.yaml text eol=lf
+*.toml text eol=lf
+*.sh   text eol=lf
+*.py   text eol=lf
+*.go   text eol=lf
+*.rs   text eol=lf
+*.txt  text eol=lf
+
+# Binaries — never touch
+*.png  binary
+*.jpg  binary
+*.jpeg binary
+*.gif  binary
+*.webp binary
+*.svg  text eol=lf
+*.ico  binary
+*.pdf  binary
+*.mp4  binary
+*.mov  binary
+*.mp3  binary
+*.wav  binary
+*.zip  binary
+*.gz   binary
+*.7z   binary
+

tractum-0.5.0/.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,89 @@
+name: Bug report
+description: Report something that's broken in Tractum.
+labels: ["bug", "needs-triage"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to file a bug.
+
+        **Security vulnerability?** Do not use this template. Follow the
+        private reporting process in
+        [SECURITY.md](https://github.com/JordanNewell/tractum/blob/main/SECURITY.md)
+        instead — public issues risk exposing unpatched flaws.
+
+  - type: textarea
+    id: summary
+    attributes:
+      label: Summary
+      description: One paragraph. What did you expect, and what happened instead?
+    validations:
+      required: true
+
+  - type: textarea
+    id: reproducer
+    attributes:
+      label: Minimal reproducer
+      description: The smallest self-contained code that triggers the bug. Paste a single Python file or a transcript.
+      placeholder: |
+        from tractum import Swarm, SwarmConfig, AgentConfig, Task
+        ...
+    validations:
+      required: true
+
+  - type: input
+    id: version
+    attributes:
+      label: Tractum version
+      placeholder: "0.3.2 (or commit SHA if installed editable)"
+    validations:
+      required: true
+
+  - type: input
+    id: python
+    attributes:
+      label: Python version
+      placeholder: "3.12.5"
+    validations:
+      required: true
+
+  - type: input
+    id: os
+    attributes:
+      label: Operating system
+      placeholder: "Ubuntu 24.04 / macOS 14 / Windows 11"
+    validations:
+      required: true
+
+  - type: dropdown
+    id: extras
+    attributes:
+      label: Extras installed
+      description: Which `tractum[...]` extras did you install? Select all that apply.
+      multiple: true
+      options:
+        - "[mcp]"
+        - "[nostr]"
+        - "[pq]"
+        - "[langgraph]"
+        - "[maf]"
+        - "[crewai]"
+        - "[benchmark]"
+        - "[runner]"
+        - "[persist]"
+        - "[docs]"
+        - "[dev]"
+        - "none / base only"
+
+  - type: textarea
+    id: logs
+    attributes:
+      label: Logs / traceback
+      description: Paste the full traceback or relevant log lines. Wrap in triple backticks. No API keys.
+      render: shell
+
+  - type: textarea
+    id: notes
+    attributes:
+      label: Anything else?
+      description: Workarounds you tried, related issues, context.

tractum-0.5.0/.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,11 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Security vulnerability (read SECURITY.md, do NOT use a public issue)
+    url: https://github.com/JordanNewell/tractum/blob/main/SECURITY.md
+    about: Found a security issue? Follow the private reporting process in SECURITY.md.
+  - name: Docs site
+    url: https://jordannewell.github.io/tractum/
+    about: API reference, transports, adapters, and benchmarks.
+  - name: Questions / discussions
+    url: https://github.com/JordanNewell/tractum/discussions
+    about: Usage questions and design discussion go in Discussions, not Issues.

tractum-0.5.0/.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,64 @@
+name: Feature request
+description: Suggest an idea for Tractum.
+labels: ["enhancement", "needs-triage"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for the idea. Tractum is intentionally lean — every new
+        runtime dependency needs to justify its weight. The strongest
+        feature requests tie back to the core wedge (verifiable
+        multi-agent consensus) and work without bloating the base install.
+
+  - type: textarea
+    id: problem
+    attributes:
+      label: The problem
+      description: What are you trying to do that Tractum doesn't let you do today? What's the current workaround, and why is it painful?
+    validations:
+      required: true
+
+  - type: textarea
+    id: proposal
+    attributes:
+      label: The proposal
+      description: What would the API look like? Sketch the smallest version that solves your problem.
+      placeholder: |
+        from tractum import ...
+    validations:
+      required: true
+
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives considered
+      description: What else did you try? Why didn't it work?
+
+  - type: dropdown
+    id: scope
+    attributes:
+      label: Area
+      multiple: true
+      options:
+        - Core SDK (tractum.swarm, .consensus, .coordinator)
+        - Signing / receipts (tractum.signing)
+        - Transports (JSON / W3C VC / Nostr)
+        - Adapters (LangGraph, future: CrewAI, A2A, AutoGen)
+        - MCP server (tractum.server)
+        - Tool layer (tractum.tools)
+        - Docs / examples
+        - Other
+
+  - type: checkboxes
+    id: lean
+    attributes:
+      label: Lean-install check
+      description: A reminder that the base `pip install tractum` stays at 4 deps.
+      options:
+        - label: This feature can ship without adding a base-install dependency (or it belongs in an optional extra).
+          required: true
+
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional context

tractum-0.5.0/.github/ISSUE_TEMPLATE/security_report.md

@@ -0,0 +1,38 @@
+---
+name: Security report (read me first)
+about: Found a security vulnerability? This is NOT the right place — read below.
+title: "[SECURITY] DO NOT POST DETAILS HERE"
+labels: ["security", "do-not-disclose"]
+---
+
+---
+
+:rotating_light: **Do not post vulnerability details in this issue.**
+
+:rotating_light: This issue tracker is **public**. Anything you write here
+is visible to the world and indexed forever — including by anyone who would
+exploit the bug before a fix ships.
+
+## Report vulnerabilities privately
+
+Follow the private reporting process described in
+**[SECURITY.md](https://github.com/JordanNewell/tractum/blob/main/SECURITY.md)**:
+
+1. Email **<security@jordannewell.com>** with a description, reproducer,
+   and affected versions.
+2. If you have a PGP key, encrypt the report. (The project's PGP fingerprint
+   will be published in SECURITY.md once generated.)
+3. Do **not** open a public GitHub issue, blog post, or tweet until a fix
+   has shipped and coordinated disclosure is complete.
+
+See [SECURITY.md](https://github.com/JordanNewell/tractum/blob/main/SECURITY.md)
+for the full scope, SLA, threat model link, and disclosure policy.
+
+## After you've emailed
+
+You can open a placeholder issue here — **without vulnerability details** —
+saying "I sent a security report via email on YYYY-MM-DD, awaiting ack." That
+lets us track the timeline publicly without exposing anything.
+
+This template exists only to redirect you. Anything posted here with actual
+vulnerability details will be deleted on sight.

tractum-0.5.0/.github/workflows/ci.yml

@@ -0,0 +1,59 @@
+name: CI
+
+on:
+  push:
+    branches: [main, "feat/**"]
+  pull_request:
+    branches: [main]
+
+jobs:
+  test:
+    runs-on: ${{ matrix.os }}
+    strategy:
+      fail-fast: false
+      matrix:
+        os: [ubuntu-latest, windows-latest]
+        python-version: ["3.11", "3.12", "3.13"]
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+          cache: pip
+
+      - name: Install package + dev deps
+        run: |
+          python -m pip install --upgrade pip
+          pip install -e ".[mcp,pq,dev]"
+
+      - name: Lint (ruff)
+        run: ruff check tractum/ tests/ examples/
+
+      - name: Test (pytest)
+        run: pytest tests/ -v
+
+  build:
+    needs: test
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+          cache: pip
+      - run: pip install --upgrade pip build
+      - name: Build wheel
+        run: python -m build --wheel
+      - name: Verify wheel contents
+        run: |
+          python -c "
+          import zipfile, glob
+          w = glob.glob('dist/*.whl')[0]
+          names = zipfile.ZipFile(w).namelist()
+          assert 'tractum/__init__.py' in names, 'missing tractum package'
+          assert 'tractum/server.py' in names, 'missing MCP server'
+          print('wheel OK:', w)
+          "

tractum-0.5.0/.github/workflows/docs.yml

@@ -0,0 +1,76 @@
+name: Docs
+
+on:
+  push:
+    branches: [main]
+    paths:
+      - "docs/**"
+      - "mkdocs.yml"
+      - "tractum/**"
+      - "pyproject.toml"
+      - ".github/workflows/docs.yml"
+  pull_request:
+    branches: [main]
+    paths:
+      - "docs/**"
+      - "mkdocs.yml"
+      - "tractum/**"
+      - "pyproject.toml"
+      - ".github/workflows/docs.yml"
+  # Allow manual runs from the Actions tab.
+  workflow_dispatch:
+
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+# Only one docs build/deploy at a time per ref. Newer runs cancel older ones.
+concurrency:
+  group: pages
+  cancel-in-progress: true
+
+jobs:
+  build:
+    name: Build docs site
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+          cache: pip
+          cache-dependency-path: pyproject.toml
+
+      - name: Install Tractum + docs extras
+        run: |
+          python -m pip install --upgrade pip
+          pip install -e ".[docs]"
+
+      - name: Build site (strict)
+        # `--strict` fails the build on broken mkdocstrings references,
+        # missing imports, or any warning — catches API drift at CI time.
+        run: mkdocs build --strict
+
+      - name: Upload Pages artifact
+        if: github.event_name == 'push' && github.ref == 'refs/heads/main'
+        uses: actions/upload-pages-artifact@v3
+        with:
+          path: site
+
+  deploy:
+    name: Deploy to GitHub Pages
+    # Only deploy on pushes to main — PR builds verify the build passes,
+    # they don't publish.
+    if: github.event_name == 'push' && github.ref == 'refs/heads/main'
+    needs: build
+    runs-on: ubuntu-latest
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    steps:
+      - name: Deploy to GitHub Pages
+        id: deployment
+        uses: actions/deploy-pages@v4

tractum-0.5.0/.github/workflows/gitleaks.yml

@@ -0,0 +1,24 @@
+name: Gitleaks
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+permissions:
+  contents: read
+
+jobs:
+  gitleaks:
+    name: Secret scan (gitleaks)
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Run gitleaks
+        uses: gitleaks/gitleaks-action@v2
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

tractum-0.5.0/.github/workflows/publish.yml

@@ -0,0 +1,75 @@
+name: Publish
+
+# Fires on v* tags (the convention from harbormasterd). Also exposes a
+# manual workflow_dispatch trigger so we can re-publish an existing tag
+# if needed (e.g., first time after setting up the secret).
+on:
+  push:
+    tags: ['v*']
+  workflow_dispatch:
+    inputs:
+      tag:
+        description: 'Tag to publish (e.g. v0.3.0)'
+        required: true
+        type: string
+
+permissions:
+  contents: read
+
+jobs:
+  build:
+    name: Build wheel + sdist
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout (tag from input, or the pushed tag)
+        uses: actions/checkout@v4
+        with:
+          ref: ${{ inputs.tag || github.ref }}
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: '3.12'
+          cache: pip
+
+      - name: Install build tooling
+        run: pip install --upgrade pip build twine
+
+      - name: Build wheel + sdist
+        run: python -m build
+
+      - name: Verify wheel contents
+        run: |
+          python -c "
+          import zipfile, glob
+          w = sorted(glob.glob('dist/*.whl'))[-1]
+          names = zipfile.ZipFile(w).namelist()
+          assert 'tractum/__init__.py' in names, 'missing tractum package'
+          assert 'tractum/server.py' in names, 'missing MCP server'
+          print('wheel OK:', w)
+          "
+
+      - name: Check metadata
+        run: twine check dist/*
+
+      - name: Upload artifacts
+        uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    name: Publish to PyPI
+    needs: build
+    runs-on: ubuntu-latest
+    environment: pypi  # matches PyPI Trusted Publishing config
+    permissions:
+      id-token: write  # required for OIDC trusted publishing
+    steps:
+      - name: Download artifacts
+        uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1

tractum-0.5.0/.gitignore

@@ -0,0 +1,88 @@
+# Claude
+.claude/
+
+# ZCode agent state (never commit — may contain live API keys)
+.zcode/
+
+# Python
+__pycache__/
+*.py[cod]
+*$py.class
+*.so
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+/lib/
+/lib64/
+parts/
+sdist/
+var/
+wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+.venv/
+venv/
+ENV/
+env/
+
+# Environment
+.env
+.env.local
+.env.*.local
+
+# IDE
+.vscode/
+.idea/
+*.swp
+*.swo
+*~
+
+# OS
+.DS_Store
+Thumbs.db
+
+# Logs
+*.log
+logs/
+
+# Database
+*.db
+*.sqlite
+*.sqlite3
+
+# Node (dashboard)
+node_modules/
+.next/
+out/
+
+# Testing
+.coverage
+.pytest_cache/
+htmlcov/
+.tox/
+
+# Docs build output (deployed via GitHub Pages, not committed)
+site/
+
+# Docker
+.dockerignore
+
+# Session handoff (NOT for public repo - contains flip strategy)
+HANDOFF.md
+
+# Benchmark competitive research (NOT for public repo)
+BENCHMARK-RESEARCH.md
+
+# Benchmark raw output (regenerable, large, noisy)
+benchmarks/raw/
+
+# Benchmark appliance report output (regenerable; lands in the compose volume)
+benchmarks/out/
+
+# OG image working files (only the canonical tractum-og.png is committed)
+assets/og/tractum-og-v030*.png

tractum-0.5.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,77 @@
+# 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:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall community
+
+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.
+
+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 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 **security@jordannewell.com** (general conduct reports; for security vulnerabilities specifically, follow the private process in [SECURITY.md](SECURITY.md)). 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, version 2.1, available at https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by Mozilla's code of conduct enforcement ladder.
+
+For answers to common questions about this code of conduct, see the FAQ at https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.