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_agencyorgao_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)

Release files for winnex-tracer 1.0.0

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.0.0
File Size Uploaded
winnex_tracer-1.0.0.tar.gz 114.2 kB Details

Built distribution (wheel)

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

Total release size: 277.8 kB

Release files / winnex_tracer-1.0.0.tar.gz

Download URL winnex_tracer-1.0.0.tar.gz
Size 114.2 kB
Tags Source
SHA-256 checksum
How to use checksums
735d82ac2319461803b109e319e08aa705f2ceeec79b4fa6eff5ed7e689200a7
BLAKE2b-256 checksum
How to use checksums
077df44c41b36b7eac0579c79e965518ac52148ffd0f021cd78fc2987cb98e1e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Aug 20, 2026.

Transparency log

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

Download URL winnex_tracer-1.0.0-py3-none-any.whl
Size 163.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
393c1c471392d4bd11c7d4c92b22c4bfd8de4838d0e91a1e9d9bb7b5602660aa
BLAKE2b-256 checksum
How to use checksums
a74afe14a5a8f212db82f68ef1a29da470e783cc80e77d3551a9f633ff1a2f84
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Aug 20, 2026.

Transparency log

Release history Release notifications | RSS feed

1.1.0

2 release files

This release

1.0.0 This release

2 release files

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