sayfirst-contract 0.3.0__tar.gz

sayfirst_contract-0.3.0/.gitignore

@@ -0,0 +1,10 @@
+# SPDX-License-Identifier: Apache-2.0
+__pycache__/
+*.py[cod]
+.pytest_cache/
+.ruff_cache/
+.venv/
+dist/
+
+# The working report of a change, kept beside the tree and never published.
+.sdd-quiet-gaps-report.md

sayfirst_contract-0.3.0/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_contract-0.3.0/NOTICE

@@ -0,0 +1,12 @@
+sayfirst control plane
+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
+TRADEMARKS.md.

sayfirst_contract-0.3.0/PKG-INFO

@@ -0,0 +1,146 @@
+Metadata-Version: 2.5
+Name: sayfirst-contract
+Version: 0.3.0
+Summary: The public domain contract and its generated binding
+Project-URL: Repository, https://github.com/fredaime/sayfirst-control-plane
+Project-URL: Documentation, https://github.com/fredaime/sayfirst-control-plane/blob/main/packages/contract/README.md
+Project-URL: Changelog, https://github.com/fredaime/sayfirst-control-plane/blob/main/CHANGELOG.md
+Author-email: fredaime <frederic.aime@gmail.com>
+License-Expression: Apache-2.0
+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
+Provides-Extra: stub
+Requires-Dist: sayfirst-contract-stub==0.3.0; extra == 'stub'
+Description-Content-Type: text/markdown
+
+<!-- SPDX-License-Identifier: Apache-2.0 -->
+# `sayfirst` contract
+
+This distribution publishes generation 1 of the transport-neutral domain
+contract and its generated HTTP-over-Unix-socket binding. It has no runtime
+dependencies. The scriptable fake is available only through the `stub` extra.
+
+## Scenarios
+
+<!-- BEGIN GENERATED SCENARIOS -->
+
+| Scenario | Binds | Article | Expected |
+|---|---|---:|---|
+| `allow` | both | 1 | `grant=present`, `outcome=allow`, `reason=policy_allows` |
+| `deny` | both | 1 | `outcome=deny`, `reason=policy_denies` |
+| `grant_expired_by_lifetime` | client | 10 | `grant=present`, `grant_use=expired`, `outcome=allow`, `reason=policy_allows` |
+| `grant_hit_within_lifetime` | client | 10 | `grant=present`, `grant_use=hit`, `outcome=allow`, `reason=policy_allows` |
+| `grant_miss_after_policy_version_change` | both | 10 | `after_policy_change={'grant': 'absent', 'outcome': 'deny', 'reason': 'policy_denies'}`, `grant=present`, `outcome=allow`, `reason=policy_allows` |
+| `grant_void_on_arguments_change` | client | 3 | `grant=present`, `grant_use=arguments_changed`, `outcome=allow`, `reason=policy_allows` |
+| `grant_void_on_connection_loss` | client | 10 | `grant=present`, `grant_use=connection_lost`, `outcome=allow`, `reason=policy_allows` |
+| `missing_policy` | both | 1 | `outcome=deny`, `reason=policy_absent` |
+| `no_grant_on_deny` | both | 10 | `grant=absent`, `outcome=deny`, `reason=policy_denies` |
+| `no_grant_without_signal_channel` | both | 10 | `grant=absent`, `outcome=allow`, `reason=policy_allows` |
+| `policy_unavailable_is_could_not_ask` | both | 1 | `grant=absent`, `problem=policy_unavailable`, `result=could_not_ask` |
+| `review_approve` | both | 12 | `outcome=suspend`, `reason=policy_requires_review`, `state=approved`, `after_resolution.outcome=allow`, `after_resolution.reason=approval_granted` |
+| `review_expire` | both | 12 | `outcome=suspend`, `reason=policy_requires_review`, `state=expired` |
+| `review_reject` | both | 12 | `outcome=suspend`, `reason=policy_requires_review`, `state=rejected`, `after_resolution.outcome=deny`, `after_resolution.reason=approval_rejected` |
+| `strictest_rule_wins` | server | 1 | `grant=absent`, `outcome=deny`, `reason=policy_denies` |
+| `unknown_outcome` | client | 13 | `problem=outcome_unknown`, `reported_outcome=unknown`, `result=could_not_ask` |
+| `unreachable` | client | 1 | `problem=unreachable`, `result=could_not_ask` |
+
+<!-- END GENERATED SCENARIOS -->
+
+## Server conformance replay
+
+Run each server-bound scenario — every row of the table above whose `binds` is
+`both` or `server` — against a daemon instance already arranged for that
+scenario:
+
+```console
+sayfirst-conformance replay \
+  --socket allow=/run/conformance/allow.sock \
+  --socket deny=/run/conformance/deny.sock \
+  --socket grant_miss_after_policy_version_change=/run/conformance/grant_miss_after_policy_version_change.sock \
+  --socket missing_policy=/run/conformance/missing_policy.sock \
+  --socket no_grant_on_deny=/run/conformance/no_grant_on_deny.sock \
+  --socket no_grant_without_signal_channel=/run/conformance/no_grant_without_signal_channel.sock \
+  --socket policy_unavailable_is_could_not_ask=/run/conformance/policy_unavailable_is_could_not_ask.sock \
+  --socket review_approve=/run/conformance/review_approve.sock \
+  --socket review_expire=/run/conformance/review_expire.sock \
+  --socket review_reject=/run/conformance/review_reject.sock \
+  --socket strictest_rule_wins=/run/conformance/strictest_rule_wins.sock
+```
+
+Name every server-bound scenario once: with `--socket SCENARIO=PATH`, or, for
+one the deployment cannot arrange a daemon for, with
+`--expected-absent SCENARIO=REASON`. A scenario named by neither has no daemon
+to replay against, and it fails. Client-only scenarios are reported as not
+applicable because their `binds` value does not include `server`. Every result
+line contains the scenario name, `proven`, `failed`, or `not-applicable`, and a
+reason, and the last line is the whole run's verdict: `proven` when every
+server-bound scenario is proven, `failed` when any one failed, and `unknown`
+when none failed and not every one was replayed — an expected absence, or a
+platform the client cannot verify a peer on — even when another scenario was
+proven. The exit status is that verdict's: `0` proven, `1` failed, `3` unknown.
+An invalid invocation replays nothing and exits `2`.
+
+The command has no way to change a daemon's policy or to move its clock, so
+three arrangements are the deployment's to make. The daemon for
+`grant_miss_after_policy_version_change` is asked the same question twice, and
+must answer the second under a policy that denies it. The daemon for
+`policy_unavailable_is_could_not_ask` must be unable to read its policy when it
+is asked; since a daemon refuses to start on a policy it cannot read, the file
+is broken after the start. And the daemons for the three that end a wait must
+serve both approval operations — the one for `review_expire` suspending with a
+wait shorter than the replay's `--deadline-wait-seconds`, and reading as
+expired as soon as that wait has passed.
+
+`sayfirstd conformance replay` is the same replay under the operator surface:
+the same options, the same whole-run line and the same exit statuses. Its
+scenario lines carry the name, the verdict and the reason; those of
+`sayfirst-conformance` add whether the scenario binds the server and how many
+expected members its verdict rests on.
+
+The default expects each per-user daemon to run as the invoking user. System
+daemon tests name its numeric account with `--expected-uid`. The client checks
+that identity before sending each request. `review_expire` waits 61 seconds by
+default; a test harness can inject its clock through `SocketHarness` instead.
+
+The repository acceptance suite uses the same mapping convention under
+`SAYFIRST_CONFORMANCE_SOCKET_DIR`: it looks for `<scenario>.sock` there and
+uses `SAYFIRST_CONFORMANCE_EXPECTED_UID` when the daemon does not run as the
+test user. When the socket directory is not configured, each case is an
+expected absence whose reason states that observed configuration fact. When it
+is configured, the same inventory runs live and carries no absence claim.
+
+## Distribution boundary
+
+The reusable replayer and its HTTP-over-Unix-socket client remain in this
+contract distribution. The client verifies the server's peer credential through
+the same adapters as the transport client, `transport.peer`, and maps failures
+to `impostor`, `peer_credential_unavailable`, `unreachable`, and
+`answer_unreadable`. A platform no adapter covers is not applicable to a
+replay, and on the path a boundary asks through, `hold_decision`, it is the
+could-not-ask `peer_identity_unsupported`. The socket client is published from
+`binding.http_unix_socket.client`; the replay harness is in the sibling
+`replay` module.
+
+This repository publishes the `sayfirst-conformance` distribution, the
+`sayfirst_conformance` import package and the `sayfirst-conformance` script;
+it also publishes the operator surface that inspects the daemon, from
+`packages/cli`, as the distribution `sayfirstd`, the import package `sayfirstd`
+and the console script `sayfirstd`. Each of those names is claimed once, by one
+distribution, and `tests/test_client_distribution_names.py` holds that against
+the `[project]` tables. The surface re-exports this operation as `sayfirstd
+conformance replay` while depending on this contract and on no server
+distribution.
+
+The distribution `sayfirst-cli`, the import package `sayfirst_cli` and the
+console script `sayfirst` belong to the product command-line interface and are
+not published from this repository; the operator settled that on 2026-09-05.
+
+This distribution installs no console script of its own, so nothing here is
+bound to the name of a surface that forwards to it. The operator surface
+`sayfirstd` is the one that reaches this operation today; the product
+command-line interface may reach it through these same modules, and no release
+of it does so yet.

