Skip to main content

systemictau-declare

DOI PyPI

Declare the time generator. Do not predict without controls.

systemictau-declare is a thin protocol layer on top of systemictau 4.6.x and nested-recd. It does not replace the motor. It freezes the operational contract that scientific runs should share: window, weights, gate bands, surrogate, and a FAR seal that refuses to claim an event when no controls were supplied.

from systemictau_declare import Protocol, declare

P = Protocol.frozen_v1()          # window=13, m=3, θ3=0.08, weights=(0.6, 0.4)
rep = declare(X, time=t, protocol=P, controls=None)
print(rep.seal.far)               # 'undefined'  — no event is claimed
pip install "systemictau-declare[report]"
recd-declare data.csv --protocol frozen_v1 --out report.html
recd-declare data.csv --controls controls.csv --out report.html

The top-level function is named declare, not predict_outbreak.

What this package is for

Complex-systems papers routinely index series by laboratory time (t) and then speak of “the time of the system”. RECD constructs a second generator (T_n) from ordinal concordance. Nested excess³ measures depth of reorganization. None of that is usable as science if every notebook retunes (\theta_3) and paints a red light without a false-alarm rate.

This package exists so that:

  1. The protocol is frozen (protocols/frozen_v1.yaml, hashed).
  2. The two clocks stay two fields ((t) vs (T_n); (\Delta T_n) is not (\Delta\mathrm{excess}^3)).
  3. FAR is a seal, not a footnote: undefined | event-only | estimated.
  4. A one-page report can be cited. Ontology, Polo, and crash buttons are out of scope.

Read the software paper: papers/why_systemictau_declare.pdf
(Español: papers/por_que_existe_systemictau_declare.pdf)
Usage manual: docs/MANUAL.pdf

What this package is not

  • Not a replacement for the SI second.
  • Not a proof that (\Sigma^{\mathrm{RECD}}) is Clausius production (CT-4C remains open).
  • Not a Williams–Beer PID atom.
  • Not a dengue / Holter / market predictor.
  • Not Module CT. Lean is cited, not imported at runtime.

Install

python -m pip install "systemictau-declare[report]"
# or from this repository
python -m pip install -e ".[report,dev]"

Requires systemictau>=4.6.0,<5 and nested-recd>=0.2.0. Version 0.1.2 starts against those pins as published on PyPI (nested-recd 0.2.0 does not accept compute_res; systemictau 4.6.0's import systemictau is broken and is bypassed).

Minimal example

import numpy as np
from systemictau_declare import Protocol, declare, g0_independent_ar, write_report

X = g0_independent_ar(T=400, N=4, seed=0)
rep = declare(X, protocol=Protocol.frozen_v1())
assert rep.seal.far == "undefined"
assert rep.seal.event_claimed is False
write_report(rep, "report.html")

Any deviation from frozen_v1 must go through Protocol.exploratory(...). The report is then marked EXPLORATORY. Weights cannot be fit().

Citation

See CITATION.cff and the paper in papers/.

License

MIT. Author: Johel Padilla-Villanueva.

Metadata

Release files for systemictau-declare 0.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 systemictau-declare 0.1.2
File Size Uploaded
systemictau_declare-0.1.2.tar.gz 23.8 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for systemictau-declare 0.1.2
File Interpreter ABI Platform
systemictau_declare-0.1.2-py3-none-any.whl Python 3 none any Details

Total release size: 46.8 kB

Release files / systemictau_declare-0.1.2.tar.gz

Download URL systemictau_declare-0.1.2.tar.gz
Size 23.8 kB
Tags Source
SHA-256 checksum
How to use checksums
322ea8520da2ae4caa27d7cf5dbe6c2190d9ee28b52e48c853177c7ff8206b68
BLAKE2b-256 checksum
How to use checksums
116c7adcddb3274a7862f2e145dccc6c10e5b2f5d649a4e1982eae2194b22ae2
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 Sep 20, 2026.

Transparency log

Release files / systemictau_declare-0.1.2-py3-none-any.whl

Download URL systemictau_declare-0.1.2-py3-none-any.whl
Size 23.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
7b39fe77d67af2f05138c0ec8db8c98a63a4f280d1208ec8a350ecfd1268191b
BLAKE2b-256 checksum
How to use checksums
515efe5a9fcbe45ec1e75ddac00835928e0c3a0cb77aba518c75a1034ced402c
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 Sep 20, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.1.2 This release

2 release files

0.1.1

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