Publish the package and its documentation, and move to the papers organization

Add the Zensical documentation of the Python package (docs/package, built by the docs
workflow), merge the standard publish workflow with the setuptools-scm tag check, add the
SPDX header rule to ruff, restructure the README, and point every repository and registry
address at the Gitea organization papers.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01B8cL4zN4XpaQF5cBtASzfq
This commit is contained in:
alexmandClaude committed 2026-10-19 04:23:49 -04:00
1 parent bdbf03ebee
commit 30d310f64d
37 files changed
+1005 -83

No files matched your search

+14
View File
@@ -0,0 +1,14 @@
# LLM assistance
Large language models (Anthropic's Claude, through Claude Code) write much of this code, its tests and its documentation, and we do not hide it.
The repository is built so that this is safe to rely on.
- **A person reviews every change.** A model proposes a commit; it does not decide one.
- **Checks gate the code.** `pixi run check` runs the formatter, the linter with the full rule set, the type checker, the Markdown lint, the pytest suite and the repository's own checker, `paperspec check`.
CI runs the same, with branch coverage that fails under 90%, and the stress test.
- **The oracle checks itself.** Every expected value in the vectors and fixtures is computed by the code and rebuilt byte for byte, so a change that alters a computed value shows up as a changed file in the diff.
- **Assisted commits are marked.** Each carries a `Co-Authored-By` trailer naming the model, and a `Claude-Session` trailer linking the session.
- **Claude's working material stays out of the repository.** Plans, notes and review reports live in an untracked `work/` folder.
The specification is the authority.
Where a model's code and a chapter disagree, the chapter wins and the code is the bug.