shulchan-aruch
Experimental. Lookup library for a personal codification of the Shulchan Aruch.
The published table is empty. lookup reads a local codex on the machine
where an entry was accepted. A citation with no local entry returns
not_codified.
Writes require the owner key. shulchan login --owner stores that key only
when it matches the hash shipped in this release. shulchan login stores an
OpenRouter API key. shulchan work drafts one citation through OpenRouter.
/accept writes the draft. /drop leaves the codex unchanged.
shulchan gui opens a local page at http://127.0.0.1:8731/. The page shows
the installed version, the project page, the owner, OpenRouter, and whether
shulchan-mcp is running. Lookup, draft, and accept use the same functions
as the command. The page also walks one ruling through the writing process.
A ruling is written the way the table was written, in six bits: place, sources, disagreement, decision, practice, and wording. Put the Rif, the Rambam, and the Rosh on the table. Where they differ, follow two of the three unless you say why not. Note where your own practice differs. Discuss the open bit. Settle it when that bit is finished. Only the short se'if is stored, and only after it is read back and accepted.
shulchan interview CITATION opens that ruling. --say records your line
and does not advance. --interviewer records the interviewer's line.
--settle stores the bit and opens the next. --back reopens the previous
bit. --accept writes the settled wording into the codex.
shulchan-mcp is a stdio MCP with lookup, status, draft_entry,
accept, interview_open, interview_say, interview_settle,
interview_back, and interview_accept. Draft, accept, and the interview
writes require the owner key.
The Eloq name of the lemma shulchan-aruch is שולקאן-ארוק.
from shulchan_aruch import lookup
lookup("Orach Chaim 1")
Install: pip install shulchan-aruch
shulchan is a registered name for this project. The index rejected
shulchanaruch as too similar to this project.
Metadata
Release files for shulchan-aruch 0.1.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 | Provenance | Actions |
|---|---|---|---|---|
| shulchan_aruch-0.1.3.tar.gz | 19.3 kB | Without provenance | Details for shulchan_aruch-0.1.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| shulchan_aruch-0.1.3-py3-none-any.whl | Python 3 | none | any | Details for shulchan_aruch-0.1.3-py3-none-any.whl |
Total release size: 37.7 kB
Release files / shulchan_aruch-0.1.3.tar.gz
| Download URL | shulchan_aruch-0.1.3.tar.gz |
|---|---|
| Size | 19.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a3ec72a9ea77505e52562bdc24e03f3c1d585ac679ed7598b7bf349515d555b5
|
|
BLAKE2b-256 checksum How to use checksums |
9b816559414dec6bf16600cd622dd7de0dc6a5ed8a178654610773f369d92ba7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.6
|
Release files / shulchan_aruch-0.1.3-py3-none-any.whl
| Download URL | shulchan_aruch-0.1.3-py3-none-any.whl |
|---|---|
| Size | 18.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3bd2e56dbea5d8d80512a67b67a5356b7dde2fd2d42ffdc844aab9552d7cf6c8
|
|
BLAKE2b-256 checksum How to use checksums |
419442b3e691cde40757429ea5a6e9de87f82c3d74265a651e9f52a2a156507e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.6
|
Security for shulchan-aruch 0.1.3
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.