elecdef 0.1.0__tar.gz

elecdef-0.1.0/.gitattributes

@@ -0,0 +1 @@
+* text=auto eol=lf

elecdef-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,31 @@
+name: ci
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+permissions:
+  contents: read
+
+jobs:
+  ci:
+    runs-on: ubuntu-24.04
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        with:
+          fetch-depth: 0
+          fetch-tags: true
+      - uses: astral-sh/setup-uv@07a047e608db84b3d8c06cd9a7c7dcc9c355c18e # v10.3.2
+        with:
+          version: "0.13.5"
+      - run: uv sync
+      - run: uv python install 3.14
+      - run: uvx --from rust-just==1.59.0 just ci
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        if: github.event.repository.private == false
+        with:
+          repository: OleJBondahl/refdef
+          path: sibling
+      - run: uv run python scripts/family_compare.py sibling
+        if: github.event.repository.private == false

elecdef-0.1.0/.github/workflows/docs.yml

@@ -0,0 +1,35 @@
+name: docs
+
+on:
+  push:
+    tags: ["v*.*.*"]
+
+permissions:
+  contents: read
+
+jobs:
+  build:
+    runs-on: ubuntu-24.04
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+      - uses: astral-sh/setup-uv@07a047e608db84b3d8c06cd9a7c7dcc9c355c18e # v10.3.2
+        with:
+          version: "0.13.5"
+      - run: uv run python scripts/build_site.py
+      - uses: actions/configure-pages@45bfe0192ca1faeb007ade9deae92b16b8254a0d # v6.0.0
+      - uses: actions/upload-pages-artifact@fc324d3547104276b827a68afc52ff2a11cc49c9 # v5.0.0
+        with:
+          path: .site/
+
+  deploy:
+    needs: build
+    runs-on: ubuntu-24.04
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    permissions:
+      pages: write
+      id-token: write
+    steps:
+      - id: deployment
+        uses: actions/deploy-pages@368f82528645a54fb793d4d04e342629a3f51346 # v5.0.1

elecdef-0.1.0/.github/workflows/publish.yml

@@ -0,0 +1,39 @@
+name: publish
+
+on:
+  push:
+    tags: ["v*.*.*"]
+
+permissions:
+  contents: read
+
+jobs:
+  build:
+    runs-on: ubuntu-24.04
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+      - uses: astral-sh/setup-uv@07a047e608db84b3d8c06cd9a7c7dcc9c355c18e # v10.3.2
+        with:
+          version: "0.13.5"
+      - name: The tag matches the package version
+        run: test "v$(uv version --short)" = "$GITHUB_REF_NAME"
+      - run: uv build
+      - uses: actions/upload-artifact@cf430e030ddbb5b0abf93d22962f4752f3646cd9 # v7.0.2
+        with:
+          name: dist
+          path: dist/
+
+  pypi:
+    needs: build
+    runs-on: ubuntu-24.04
+    environment: pypi
+    permissions:
+      id-token: write # trusted publishing: no token secret
+    steps:
+      - uses: actions/download-artifact@9000827ccba6bdab643e8b6fd33ac0654aef8333 # v8.0.2
+        with:
+          name: dist
+          path: dist/
+      - uses: pypa/gh-action-pypi-publish@7245906fb61fa33a13554f9d5fb856fe61758086 # v1.14.3
+        with:
+          attestations: true

elecdef-0.1.0/.gitignore

@@ -0,0 +1,12 @@
+.venv/
+__pycache__/
+.ruff_cache/
+.pytest_cache/
+.coverage
+.superpowers/
+claude-tools/
+dist/
+.site-src/
+.site/
+.elecdef/
+.cache/

elecdef-0.1.0/.python-version

@@ -0,0 +1 @@
+3.15.0

elecdef-0.1.0/AGENTS.md

