Skip to main content

coreason-scribe

The "Compliance Officer in a Box" | Unified GxP Documentation Engine

CI/CD codecov Python Ruff pre-commit Poetry License

Executive Summary

coreason-scribe is the GxP documentation automation engine for the CoReason ecosystem. It addresses the "Validation Gap" where documentation inevitably drifts from code.

By treating Documentation as Code, coreason-scribe parses your agent's logic, uses AI to generate human-readable summaries (System Design Specifications), enforces Risk-Based Traceability (Requirements ↔ Tests), and facilitates a rigorous "Draft-Review-Sign" workflow. It ensures that no release is published without a cryptographically signed artifact proving it meets all requirements.

coreason-scribe can operate as a local CLI tool for developers or as a Compliance Microservice (FastAPI) integrated into CI/CD pipelines (e.g., coreason-publisher) and review platforms (coreason-foundry).

Core Philosophy: "Code is Truth. AI Drafts. Humans Ratify. Diffs Reveal Risk."

  1. AI as the Drafter: Scans Python AST and generates plain-English business logic summaries.
  2. Risk-Based Traceability: Enforces 100% test coverage for High Risk features.
  3. Semantic Delta: Surfaces logical drift between versions, not just line-by-line diffs.
  4. 21 CFR Part 11 Signatures: Requires cryptographic signatures for release certification.

Getting Started

Prerequisites

  • Python 3.12+
  • Poetry

Installation

poetry install

Basic Usage

Generate a draft SDS from your source code:

poetry run python -m coreason_scribe.main draft \
  --source ./src \
  --output ./build \
  --version "0.1.0"

Run a compliance check (CI/CD Gate):

poetry run python -m coreason_scribe.main check \
  --agent-yaml ./agent.yaml \
  --assay-report ./assay_report.json

For detailed instructions, see the Usage Guide.

Server Mode (Microservice)

Start the REST API server:

poetry run uvicorn coreason_scribe.server:app --port 8001
# OR
docker run -p 8001:8001 coreason-scribe:latest

Documentation

Development

This project follows a strict iterative, atomic, test-driven development protocol.

  • Linting: poetry run pre-commit run --all-files
  • Testing: poetry run pytest

Metadata

Release files for coreason-scribe 0.4.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-scribe 0.4.0
File Size Uploaded
coreason_scribe-0.4.0.tar.gz 21.5 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for coreason-scribe 0.4.0
File Interpreter ABI Platform
coreason_scribe-0.4.0-py3-none-any.whl Python 3 none any Details

Total release size: 50.2 kB

Release files / coreason_scribe-0.4.0.tar.gz

Download URL coreason_scribe-0.4.0.tar.gz
Size 21.5 kB
Tags Source
SHA-256 checksum
How to use checksums
41b5d0b8114361df5056245c7206d80fc6cbc4b1e241749427757c21c9deaf27
BLAKE2b-256 checksum
How to use checksums
3f6f39f3644d592f42f88ddeb404fda316d7a60fb12f07cae6e24b56ec989bc8
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 31, 2026.

Transparency log

Release files / coreason_scribe-0.4.0-py3-none-any.whl

Download URL coreason_scribe-0.4.0-py3-none-any.whl
Size 28.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
df8726d80d2957b0a38e417b6003cfd240b165ed21b933b1c5b6997e5edee1d7
BLAKE2b-256 checksum
How to use checksums
b4bb329059bd1cee0da8411eaf2b17d3b5e7c7133a6c099162f78b920a8f276e
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 31, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.4.0 This release

2 release files

0.3.1

2 release files

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