Ingest sits between unstructured input (bytes, CSV uploads) and typed subledger rows. Runbooks useDocumentation Index
Fetch the complete documentation index at: https://docs.ntropii.com/llms.txt
Use this file to discover all available pages before exploring further.
ntro.ingest for shared outcome contracts and tenant Postgres writes into the ingest schema — see also Subledgers for ledgers.* and Workflows overview for orchestration.
Package layout
| Module | Role |
|---|---|
ntro.ingest.IngestOutcome | Structured summary of one ingest attempt: parsed/accepted/rejected counts, status, message, optional reasons and progress. |
IngestIssueSummary / IngestProgressSnapshot | Supporting types for reject reasons and progress gates. |
insert_submitted_record | Persists structured rows to ingest.submitted_records (data-ingest / agent submissions). |
insert_extracted_record | Persists reviewed AI extraction to ingest.extracted_payloads. |
IngestOutcome is re-exported from ntro.workflow next to NtroWorkflow so workflow code can depend on a single import surface.
User feedback from workflows
NtroWorkflow.set_user_feedback(kind=..., payload=...) attaches a workflow-agnostic envelope to the current pending action:
- Top-level
feedbackon the pending action display_hint.config.feedbackfor Tenant UI components (e.g.FILE_UPLOADreadskind: "ingest"and shows counts / message)
await_signal_with_action merges the latest stored feedback into the merged action so operators keep seeing progress.
Example: attach ingest feedback
Data lifecycle (reference)
- Unstructured — raw files / bytes (
ingest.submitted_documents). - Loosely structured —
ntro.ingestoutcomes +ingest.submitted_records/ events. - Structured + typed —
ntro.subledger/ledgers.*. - External GL shape —
ntro.capabilities.glposting contracts when applicable.
Related
Workflows overview
NtroWorkflow, @ui_step, and pending-action wiring.Subledgers
Domain rows after ingest.