@@ -0,0 +1,12 @@
+# Agent guide
+
+- Docs site: https://olejbondahl.github.io/elecdef/
+- Surface: `python -m elecdef api`, snapshot in `docs/api-snapshot.txt`
+- Guide: `docs/guide/`
+- Design: `DESIGN.md`
+- Rules: `RULES.md`
+- A change follows RULES.md.
+- Design-review paths: `DESIGN.md`, `RULES.md`, `docs/api-snapshot.txt`, `src/elecdef/tables/`.
+  A commit touching them needs a `Design-review: <ID>` trailer.
+- A need the surface does not meet is a reviewed design change, never a workaround.
+- Use `uv` only, with exact pins.

elecdef-0.1.0/CLAUDE.md

@@ -0,0 +1,48 @@
+# elecdef: agent guide
+
+elecdef is a standard-agnostic electrical engineering vocabulary: strict, typed, immutable Python
+values with no runtime dependency. A sibling library follows the same family rules.
+Docs: <https://olejbondahl.github.io/elecdef/>. Surface: `python -m elecdef api`.
+
+## Read first
+
+Read `DESIGN.md`, then `RULES.md`. They bind: a change follows RULES.md, and code that disagrees
+with them is wrong. Family rules F1-F17 are shared with the sibling library; E1-E19 are ours.
+
+## Gate
+
+`just ci` runs locally (no hosted gate beyond one CI job): ruff, ty, vulture, pytest with a 95 %
+coverage floor, the tests on Python 3.14, the two guards, and the strict site build. Its last
+stdout line is `site built: .site`. Each shared test guards one family rule:
+
+- `test_deps` (F1): no runtime dependency, stdlib and the package only.
+- `test_pure` (F2), `test_check` and `test_malformed` (F3): frozen values, no I/O, issues as values.
+- `test_vocab` (F4): a closed vocabulary is never a bare `str`.
+- `test_boundary` (F5, F6, F13): no boundary names, no application default, no sibling import.
+- `test_wording` (F7 and the em-dash rule): no standard cited by number, clause or year.
+- `test_surface` (F8, F15): the snapshot equals `python -m elecdef api`; no operators on surface classes.
+- `test_docs` (F9) and `test_site`: every name has a docstring and a runnable guide block.
+- `test_lean` (F10): no nested def, 300 code lines, short docstrings, every noqa with a reason.
+- `test_release_guard` (F11) and `test_design_guard` (F12): the guard scripts can fail.
+- `test_licence` (F14), `test_agents` (F16), `test_standalone` (F17), `test_family_rules`, `test_pyproject_pins`.
+
+## Process
+
+- F12: a commit that touches a review path (`DESIGN.md`, `RULES.md`, `docs/api-snapshot.txt`,
+  `src/elecdef/tables/`) carries a trailer `Design-review: <ID>`. The maintainer approves the
+  contract; the design reviewer approves surface and table changes.
+- F13: a missing need is a reviewed extension of the surface, never a workaround or a private import.
+- F17: name no application anywhere, in a tracked or an untracked file, or in a commit message.
+- One source of truth for the surface: `docs/api-snapshot.txt`, regenerated with `just api-write`,
+  never edited by hand. A new surface name adds its door to `[tool.family].doors` and `_api.DOORS`
+  together, a docstring, a runnable guide block, a CHANGELOG line and its `docs/llms.txt` lines.
+- The identical test set listed in `scripts/family_files.txt` is copied byte for byte between the
+  sibling repositories; `scripts/family_compare.py` checks it. Edit it in both or in neither.
+
+## Style
+
+- `uv` only; no bare `python` or `pip`. Dependencies are exact pins (`name==X.Y.Z`).
+- No em-dashes in any text file.
+- Lean limits (F10): 15 statements, 12 branches, complexity 8, no nested `def`, 300 code lines per
+  module, docstrings of one summary line plus at most two of why, `# noqa: CODE - reason`.
+- Stage named paths with git; never `git add -A`.

elecdef-0.1.0/DESIGN.md

