ldtc¶
Top-level package overview. Use this page as the entry point for
the API reference; each subpackage has its own page in the
sidebar with a curated layout. The package docstring below is
the same one you get from import ldtc; help(ldtc) in a Python
shell.
ldtc
¶
LDTC: a real-time NC1/SC1 verification harness.
LDTC (Loop-Dominance Theory of Consciousness) is a single-machine harness for falsifying or accepting the closed-loop (NC1) and steady-state under perturbation (SC1) criteria from the LDTC paper. The package is split into small, focused subpackages that mirror the paper's section structure:
| Subpackage | Responsibility |
|---|---|
runtime |
Fixed-Δt scheduler, window utilities, and timing guards. |
lmeas |
Loop / exchange influence (𝓛) estimators, metrics, diagnostics, and partition management. |
arbiter |
Refusal arbiter and controller policy that decide whether a step may proceed. |
guardrails |
Audit log, Δt governance, LREG (live registry), and smell-tests. |
attest |
Device-signed derived indicators and key handling. |
reporting |
Timelines, tables, and run bundles for human and machine consumption. |
omega |
Perturbation primitives (the Ω battery: power sag, ingress flood, command conflict, ...). |
plant |
Software and hardware adapters and small process models. |
The CLI entrypoint ldtc.cli.main orchestrates these pieces into a
verification run that produces device-signed indicator artifacts and a
human-readable timeline.
Example
Run a baseline verification with the included R0 profile:
Then inspect indicators:
Notes
The package version is exposed as ldtc.__version__ and is the
single source of truth used by python -m ldtc.cli.main --version,
the docs site, and pyproject.toml (kept in sync via the
semantic_release.version_variables configuration).
See Also
Online docs: https://docs.ldtc.dev/.
The paper (paper/main.tex) for the formal definitions of NC1, SC1,
Mq, ε, τ_rec, and σ.
Modules:
| Name | Description |
|---|---|
arbiter |
Arbitration and refusal policy for boundary preservation. |
attest |
Attestation and indicator export. |
cli |
Command-line interface for LDTC. |
guardrails |
Guardrails and governance for LDTC runs. |
lmeas |
Loop-measurement primitives. |
omega |
|
plant |
Plant models and adapters. |
reporting |
Reporting helpers for verification artifacts. |
runtime |
Runtime utilities for fixed-interval scheduling and sliding windows. |
Subpackages¶
| Subpackage | Page | One-liner |
|---|---|---|
ldtc.runtime |
runtime | Fixed-Δt scheduler and sliding-window buffer. |
ldtc.plant |
plant | Software plant and UDP / serial hardware adapter. |
ldtc.lmeas |
lmeas | "L" measurement: estimators, partition, metrics, diagnostics. |
ldtc.guardrails |
guardrails | LREG enclave, audit log, Δt governance, smell tests. |
ldtc.arbiter |
arbiter | Refusal semantics and homeostasis controller. |
ldtc.omega |
omega | Labeled Ω perturbations. |
ldtc.attest |
attest | Device-signed indicators and exporter. |
ldtc.reporting |
reporting | Paper-style timelines, SC1 tables, and verification bundles. |
ldtc.cli |
cli | The ldtc * subcommands. |
See also¶
- Architecture: the static module map and data-flow diagram.
- Lifecycle: how the modules above cooperate during one CLI invocation.
- Mental model: the one-paragraph story.