attention-firewall
attention-firewall (CLI: fw) is an open-source, local-first tool that helps
one knowledge worker measure and protect their bandwidth. It is inspired by
Cal Newport's Slow Productivity and implements his pull-based, two-column
project management style: a hard-capped Active column of slots for the
things you are actually working on, and a Holding column for everything
else that has been asked of you. Work is pulled into an active slot when one
opens. It is never pushed in by whoever asked loudest. The tool exists for the
people who get invited onto every project and need an honest number to answer
"when can you take this?" with a date instead of a yes.
Install
uv tool install attention-firewall
fw --version
Contributing
The project uses uv for everything. Never pip.
uv sync --locked
uv run pre-commit install
Every commit runs ruff, pytest (with a 70% coverage floor), and detect-secrets
through pre-commit. CI runs the same hooks. See AGENTS.md for the full rules
of engagement.
Metadata
Release files for attention-firewall 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 | Provenance | |
|---|---|---|---|---|
| attention_firewall-0.1.0.tar.gz | 1.7 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| attention_firewall-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.3 kB
Release files / attention_firewall-0.1.0.tar.gz
| Download URL | attention_firewall-0.1.0.tar.gz |
|---|---|
| Size | 1.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
44d6bb45970c0d0cc6f791cb3da303509b98c3140a0a34f525d0a052d444d4cb
|
|
BLAKE2b-256 checksum How to use checksums |
94b6e885867e7c25bc6a7a475e6b3df0619f5d51490b4a758b02c2d2e18b5087
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 14, 2026.
Transparency logRelease files / attention_firewall-0.1.0-py3-none-any.whl
| Download URL | attention_firewall-0.1.0-py3-none-any.whl |
|---|---|
| Size | 2.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
578c12441850c811b5605a59bbe0594eaef8bdc8157e3b05370cb6b2317bb401
|
|
BLAKE2b-256 checksum How to use checksums |
458b9c0d5cf29eae70248f4913ab5bfd4847ce3850626916203be9591cbb9747
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 14, 2026.
Transparency logSecurity for attention-firewall 0.1.0
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for attention_firewall-0.1.0.tar.gz
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 Sep 14, 2026.
Transparency logA 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.