Skip to main content

zpe-taste

License: SAL v7.1 CI

What This Is

Public evidence record for the taste lane. Negative-reference boundary and audit limits define the claim surface.

The finding for this lane is a bounded negative: the current taste lane object is not geometry-bearing under the evaluation committed here. Identity controls score 1.0 across all four geometry metrics, confirming the evaluation machinery discriminates correctly before the lane object is tested. The lane object scores well below every pass threshold — that result is what this repository preserves and publishes.

This repository does not claim that biological taste coding is impossible. It claims one narrow thing: the committed object did not pass.

Codec Mechanics

ZPE-Taste Codec Mechanics animation

Field Value
Architecture TASTE_REFERENCE_STREAM
Encoding TASTE_NEGATIVE_REFERENCE_V1
Mechanics Asset .github/assets/readme/lane-mechanics/TASTE.gif

Key Metrics

Metric Value Baseline
metric_fit 0.207 0.6 gate (gap −0.393)
topology_fit 0.156 0.5 gate (gap −0.344)
local_injectivity 0.250 0.5 gate (gap −0.250)
graph_fit 0.181 0.5 gate (gap −0.319)

Source: proofs/artifacts/taste_negative_reference.json

Repo Identity

Field Value
Identifier ZPE-Taste
Repository https://github.com/Zer0pa/ZPE-Taste
Section encoding
Visibility PUBLIC
Architecture TASTE_REFERENCE_STREAM
Encoding TASTE_NEGATIVE_REFERENCE_V1
Commit SHA 900726f407cf
License SAL-7.0
Authority Source proofs/artifacts/taste_negative_reference.json

Readiness

Field Value
Verdict PARTIAL
Checks 4/4
Anchors 4 display anchors
Commit 900726f407cf
Authority proofs/artifacts/taste_negative_reference.json

Honest Blocker

This repository does not claim that biological taste coding is impossible.; This repository does not settle disputed models of cortical taste organization.; This repository does not claim that a different native taste object could never support a geometry-bearing representation.

What We Prove

  • The committed reference packet preserves the narrow negative verdict for the current taste lane object.
  • The evaluation machinery discriminates (identity control 1.0), so the lane object scores are meaningful, not noise.

What We Don't Claim

  • This repository does not claim that biological taste coding is impossible.
  • No comparative benchmarks are published for this lane. This is a no-comp lane by design.

Verification Status

Code Check Verdict
V_01 Reference packet and manifest preserve the narrow negative verdict and biological non-claim. PASS
V_02 Identity control scores 1.0 across all four geometry metrics — evaluation machinery discriminates. PASS
V_03 Scope and boundary documents are present in the tracked tree. PASS
V_04 Fresh-clone install and read-only falsification commands run locally. PASS

Proof Anchors

Path State
proofs/artifacts/taste_negative_reference.json VERIFIED
proofs/manifests/CURRENT_REFERENCE_PACKET.md VERIFIED
PUBLIC_AUDIT_LIMITS.md VERIFIED
docs/LEGAL_BOUNDARIES.md VERIFIED

Repo Shape

Field Value
Proof Anchors 4 display anchors
Modality Lanes 1
Architecture TASTE_REFERENCE_STREAM
Encoding TASTE_NEGATIVE_REFERENCE_V1
Verification 4/4 checks
Authority Source proofs/artifacts/taste_negative_reference.json

Quick Start

python3 -m venv .venv
. .venv/bin/activate
python -m pip install --upgrade pip
pip install .
python -m zpe_taste.verify
python -m unittest discover -s tests -v

Scope Document

See docs/SCOPE.md for the explicit public claim boundary, and PUBLIC_AUDIT_LIMITS.md for the outsider audit boundary.

Upcoming Workstreams

This section captures the active lane priorities — what the next agent or contributor picks up, and what investors should expect. Cadence is continuous, not milestoned.

  • Taste lane object — conceptual rethink — Zero-Base Scientific Thinking — GPD Research and Planning Pending. Current lane object is not geometry-bearing (metric_fit 0.207 vs threshold 0.6, topology_fit 0.156 vs 0.5) — published as falsification. Active rethinking: what is the actual encodable taste object? Receptor-space (parallel to ZPE-Smell), psychophysical-space, or something else? No new engineering until the conceptual model resolves.

Metadata

Release files for zpe-taste 0.1.0

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

Source distribution (sdist)

Source distribution for zpe-taste 0.1.0
File Size Uploaded Provenance
zpe_taste-0.1.0.tar.gz 30.9 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for zpe-taste 0.1.0
File Interpreter ABI Platform
zpe_taste-0.1.0-py3-none-any.whl Python 3 none any Details

Total release size: 62.3 kB

Release files / zpe_taste-0.1.0.tar.gz

Download URL zpe_taste-0.1.0.tar.gz
Size 30.9 kB
Tags Source
SHA-256 checksum
How to use checksums
eae769c92cbf685deb60678ea623542e3caf85607984787012b7e286ae4115fe
BLAKE2b-256 checksum
How to use checksums
775db16517eb7776ce0546a1c24ceb85c8bcdd199dda09b0216d844239e26d3f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

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 May 3, 2026.

Transparency log

Release files / zpe_taste-0.1.0-py3-none-any.whl

Download URL zpe_taste-0.1.0-py3-none-any.whl
Size 31.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
87b0068a0034f39f11ab9299cbf069174d05f693fec18f2dc83e2bffd2a1c192
BLAKE2b-256 checksum
How to use checksums
51a60329b0b12cc690d22ce75bcfa2e35034e9f4013d3cde4d28af8f13df4ab4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

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 May 3, 2026.

Transparency log

Security for zpe-taste 0.1.0

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.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for zpe_taste-0.1.0.tar.gz

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 May 3, 2026.

Transparency log

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.

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files Full 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