Skip to main content

coreason-publisher

The Regulatory Gatekeeper & Artifact Packager

CI Python License Ruff

coreason-publisher is the "Final Gatekeeper" of the CoReason platform. It orchestrates the transition of an agent from a mutable "Development Experiment" to an immutable "Clinical-Grade Product."

It solves the "Big AI" problem in GxP environments. Agents are not just code; they are a complex dependency of Logic (Prompts), Evidence (Test Results), and Binary Assets (Fine-Tuned Weights). This package bundles these diverse assets into a verifiable package, manages the Git LFS (Large File Storage) pointers for heavy models, and enforces a strict Two-Stage Governance Workflow (Submission $\to$ SRB Approval) before any code reaches production.

It can be run as a CLI tool for local development or as a Centralized Service (REST API) for platform integration.

Functional Philosophy

The agent must implement the Package-Propose-Approve-Merge Loop:

  1. The "Thick" Artifact: A release is monolithic. It must contain the exact Prompts, Code, Test Data, and Model Weights used during validation. If one piece is missing, the release is void.
  2. Governance as Code: The Scientific Review Board (SRB) approval is a digital state transition, not an email. coreason-publisher blocks the Git merge until a cryptographically signed approval from an authorized SRB member is registered.
  3. Semantic Versioning (SemVer): The tool manages versioning (v1.0 $\to$ v1.1) automatically based on the nature of the change (Patch/Minor/Major), preventing human error.
  4. Reproducibility: The "Council of Models" (the specific LLM versions used for testing) must be locked in the release manifest to ensure the test results are reproducible 5 years from now.

Key Features

  • Governance Service (API): Exposes REST endpoints (/propose, /release) for Foundry/Assay integration.
  • Artifact Bundling: Aggregates code, data, and models into a single deployment folder.
  • Git LFS Management: Automatically handles large files and model weights.
  • Governance as Code: Blocks merges until a cryptographically signed SRB approval is received.
  • Automated Versioning: Manages SemVer based on change types (Patch/Minor/Major).
  • Reproducibility: Locks the specific "Council of Models" used for validation.

Documentation

For detailed documentation, please refer to the docs/ directory or the deployed MkDocs site:

Quick Start

Prerequisites

  • Python 3.12+
  • Poetry
  • Git LFS

Installation

git clone https://github.com/CoReason-AI/coreason_publisher.git
cd coreason_publisher
poetry install

Server Mode

Run the service via Docker:

docker run -p 8000:8000 \
  -e GITLAB_TOKEN="<token>" \
  coreason-publisher:latest

CLI Usage

To propose a new release locally:

poetry run python -m coreason_publisher.main propose \
    --project-id <PROJECT_ID> \
    --draft-id <DRAFT_ID> \
    --bump minor \
    --user-id <USER_ID> \
    --description "Release description"

For more details, see the Usage Guide.

Metadata

Release files for coreason-publisher 0.5.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 coreason-publisher 0.5.0
File Size Uploaded
coreason_publisher-0.5.0.tar.gz 29.5 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for coreason-publisher 0.5.0
File Interpreter ABI Platform
coreason_publisher-0.5.0-py3-none-any.whl Python 3 none any Details

Total release size: 74.5 kB

Release files / coreason_publisher-0.5.0.tar.gz

Download URL coreason_publisher-0.5.0.tar.gz
Size 29.5 kB
Tags Source
SHA-256 checksum
How to use checksums
681562ba361332984766f2129f901e389558a19192734e70842de73e1f1dd9d1
BLAKE2b-256 checksum
How to use checksums
f7ec74c31e6de712a18b3d87acd803a46e8f36eafd3a52a634cda61e9b9ed786
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 Jan 29, 2026.

Transparency log

Release files / coreason_publisher-0.5.0-py3-none-any.whl

Download URL coreason_publisher-0.5.0-py3-none-any.whl
Size 45.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
db694493fbc97bafaa30b95d38f75b312bd687a9b6d6714da2cfbc9448f3ede5
BLAKE2b-256 checksum
How to use checksums
f1e0308b693eb717df3c9cc9b98d2e7bbee09ddcad0c8890ef31870bf81f57e1
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 Jan 29, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.5.0 This release

2 release files

0.4.1

2 release files

0.4.0

2 release files

0.2.0

2 release files

0.1.0

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