Skip to main content

PTCNA — Prime Tensor Circled Neural Architecture

One architecture, four layers. Not four repos — four layers of one thing. PTCNA consolidates the former The-Interdependency repos pcna, pcta, and pcsa into a single package and is the single upstream that feeds interdependent-lib.

The four layers

Each layer's tensors divide into the next; every circle, seed, and core is itself a tensor.

Module Layer Divides… → … Tensor kind Back-propagation
ptcna.neural neural (base) neural tensors neural yes — the only differentiable layer
ptcna.circle circle neural tensors → circles auditing / timing no
ptcna.seed seed circles → seeds auditing / timing no
ptcna.core core seeds → cores auditing / timing no
  • Back-propagation lives only in the neural layer. Circle, seed, and core tensors are auditing and timing tensors — they do not differentiate.
  • fiqs gate when cores propagate internally, per Fick's first law J = −D ∇φ (structure diffusing down its field gradient). Timing, not gradient descent. The fiq substrate lives in ptcna.core.prime_core.
  • PCEA (Prime Circular Encryption Algorithm) is not a layer — it stays a separate, orthogonal repo (the guardian: "last state as key" at every layer).

Provenance

Layer Migrated from Was
neural The-Interdependency/pcna (core/) Prime Circular Neural Architecture
seed The-Interdependency/pcta Prime Circled Tensor Architecture (circles → seeds)
core The-Interdependency/pcsa (ptca/ + prime_core/) Prime Tensor Core Architecture (was PTCA)
circle new (audit extracted from the neural engine — see docs/architecture.md) previously unnamed

Install & test

pip install -e ".[dev]"      # neural layer needs numpy; seed/core are stdlib-only
pytest                       # testpaths = ptcna

Status

Alpha (0.1.1). All four layers import and the repository test suite passes. The layer boundary is now executable rather than only descriptive:

  • ptcna.circle.CircleTensor is the one circle type used by circle, seed, and core composition.
  • ptcna.neural.NeuralScalar is the only PTCNA type that owns reverse-mode gradients; structural hosts carry it opaquely.
  • UCNS integration reports a typed suspended state and fails closed until a reviewed PTCNA-specific higher-gonol producer profile exists.
  • EDCM remains an external authority. ZetaEngine accepts an explicitly injected measurement provider; PTCNA contains no shadow EDCM module.

The core layer still intentionally exposes PTCA-named public objects such as PTCATensor and PTCAInstance; those names live in the correct layer. History and unresolved evidence boundaries live in docs/architecture.md.

License: MPL-2.0.

Metadata

Release files for ptcna 0.1.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for ptcna 0.1.1
File Size Uploaded Provenance
ptcna-0.1.1.tar.gz 61.8 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for ptcna 0.1.1
File Interpreter ABI Platform
ptcna-0.1.1-py3-none-any.whl Python 3 none any Details

Total release size: 140.8 kB

Release files / ptcna-0.1.1.tar.gz

Download URL ptcna-0.1.1.tar.gz
Size 61.8 kB
Tags Source
SHA-256 checksum
How to use checksums
0adcfbe99f9769a751930010384b77760651580560fde6a08be98f1fe2e64730
BLAKE2b-256 checksum
How to use checksums
e9205900f312e769242ccf6a31f463b78d0991b5a7f0a386213e930563ac5d3b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.14.6

Release files / ptcna-0.1.1-py3-none-any.whl

Download URL ptcna-0.1.1-py3-none-any.whl
Size 79.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
c5195bf0b9fbc7c930e0b3449d99f39361b01549c681b09356fcb2cb555ed6a9
BLAKE2b-256 checksum
How to use checksums
c0da12de9f157aabef736172c7e2c611e44aa04c5ad8d0b8cb40c6b5341da04d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.14.6

Security for ptcna 0.1.1

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.

No provenance found

None of the files in this release were uploaded with provenance metadata.

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.

Release history Release notifications | RSS feed

This release

0.1.1 This release

2 release files No provenance

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