pythia-plsql 0.7.1__tar.gz → 0.9.0__tar.gz

{pythia_plsql-0.7.1/scripts/pythia_plsql.egg-info → pythia_plsql-0.9.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pythia-plsql
-Version: 0.7.1
+Version: 0.9.0
 Summary: PL/SQL development for AI agents on Oracle Database - expert data-dictionary queries, impact analysis, and a snapshot-verified write path with honest rollback.
 License: MIT
 Project-URL: Homepage, https://github.com/thaildhe172591/pythia
@@ -81,7 +81,8 @@ is the missing input, and forbids it to guess past them:
 
 - **Before any write**: the full preview — diff, dependents, warnings — is
   relayed verbatim, and the agent waits for a real yes. A compliment is not a
-  yes. Silence is not a yes.
+  yes. Silence is not a yes. And the wait is no longer a matter of obedience:
+  the write cannot complete until the developer mints the approval themselves.
 - **When the blast radius is large**: ten or more dependents, or anything
   cross-schema, goes to the developer *before code is written*, not after.
 - **When sources of truth disagree**: a standards document says one thing,
@@ -96,12 +97,15 @@ is the missing input, and forbids it to guess past them:
 ### 3 · Do — act inside a pipeline that cannot lie
 
 Only after Learn and Ask does anything touch the database, and then only
-through one door: **snapshot → impact → preview → token → apply → verify →
-report**. DDL self-commits in Oracle, so the snapshot is the only real undo —
-it runs first and no flag disables it. A content-bound token guarantees what
-lands is byte-for-byte what was approved. And the CLI enforces the gates
-itself: a headless agent cannot `--yes` its own writes or loosen policy —
-that takes a human at a real terminal.
+through one door: **snapshot → impact → preview → token → approve → apply →
+verify → report**. DDL self-commits in Oracle, so the snapshot is the only real
+undo — it runs first and no flag disables it. A content-bound token guarantees
+what lands is byte-for-byte what was previewed, and a **developer-minted grant**
+guarantees a person approved it at all: `pythia approve` runs only at a human's
+own console, and without its one-time grant `apply --confirm` refuses. The
+agent's command line is unchanged; what changed is that it now stops until
+someone acts. A headless agent cannot `--yes` its own writes, cannot approve
+them, and cannot loosen policy — each of those takes a human at a real terminal.
 
 The same discipline holds when the *developer* does the work: `src` and
 `impact` silently snapshot what they read, so even a change made by hand in
@@ -162,7 +166,7 @@ and WSL are all CI-tested.
 | `args` signatures | `invalid` everything broken | `unistr` exact non-ASCII literals |
 | `ddl` via DBMS_METADATA | `plscope` exact identifier usages | `agent-user` least-privilege setup |
 | `cols` columns + types | `similar` programs named like this | `history` every captured version |
-| `grep` search all source | | |
+| `grep` search all source | | `approve` the developer's one-time grant |
 | `sql` free query (SELECT/WITH only) | | |
 
 Every command takes `--json` (machine output), `--conn` (pick a connection), and
@@ -207,7 +211,7 @@ Per-group write policy, `.pythia/policy.json` (defaults shown):
 | Group | Default | Is rollback real? |
 |---|---|---|
 | `plsql_source` | `confirm` | **Yes — completely.** Source is recoverable from `ALL_SOURCE`. |
-| `data_dml` | `deny` | **No.** After commit only Flashback Query remains, within undo retention. |
+| `data_dml` | `deny` | **No.** After commit only Flashback Query remains, within undo retention. Revalidation checks the row set *before* the write; it is not an undo. |
 | `structural` | `deny` | **Almost never.** `DROP COLUMN` is permanent; a dropped table may be in the Recycle Bin. |
 | `grants` | `deny` | Yes, but by hand. |
 | `session` | `allow` | Not needed. |

{pythia_plsql-0.7.1 → pythia_plsql-0.9.0}/README.md

@@ -67,7 +67,8 @@ is the missing input, and forbids it to guess past them:
 
 - **Before any write**: the full preview — diff, dependents, warnings — is
   relayed verbatim, and the agent waits for a real yes. A compliment is not a
-  yes. Silence is not a yes.
+  yes. Silence is not a yes. And the wait is no longer a matter of obedience:
+  the write cannot complete until the developer mints the approval themselves.
 - **When the blast radius is large**: ten or more dependents, or anything
   cross-schema, goes to the developer *before code is written*, not after.
 - **When sources of truth disagree**: a standards document says one thing,
@@ -82,12 +83,15 @@ is the missing input, and forbids it to guess past them:
 ### 3 · Do — act inside a pipeline that cannot lie
 
 Only after Learn and Ask does anything touch the database, and then only
-through one door: **snapshot → impact → preview → token → apply → verify →
-report**. DDL self-commits in Oracle, so the snapshot is the only real undo —
-it runs first and no flag disables it. A content-bound token guarantees what
-lands is byte-for-byte what was approved. And the CLI enforces the gates
-itself: a headless agent cannot `--yes` its own writes or loosen policy —
-that takes a human at a real terminal.
+through one door: **snapshot → impact → preview → token → approve → apply →
+verify → report**. DDL self-commits in Oracle, so the snapshot is the only real
+undo — it runs first and no flag disables it. A content-bound token guarantees
+what lands is byte-for-byte what was previewed, and a **developer-minted grant**
+guarantees a person approved it at all: `pythia approve` runs only at a human's
+own console, and without its one-time grant `apply --confirm` refuses. The
+agent's command line is unchanged; what changed is that it now stops until
+someone acts. A headless agent cannot `--yes` its own writes, cannot approve
+them, and cannot loosen policy — each of those takes a human at a real terminal.
 
 The same discipline holds when the *developer* does the work: `src` and
 `impact` silently snapshot what they read, so even a change made by hand in
@@ -148,7 +152,7 @@ and WSL are all CI-tested.
 | `args` signatures | `invalid` everything broken | `unistr` exact non-ASCII literals |
 | `ddl` via DBMS_METADATA | `plscope` exact identifier usages | `agent-user` least-privilege setup |
 | `cols` columns + types | `similar` programs named like this | `history` every captured version |
-| `grep` search all source | | |
+| `grep` search all source | | `approve` the developer's one-time grant |
 | `sql` free query (SELECT/WITH only) | | |
 
 Every command takes `--json` (machine output), `--conn` (pick a connection), and
@@ -193,7 +197,7 @@ Per-group write policy, `.pythia/policy.json` (defaults shown):
 | Group | Default | Is rollback real? |
 |---|---|---|
 | `plsql_source` | `confirm` | **Yes — completely.** Source is recoverable from `ALL_SOURCE`. |
-| `data_dml` | `deny` | **No.** After commit only Flashback Query remains, within undo retention. |
+| `data_dml` | `deny` | **No.** After commit only Flashback Query remains, within undo retention. Revalidation checks the row set *before* the write; it is not an undo. |
 | `structural` | `deny` | **Almost never.** `DROP COLUMN` is permanent; a dropped table may be in the Recycle Bin. |
 | `grants` | `deny` | Yes, but by hand. |
 | `session` | `allow` | Not needed. |

{pythia_plsql-0.7.1 → pythia_plsql-0.9.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "pythia-plsql"
-version = "0.7.1"
+version = "0.9.0"
 description = "PL/SQL development for AI agents on Oracle Database - expert data-dictionary queries, impact analysis, and a snapshot-verified write path with honest rollback."
 readme = "README.md"
 license = { text = "MIT" }