sayfirst_contract-0.3.0/README.md

@@ -0,0 +1,127 @@
+<!-- SPDX-License-Identifier: Apache-2.0 -->
+# `sayfirst` contract
+
+This distribution publishes generation 1 of the transport-neutral domain
+contract and its generated HTTP-over-Unix-socket binding. It has no runtime
+dependencies. The scriptable fake is available only through the `stub` extra.
+
+## Scenarios
+
+<!-- BEGIN GENERATED SCENARIOS -->
+
+| Scenario | Binds | Article | Expected |
+|---|---|---:|---|
+| `allow` | both | 1 | `grant=present`, `outcome=allow`, `reason=policy_allows` |
+| `deny` | both | 1 | `outcome=deny`, `reason=policy_denies` |
+| `grant_expired_by_lifetime` | client | 10 | `grant=present`, `grant_use=expired`, `outcome=allow`, `reason=policy_allows` |
+| `grant_hit_within_lifetime` | client | 10 | `grant=present`, `grant_use=hit`, `outcome=allow`, `reason=policy_allows` |
+| `grant_miss_after_policy_version_change` | both | 10 | `after_policy_change={'grant': 'absent', 'outcome': 'deny', 'reason': 'policy_denies'}`, `grant=present`, `outcome=allow`, `reason=policy_allows` |
+| `grant_void_on_arguments_change` | client | 3 | `grant=present`, `grant_use=arguments_changed`, `outcome=allow`, `reason=policy_allows` |
+| `grant_void_on_connection_loss` | client | 10 | `grant=present`, `grant_use=connection_lost`, `outcome=allow`, `reason=policy_allows` |
+| `missing_policy` | both | 1 | `outcome=deny`, `reason=policy_absent` |
+| `no_grant_on_deny` | both | 10 | `grant=absent`, `outcome=deny`, `reason=policy_denies` |
+| `no_grant_without_signal_channel` | both | 10 | `grant=absent`, `outcome=allow`, `reason=policy_allows` |
+| `policy_unavailable_is_could_not_ask` | both | 1 | `grant=absent`, `problem=policy_unavailable`, `result=could_not_ask` |
+| `review_approve` | both | 12 | `outcome=suspend`, `reason=policy_requires_review`, `state=approved`, `after_resolution.outcome=allow`, `after_resolution.reason=approval_granted` |
+| `review_expire` | both | 12 | `outcome=suspend`, `reason=policy_requires_review`, `state=expired` |
+| `review_reject` | both | 12 | `outcome=suspend`, `reason=policy_requires_review`, `state=rejected`, `after_resolution.outcome=deny`, `after_resolution.reason=approval_rejected` |
+| `strictest_rule_wins` | server | 1 | `grant=absent`, `outcome=deny`, `reason=policy_denies` |
+| `unknown_outcome` | client | 13 | `problem=outcome_unknown`, `reported_outcome=unknown`, `result=could_not_ask` |
+| `unreachable` | client | 1 | `problem=unreachable`, `result=could_not_ask` |
+
+<!-- END GENERATED SCENARIOS -->
+
+## Server conformance replay
+
+Run each server-bound scenario — every row of the table above whose `binds` is
+`both` or `server` — against a daemon instance already arranged for that
+scenario:
+
+```console
+sayfirst-conformance replay \
+  --socket allow=/run/conformance/allow.sock \
+  --socket deny=/run/conformance/deny.sock \
+  --socket grant_miss_after_policy_version_change=/run/conformance/grant_miss_after_policy_version_change.sock \
+  --socket missing_policy=/run/conformance/missing_policy.sock \
+  --socket no_grant_on_deny=/run/conformance/no_grant_on_deny.sock \
+  --socket no_grant_without_signal_channel=/run/conformance/no_grant_without_signal_channel.sock \
+  --socket policy_unavailable_is_could_not_ask=/run/conformance/policy_unavailable_is_could_not_ask.sock \
+  --socket review_approve=/run/conformance/review_approve.sock \
+  --socket review_expire=/run/conformance/review_expire.sock \
+  --socket review_reject=/run/conformance/review_reject.sock \
+  --socket strictest_rule_wins=/run/conformance/strictest_rule_wins.sock
+```
+
+Name every server-bound scenario once: with `--socket SCENARIO=PATH`, or, for
+one the deployment cannot arrange a daemon for, with
+`--expected-absent SCENARIO=REASON`. A scenario named by neither has no daemon
+to replay against, and it fails. Client-only scenarios are reported as not
+applicable because their `binds` value does not include `server`. Every result
+line contains the scenario name, `proven`, `failed`, or `not-applicable`, and a
+reason, and the last line is the whole run's verdict: `proven` when every
+server-bound scenario is proven, `failed` when any one failed, and `unknown`
+when none failed and not every one was replayed — an expected absence, or a
+platform the client cannot verify a peer on — even when another scenario was
+proven. The exit status is that verdict's: `0` proven, `1` failed, `3` unknown.
+An invalid invocation replays nothing and exits `2`.
+
+The command has no way to change a daemon's policy or to move its clock, so
+three arrangements are the deployment's to make. The daemon for
+`grant_miss_after_policy_version_change` is asked the same question twice, and
+must answer the second under a policy that denies it. The daemon for
+`policy_unavailable_is_could_not_ask` must be unable to read its policy when it
+is asked; since a daemon refuses to start on a policy it cannot read, the file
+is broken after the start. And the daemons for the three that end a wait must
+serve both approval operations — the one for `review_expire` suspending with a
+wait shorter than the replay's `--deadline-wait-seconds`, and reading as
+expired as soon as that wait has passed.
+
+`sayfirstd conformance replay` is the same replay under the operator surface:
+the same options, the same whole-run line and the same exit statuses. Its
+scenario lines carry the name, the verdict and the reason; those of
+`sayfirst-conformance` add whether the scenario binds the server and how many
+expected members its verdict rests on.
+
+The default expects each per-user daemon to run as the invoking user. System
+daemon tests name its numeric account with `--expected-uid`. The client checks
+that identity before sending each request. `review_expire` waits 61 seconds by
+default; a test harness can inject its clock through `SocketHarness` instead.
+
+The repository acceptance suite uses the same mapping convention under
+`SAYFIRST_CONFORMANCE_SOCKET_DIR`: it looks for `<scenario>.sock` there and
+uses `SAYFIRST_CONFORMANCE_EXPECTED_UID` when the daemon does not run as the
+test user. When the socket directory is not configured, each case is an
+expected absence whose reason states that observed configuration fact. When it
+is configured, the same inventory runs live and carries no absence claim.
+
+## Distribution boundary
+
+The reusable replayer and its HTTP-over-Unix-socket client remain in this
+contract distribution. The client verifies the server's peer credential through
+the same adapters as the transport client, `transport.peer`, and maps failures
+to `impostor`, `peer_credential_unavailable`, `unreachable`, and
+`answer_unreadable`. A platform no adapter covers is not applicable to a
+replay, and on the path a boundary asks through, `hold_decision`, it is the
+could-not-ask `peer_identity_unsupported`. The socket client is published from
+`binding.http_unix_socket.client`; the replay harness is in the sibling
+`replay` module.
+
+This repository publishes the `sayfirst-conformance` distribution, the
+`sayfirst_conformance` import package and the `sayfirst-conformance` script;
+it also publishes the operator surface that inspects the daemon, from
+`packages/cli`, as the distribution `sayfirstd`, the import package `sayfirstd`
+and the console script `sayfirstd`. Each of those names is claimed once, by one
+distribution, and `tests/test_client_distribution_names.py` holds that against
+the `[project]` tables. The surface re-exports this operation as `sayfirstd
+conformance replay` while depending on this contract and on no server
+distribution.
+
+The distribution `sayfirst-cli`, the import package `sayfirst_cli` and the
+console script `sayfirst` belong to the product command-line interface and are
+not published from this repository; the operator settled that on 2026-09-05.
+
+This distribution installs no console script of its own, so nothing here is
+bound to the name of a surface that forwards to it. The operator surface
+`sayfirstd` is the one that reaches this operation today; the product
+command-line interface may reach it through these same modules, and no release
+of it does so yet.

