sentience-governor 0.2.2__tar.gz

sentience_governor-0.2.2/CHANGELOG.md

@@ -0,0 +1,250 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/),
+and this project adheres to [Semantic Versioning](https://semver.org/).
+
+## [0.2.2] — 2026-04-28
+
+Patch release. No API changes. No command changes.
+
+### Fixed
+
+- **Default network timeout for `sentience-sync` raised from 15 seconds
+  to 30 seconds.** First-call latency on the cloud sync endpoint can
+  exceed 15 seconds on slower client networks, causing
+  `sentience-sync run` to fail with a network-error message even when
+  the request would have eventually succeeded. The new default
+  comfortably covers typical first-call latency while still failing
+  fast on a genuinely unreachable network. Operators can override
+  via the `SENTIENCE_SYNC_TIMEOUT_SECONDS` environment variable or
+  the `timeout_seconds` config key.
+- **Removed misleading `(placeholder)` suffix from `sentience-sync
+  status` output.** The status command previously appended
+  "(placeholder)" next to the production endpoint URL, suggesting
+  configuration was incomplete when it wasn't. Output now shows the
+  endpoint URL plainly.
+
+### Changed
+
+- **README and userdocs now recommend `pipx install sentience-governor`
+  as the canonical install method.** Modern macOS and Linux Pythons
+  enforce PEP 668 and refuse `pip install` outside a virtualenv;
+  `pipx` is the standard fix. Library integration via
+  `pip install sentience-governor` inside an active venv is still
+  documented and supported. Updated install guide and troubleshooting
+  cover both paths.
+
+## [0.2.1] — 2026-04-26
+
+Patch release. No API changes. No command changes.
+
+### Fixed
+
+- **Default network timeout for `sentience-sync` raised from 5 seconds
+  to 15 seconds.** The previous default was too tight for first-call
+  latency on the cloud sync endpoint and could cause `sentience-sync
+  register` to fail with a network-error message on first use. The new
+  default covers normal first-call latency comfortably while still
+  failing fast on a genuinely unreachable network. Operators on slow
+  links can raise the timeout further via the
+  `SENTIENCE_SYNC_TIMEOUT_SECONDS` environment variable or the
+  `timeout_seconds` config key.
+
+### Notes
+
+- macOS users running Python from python.org may see `SSL:
+  CERTIFICATE_VERIFY_FAILED` on first network call. This is a known
+  Python packaging quirk, not a Sentience issue. One-time fix:
+  `/Applications/Python\ 3.13/Install\ Certificates.command` (adjust
+  the version number to match your Python install). The troubleshooting
+  guide covers this in detail.
+
+## [0.2.0] — 2026-04-23
+
+First release talking to a live production endpoint. The
+governance runtime itself is unchanged from 0.1.9; the minor
+bump is driven by a breaking change in the
+`sentience-sync register` CLI surface.
+
+### Breaking
+
+- **`sentience-sync register` now requires `--email` and
+  `--name`.** Scripts that invoke `register` without these
+  flags will fail before any network call. This aligns the
+  CLI with the server's contract — contact info is required
+  because Sentience Sync is an opt-in communication channel.
+- **The Sentience Sync local state file format is bumped from
+  v1 to v2.** New fields: `installation_secret`,
+  `contact_email`, `contact_name`. No manual migration needed
+  — v1 state files are loaded cleanly, new fields default to
+  empty, and the file is re-written as v2 on the next
+  successful save. Upgrading from 0.1.9 is transparent.
+
+### Added
+
+- **Live production endpoint at `https://sync.getsentience.ai/v1`.**
+  All three routes — `/register`, `/sync`, `/update-check` —
+  are now served by a real backend. Previous versions shipped
+  with a placeholder URL.
+- **Bearer-token authentication on `/v1/sync`.** The
+  `installation_secret` returned at register time is stored
+  locally and presented on every subsequent sync call.
+- **`user_agent` field in registration payloads.** Identifies
+  CLI version + Python version + OS for server-side
+  observability.
+- **Duplicate-sync contract.** Re-running `sentience-sync run`
+  for a window that was already uploaded is now a successful
+  no-op. The server returns `duplicate=true`, the CLI prints
+  `Already uploaded for this window (sync_run_id=<id>)`, and
+  exits 0. Expected behaviour for cron retries.
+- **Targeted error messages.** Every expected failure path
+  surfaces a specific, actionable message:
+  - "Not registered. Run `register` first." — for a clean
+    first run
+  - "Registration incomplete or outdated. Run `register` again."
+    — for an upgrade-from-0.1.9 or corrupted state
+  - "Authorization failed. Your installation_secret may be out
+    of sync. Run `register` again (your installation ID will
+    be preserved)." — for a 401 response
+- **State-file permission hardening on POSIX.** The state file
+  is written with owner-only permissions (`0600`). On Windows,
+  best-effort equivalent with a warning if unavailable.
+- **Optional `--organization` and `--role` flags on register.**
+  For teams that want to tag their installation with more than
+  just the operator name.
+
+### Changed
+
+- **Default endpoint is live, not a placeholder.** The
+  "placeholder endpoint" caveat is gone from every surface —
+  documentation, CLI help output, code comments.
+- **`/v1/update-check` is now a GET with query string** (was a
+  POST with a body). No auth required. Matches the server's
+  public API.
+- **Payload shapes match the server contract exactly.**
+  Internal fields (`language_binding`, `deployment_label`)
+  that were never adopted server-side are dropped from the
+  wire format.
+
+### Security
+
+- **`installation_secret` stored in owner-readable JSON.** This
+  is best-effort local hardening — meaningful protection
+  against accidental exposure (other local users, backup
+  tarballs) but not a defense against local root. A
+  compromised secret can be rotated without creating a
+  duplicate installation.
+- **Bearer token never appears in the request body.** Only in
+  the `Authorization` header.
+- **Source IPs hashed server-side.** The raw source IP of a
+  sync request is SHA-256 hashed with a server-side pepper on
+  arrival and never stored.
+
+### Correctness invariant
+
+- **`register` never regenerates your `installation_id`** once
+  one exists locally. `--force` refreshes the secret but
+  preserves the ID. This keeps your history intact across
+  re-registrations and makes the server's recovery flow work
+  cleanly without creating duplicate rows.
+
+### Upgrade notes from 0.1.9
+
+1. `pip install --upgrade sentience-governor`
+2. Run `sentience-sync register --email you@example.com --name "Your Name"`
+3. Your existing `installation_id` is preserved; a fresh
+   `installation_secret` is issued and stored locally
+4. Any scripts that invoked `sentience-sync register` without
+   flags will need to be updated — the flags are now required
+
+Everything else continues to work. Per-session traces,
+`sentience` / `sentience-cli`, the Claude Code hook, and all
+library-integration paths are unchanged.
+
+## [0.1.9] — 2026-04-17
+
+Public release of the Sentience Governor open-tier runtime,
+including execution-boundary instrumentation, policy evaluation, local
+trace generation, and CLI tooling.
+
+### Added
+- Core governance runtime with 5 control points:
+  AGENT_REGISTERED, INTENT_DECLARED, SCOPE_ASSERTED,
+  CONTEXT_SNAPSHOT, MEMORY_WRITE_ATTEMPT
+- GOVERNANCE_ERROR event for runtime faults (sink failure, schema
+  violation, intercept failure, timeout)
+- MCP wrapper path (`wrap_mcp_client`) with `SentienceMCPAdapter`
+- LangChain adapter: `SentienceCallbackHandler` and
+  `SentienceMiddleware`
+- Honest intent classification: inferred inputs are marked
+  `intent_source=inferred` with `intent_confidence=inferred_low`,
+  never `explicit`
+- EventBuilder with 5 default policy rules (POL-001 through
+  POL-005) and 8 advisory flags
+- Session manager with IDLE → ACTIVE → CLOSING → CLOSED lifecycle
+- In-process per-session cache for intent baseline and sensitivity
+  tier tracking
+- Three sinks: StdoutSink, FileSink, HttpLocalSink with fail-open
+  semantics
+- CLI trace viewer (`sentience-cli`) supporting NDJSON and JSON
+  array input formats
+- Sentience Sync CLI (`sentience-sync`) for optional, explicit,
+  opt-in telemetry
+- Wrapper-based integration model requiring no modification to
+  agent logic
+- Open-tier design: observe-only, fail-open runtime with no
+  network calls or execution blocking
+- Claude Code hook adapter
+  (`sentience_governor.wrapper.claude_code_hook`) with
+  `sentience-claude-code-hook` CLI entry point. Zero-code
+  integration via `.claude/settings.json` produces governance
+  traces for every Claude Code tool invocation (`Bash`, `Edit`,
+  `Write`, `Read`, `Grep`, `Glob`, `WebFetch`, `WebSearch`,
+  `Agent`, and every `mcp__<server>__<tool>`). Observe-only,
+  fail-open, no credentials required.
+- **Per-session trace files by default** for the Claude Code
+  hook. Default sink is now a directory
+  (`~/.sentience/traces/claude-code/`) with one `<session_id>.jsonl`
+  file per Claude Code session, bounding growth naturally. Setting
+  `SENTIENCE_CLAUDE_CODE_SINK_PATH` to a path ending in `.jsonl`
+  keeps the legacy shared-file mode for operators who want every
+  session in one interleaved trace.
+- `sentience-cli` now accepts a directory argument: it globs
+  `*.jsonl` inside, merges the sessions, and renders them in one
+  pass. Single-file usage unchanged.
+- Sink-backed session resumption primitive
+  (`sentience_governor.session_manager.resumption`): atomic
+  sidecar index, forward-validation, linear-scan fallback,
+  file-locked read-plus-append critical section. Enables chain
+  continuity across fresh Python processes (used today by the
+  Claude Code hook; reusable by future adapters that need
+  process-restart survival).
+- `SessionManager.session_start` gains optional
+  `initial_sequence` and `initial_last_event_id` parameters for
+  pre-seeding chain state when resuming from disk. Defaults
+  preserve the original fresh-session behaviour for every
+  existing caller.
+- **New `sentience` top-level CLI** (subcommands: `status`, `list`,
+  `open`). Purpose-built for the agent-hook workflow where a single
+  Claude Code session can produce hundreds of tool calls. Uses a
+  baseline-noise classifier (pattern match + >80% frequency
+  threshold) to separate real anomalies from expected noise, then
+  renders a six-block output: Header, Summary (with `Status: ⚠` or
+  `Status: ✓` anchor), Focus (plain-English "what to pay attention
+  to"), Notes (baseline framing, shown only when relevant), Key
+  Events (anomalies only, max 10 with plain-English glosses), Full
+  Trace (one-liner per event), and Footer (tips + raw JSONL path).
+  The existing `sentience-cli` stays unchanged for library/MCP/
+  LangChain/golden-trace use — two-CLI architecture by design.
+- `sentience open --latest --summary` — skips the Full Trace block
+  so the rendered output fits on one terminal screen for busy
+  sessions. Every other block prints as usual; the JSONL file on
+  disk is unchanged.
+- Locked gloss table and event formatting table documented in the
+  plan (`docs/plans/sentience-cli-v1-ux.md`) and implemented in
+  `sentience_governor/cli/ux.py`. Unknown tools render with tool
+  identity preserved (`<tool_name> → ???`), enabling forward-
+  compatibility with future coding-agent adapters without code
+  changes.

sentience_governor-0.2.2/LICENSE

@@ -0,0 +1,191 @@
+
+                                 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 the 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 the 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 any 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
+
+   Copyright 2026 Crescere Labs, Inc.
+
+   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.

sentience_governor-0.2.2/MANIFEST.in

@@ -0,0 +1,10 @@
+include LICENSE
+include README.md
+include CHANGELOG.md
+include pyproject.toml
+recursive-include sentience_governor *.py
+recursive-include sentience_sync *.py
+prune tests
+prune examples
+prune docs
+prune server