sayfirst-cli 0.2.0__py3-none-any.whl

sayfirst_cli-0.2.0.dist-info/METADATA

@@ -0,0 +1,297 @@
+Metadata-Version: 2.5
+Name: sayfirst-cli
+Version: 0.2.0
+Summary: The product command-line interface of the sayfirst control plane
+Project-URL: Repository, https://github.com/fredaime/sayfirst-cli
+Project-URL: Documentation, https://github.com/fredaime/sayfirst-cli/blob/main/README.md
+Project-URL: Changelog, https://github.com/fredaime/sayfirst-cli/blob/main/CHANGELOG.md
+Author-email: fredaime <frederic.aime@gmail.com>
+License-Expression: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Classifier: Development Status :: 4 - Beta
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Requires-Python: <3.15,>=3.12
+Requires-Dist: sayfirst-boundary==0.2.0
+Requires-Dist: sayfirst-contract==0.2.0
+Description-Content-Type: text/markdown
+
+<!-- SPDX-License-Identifier: Apache-2.0 -->
+# `sayfirst` command-line interface
+
+The open-source command-line interface of the `sayfirst` control plane: the
+product CLI a user installs to connect an existing program to the boundary, to
+read what was decided, and to verify it afterwards. [`QUICKSTART.md`](QUICKSTART.md)
+installs it beside its daemon and walks one governed decision end to end — every
+command on that page was run before it was written down.
+
+Its content arrives as the partition of the private CLI, by copy with a
+provenance review, slice by slice. The first slice is here and it runs:
+[`docs/PARTITION.md`](docs/PARTITION.md) says what crosses and what is still
+open, and [`docs/PROVENANCE.md`](docs/PROVENANCE.md) says what arrived by copy
+— today, nothing, and why that is the right answer rather than an omission.
+
+## Three directions
+
+A client of this control plane does **three** things, and this repository ships
+all three.
+
+**Before an effect, it asks.** One question — a capability, a scope — put to the
+daemon over a socket whose peer it verified, and one answer rendered as it was
+given: allow, deny or suspend, and "could not ask" when the daemon could not be
+reached. That is `sayfirst ask`, and it is what the first slice implements.
+
+**It puts the boundary in front of somebody else's program.** `sayfirst
+instrument run --pack DIR … -- <program>` runs a program with the named effects
+asked about first, reversibly and with nothing written anywhere; `sayfirst
+instrument verify` runs it again under the interpreter's own audit hook and
+proves, from that and the scope's evidence chain alone, that every effect of a
+named kind was preceded by a decision; `sayfirst instrument apply` is reserved
+for the committed code modification and refuses, saying so. `sayfirst packs
+list` prints the convenience packs this distribution ships, one line each with
+the path `--pack` accepts, and `sayfirst packs check PATH` reads one the way the
+engine will before anything runs with it.
+[`docs/PACKS.md`](docs/PACKS.md) is the whole of it.
+
+**Afterwards, it reads and verifies.** Every read *from the daemon* names its
+scope explicitly (`--scope`) — the writer's `local` default does not apply. The
+two offline checks name a path instead and take no scope at all: `evidence audit
+--file` checks one saved bundle and `evidence exports` a directory of them, and
+both refuse `--scope`, because the file says which scope it holds. This is a
+surface rather than a list, and it grows by slices; what it answers today is
+below, and `sayfirst --help` is the claim that is kept in the dispatch itself.
+
+`sayfirst trace` reads back the record of one decision and follows it into the
+evidence that holds it: the record itself, and where it sits in the chain,
+bounded to the pages the read walks.
+
+`sayfirst explain` reads the reason the control plane gave for a decision — the
+rule it applied and the policy version it ran under — in the plane's own words,
+adding none of its own.
+
+`sayfirst evidence history` and `sayfirst evidence audit` page through scoped
+evidence: `history` renders what each page holds, `audit` puts the served
+verdict beside a local check and names a finding wherever the two disagree;
+`--file` checks an already-saved bundle offline, without opening a socket.
+
+`sayfirst evidence export` saves a bundle a third party can verify with the
+contract distribution alone, offline, no server code and no daemon; `--out`
+names where it is saved. A bundle taken while the daemon's current epoch is
+still open verifies with coverage `unknown` rather than `complete` — the honest
+answer, not a failure. `sayfirst evidence exports` lists and re-verifies every
+`*.json` bundle saved in a directory.
+
+`sayfirst approvals show` reads where one suspended wait stands: its state,
+when it was asked, when it ends, and — once a person has acted — when and why.
+`sayfirst approvals approve` and `sayfirst approvals reject` end that wait
+exactly once, an optional `--reason` and all, and render the same record
+`show` would: one person's act, and nothing that counts signatures or names a
+designation (article 12). These three follow the exit codes below, with no case
+of their own: an approval already resolved, asked again, answers
+`approval_resolved`, which the registry classifies as a refusal — so it is the
+`3` below, like every other refusal, and this client special-cases nothing.
+
+`trace`, `explain` and `evidence history` exit `0` on a read, whatever the
+record's own outcome. `evidence audit`, `evidence export` and `evidence exports`
+exit with the local check's result instead: `0` when it holds, `6` when it finds
+what the plane did not say, `7` when it cannot conclude — which is the ordinary
+answer for a bundle taken while the epoch is still open, and why
+`sayfirst evidence export && …` is not how to script one. A chain the verifier
+could not judge — an entry declaring a recipe this generation holds no reader
+for, a range assembled out of order, an instant outside the calendar — is `7`
+as well, with the sequence it stopped at: the answer arrived and the check could
+not conclude, which is neither a failure to obtain the answer nor a finding
+against the chain. Every command that reads from the control plane exits `3`
+when the request was refused, `4` when the plane could not be read from or the
+answer itself could not be read at all, and `64` on a misused invocation; a
+usage error the parser catches exits `2` everywhere.
+
+`sayfirst instrument verify` uses the same two local-check codes for the proof
+it makes: `0` only when every point of every designated pack was `governed` and
+no effect went unjudged, `6` for an effect no decision preceded — a finding this
+client made, never a denial the plane gave — and `7` when the check could not
+conclude, which includes a path the run never walked and an effect this proof
+could not judge. A run that concluded nothing at all says which of its endings
+happened, and answers with that ending's own code: `4` when the chain could not
+be read, before the program started or while it ran, and when the verifier never
+saw the program's own code start; `64` when the invocation was refused before it
+began; `7` when findings arrived and would not read. `sayfirst instrument run`
+owns none of these: it passes the governed program's own ending through
+untouched, and answers `64` only for mistakes in the invocation. `sayfirst packs
+list` exits `64` when a pack this distribution ships will not read — it names it,
+prints the rest of the list anyway, and never ends in a traceback.
+
+The operator closed Q-A on 2026-09-05: this repository owed the evidence
+surface, and its promise to read and verify became a commitment with a date on
+it — kept, as of this slice. [`docs/PARTITION.md`](docs/PARTITION.md) records
+the decision; [`docs/EVIDENCE-SURFACE.md`](docs/EVIDENCE-SURFACE.md) records
+what shipped and the contract support it used. Export verification uses the
+recipe and vectors from the contract distribution, without importing server
+code.
+
+None of the three defines control semantics or derives a decision. A client
+"explains and invokes" control semantics; it "never defines them, never keeps a
+decision past the lifetime the
+control plane gave it, and never derives an answer the control plane did not
+give" (article 1). Asking, instrumenting and reading are three ways of carrying
+an answer someone else made — the third of them, the verifier, reads the
+interpreter and the chain and reaches no verdict of its own about policy — and
+that is why all three belong to a client.
+
+## The first slice
+
+One command, end to end, against the open control plane's contract
+distribution: `sayfirst ask` puts one question to the daemon and renders its
+answer.
+
+```console
+$ sayfirst ask --capability example.effect --scope local --socket /run/user/1000/sayfirst.sock
+verified: true (server_uid 1000, expected 1000)
+outcome: allow
+reason: policy_allows
+capability: example.effect in scope local
+decision: decision-1 at 2026-09-04T20:11:45.929523+00:00
+policy version: sha256:44d91909ffe6283e67c73bad39d698448aa5e8bbdc1b5aa64a635a604e12f7e1
+```
+
+When the daemon cannot be reached, it says that, and it says it as its own
+result rather than as a refusal:
+
+```console
+$ sayfirst ask --capability example.effect --socket /run/user/1000/absent.sock
+verified: false (server_uid not stated, expected not stated)
+could not ask: unreachable: [Errno 2] No such file or directory
+retryable: true
+$ echo $?
+4
+```
+
+It exits `0` on `allow`, `1` on `deny`, `5` on `suspend`, `3` when the request
+was refused and `4` when the control plane could not be asked — because
+article 1 requires that "denied" and "could not ask" never read as each other.
+There is no `--url` and nothing that takes a token: the boundary says who the
+caller is, and it says so from the socket (article 6).
+
+## The gate
+
+`scripts/gate.sh` is the whole gate: format, lint, tests, and the guard that
+installs this distribution into an empty environment and reads back everything
+that arrived with it. That last one is article 13 made mechanical rather than
+promised — and it proves on every run that it can fail, by planting a web
+framework into the environment that has just passed and requiring the check to
+reject it.
+
+`sayfirst-contract` is on no index, because article 0 forbids publishing
+anything until the marks are filed. So the gate is told where a checkout of the
+control plane's repository is:
+
+```console
+$ SAYFIRST_CONTRACT_SOURCE=../sf-control-plane-lt ./scripts/gate.sh
+```
+
+It fails, rather than skipping, when it is not told. A skipped guard is a guard
+that cannot fail.
+
+## What binds here
+
+The constitution of the open control plane —
+[`CONSTITUTION.md`](https://github.com/fredaime/sayfirst-control-plane/blob/main/CONSTITUTION.md),
+in that repository — binds this repository too. Its article 0 says so: it binds
+"this repository and every other open repository of the project", and an open
+repository adopts it **by pointer, never by copy, because a copy drifts**.
+
+**That pointer became a link in the act that published this repository, and was
+not one before.** The open control plane is published as a repository created
+fresh (article 0), and until it existed the only URL this document could have
+carried was the one repository the project has decided never to publish — a link
+that would have resolved for nobody from the first public minute, in the
+document a newcomer reads first. `docs/publication-checklist.md` orders the
+control plane before this client for that reason, and
+`tests/test_pointers_survive_publication.py` still reddens on any reader-facing
+link to the repository that is never published — it is what kept the promise
+from being made early. The same applies to `TRADEMARKS.md`, which is why this
+repository carries one that points rather than one that copies.
+
+The articles this repository will answer to first:
+
+- **article 1** — a client explains and invokes control semantics; it never
+  defines them, never keeps a decision past the lifetime it was given, and never
+  derives an answer the control plane did not give;
+- **article 13** — the client depends on the contract distribution and never on
+  the server distribution, so installing it never installs a web framework or a
+  database layer;
+- **article 14** — nothing here imports, names or is shaped by a private
+  product; files that arrive from a private repository arrive by copy with a
+  provenance review;
+- **article 15** — Apache-2.0, contributions under the Developer Certificate of
+  Origin, read on every pull request by
+  `scripts/check_developer_certificate_of_origin.py`, which refuses a commit
+  carrying no well-formed sign-off and refuses a range it cannot read rather
+  than reporting it as passing.
+
+## The name
+
+The product and the command are **`sayfirst`**, decided by the operator on
+2026-09-04. Every
+distribution the open side publishes takes it as a prefix, the way the retired
+placeholder always said they would: this CLI as `sayfirst-cli`, and the plane as
+`sayfirst-control-plane` where the plane is named. *Which* distributions this
+repository ships is a different question — that is the partition, and it is not
+decided.
+
+### Who holds the command — decided, 2026-09-05
+
+This repository claims the distribution `sayfirst-cli`, the import package
+`sayfirst_cli` and the console script `sayfirst`. Until 2026-09-05 that was an
+assumption, stated as one: the control plane's repository claimed the same three
+names for its operator surface, each repository's guard read its own manifest
+and passed, and no test anywhere could see the other tree. The operator settled
+it on 2026-09-05, and all three names in all three forms belong to the product
+command-line interface, which is this repository.
+
+The control plane's repository is giving them up: its operator surface — the
+commands that inspect its daemon — takes the daemon's own form of the product
+name instead, the conventional Unix shape in which the daemon and the commands
+that inspect it share one binary. That change is on a branch there, dated
+2026-09-05 and not merged, so until it merges both trees still declare the three
+names. Nothing had been published under either claim (article 0), so the
+collision was a fact about two source trees and never about an installed
+environment. [`docs/PARTITION.md`](docs/PARTITION.md) records
+the question and its answer as Q-D.
+
+Deciding the name did **not** unblock publishing on its own. Article 0 forbids
+publishing anything under it — no package on an index, no public repository, no
+announcement — until three conditions hold together:
+
+1. **the name is decided** — met, 2026-09-04;
+2. **the marks are filed** — no file here can read a registry, so this
+   repository asserts nothing about it and a session reading this file must not
+   read the decided name as evidence of it. The date the filing was made and the
+   reference it produced are recorded on `docs/publication-checklist.md`, and
+   article 0 puts that act before any public repository of this project;
+3. **every occurrence of the placeholder is replaced** — done here; the
+   condition is project-wide, and the other repositories' occurrences are not
+   this repository's to change.
+
+## What is still not decided
+
+- **The partition.** Which parts of the private CLI cross, and what is renamed
+  on the way, is measured privately and executed slice by slice.
+  [`docs/PARTITION.md`](docs/PARTITION.md) proposes the open command surface,
+  names the three questions it does not close, and says plainly which of its
+  lines is a decision and which is a choice it made to keep moving. Two of its
+  questions are now answered — Q-D, the name collision, and Q-A, the evidence
+  surface — and both stay in the document, marked closed and dated.
+
+## Boundary with the control plane
+
+The control plane's operator surface keeps `status`, `doctor`,
+`policy show|history` and `plugins list`, which inspect its daemon's own state.
+`systems {register,retire}` also stays there pending its separate question.
+The 2026-09-05 decision assigns `trace`, `explain` and
+`evidence {audit,history,exports,export}` to this product client: they read the
+decisions and evidence the plane supplied. Q-B, Q-C and Q-E remain open; Q-D
+was already closed.

sayfirst_cli-0.2.0.dist-info/RECORD

@@ -0,0 +1,35 @@
+sayfirst_cli/__init__.py,sha256=8zgvziBPj_nkJGMyux6TNzilJB98tKmFWxMvdfI8ywA,112
+sayfirst_cli/approvals.py,sha256=RDhFSO9OtJcJW1jEoZiUCXsnh_mIHBDCix8-bWyOY08,5486
+sayfirst_cli/ask.py,sha256=wMvFQ5OF4AzKQ4m3Yx-c_UBJ2DgwlPrXIDZo9ZisD9A,7024
+sayfirst_cli/evidence.py,sha256=ce5z98Jk32W5snUx9NL8QMKOdz6F86LeFhw7Y4XNgcM,30378
+sayfirst_cli/exit_codes.py,sha256=8OswtauKZRSzFbsWBM3uRMbeSC3pRfjElbDLgaO1AJY,4269
+sayfirst_cli/explain.py,sha256=dMS-2--dbakoqGrvftFNU4aYoa6F5roiZ2B-bbLOOhU,1206
+sayfirst_cli/main.py,sha256=oumnv_oM0PDVxA-DMgFE7HlO3ybsmdaTUliRQZFPCAk,3185
+sayfirst_cli/packs_cmd.py,sha256=CU-oWDNzPHiNbpQZ7-_qAQXPcBDL7UIx32YvPjFGHe0,4936
+sayfirst_cli/pages.py,sha256=u5q8AiSAYA0FRZHj03lUtxkJokyzBQCcckk8pwUX0FU,4135
+sayfirst_cli/reads.py,sha256=cxuJ55woWlk5w33098ZofFpuMxlML9ITkB-_7YsH-N0,10511
+sayfirst_cli/render.py,sha256=3iokEciq6GYbF3aSBFkldUTU4EAB71WRuc2QB_P-ztc,5725
+sayfirst_cli/trace.py,sha256=W25lDI2ms55EIhT3EGavvBnJR5f_driZj-NAvcgLZMc,3733
+sayfirst_cli/instrument/__init__.py,sha256=XaUxOjGVni0ky3TMUAz0wVsbYajYX1GqBVzXj82aDas,778
+sayfirst_cli/instrument/commands.py,sha256=tXeAxFzMTLuIjF_97IcsSO0Ue9nfI4ZTERP7urXt0dI,8722
+sayfirst_cli/instrument/engine.py,sha256=ZjGKneNTo2vi8grrRVLZ4VmWJovYV0uiLZ9aIAg28tU,18300
+sayfirst_cli/instrument/harness.py,sha256=5sOw3eo_ZtIcWUh9MFj75jtoWc_RK_oEs7lcBpbSQh0,55202
+sayfirst_cli/instrument/launch.py,sha256=1O5DhLFMJIVQrXDH6pVg9gpxzvXVgeeEDdZjwQ7pjrA,19935
+sayfirst_cli/instrument/manifest.py,sha256=ESMCZQUmQIAa9cV7QtAjvs6jgBc677vKI6S9z8LHqOI,18367
+sayfirst_cli/instrument/verify.py,sha256=VLRoZw8hgr6GBsAOlFjIZLOWCmVB2FzahHO5uK0hC8Y,24651
+sayfirst_cli/packs/__init__.py,sha256=BKoZs2tFDTLr6vHx_jX0-jPKURL47lQt3ZxILtPz8CU,579
+sayfirst_cli/packs/database/NOTE.md,sha256=EDV00TSw6YR5USwmyCXWZAbQIWaZPNTDuSoHZQlOlhA,264
+sayfirst_cli/packs/database/interpose.py,sha256=gQwjIzbXSn7vg6XBt9IfGuPr9wJLocv3bu-rA3GMM4I,4308
+sayfirst_cli/packs/database/pack.toml,sha256=yJI5For50MJjMwMIkBWzvTblbbQr1jW19NYpTOm-ZYo,259
+sayfirst_cli/packs/http-client/NOTE.md,sha256=VmHzo9bfolFrf6YClRLk_Uc_q6W4e4_sz53-dH4nS1Q,271
+sayfirst_cli/packs/http-client/interpose.py,sha256=egTSO1lyFxv0cIULV9PmMBeyuutYTYfcVGbYOjMbJrg,3221
+sayfirst_cli/packs/http-client/pack.toml,sha256=3zFrhCZB9dwHnzFBIpUEYSSluoSMz0UZ5QXSOOOozkw,260
+sayfirst_cli/packs/subprocess/NOTE.md,sha256=nTwLjZqUNNoNB-pPye0bDARFWtVC2BpF26KjM-vH10o,278
+sayfirst_cli/packs/subprocess/interpose.py,sha256=tsbiz5kyxZkVL_NlQ4uz1iRDKIf_5x4L1TGp_Yc91ho,3955
+sayfirst_cli/packs/subprocess/pack.toml,sha256=2aKVEL2G_VSoH-frHPBcw--vL-3p23vsY3jIIdv0EBw,259
+sayfirst_cli-0.2.0.dist-info/METADATA,sha256=1gQvQ37L55XYGu8Ck4xuKl_NvJ7Qg3K6yN4RrP55GZI,16243
+sayfirst_cli-0.2.0.dist-info/WHEEL,sha256=zOwg4jB6zX2kU910N-cMawjivD6tO8NEWvE12je1bVk,87
+sayfirst_cli-0.2.0.dist-info/entry_points.txt,sha256=U5lrZxS9GCMN19c-MiO6TaHgVCiS-6XF51WnQ0JTAm4,51
+sayfirst_cli-0.2.0.dist-info/licenses/LICENSE,sha256=z8d0m5b2O9McPEK1xHG_dWgUBT6EfBDz6wA0F7xSPTA,11358
+sayfirst_cli-0.2.0.dist-info/licenses/NOTICE,sha256=MCkBvwpULbgh40rntVwPX_vjsx9LZIDYA8t6wGIXiMc,620
+sayfirst_cli-0.2.0.dist-info/RECORD,,

sayfirst_cli-0.2.0.dist-info/WHEEL

@@ -0,0 +1,4 @@
+Wheel-Version: 1.0
+Generator: hatchling 1.32.0
+Root-Is-Purelib: true
+Tag: py3-none-any

sayfirst_cli-0.2.0.dist-info/entry_points.txt

@@ -0,0 +1,2 @@
+[console_scripts]
+sayfirst = sayfirst_cli.main:run

sayfirst_cli-0.2.0.dist-info/licenses/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

sayfirst_cli-0.2.0.dist-info/licenses/NOTICE

@@ -0,0 +1,13 @@
+sayfirst command-line interface
+Copyright 2026 Frédéric Aime
+
+This product is licensed under the Apache License, Version 2.0 (the "License");
+you may not use these files except in compliance with the License. A copy of the
+License is in the LICENSE file at the root of this repository.
+
+Distributions that incorporate this software must reproduce the attribution
+notices this file carries (Apache License 2.0, section 4(d)).
+
+The Apache License grants no rights in the names and marks of this project; see
+the TRADEMARKS.md file at the root of this repository, which states where the
+project's one marks policy lives.