AgencityLab Documentation¶
Foundations
- AgencityLab overview
- Theory-to-code mapping
- Status vocabulary
- Scientific decisions for the reference implementation
- Source notes and resolved divergences
- Reference canonical pipeline
- Canonical parameter policy
- Operator mapping
- Continuous sampled pipeline versus Volume-2 discrete formulation
- Exact null/rest-state convention
- Numerical safeguards versus physics
- Interpretation boundary
- Conformance test contract
- Scientific validation — v0.4
Scientific computation and analysis
- Scientific API map
- I want to calculate Agencity for a signal
- I want to analyse a result
- I want an observable spatial field
- I want to study the autonomous field
- Biology
- Thermodynamics
- Gravity
- Quantum
- Cosmology
- Stable workflows and utilities
- Package root
- Generic dynamics
- Runtime configuration boundary
- Result and serialization boundary
- Software status versus scientific status
- Biological Agencity
- Public API contract — AgencityLab 1.0
- Stable 1.0 entry points
- Semantic Versioning policy
- Canonical physical-parameter contract
- Canonical identities
- Reference call
- Result and reproducibility contract
- Continuous sampled computation versus discrete Volume-2 computation
- Diagnostics are not canonical physics
- Batch
- Streaming
- Multiscale
- Multivariate computation and zero power
- Runtime and acceleration boundary
- Experimental and research interfaces
- Scientific limitations
- Observable Spatial Agencity Fields
- Dynamical Agencity Field Foundations
- Classical Dynamical Agencity Field
- Effective beta field and flat-field conservation laws
- Coherent Structures and Field Topology
- Mathematical extension completeness
- Unified Agencity Thermodynamics
- Classical Agencity Gravity
- Quantum Agencity primitives
- Cosmological Agencity
- Field extension contracts
- Scientific-status taxonomy
- Observable field versus autonomous dynamical field
- Scientific progression
- Status by layer
- Units contract
- Parameter provenance
- Shared model metadata
- Shape and validation contracts
- Two distinct Agencial entropy formulations
- Governance for problematic formulas
- Future dependencies
- Agencity Analysis — v0.5
- Multiscale & Extensions
- v0.7 — Scientific UX
- Engineering & Performance — v0.8
- AgencityLab 1.0 release readiness
Reference and tutorials
- Reference library: signals, datasets, and scenarios
- Theory of Agencity
- Canonical equations
- Principles
- Principle 0 — Existence and objectivity
- Principle 1 — Agential power balance
- Principle 2 — Irreversibility
- Principle 3 — Contrast and critical surface
- Principle 4 — Orientation and coherence
- Principle 5 — Minimality
- Principle 6 — Memory/coherence coupling
- Principle 7 — Extensivity and intensivity
- Principle 8 — Structural stability
- Important v1.0 clarification
- Interpretation
- Quickstart: from signal to scientific result
- Preprocessing Tutorial
- Full scientific workflow
- API Reference
- Examples
- Bibliography
- Glossary
Project status¶
AgencityLab 1.2.0 is the current stable public software release. This minor
release adds the experimental agencitylab.biology mapping layer, including
versioned biological references, metrology, biological tau and causal w,
frozen protocols and thin orchestration over the existing Agencity APIs,
without changing the canonical equations. Version 1.1.3 hardened numerical
beta-trajectory curvature; 1.1.2 hardened unresolved-velocity and structural
phase-turn handling; 1.1.1 hardened runtime validation and regime diagnostics;
1.1.0 introduced the reference library, and 1.0.0 remains the first stable
compatibility baseline.
Use the scientific API map first. The main scalar entry point is
agencitylab.compute_agencity; interpretation belongs under
agencitylab.analysis; spatial/autonomous field work under
agencitylab.fields; biological mapping under agencitylab.biology; and
thermodynamics, gravity, quantum and cosmology under their corresponding
namespaces.
Observable spatial orchestration, generic field numerics and the biological
mapping remain experimental. Autonomous phi, effective-beta dynamics, flat-field
conservation, coherent structures, thermodynamics and classical gravity remain
research. Quantum/agenton and homogeneous cosmology remain speculative.
Software stability is distinct from empirical validation.
The bridge from observable beta_obs to autonomous phi remains explicit:
phi = sqrt(P_c * tau) * beta. The Chapter-16 flat-field (+,-,-,-) convention
and Chapter-19 gravity (-,+,+,+) convention remain explicitly distinct.
Runtime configuration contains software options only. Physical/contextual quantities must be supplied explicitly to the scientific API that owns them. The stable canonical scalar pipeline is NumPy based; optional JAX and Numba components are explicitly separate acceleration primitives rather than hidden alternate canonical pipelines.
The incorrect pre-1.0 tanh-based Agencity dynamical model is not distributed in 1.0. Generic dynamical-system helpers remain where they are scientifically neutral.
AgencityResult contains canonical result data and reproducibility metadata.
Diagnostics, signatures, multiscale products and reports remain separate
workflow artifacts. Stable result serialization begins with schema 1.0.
Canonical target quantities¶
The reference scalar construction uses observable u, normalized u*,
activation X*, activity A*, memory M, organisation O, dynamic intensity
D, structural intensity S, logarithmic contrast J, structural orientation
Theta, intrinsic state beta, and flux b = P_c beta.
Canonical computation, numerical safeguards, diagnostics, experimental extensions, research models and speculative extensions remain separately labelled.