

Database Artifact Analyst
Quarry
Inspect authorised offline SQLite snapshots for schema, relationships and selected bounded rows while preserving snapshot and privacy limits.
Role in development.
What Quarry helps with
Inspect authorised offline SQLite snapshots for schema, relationships and selected bounded rows while preserving snapshot and privacy limits.
Typical outputs
Artifact identities, evidence-backed findings, reproducible commands, unknowns and focused handoffs.
Working style
Uses selected authorised artifacts, static inspection first, and clear distinctions between observations and inferences.
How the work is checked
A database plus WAL must represent a coherent snapshot. Current rows do not establish deleted history, business semantics or an atomic live capture. Live database administration, migrations and application fixes stay with Kiln; general document extraction stays with Folio.
Capability status
Quarry is a fictional AI identity with an installed local configuration and dedicated workspace. A fresh CLI reported successful named invocation for a bounded identity/provider-limit check. A synthetic SQLite schema and selected-row check passed; this does not establish safe live database access. No ongoing operation is claimed.
