Public package boundary
MK10-PRO has two public surfaces with different authority:
- GitHub
mainis the current governed source surface. - PyPI
mk10-pro1.0.2 is an immutable historical package artifact published before the current source-boundary cleanup.
Current source state:
- Package version:
1.0.2 - Repository license boundary:
Apache-2.0 - PyPI publishing: disabled by
PYPI_DISABLED - No new PyPI artifact is authorized unless
PYPI_DISABLEDis removed under governance.
The existing PyPI 1.0.2 package metadata may still show its upload-time metadata. That does not make PyPI the current governance surface. The repository source, package boundary files, and disabled publishing marker define the current maintained state.
Start here
Installed package:
pip install mk10-pro==1.0.3
mk10 proof
mk10 boundary
mk10 witness
Source checkout:
git clone https://github.com/kaaffilm/MK10-PRO.git
cd MK10-PRO
bash scripts/release-proof.sh
Release identity:
MK10-PRO v1.0.3 — Witness Release
Success lines:
MK10-PRO PROOF: PASS
MK10-PRO BOUNDARY: PASS
MK10-PRO WITNESS: PASS
MK10-PRO RELEASE PROOF: PASS
SYS-002
MK10-PRO
Execution index (frozen)
STATUS: REGISTERED
REGISTRY: https://speedkit.eu
SNAPSHOT: https://speedkit.eu/REGISTRY_SNAPSHOT.json
Registered system. Identity governed by SPEEDKIT registry.
MK10-PRO v1.0 — Deterministic Pre‑Delivery Truth Infrastructure
STATUS: FINAL / AUTHORITATIVE / CLOSED / FINISHABLE
SCOPE (HARD BOUNDARY): Pre‑delivery truth only. Formal playability under declared specifications. No cinema playback. No devices. No operators. No trust. No exceptions.
For scope limits and common misinterpretations, see:
EXECUTIVE DEFINITION (NON‑MARKETING)
MK10‑PRO is deterministic audiovisual infrastructure that converts mastering into provable, durable facts instead of trusted outputs.
If a claim cannot be proven — how a master was produced, what transformed it, which rules governed it, who approved its promotion, or whether it is formally playable under a declared specification — MK10‑PRO treats that claim as invalid.
This is not a tool. It is infrastructure.
SYSTEM AXIOMS (IMMUTABLE)
- Truth is executable — claims emerge only from execution.
- Evidence is the product — files are inputs, not outcomes.
- Policy is law — configuration cannot override rules.
- Verification is hostile — no engine, no trust, no authority required.
- Determinism is mandatory — same inputs must yield identical outputs.
- Scope ends before institutions — hardware, venues, operators are out of bounds.
If any axiom is violated, MK10‑PRO is invalid by definition.
QUICK START
# Install dependencies
pip install -r requirements.txt
# OR
make install
# Ingest source assets
mk10 ingest --source /path/to/assets
# Execute mastering pipeline
mk10 execute --dag pipeline.yaml
# Promote to release
mk10 promote --title "MyTitle" --version "v1.0" --state RELEASE
# Verify an MTB
mk10 verify --mtb /path/to/mtb.zip
Runtime Dependencies
Required:
pyyaml>=6.0— YAML parsing (policy rules, config)jsonschema>=4.0— JSON schema validation (MTB, evidence, ingest)click>=8.0— CLI frameworkcryptography>=41.0— Cryptographic operationspycryptodome>=3.19.0— Additional crypto support
Full list: See requirements.txt
THE ACTUAL PRODUCT: MASTER TRUTH BUNDLE (MTB)
Files are not the product.
The Master Truth Bundle (MTB) is the product.
An MTB is a sealed, self‑contained, verifiable object that represents a title/version as fact.
If the MTB validates, the title exists. If it does not, the title is not real.
GOVERNING PROMISE — "NO FILE FALLS AGAIN"
A master is considered safe only if it can always:
- Be located
- Be verified
- Be explained
- Be reproduced
- Be proven formally playable under its specification
- Be re‑delivered without ambiguity
If any condition fails, MK10‑PRO refuses the claim.
LICENSE
See LICENSE file for details.
FINAL AUTHORITY STATEMENT
If MK10‑PRO says a title exists, it exists. If MK10‑PRO refuses a claim, the claim is invalid.
There is no appeal to trust. There is only proof.
Release files for mk10-pro 1.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| mk10_pro-1.0.3.tar.gz | 58.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mk10_pro-1.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size:122.0 kB
Release files / mk10_pro-1.0.3.tar.gz
| Download URL | mk10_pro-1.0.3.tar.gz |
|---|---|
| Size | 58.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
924b00c69b216c421c3de7ca89ec4bfd15545f2b6039e0cf3be2cfc702301f6e
|
|
BLAKE2b-256 checksum How to use checksums |
d6a1e3240e2cb45e35d03bc1b4c1126551a1740755332c805dce2729e4ab21e3
|
| 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 Apr 30, 2026.
Transparency logRelease files / mk10_pro-1.0.3-py3-none-any.whl
| Download URL | mk10_pro-1.0.3-py3-none-any.whl |
|---|---|
| Size | 63.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ee0156383615dc05fa3cdfb13bb98d0f5c31ae59f7d8ebda8413858dde467263
|
|
BLAKE2b-256 checksum How to use checksums |
3abd91d67f4ca1e72b2a7e07e1f3f38852882bc981525dcd91cb9efae182ac85
|
| 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 Apr 30, 2026.
Transparency log