Coders In Hoods

Courses
Answers
Setup
Bookmarks

Coders In Hoods Academy

Every course is free. Sign in to start, and your progress, quiz scores and bookmarks follow you.

Academy

Courses
Paths
Exercise answers
Setup guides
Bookmarks

Coders In Hoods

The agency
Coaching for teams

Social

LinkedIn
X (Twitter)

Contact

codersinhoods@gmail.com

© Coders In Hoods · since 2019

Free · no card

Coders In Hoods Academy

Sign in to start learning

Free, no card. We use your account to save progress, quiz scores, bookmarks and occasionally send updates from our team.

Course overview

Document Ingestion Pipelines

Free · sign in to start and track progress

1 · Reading real-world documents

1What a real case file contains
2Parsing: text layers to vision models
3Tables, plans and handwriting
4Structured extraction at scale

2 · Running ingest in production

5Durable ingest pipelines
6Re-ingestion, versioning and backfills
Exercise answers
- Answer: Build incremental re-ingestion with early cutoff
7PII detection and redaction
8Ingest evals and the hand-off

CapstoneIngest a case file end to end Reference implementation

Module 2 · Running ingest in production · Lesson 6

Re-ingestion, versioning and backfills

How to change parsers, prompts, schemas and models without re-running everything or losing history - content hashing, version keys per stage, early cutoff, document lineage, diff-before-promote, and bulk backfills through batch APIs.

70 min 1 video 3 exercises 7-question quiz Answers

Setup for the exercises:Install Claude Code Python with uv

By the end of this lesson you can

Model ingest as a build graph whose artefacts are keyed by input hash and stage version, and compute what a change invalidates
Apply early cutoff so unchanged intermediate outputs stop a rebuild from propagating
Version documents in the business sense (supersession, amendment) separately from pipeline versions, and keep what each agent saw
Plan a re-ingestion with an impact estimate, a shadow run and a field-level diff before promotion
Run a backfill through a batch API with stable request IDs, resumability and isolation from live traffic

The first version of your ingest pipeline will not be the last. Mistral releases a better OCR model; a fee earner asks for the break clause to be extracted from every lease; the TA6 gets a new edition; you find that the money normaliser mishandled "(£1,200.00)". Each change raises the same three questions. What must be recomputed? What will change for matters already in flight, and was it for the better? And when an agent advised on a matter last March, what exactly did it read? A pipeline that can't answer these either re-runs everything (expensively, and silently changing old matters) or never re-runs anything (and serves stale extractions for ever).

On this page

Intuition: ingest is a build
Keys: input hash plus stage version
Two meanings of "version"
Re-ingest in four steps
Backfills through batch APIs
Worked example: two changes to the archive
Connections
Summary
Sources & further reading
Quiz

The first version of your ingest pipeline will not be the last. Mistral releases a better OCR model; a fee earner asks for the break clause to be extracted from every lease; the TA6 gets a new edition; you find that the money normaliser mishandled "(£1,200.00)". Each change raises the same three questions. What must be recomputed? What will change for matters already in flight, and was it for the better? And when an agent advised on a matter last March, what exactly did it read? A pipeline that can't answer these either re-runs everything (expensively, and silently changing old matters) or never re-runs anything (and serves stale extractions for ever).

Free · sign in to start

Sign in to keep reading.

Free, no card. We use your account to save progress, quiz scores, bookmarks and occasionally send updates from our team.

8 more sections
3 hands-on exercises
A 7-question quiz
Progress, quiz scores and bookmarks