القائمة
Run `mix customer.pipeline_status` to report a customer's law corpus readiness — from applicability through LAT parsing, fractalaw enrichment, to Baserow-ready governed duties.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Build a LAT parse session from a customer's applicable laws. Applies all necessary filters (in-force, not-revoked, missing LAT, making classification) before creating the session to avoid wasting parse effort on laws that don't need processing.
Safe procedures for modifying the database schema. Covers the uk_lrt view + INSTEAD OF trigger pattern, column type changes on partitioned tables, and migration best practices.
Create a scrape session programmatically from data (CSV, list of law names, query results). Handles session + record creation with correct schema constraints so records appear in the admin UI.
Sync a customer's legal register, duties, and actor tuples to Baserow. Covers the three-table model, significance filters, sync config, and common issues.
Generate a data quality report comparing a customer's legacy vendor register (Enhesa, Nimonik, etc.) against SertantAI's enriched legal database. Produces confusion matrix, revoked law analysis, coverage gaps, duty density, and family distribution. Outputs .md report + .csv appendices. Designed for customer senior management.
Import a customer's legacy legal register CSV (Enhesa, Nimonik, etc.), transform and match against LRT, group results into matched/scrapeable/not-handled, and create a scrape session for missing laws. First phase of customer onboarding.
| name | Customer Pipeline Status |
| description | Run `mix customer.pipeline_status` to report a customer's law corpus readiness — from applicability through LAT parsing, fractalaw enrichment, to Baserow-ready governed duties. |
cd backend
# QQ default org
mix customer.pipeline_status
# Specific org
mix customer.pipeline_status --org-id c075d56b-8420-4408-b695-ccfbc1ba15ec
# Per-law detail table
mix customer.pipeline_status --verbose
# Only show flagged laws (issues needing attention)
mix customer.pipeline_status --flags
Columnar table: law_name, title, live status, LAT count, taxa %, fractalaw stage, duty count.
1. Applicable (org_applicabilities status=yes)
2. In-force check (legal_register.live)
3. LAT parsed (legal_register.lat_count > 0)
4. Taxa enriched (legal_articles.taxa_enriched_at)
5. Fractalaw stage (needs_lat → needs_embed → needs_parse → needs_classify → needs_validate → ready_to_publish → published)
6. Governed duties (Obligation DRRP + non-Gvt active actors, aggregated to provision level)
Obligation = duties/responsibilities in Hohfeldian vocabGvt: and EU: prefixescustomer-onboarding-import — initial CSV import and applicability seedingcustomer-quality-report — quality analysis comparing vendor vs SertantAIlat-parse-session — parse LAT for applicable lawsprod-data-sync — sync data to production