sayfirst_contract-0.3.0/hatch_build.py

@@ -0,0 +1,50 @@
+# SPDX-License-Identifier: Apache-2.0
+"""Wheel-only build facts and repository notices."""
+
+from __future__ import annotations
+
+import os
+import tempfile
+from datetime import UTC, date, datetime
+from pathlib import Path
+from typing import Any
+
+from hatchling.builders.hooks.plugin.interface import BuildHookInterface
+
+
+class CustomBuildHook(BuildHookInterface):
+    """Embed the build date and reproduce repository notices in the wheel."""
+
+    def initialize(self, version: str, build_data: dict[str, Any]) -> None:
+        # In the workspace the notices live at the repository root and have to
+        # be carried in by hand. In an unpacked source distribution they
+        # travel beside the package, where the backend's own licence globs
+        # already find them, so carrying them again would add the same file
+        # twice.
+        root = Path(self.root)
+        if not (root / "LICENSE").is_file():
+            metadata_directory = (
+                f"{self.metadata.core.name.replace('-', '_')}-{self.metadata.version}.dist-info"
+            )
+            repository = root.parents[1]
+            build_data["force_include"].update(
+                {
+                    str(repository / "LICENSE"): f"{metadata_directory}/licenses/LICENSE",
+                    str(repository / "NOTICE"): f"{metadata_directory}/licenses/NOTICE",
+                }
+            )
+        epoch = os.environ.get("SOURCE_DATE_EPOCH")
+        build_date = (
+            datetime.fromtimestamp(int(epoch), UTC).date() if epoch is not None else date.today()
+        )
+        with tempfile.NamedTemporaryFile(
+            mode="w", prefix="sayfirst-build-", suffix=".py", delete=False, encoding="utf-8"
+        ) as descriptor:
+            descriptor.write(
+                f'# SPDX-License-Identifier: Apache-2.0\nBUILD_DATE = "{build_date.isoformat()}"\n'
+            )
+            self._descriptor = Path(descriptor.name)
+        build_data["force_include"][str(self._descriptor)] = "sayfirst_contract/_build_info.py"
+
+    def finalize(self, version: str, build_data: dict[str, Any], artifact_path: str) -> None:
+        self._descriptor.unlink(missing_ok=True)