@@ -0,0 +1,209 @@
+# elecdef: design
+
+`elecdef` defines what electrical and electronic things are: a coil, a contact, a terminal, a
+connection, a fuse, a power supply, a PLC channel, a conductor, a cable. Each is a block with
+typed, exact, kind-checked values, its pin markings and its internal links. This file is the
+current truth of the model; `RULES.md` is the rule set every change follows.
+
+## 1. Purpose
+
+elecdef is for every electrical and electronic engineer working in Python: one typed, exact
+definition of each basic thing in the electrical world, so that nobody types a coil, a contact or
+a cable again. A parts library describes a real product by filling the blocks' values. An
+application, a script or a notebook reads the values through one small typed surface. The
+library judges nothing: it holds facts and looks them up. It has no runtime dependency and
+runs with or without the rest of the family.
+
+## 2. The family
+
+| Library | Owns | Never holds |
+|---|---|---|
+| `symdef` | how a thing is drawn: symbols, frames, ports, geometry | a rating, a unit, a marking's meaning |
+| `elecdef` | what a thing is: blocks, values, markings, internal links | a coordinate, a page, a designation string, a drawing key's meaning |
+| `refdef` | what a thing is called: designations, levels, letter codes, numbering, sort | a device fact, a marking's meaning |
+| an application | how a project connects, lays out, checks and prints | a copy of any fact above |
+
+A fact lives in exactly one library. A block names its symbol by a `Symbol(key, version)` and
+reads nothing from `symdef`. A pin marking (`13`, `A1`, `95`) is an elecdef fact; the string
+`-K1:13` is a refdef fact; which wire lands on it is the application's fact.
+
+## 3. Core model
+
+### 3.1 Values
+
+A `Quantity` is a `Decimal` and a `Unit`. A `Unit` is an enum member carrying a symbol, a `Kind`
+(voltage, current, power, apparent power, resistance, frequency, time, length, area, gauge,
+torque, ratio, temperature, temperature difference) and an exact factor to the kind's base unit.
+`U.V(24)`, `U.MM2("2.5")` is the one spelling; a `float` is refused. `==` compares as written,
+`same()` and ordering compare in base units, `to(unit)` converts within a kind and refuses across
+kinds. Percent is a unit of kind ratio. Degrees Celsius and kelvin are different kinds.
+
+A `Range` is written the way a datasheet states it: a role and up to three ends.
+
+```python
+Range(Role.RATED, nom=U.V(24), min=U.V("20.4"), max=U.V(30), at=At(Current.DC))
+Range(Role.LIMITING, max=U.V(250))
+Range(Role.REFERENCE, min=U.DEG_C(23), max=U.DEG_C(27))
+```
+
+`role` is positional and required: `RATED` is what the maker states for the stated conditions,
+`LIMITING` is an extreme the thing withstands, `REFERENCE` is the band other figures are stated
+for. `nom` is the marked value; an optional `typ` holds a measured typical and is never confused
+with it. `tolerance` is a property returning exact fractions derived from the ends; it is never
+written. Every end has one kind. `contains(quantity)` and `covers(range)` are the two tests.
+
+`At` is the set of conditions a figure holds under, one per kind: a `Quantity` (at 400 V), a
+`Range` (up to 250 V), or an enum member (`Current.DC`, `Utilisation.AC_3`, `CoilState.HOLD`,
+`ConductorKind.FINE`). A condition's kind is its unit's kind or its enum class. AC and DC are
+conditions, not fields, so one `Ranges` field (a tuple of `Range`) holds the 50 Hz, the 60 Hz
+and the DC figures side by side.
+
+### 3.2 Lookup
+
+`pick(ranges, *ask) -> Pick(found, issue)` returns the single range whose conditions cover the
+ask. A `Range` condition covers by inclusion, a `Quantity` by equality in base units, an enum by
+identity. A row may state more kinds than the ask names; the ask may not name a kind the row
+lacks. No covering row gives the issue `NO_RATING`; more than one gives `AMBIGUOUS_RATING`;
+there is no silent first match. This is data access. Whether a load is acceptable against the
+found range is the application's check, and elecdef stops at `found`.
+
+### 3.3 Blocks
+
+A block is a frozen dataclass stating what one kind of thing is. Every property may be unfilled.
+A property is a `Quantity` for a dimension or a count-like figure, a `Range` for an electrical
+figure, `Ranges` when it varies with conditions, an enum for a closed vocabulary, `int` or `bool`
+otherwise. Every quantity field declares its kind; a value of another kind is refused at
+construction. A field that holds a closed set is an enum, never a string.
+
+Blocks compose by typed fields, by value: `Relay.coil: Coil`, `Relay.contacts: tuple[Contact,
+...]`, `Coil.connection: Connection`. A leaf defined once is passed by reference into every block
+that has it; equality is by value. `elecdef.connections` ships technology-only leaves (`SCREW`,
+`PUSH_IN`, ...) with ranges unfilled; a parts library derives its vendor leaves from them with
+`dataclasses.replace` and shares those. Family identity of a derived leaf is not tracked. A
+`Connection` belongs to the pins a block owns itself: a block that owns pins directly has one
+`connection` field (a terminal block has one per side in `sides`), and a block whose pins all
+come from its sub-blocks has none. So `Coil`, `Contact`, `SupplyInput`, `ChannelGroup`, `Fuse`,
+`FuseHolder`, `Breaker`, `Overload`, `PowerSupply` (its output pins), `Connector` and `Device`
+carry one; `Relay`, `Contactor`, `ContactBlock`, `PlcCard` and `Computer` carry none.
+
+There is one base class, `Block`, for mechanism only: it runs the kind check and normalises a
+bare `Range` given to a `Ranges` field. An application never subclasses a block; `check` reports a
+block whose class is not in the catalogue. A family template and a product are the same class:
+the template holds ranges and gaps, the product holds values.
+
+### 3.4 Pins, markings and links
+
+A `Pin` is `(marking, role, side, alternates)`; a `Link` is `(markings, kind, closed_at_rest)`, `markings` a pair, with
+kind `CONDUCTIVE`, `SWITCHED` or `PROTECTIVE`. Markings follow the block: `elecdef.pins` derives
+them by form, index and `Marking` scheme (`AUX` n3-n4, n1-n2, n1-n2-n4; `MAIN` 1/L1-2/T1 ...;
+`OVERLOAD` 95-96, 97-98; `TIMER` n5-n6-n8; `PLAIN` 1-8) with alternates as data. A composite
+numbers its unnumbered sub-blocks on every read: a relay's contacts 1..n, a contactor's main
+poles then its auxiliaries, a contact block from `numbered_from`, a card's channels across its
+groups. A product may give pins outright; a coil or contact stores only those and computes the rest, so `replace` never leaves a stale marking. A composite's `pins` and `links` are computed over its
+sub-blocks and stored nowhere else. A marking is a non-empty string of letters, digits and
+`/ + - . '`, so every marking reads back unchanged in a designation string such as `-K1:13`.
+
+### 3.5 Product
+
+`Product(mpn, manufacturer, block, name)` is the one identity envelope: a block with its values
+filled, under a maker's part number. An application wraps it in its own record (suppliers,
+footprint, class letter) and never copies a block value out of it.
+
+### 3.6 Issues
+
+`check(block | product) -> tuple[Issue, ...]` reports content problems as values: an end below
+another, a marking that repeats, a marking outside the character set, a link naming no pin, a
+block kind missing a figure it needs, a class outside the catalogue. An `Issue` is `(code:
+IssueCode, message, subject)`. `IssueCode` has eight members: the six that `check` reports and the
+two that `pick` returns (`NO_RATING`, `AMBIGUOUS_RATING`). A malformed call (a wrong type, a wrong
+kind, two conditions of one kind in an `At`) raises `TypeError`; content never does.
+
+## 4. v1 catalogue
+
+| Block | Reuses | States |
+|---|---|---|
+| `Body` | - | width, height, depth; ip; temperature (rated, storage); mounting |
+| `Connection` | - | technology; conductor area per conductor kind; AWG as stated; conductors per clamp; strip length; torque; screw; pitch; material |
+| `Rating` | - | operational voltage per current kind; insulation and impulse voltage; thermal current; frequency; overvoltage category; pollution degree |
+| `SupplyInput` | Connection | what a powered thing draws: voltage and current per conditions; its supply pins |
+| `Contact` | Connection | form (make, break, changeover) and features; switching current per voltage, current kind and utilisation code; limiting voltage; minimum load; material; life |
+| `Coil` | Connection | kind; voltage per current kind and frequency; pick-up and drop-out as ratio; resistance; power and apparent power per coil state; times; suppression; A1-A2 |
+| `Conductor` | - | material; class; area; insulation; temperature; colour; voltages |
+| `Cable` | Conductor | cores (number, colour, pair, drain); screen; armour; diameter; bend radii; sheath; temperature; flags; opaque type code with scheme |
+| `TerminalBlock` | Connection per side, Rating, Body | kind; levels with marking and potential; sides; cross-section; width; rail |
+| `Relay` | Coil, Contact, Body | kind; contacts; latching; force-guided; timer function |
+| `Contactor` | Coil, Contact, Rating, Body | main poles; auxiliaries (a mirror contact is an auxiliary with that feature) |
+| `ContactBlock` | Contact, Body | a coil-less carrier: snap-on auxiliary block, button block, limit switch; actuator; first number |
+| `Overload` | Contact, Connection, Body | poles; setting; trip class; reset; phase failure; auxiliaries |
+| `Fuse`, `FuseHolder` | Connection, Rating, Body | system; class; current; voltage and breaking capacity per current kind; speed; indicator; poles; disconnect |
+| `Breaker` | Connection, Rating, Contact, Body | poles; current; curve; breaking capacities; auxiliaries |
+| `PowerSupply` | SupplyInput, Contact, Connection, Body | kind; input; output voltage and current; boost; hold-up; overload behaviour; circuit class; isolation; redundancy; efficiency; OK contact (`ok_contact`) |
+| `Channel`, `ChannelGroup` | Connection | signal and number; digital input, digital output, analog or relay data; a group's markings, commons, isolation and connection, written once for many channels |
+| `PlcCard` | SupplyInput, ChannelGroup, Body | form; role; bus; groups; safety levels |
+| `Connector` | Rating, Connection, Body | family; coding; poles; gender; locking |
+| `Computer` | SupplyInput, Connector, Body | supply; power; ports |
+| `Device` | Rating, Connection, Body | pins and links given outright: the typed fallback for a thing with no block yet |
+
+Vocabularies ship as enums in `elecdef.vocab`: industry codes are the member names
+(`Utilisation.AC_3`, `FuseClass.gG`, `TripCurve.C`) with short descriptions in our own words.
+Data tables ship as generated Python in `elecdef.tables`: the cross-section series, the AWG
+formula, colour letter codes, the 44-core colour sequence, breaker curve bands, trip classes,
+cable voltage digits, overvoltage categories, the E series. A table row ships only when its
+value is confirmed; a contested row waits.
+
+## 5. Public surface
+
+Top level (`elecdef.__all__`): `Unit`, `Quantity`, `Range`, `Ranges`, `Role`, `At`, `pick`,
+`Pick`, `Issue`, `IssueCode`, `check`, `Symbol`, `Product`, `Body`, `Rating`, `Connection`,
+`Contact`, `Coil`, `Relay`, `Contactor`, `ContactBlock`, `Overload`, `TerminalBlock`, `Fuse`,
+`Breaker`, `PowerSupply`, `PlcCard`, `Device`. Twelve doors, each with its own `__all__` of the
+names not exported at top level: `elecdef.vocab` (`Kind` and every vocabulary enum),
+`elecdef.pins` (`Pin`, `PinRole`, `Side`, `Link`, `LinkKind`, `Marking` and the marking
+functions), `elecdef.connections` (`SCREW`, `SPRING_CAGE`, `PUSH_IN`, `TENSION`, `IDC`, `CRIMP`,
+`SOLDER`, `PRESS_IN`, `PLUG_IN`, `BOLT`, `WIRE_WRAP`, `THT`, `SMD`), `elecdef.tables`,
+`elecdef.supply` (`SupplyInput`), `elecdef.fuse` (`FuseHolder`), `elecdef.plc` (`Channel`,
+`ChannelGroup`, `DigitalInput`, `DigitalOutput`, `AnalogIo`), `elecdef.terminal` (`Level`),
+`elecdef.conductor` (`Conductor`), `elecdef.cable` (`Cable`, `Core`, `TypeCode`),
+`elecdef.connector` (`Connector`), `elecdef.computer` (`Computer`, `Port`). The examples in this file assume `from elecdef import
+Unit as U`. `python -m elecdef api` prints every surface name with its signature and docstring;
+`docs/api-snapshot.txt` is that output, and a test fails when they differ.
+
+## 6. Out of scope
+
+Checks and judgements (is this load acceptable, is this wire big enough), derating and
+temperature factors, conductor resistance, cable type-code decoding (the `Scheme` enum and the
+opaque `TypeCode` leave the slot), calculations across blocks, instances and topology, where a
+pin is wired, drawing, designations and PLC tags, file reading or writing, multilingual names,
+assemblies of several products. Pilot devices, sensors, motors, passives and semiconductors
+arrive as blocks after v1; until then they are a `Device`.
+
+## 7. Docs and agents
+
+The repository publishes a GitHub Pages site built with Zensical (as `symdef` does) from the first
+public release. The site holds this design, the rules, a guide with one runnable example per
+surface name, and an API reference generated from the docstrings, so a name documented in code
+is documented on the site by construction. The strict Zensical docs build runs in CI.
+
+`llms.txt` at the site root lists, in plain text, what the library is, the surface names, the
+guide pages and the rules, with one link each. `AGENTS.md` at the repository root tells an
+agent: read `DESIGN.md` then `RULES.md`; read the surface with `python -m elecdef api` and never
+the source to use the library; every public name has an example under `docs/guide/`; the tests
+named in `RULES.md` are the definition of done; a change that touches the surface, the design or
+the rules needs a design review before it is written.
+
+## 8. How it changes
+
+Semantic versioning. Every surface change carries a changelog line. A pull request that edits
+`DESIGN.md` or `RULES.md`, changes `docs/api-snapshot.txt` or changes a shipped table under
+`src/elecdef/tables/`, carries a `Design-review:` trailer naming an approved review; a guard
+script fails it otherwise. An application's missing need is never met by a workaround in the
+application or a private path into the library: it is a reviewed design change that extends the
+surface. An application that adopts elecdef shrinks: it deletes its copy of the fact and reads
+the surface.
+
+Who approves is family rule F12: the maintainer approves the contract, and the design reviewer approves surface and table changes.
+
+## 9. Licence
+
+MIT, covering the code and the shipped tables. An open source used for a table is credited in
+the README and is never share-alike or non-commercial.

