Skip to main content

winnex-tracer

The unified Winnex tracer family — one package, namespaced domains.

Shared core (WORM storage, Ed25519 signing, AuditCommitment) plus the gov/med/jus/gap domains, in a single pip package. Each domain lives under its own namespace (winnex_tracer.gov, winnex_tracer.med, ...) so there is no module collision between the old separate tracer-gov/med/jus/gap packages (which all used top-level core/persistence/api).

winnex_tracer/
├── core/    — WORM, Signer (Ed25519/ICP), AuditLogTracker, RetentionPolicy, commitment
├── gov/     — TracerEngine, 9 jurisdictions, LGPD/LAI/TCU/CGU compliance
├── med/     — MedicalEngine, clinical triage, FHIR
├── jus/     — LegalEngine, e-Discovery, evidence chain
└── gap/     — GapEngine, SEC loader, gap analysis

Install

pip install winnex-tracer                # core only (WORM, Signer, commitment)
pip install winnex-tracer[gov]           # + government domain + FastAPI
pip install winnex-tracer[med]           # + healthcare domain
pip install winnex-tracer[jus]           # + legal domain
pip install winnex-tracer[gap]           # + financial domain
pip install winnex-tracer[all]           # everything

The search engine (winnex-madhava >= 1.9.2) is an optional extra (winnex-tracer[madhava]) — each domain works with a built-in fallback.

The AuditCommitment (production audit trail)

The C++ motor returns a compact commitment (total_excluded_count + global_threshold + a deterministic boundary sample) instead of the full O(N) certificate (~2 MB at scale). winnex_tracer.core signs it with Ed25519 for non-repudiation, then stores the ~500-byte record in the WORM.

from winnex_tracer.core import make_worm_record, verify_record, public_key_hex
from winnex_tracer.persistence import WormStorage

record = make_worm_record(engine, query, k=10, max_sample=50)  # ~500 B
WormStorage(base_path="/var/lib/tracer/worm").append(record)

v = verify_record(record, public_key_hex())   # VALID / INVALID

Regionalized government metadata (global / multilanguage)

The gov domain is global: each jurisdiction uses its own field names.

Jurisdiction Language Required fields
br-gv pt-BR orgao_requisitante, cpf, funcao, base_de_dados, sensibilidade, finalidade
pt-gv pt-PT orgao_requisitante, numero_identificacao, funcao, ...
us-gv / eu-gv / global EN requesting_agency, operator_id, role, source_database, sensitivity, purpose

Generic English field names are auto-mapped to the regional names for Portuguese jurisdictions (e.g. requesting_agency → orgao_requisitante), so one client works across jurisdictions:

from winnex_tracer.gov.core import TracerEngine, Config

eng = TracerEngine(Config(jurisdiction="br-gv"))
eng.validate_metadata({"requesting_agency": "TCU", "cpf": "...", ...})  # []

License

Business Source License 1.1 (BSL 1.1) | pay@winnex.ai | Winnex Brasil Soluções Empresariais LTDA (CNPJ 58.364.637/0001-47)

Metadata

Release files for winnex-tracer 1.1.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for winnex-tracer 1.1.1
File Size Uploaded Provenance Actions
winnex_tracer-1.1.1.tar.gz 135.4 kB With provenance Details for winnex_tracer-1.1.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for winnex-tracer 1.1.1
File Interpreter ABI Platform Actions
winnex_tracer-1.1.1-py3-none-any.whl Python 3 none any Details for winnex_tracer-1.1.1-py3-none-any.whl

Total release size: 322.7 kB

Release files / winnex_tracer-1.1.1.tar.gz

Download URL winnex_tracer-1.1.1.tar.gz
Size 135.4 kB
Tags Source
SHA-256 checksum
How to use checksums
469ab56941349fbf5794d2b589d9380113f872a1dd6206e21f1617575327829c
BLAKE2b-256 checksum
How to use checksums
afa9e983ccf6c7686cde7c79d4af090eed0072582eea79d8a83ebdbd5fe3b36b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 29, 2026.

Transparency log

Release files / winnex_tracer-1.1.1-py3-none-any.whl

Download URL winnex_tracer-1.1.1-py3-none-any.whl
Size 187.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
a3fe9a953ea5e27cf39a7af94fd34dae40e7ca34331c884b685f9116290dcbb5
BLAKE2b-256 checksum
How to use checksums
59206d332bb36a2796825a2d16ef4a1b2d48aed157fc54c1aca128e4f3950dee
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 29, 2026.

Transparency log

Security for winnex-tracer 1.1.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for winnex_tracer-1.1.1.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 29, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page