TRAQ Server Documentation

This documentation is generated from in-code docstrings using Sphinx.

Contents

• Server Architecture Notes
  • Managed Extraction Context by Recording Granularity
  • Round Reconciliation Boundary
  • Standalone Tree Identification
• API Reference
  • Module: app.main
  • Extractor: Advanced Assessment Needed
  • Module: app.extractors.common
  • Module: app.extractors.registry
  • Module: app.pdf_fill
  • Module: app.report_letter
  • Module: app.traq_2_schema.build_traq_full_map
• Tree Identity Contract
  • Purpose
  • Operational rule
  • Authoritative source
  • Resolution rule
  • Database model
  • Client contract impact
  • Runtime API contract
  • Implementation status
• CLI User Guide
  • Purpose
  • Modes
  • Prerequisites
  • Interactive Use
  • What Is Covered
  • Known Limits
  • Common Cloud Workflows
  • Round Test Files
  • How To Read Failures
  • What To Update When Commands Change
• Local Development
  • Purpose
  • Supported local modes
  • Prerequisites
  • Repo bootstrap
  • Environment file
  • Local PostgreSQL workflow
  • Running the server
  • Running the admin CLI
  • Artifact retrieval workflow
  • Automated tests
  • Release verification helper
  • PostgreSQL parity lane
  • Manual smoke testing
  • Local Docker smoke test
  • Local data handling
  • Practical guidance
• Testing And Validation
  • Purpose
  • Local developer validation
  • What it covers
  • CI validation
  • Deployment validation
  • Post-deploy verification
  • Interpretation
  • Practical standard
• Database Schema
  • Purpose
  • Design rules
  • Model modules
  • Core tables
  • Intent by table
  • Operational direction
• Database Workflow
  • Purpose
  • Read model
  • Write model
  • Pruning model
  • Reporting model
  • Read-only query tool
• Archive Retention
  • Purpose
  • Policy
  • Why
  • Implementation boundary
• GeoJSON Storage
  • Purpose
  • Current approach
  • Why JSONB first
  • PostGIS direction
  • Current tooling
• Runtime vs Export Boundary
  • Purpose
  • Rule
  • Runtime authority
  • Artifact storage
  • Export/debug copies
  • Operational rule
  • Why this matters
• Legacy Import
  • Purpose
  • Tool
  • Current import scope
  • What this phase is for
  • Initial success conditions
  • Recommended verification queries
  • Next phase after success
• Legacy Import Validation 2026-03-14
  • Purpose
  • Environment
  • Import command used
  • Importer result
  • Observed filesystem reality
  • What imported successfully
  • Important findings
  • Assessment against initial success conditions
  • Recommended next changes
• Database Store Plan
  • Purpose
  • Module
  • Scope
  • Contract goal
  • Why this matters first
  • Current status
  • Next migration step