elecdef-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Ole Johan Bondahl
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

elecdef-0.1.0/PKG-INFO

@@ -0,0 +1,34 @@
+Metadata-Version: 2.5
+Name: elecdef
+Version: 0.1.0
+Summary: Standard-agnostic electrical engineering vocabulary as strict, typed, immutable Python values
+Project-URL: Repository, https://github.com/OleJBondahl/elecdef
+Author: Ole Johan Bondahl
+License-Expression: MIT
+License-File: LICENSE
+Requires-Python: >=3.14
+Description-Content-Type: text/markdown
+
+# elecdef
+
+Standard-agnostic electrical engineering vocabulary as strict, typed, immutable Python values.
+The library has no runtime dependencies and does no file, network, clock or random access.
+Every value is a frozen dataclass or an enum.
+
+Status: pre-release, version 0.1.0. The package is an empty scaffold.
+
+## Install
+
+```text
+uv add elecdef
+```
+
+Compatible with IEC conventions.
+
+Documentation: <https://olejbondahl.github.io/elecdef/>
+
+Licence: MIT.
+
+<!-- credit:start -->
+Credits: none yet.
+<!-- credit:end -->

elecdef-0.1.0/README.md

@@ -0,0 +1,23 @@
+# elecdef
+
+Standard-agnostic electrical engineering vocabulary as strict, typed, immutable Python values.
+The library has no runtime dependencies and does no file, network, clock or random access.
+Every value is a frozen dataclass or an enum.
+
+Status: pre-release, version 0.1.0. The package is an empty scaffold.
+
+## Install
+
+```text
+uv add elecdef
+```
+
+Compatible with IEC conventions.
+
+Documentation: <https://olejbondahl.github.io/elecdef/>
+
+Licence: MIT.
+
+<!-- credit:start -->
+Credits: none yet.
+<!-- credit:end -->