org-unit
Digitalize the organizational structure (Aufbauorganisation) of a juristical person.
Built using the sw-dev-agent-framework
development process, starting from concept.md.
Development phases
| Phase | Skill | Status | Output |
|---|---|---|---|
| 1. Requirements | gather-requirements-en |
in progress | requirements.md |
| 2. Design | design-architecture-en |
pending | architecture.md |
| 3. Implement | apply-tdd-loop-en |
pending | src/ + tests/ |
| 4. Review | code-review-en |
pending | review.md |
| 5. Release | release-sw-project-en |
pending | tagged release |
Setup
uv sync
uv run sw-dev-agent start "Digitalize the organizational structure of a juristical person - see concept.md"
Run (Podman)
podman build -t org-unit .
podman run -d \
-p 8000:8000 \
-v org-unit-data:/app/data \
--name org-unit \
org-unit:latest
- OpenAPI spec: http://localhost:8000/openapi.json
- Swagger UI: http://localhost:8000/docs
- Web GUI: http://localhost:8000
Key design decisions
See concept.md for the full agreed concept.
Short summary:
- One OrgUnit tree (self-referencing parent_id)
- Flat Person table (no hierarchy)
- Assignment bridge table (N:M, carries role_label)
- No hard delete - deactivate via valid_until
- Bi-temporal: valid_from / valid_until (9999-12-31 = active) / updated_at
- mutation_reason mandatory on every POST and PATCH
- History tables: org_unit_history, person_history, assignment_history
- SQLite in /app/data/org-unit.db (Podman volume)
- DE/EN language switch in GUI
Metadata
Release files for org-unit 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| org_unit-0.1.0.tar.gz | 75.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| org_unit-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 86.5 kB
Release files / org_unit-0.1.0.tar.gz
| Download URL | org_unit-0.1.0.tar.gz |
|---|---|
| Size | 75.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5e04e3b6a3b37dce85c99658f7ab483ff0e86991980c20a1931d78ac35e01629
|
|
BLAKE2b-256 checksum How to use checksums |
4542fc12b0d83066e91416737d6ec8afc4ecaf94468fdef74df4b313cbf2cfc9
|
| 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 May 20, 2026.
Transparency logRelease files / org_unit-0.1.0-py3-none-any.whl
| Download URL | org_unit-0.1.0-py3-none-any.whl |
|---|---|
| Size | 10.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2bc31876601e76ce5f3916223397fdb0b63082ac6612825e10c1c27324056f27
|
|
BLAKE2b-256 checksum How to use checksums |
64d720c15997a9b637025b04fa07cdf86029bcab8543bba910b3318c6d444829
|
| 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 May 20, 2026.
Transparency log