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.2

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.2
File Size Uploaded Provenance Actions
winnex_tracer-1.1.2.tar.gz 138.3 kB With provenance Details for winnex_tracer-1.1.2.tar.gz

Built distribution (wheel)

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

Total release size: 329.0 kB

Release files / winnex_tracer-1.1.2.tar.gz

Download URL winnex_tracer-1.1.2.tar.gz
Size 138.3 kB
Tags Source
SHA-256 checksum
How to use checksums
78f93b4572b2fd9b423d25ac145d78b9d40e683df442fd26fabc2ea57c109175
BLAKE2b-256 checksum
How to use checksums
1a549ec09ffaccd76214e372a1b2f0020fe9f8ceb16179762d27debeca936d53
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.2-py3-none-any.whl

Download URL winnex_tracer-1.1.2-py3-none-any.whl
Size 190.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
804cce6e76d9161dbda6fbe395f8ab0e62b5b74eb88a5c514ea5ca15a16c5859
BLAKE2b-256 checksum
How to use checksums
8d11f9768d44313f374f25ad205898fefd66263b3ac46ab1058b314b967eda01
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.2

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.2.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