How sudo-kno3/esa-suite works
esa-suite automates Phase I Environmental Site Assessment reports, from evidence collection through a reviewable Word draft. The principal workflow gathers source documents and field observations, parses and reconciles evidence, derives controlled findings, assembles and validates report sections, then delivers a draft for qualified-person review. Standalone chapter tools cover ERIS records, title searches, and physical setting; the Android field-form app supplies site observations. The editor applies tracked changes after draft generation. The graph follows the README’s product map and sampled implementation seams; several subsystem links reflect documented capabilities rather than inspected call sites.
Main entry points: pipeline/mod.rs Assessment pipeline · report.rs Report assembly · evidence/mod.rs Evidence assembly · app.rs Technical editor
Components 21
Evidence capture
- Field-form app
audit/source/field-form-app/app-kotlin/com/azimuth/fieldapp/MainActivity.kt - Field JSON export
audit/source/field-form-app/core/data/main/kotlin/com/azimuth/fieldapp/data/export/PackageWriter.kt
Report engine
- Document ingestion
report-engine/src/ingestion/mod.rs - Section engines
report-engine/src/ingestion/engines.rs - Evidence assembly
report-engine/src/pipeline/evidence/mod.rs - Assessment pipeline
report-engine/src/pipeline/mod.rs - Claims and findings
report-engine/src/claims/mod.rs - Fact graph
report-engine/src/graph/mod.rs - AI prose pass
report-engine/src/ai/pipeline.rs - Report assembly
report-engine/src/reporting/report.rs - Report sections
report-engine/src/reporting/sections/mod.rs - Release validation
report-engine/src/reporting/gate/mod.rs - Report delivery
report-engine/src/pipeline/deliver.rs
Draft and review
- Word draft
report-engine/src/reporting/output.rs - Technical editor
editing/src/app.rs - Style rules
editing/src/rules/engine.rs - Tracked changes
editing/src/docx/redline.rs
Chapter tools
- Standalone chapters
sections/3.8-physical-setting/src/engine.rs
Other components
- Assessor
- Source documents
- Qualified person
Connections 24
- Assessor → Source documents: provides
- Assessor → Field-form app: records observations
- Field-form app → Field JSON export: exports package
- Source documents → Document ingestion: parses inputs
- Field JSON export → Evidence assembly: supplies field data
- Source documents → Section engines: runs chapter extraction
- Standalone chapters → Section engines: produces chapter data
- Document ingestion → Evidence assembly: extracts evidence
- Section engines → Evidence assembly: returns JSON
- Evidence assembly → Assessment pipeline: feeds assessment
- Assessment pipeline → Claims and findings: derives findings
- Assessment pipeline → Fact graph: builds fact graph
- Assessment pipeline → Report assembly: assembles report
- Claims and findings → Report sections: informs rendering
- Fact graph → AI prose pass: provides fact context
- AI prose pass → Report assembly: refines prose
- Report assembly → Report sections: renders sections
- Report assembly → Release validation: validates draft
- Release validation → Report delivery: permits delivery
- Report delivery → Word draft: writes DOCX
- Word draft → Technical editor: opens for editing
- Technical editor → Style rules: reviews prose
- Technical editor → Tracked changes: writes redlines
- Tracked changes → Qualified person: presents for review