sayfirst_contract-0.3.0/pyproject.toml

@@ -0,0 +1,49 @@
+# SPDX-License-Identifier: Apache-2.0
+[project]
+name = "sayfirst-contract"
+version = "0.3.0"
+description = "The public domain contract and its generated binding"
+readme = "README.md"
+requires-python = ">=3.12,<3.15"
+dependencies = []
+license = "Apache-2.0"
+
+authors = [{ name = "fredaime", email = "frederic.aime@gmail.com" }]
+classifiers = [
+  "Development Status :: 4 - Beta",
+  "Programming Language :: Python :: 3",
+  "Programming Language :: Python :: 3.12",
+  "Programming Language :: Python :: 3.13",
+  "Programming Language :: Python :: 3.14",
+]
+
+# The public repository this distribution sends a reader to. It was created
+# fresh, as article 0 asks, in the act that published it on 2026-09-17, under
+# the name the operator chose. `tests/test_pointers_survive_publication.py`
+# holds these URLs, so a rename lands in every project file and in the guard
+# together or not at all. No licence classifier: the licence is declared as an
+# expression above, and an index refuses a distribution that carries both.
+[project.urls]
+Repository = "https://github.com/fredaime/sayfirst-control-plane"
+Documentation = "https://github.com/fredaime/sayfirst-control-plane/blob/main/packages/contract/README.md"
+Changelog = "https://github.com/fredaime/sayfirst-control-plane/blob/main/CHANGELOG.md"
+
+[project.optional-dependencies]
+stub = ["sayfirst-contract-stub==0.3.0"]
+
+[tool.uv.sources]
+sayfirst-contract-stub = { workspace = true }
+
+[build-system]
+requires = ["hatchling==1.32.0"]
+build-backend = "hatchling.build"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/sayfirst_contract"]
+
+[tool.hatch.build.targets.sdist.force-include]
+"../../LICENSE" = "LICENSE"
+"../../NOTICE" = "NOTICE"
+
+[tool.hatch.build.targets.wheel.hooks.custom]
+path = "hatch_build.py"