Skip to main content

CI PyPI License: MIT Python 3.10+ Coherence Score Authority Coverage Drift Density Memory Coverage version LOC tests EDGE workflows

System Architecture | Feature Catalog | TEC Summary | KPI Standards Overlay

DeepSigma

DeepSigma prevents decision amnesia in AI systems.

Log every agent decision. Detect when it drifts. Prove what happened.

Quickstart

pip install deepsigma

# Log an agent decision
coherence agent log decision.json

# Audit all logged decisions
coherence agent audit --json

# Coherence score
coherence agent score

60-Second Proof

coherence demo
BASELINE   90.00 (A)
DRIFT      85.75 (B)   red=1
PATCH      90.00 (A)   patch=RETCON  drift_resolved=true

Three states, deterministic every run:

  1. BASELINE — sealed episode, coherence scored
  2. DRIFT — data changed, drift detected automatically
  3. PATCH — governed retcon applied, coherence restored

Machine-readable: coherence demo --json

What It Does

DeepSigma is the institutional memory layer that makes AI decisions reconstructable.

Every agent decision becomes a sealed, hash-chained episode. Drift between decisions is detected automatically across 8 types. Authority is captured cryptographically, not implied. The full "why" is retrievable in under 60 seconds.

In practice:

  • the "why" is retrievable (not tribal)
  • authority is explicit (not implied)
  • changes are patched, not overwritten
  • drift is detected early and corrected consistently

Editions

One product line, one version, two editions:

  • CORE edition: minimal, demo-first, deterministic (pip install deepsigma)
  • ENTERPRISE edition: extended adapters, dashboards, and ops surfaces (repo-native under enterprise/)

Edition boundary ledger: EDITION_DIFF.md

Operating Modes

Core Mode

Use Core mode when you need fast adoption and low cognitive load.

Active Core surface at repo root:

  • run_money_demo.sh
  • src/core/
  • docs/examples/demo-stack/
  • tests/test_money_demo.py

Enterprise Mode

Use Enterprise mode when you need connectors, dashboards, extended security, broader telemetry, and integration-heavy workflows.

Dependency note:

  • pip install "deepsigma[enterprise]" installs enterprise runtime extras used by telemetry/radar tooling.
  • Full enterprise code surfaces are repository-native under enterprise/ and are run from source in this repo.

Enterprise surfaces are first-class under:

Examples of parked modules:

  • enterprise/dashboard/
  • enterprise/docker/
  • enterprise/release_kpis/
  • enterprise/schemas/
  • enterprise/scripts/
  • enterprise/src/ (non-core packages)
  • enterprise/docs/ (full enterprise docs)

Run the enterprise wedge:

make enterprise-demo
make test-enterprise

Primitive Loop: CERPA

Claim -> Event -> Review -> Patch -> Apply

CERPA is the foundational adaptation loop for the platform. Every governance flow — across IntelOps, ReOps, FranOps, AuthorityOps, and ActionOps — follows this cycle:

  1. Claim — an asserted truth or commitment
  2. Event — an observable occurrence
  3. Review — evaluate the claim against the event
  4. Patch — corrective action if drift is detected
  5. Apply — execute the patch and update state
python -m src.core.examples.cerpa_contract_demo
python -m src.core.examples.cerpa_agent_supervision_demo

Release Artifacts

Build both edition artifacts from one version line:

make release-artifacts

Outputs in dist/:

  • deepsigma-core-vX.Y.Z.zip
  • deepsigma-enterprise-vX.Y.Z.zip

Full Platform References

For the full-platform docs and architecture map, use parked docs directly:

  • enterprise/docs/positioning/positioning_manifesto.md
  • enterprise/docs/positioning/executive_briefing_one_page.md
  • enterprise/docs/release/
  • enterprise/docs/security/
  • enterprise/docs/mermaid/

Repo Snapshot (auto-generated 2026-03-07 04:23 UTC)

  • 1,732 files | 318,085 lines of code
  • 41 CI workflows | 163 test files | 5 pyproject.toml
  • 21 EDGE modules

LOC by extension: .py 105,380 .html 59,838 .json 56,166 .md 47,787 .svg 28,054 .jsonl 5,278 .tsx 2,942 .ttl 2,804 .patch 1,438 .ts 1,244

Repo Intent

  • Keep root focused on a reliable first proof.
  • Keep enterprise depth available without deleting capability.
  • Expand from Core into Enterprise intentionally, not by drift.

License

MIT

Metadata

Release files for deepsigma 2.1.3

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

Source distribution (sdist)

Source distribution for deepsigma 2.1.3
File Size Uploaded
deepsigma-2.1.3.tar.gz 304.9 kB Details

Built distribution (wheel)

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

Total release size: 600.4 kB

Release files / deepsigma-2.1.3.tar.gz

Download URL deepsigma-2.1.3.tar.gz
Size 304.9 kB
Tags Source
SHA-256 checksum
How to use checksums
176639db7ad5fb13827115cb58110d8c0f1e08df63434f85122d1ee3478e949d
BLAKE2b-256 checksum
How to use checksums
7a07f357dc36f2311689a5f119b189691a0ea7cb8d72793a3ddfe61335536c99
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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 Mar 7, 2026.

Transparency log

Release files / deepsigma-2.1.3-py3-none-any.whl

Download URL deepsigma-2.1.3-py3-none-any.whl
Size 295.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
c66461fba808c96bd0550cc838d55ee6a789263ceb5c59b9ba349d426bfd2bb9
BLAKE2b-256 checksum
How to use checksums
50ec1eb100d7621cd63d97c492cf79ea1c215e82ddf55a68fe3a5d0a71a2a4e4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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 Mar 7, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

2.1.3 This release

2 release files

2.1.2

2 release files

2.1.1

2 release files

2.1.0

2 release files

2.0.6

2 release files

2.0.4

2 release files

2.0.3

2 release files

2.0.1

2 release files

2.0.0

2 release files

1.0.0

2 release files

0.9.0

2 release files

0.8.0

2 release files

0.7.0

2 release files

0.6.4

2 release files

0.6.1

2 release files

0.5.0

2 release files

0.4.0

2 release files

0.3.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