The bred litters

Where the planned page announced intentions, pups/bred.html announced results: litters already whelped, pairings that had produced puppies. A bulldog club's own bench keeps litter records as breed history; this kennel kept them as its own working ledger, born and dated.

A bulldog club's own bench keeps litter records as breed history; this kennel kept them as its own working ledger, born and dated.

What a bred page proves

A bred-litter page is the kennel's proof of work. It shows the pairing was made, the whelping happened, and puppies exist. For a visitor the page answered the question the planned page raised; for the bench it shows the kennel kept its accounts in public, recording what its matings produced rather than only advertising what it hoped for.

The pairing logic the pages imply

Read against the roster, the bred page is where the six males and thirteen females became combinations. The record does not preserve the pairings in readable form here, but the architecture, planned, bred, available, shows a kennel that thought in litters: a pipeline from intention to birth to sale that the site's navigation made explicit.

What the record does not keep

Litter sizes, puppy names, and the fate of each litter are not in the surviving captures. The page existed; its contents are the archive's silence.

The middle of the pipeline

Between intention and sale the bred page held the facts: a mating made, a litter whelped, puppies that existed and could be counted. In the kennel's three-page architecture it is the page that converts promises into inventory, and it is the page where a careful buyer would have looked for patterns, which pairings the kennel repeated, how often litters came, whether the program was steady or sporadic. The archive kept the page and not the patterns, so the bench files the architecture where it cannot file the account.

Why the page matters to the dogs file

Every male and female page in the roster was, in the end, working material for this page. The bred litters are where the named dogs stopped being portraits and became parents, and the bench reads the page as the point where the kennel's bookkeeping met the dogs' biology.

The two spellings of a litter

The record shows the pups directory carried three pages, planned.html, bred.html, and available_.html with its underscore, plus the stray puppies_original.html. The naming inconsistency, available_ beside available, is the same handmade signature the rest of the site carries, and it suggests the pups directory was assembled over time, each page added when the litter stage it described became real enough to need one. The bench reads the directory's uneven filenames as the record of a pipeline built litter by litter.

The limits of this sheet

No litter size, no pairing, no date survives on this page, and the bench keeps the page as architecture rather than account. What it proves is that the kennel kept a results column at all, which is rarer than it should be on a breeder's site and worth recording where the results themselves are gone. The bred page is also where the file's two halves meet. the-dogs keeps the parents; the-litters keeps what the parents produced; and this page was the hinge between them, the address where a named male and a named female became a dated litter. That the archive kept the hinge and lost the pairs it joined is frustrating but consistent: the site was built to announce, and the announcements were what the capture held.

How the bench files it

The bred page is filed as the kennel's results column: the middle of a three-page pipeline that ran from planned to bred to available, a small industrial record of a small breeding operation.