INDUSTRY FIELD GUIDE
Rabbit production inventory records for AI review
A shift note can describe an intended move while the inventory still reflects the earlier group.
NAICS 112930 · Fur-Bearing Animal and Rabbit Production
A shift note can describe an intended move while the inventory still reflects the earlier group. APHIS publishes rabbit sector information, including animal health context. A producer can design a completely fictional exercise to test custody and inventory reconciliation without using animal handling or health data. APHIS rabbit sector information
Use two mock pen aliases, a proposed move and a reviewer-confirmed inventory update for only one group. Add a copied log with an outdated date. Ask what the current practice records establish and which item requires review. Keep event, source and count as separate fields.
Do not record live animals or use actual locations, veterinary records, business counterparties, production data or employee information. Use an independently written packet and no animal welfare decisions.
Describe a synthetic inventory test
Original Fiund exercise
An intended group move and a reviewed inventory update are separate records
Two fictional rabbit-group aliases and abstract pens form a records-only fixture. It includes no animal handling, welfare finding, live footage or real inventory.
| Record | Source | What it records |
|---|---|---|
| RB1 | Day-1 register | Group G-A count 12 in pen P1; G-B count 8 in P2. |
| RB2 | Day-2 records | Proposed move of G-A to P3 has no completion. Reviewed update confirms G-B relocated from P2 to P4 with count 8 unchanged. |
| RB3 | Copied export | File copied on day 3 but content header says day-1 snapshot. Lists G-B in P2 and contains no later updates. |
Question for the model
Which group has a confirmed updated location, and does the copied file or proposed move change the latest documented state?
Show the reference answer and checks
RB2 confirms G-B's relocation to P4 while retaining its count of eight. G-A's proposed P3 move lacks completion evidence, so its latest confirmed location remains P1 from RB1. RB3 is a later copy of older content, not a day-3 observation; it cannot reverse G-B's reviewed update. Preserve content reference date separately from file-copy time and request confirmation for the planned G-A event.
- Using a file's copy timestamp as the inventory reference date.
- Updating a location from a proposal without completion evidence.
Fields to preserve
- Group, count and pen alias
- Defines the inventory state.
- Proposed versus confirmed event
- Separates intention from update.
- Content date and file-copy date
- Prevents stale snapshots from appearing current.
Test another case
Add a day-4 verified G-A inventory in P3 without an exact movement time. Require the latest location to update while the historical move time remains uncertain.
Use original fictitious records. Exclude health, personnel, locations and counterparties; keep all animal decisions outside the task.
Discuss a contribution
Describe the sources you control, the task they could support and what has already been checked. Use the existing-data assessment for an archive or the collection brief for a new recording project. The contributor agreement defines Fiund’s licensing authority and compensation. A guide or fictional exercise does not establish an accepted collection or a sale.