atif-sql 0.2.0__tar.gz → 0.4.0__tar.gz

{atif_sql-0.2.0 → atif_sql-0.4.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: atif-sql
-Version: 0.2.0
+Version: 0.4.0
 Summary: ATIF-native analytics over Claude Code agent trajectories: convert, materialize, and query agent sessions with DuckDB.
 Project-URL: Homepage, https://github.com/laithalsaadoon/atif-sql
 Project-URL: Repository, https://github.com/laithalsaadoon/atif-sql
@@ -17,6 +17,7 @@ Classifier: Programming Language :: Python :: 3.13
 Classifier: Topic :: Software Development
 Classifier: Typing :: Typed
 Requires-Python: >=3.13
+Requires-Dist: anthropic>=1.11.0
 Requires-Dist: anyio>=4.11.0
 Requires-Dist: boto3>=1.42.91
 Requires-Dist: cyclopts>=5.1.1
@@ -94,6 +95,13 @@ are not supported. [RELEASING.md](RELEASING.md) says how to measure the install.
 `ATIF_SQL_EMBED_PROVIDER=gemma`, `embed` and `search` run on this machine instead and cost
 nothing. Nothing else in the tool needs a credential.
 
+`analyze` runs on OpenAI's GPT-6 models by default, and `ATIF_SQL_LLM_FAMILY=anthropic` switches
+it to Claude 5.5. It sends the user and agent turns of each session plus every tool call's name and
+the first 400 characters of its arguments. Each tool result goes as its size only, so command
+output and file contents stay on your machine unless you set
+`ATIF_SQL_SESSION_TEXT_TOOL_RESULT_BODIES=true`. The turns themselves still reach the model, so
+anything pasted into a conversation does too.
+
 ## What you can do
 
 Start with the question you want to answer or the work you want to keep. Each command links
@@ -141,7 +149,7 @@ the only thing documented as installable is the `atif-sql` CLI above.
 | `atif-converter` | Claude Code and Codex CLI transcript → ATIF converters (ours, built on Harbor's ATIF models, vendored) + per-agent fidelity policy (loss accounting per session) |
 | `atif-corpus` | Corpus materialization: discovery, watermarks, quiescence, atomic artifact writes |
 | `atif-duck` | DuckDB views + macros over the materialized corpus (core surface plus the v2 analytics surface) |
-| `atif-models` | Model alias registry + structured-output LLM client; no other package hardcodes a model id |
+| `atif-models` | Model alias registry + structured-output LLM clients for GPT-6 and Claude 5.5 on Bedrock; no other package hardcodes an LLM model id |
 | `atif-analytics` | the LLM pipelines `atif-sql analyze` runs: classify, conflicts, friction, and perceived |
 | `atif-embed` | Cohere Embed v4 on Bedrock or EmbeddingGemma 2 on this machine + LanceDB vector store + embedding backfill |
 | `atif-cli` | the composition root, and the source of the `atif-sql` command (see [What you can do](#what-you-can-do)) |
@@ -186,7 +194,7 @@ matching `ATIF_SQL_*` env var still wins.
 ```bash
 atif-sql materialize --agent codex
 atif-sql status --agent codex
-atif-sql query "SELECT agent, count(*) FROM sessions GROUP BY 1"
+atif-sql query --agent codex "SELECT agent, count(*) FROM sessions GROUP BY 1"
 ```
 
 One corpus holds one agent, so a Codex corpus and a Claude Code corpus stay
@@ -261,7 +269,7 @@ vulnerability in a tool that reads local transcripts are in
 corpus is registered (override with `ATIF_SQL_QUERY_MEMORY_LIMIT` and `ATIF_SQL_QUERY_THREADS`),
 a private spill directory outside the corpus that's removed on exit, no extension installs at
 query time (`atif-sql embed --install-extension` is where the lance extension comes from), file
-facing statements (`COPY`, `EXPORT`, `ATTACH`, `INSTALL`, `LOAD`, `PREPARE`, `EXECUTE`) refused
+facing statements (`COPY`, `EXPORT`, `ATTACH`, `DETACH`, `INSTALL`, `LOAD`, `PREPARE`, `EXECUTE`) refused
 before they run, and a refusal to run as root unless `ATIF_SQL_ALLOW_ROOT=1` says so. The details
 and the one accepted disclosure (`duckdb_settings()` lists the granted paths) are in
 [docs/reference/cli.md](docs/reference/cli.md#query).

{atif_sql-0.2.0 → atif_sql-0.4.0}/README.md

@@ -53,6 +53,13 @@ are not supported. [RELEASING.md](RELEASING.md) says how to measure the install.
 `ATIF_SQL_EMBED_PROVIDER=gemma`, `embed` and `search` run on this machine instead and cost
 nothing. Nothing else in the tool needs a credential.
 
+`analyze` runs on OpenAI's GPT-6 models by default, and `ATIF_SQL_LLM_FAMILY=anthropic` switches
+it to Claude 5.5. It sends the user and agent turns of each session plus every tool call's name and
+the first 400 characters of its arguments. Each tool result goes as its size only, so command
+output and file contents stay on your machine unless you set
+`ATIF_SQL_SESSION_TEXT_TOOL_RESULT_BODIES=true`. The turns themselves still reach the model, so
+anything pasted into a conversation does too.
+
 ## What you can do
 
 Start with the question you want to answer or the work you want to keep. Each command links
@@ -100,7 +107,7 @@ the only thing documented as installable is the `atif-sql` CLI above.
 | `atif-converter` | Claude Code and Codex CLI transcript → ATIF converters (ours, built on Harbor's ATIF models, vendored) + per-agent fidelity policy (loss accounting per session) |
 | `atif-corpus` | Corpus materialization: discovery, watermarks, quiescence, atomic artifact writes |
 | `atif-duck` | DuckDB views + macros over the materialized corpus (core surface plus the v2 analytics surface) |
-| `atif-models` | Model alias registry + structured-output LLM client; no other package hardcodes a model id |
+| `atif-models` | Model alias registry + structured-output LLM clients for GPT-6 and Claude 5.5 on Bedrock; no other package hardcodes an LLM model id |
 | `atif-analytics` | the LLM pipelines `atif-sql analyze` runs: classify, conflicts, friction, and perceived |
 | `atif-embed` | Cohere Embed v4 on Bedrock or EmbeddingGemma 2 on this machine + LanceDB vector store + embedding backfill |
 | `atif-cli` | the composition root, and the source of the `atif-sql` command (see [What you can do](#what-you-can-do)) |
@@ -145,7 +152,7 @@ matching `ATIF_SQL_*` env var still wins.
 ```bash
 atif-sql materialize --agent codex
 atif-sql status --agent codex
-atif-sql query "SELECT agent, count(*) FROM sessions GROUP BY 1"
+atif-sql query --agent codex "SELECT agent, count(*) FROM sessions GROUP BY 1"
 ```
 
 One corpus holds one agent, so a Codex corpus and a Claude Code corpus stay
@@ -220,7 +227,7 @@ vulnerability in a tool that reads local transcripts are in
 corpus is registered (override with `ATIF_SQL_QUERY_MEMORY_LIMIT` and `ATIF_SQL_QUERY_THREADS`),
 a private spill directory outside the corpus that's removed on exit, no extension installs at
 query time (`atif-sql embed --install-extension` is where the lance extension comes from), file
-facing statements (`COPY`, `EXPORT`, `ATTACH`, `INSTALL`, `LOAD`, `PREPARE`, `EXECUTE`) refused
+facing statements (`COPY`, `EXPORT`, `ATTACH`, `DETACH`, `INSTALL`, `LOAD`, `PREPARE`, `EXECUTE`) refused
 before they run, and a refusal to run as root unless `ATIF_SQL_ALLOW_ROOT=1` says so. The details
 and the one accepted disclosure (`duckdb_settings()` lists the granted paths) are in
 [docs/reference/cli.md](docs/reference/cli.md#query).

{atif_sql-0.2.0 → atif_sql-0.4.0}/docs/README.md

@@ -6,9 +6,11 @@ this codebase quietly assumes. Every factual claim carries a `path:LOC` citation
 Prose is generated; structure is mechanical. Cross-references are deterministic.
 
 Citations come as full paths or as shorthands, and each one resolves into a
-source file. A validator rejects any citation naming a file that does not exist, a line
-outside that file's range, or a shorthand with no resolvable antecedent, and it exits non-zero on the
-first one, so a citation here resolves or the tree does not ship.
+source file. The docs site build turns each one into a link and fails on the first citation naming
+a file that does not exist at the commit it links to, or a shorthand with no resolvable antecedent.
+`mise run docs:citations` also fails on a line outside its file and, against the base commit, on a
+citation whose cited lines a change moved or removed without editing the citation, so a citation
+here resolves to the code it names or the tree does not ship.
 
 ## Start here
 
@@ -24,8 +26,8 @@ first one, so a citation here resolves or the tree does not ship.
 
 - [System overview](architecture/system-overview.md): the short version, the stack, and one
   diagram of the workspace members.
-- [Module map](architecture/module-map.md): one section per member, ordered by source size, with the
-  files in each that carry the weight.
+- [Module map](architecture/module-map.md): one section per member, with the files in each that
+  carry the weight.
 - [Data flow](architecture/data-flow.md): the flows (`materialize`, `query`, `analyze`) traced end
   to end, each as a sequence diagram.
 
@@ -75,11 +77,11 @@ first one, so a citation here resolves or the tree does not ship.
 
 ## Documents this tree deliberately omits
 
-- **`analysis/ownership.md`**: the history sits under a single bot identity,
-  with no human authors. A per-person ranked table and a bus-factor list would be noise dressed as
+- **`analysis/ownership.md`**: every commit in the history names either the one maintainer or a
+  GitHub bot account. A per-person ranked table and a bus-factor list would be noise dressed as
   analysis.
 - **`reference/rpc-tools.md`**: there is no RPC, MCP, or HTTP surface. `fastapi`, `uvicorn`,
-  `starlette`, and the supabase client stack do appear in the installed dependency closure, arriving
+  `starlette`, and the supabase client stack do appear in the locked dev dependency closure, arriving
   transitively through harbor, and no first-party module imports any of them.
 
 An empty file in either slot would imply absence by omission rather than by silence, which is why

{atif_sql-0.2.0 → atif_sql-0.4.0}/packages/atif-analytics/README.md

@@ -6,11 +6,14 @@ The v2 analytics pipelines over the materialized ATIF corpus:
   read the materialized corpus (`trajectory.json` steps + `edges.jsonl`,
   each stored compressed or plain),
   render session transcripts under the documented caps, and classify through
-  `atif_models.LlmStructuredProvider` (GPT-5.6 strict structured outputs on
-  bedrock-runtime; sizes classify=luna, conflicts=sol, friction=luna,
-  perceived=terra). `classify` labels `work_category` and `goal` only.
+  `atif_models.domain.ports.LlmStructuredProvider` (GPT-6 or Claude 5.5
+  structured outputs on bedrock-runtime; sizes classify=small, conflicts=large,
+  friction=small, perceived=medium). `classify` labels `work_category` and `goal` only.
   `classify` and `conflicts` skip non-interactive sessions (`turn_audit`,
   `one_shot_job`), and `friction` and `perceived` read human turns only.
+  The transcripts carry user and agent turns and tool calls with their
+  arguments; each tool result is a size stub unless
+  `ATIF_SQL_SESSION_TEXT_TOOL_RESULT_BODIES=true`.
 * **Authorship** — `atif_analytics.domain.authorship` decides who wrote a
   user step (`human`, `stop_hook`, `task_notification`, `harness`,
   `audit_prompt`). It's a twin of `atif_duck.domain.authorship`, pinned by
@@ -22,8 +25,9 @@ The v2 analytics pipelines over the materialized ATIF corpus:
   sharded parquet caches under `<corpus_root>/analytics/<name>/`.
 
 Composition: atif-analytics imports **only** atif-models among the workspace
-packages (import-linter independence contract); atif-cli composes it with
-atif-duck's registered views via the `atif-sql analyze` command.
+packages (import-linter forbidden contract); atif-cli composes it via the
+`atif-sql analyze` command, handing it a session source over atif-duck's lake
+(`atif_cli.lake_sessions`).
 
 All pipelines default to `dry_run=True` and return plan dicts with
 `estimate_cost_tokens` projections (cost guard per CONTRACT-V2).

{atif_sql-0.2.0 → atif_sql-0.4.0}/packages/atif-analytics/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "atif-analytics"
-version = "0.2.0"
+version = "0.4.0"
 description = "LLM analytics pipelines over the materialized ATIF corpus: session classification, stance conflicts, user friction, and perceived errors."
 readme = "README.md"
 license = "Apache-2.0"
@@ -20,7 +20,7 @@ dependencies = [
     # a LOCAL source an external installer never sees, so a bare name would ship as
     # `Requires-Dist: atif-models` and resolve to whatever the newest release of
     # that name is. `[tool.commitizen] version_files` rewrites this line on a bump.
-    "atif-models==0.2.0",
+    "atif-models==0.4.0",
     "loguru>=0.7.3",
     "polars>=1.40.0",
     "pyarrow>=23.0.1",