OPERATING AGREEMENT EXTRACTION BRIEF
Suggested instructions for a general document extraction workflow

Purpose: transcribe and index supplied documents for human review. Do not make
legal conclusions or treat extracted values as verified current ownership.

1. Inventory each supplied agreement, schedule, exhibit, and amendment. Assign
   a stable document ID and retain a distinct version label and source file.
   Report referenced files or schedules that were not supplied.

2. Document fields: entity name, agreement title, and effective date exactly as
   printed. Keep execution dates and other labelled dates separate. Do not use
   upload time or file creation time as the agreement's effective date.

3. Repeating member rows: document ID, version, member name, class or interest
   label, units, stated percentage, and contribution text exactly as printed.
   Keep ownership, voting, and distribution labels separate. Do not infer a
   percentage from units or a currency from an ambiguous symbol.

4. Evidence: retain the source file, page number and section where available,
   plus a short exact excerpt supporting each important value. Do not invent
   page numbers for text-only files.

5. Missing values: leave the value empty and use a separate status: not found,
   unreadable, missing exhibit, or conflicting sources. An absent value is not
   zero. Preserve unresolved conflicts rather than silently choosing a version.

6. Review: compare every member row and important document field with the
   original source. Check row boundaries, repeated headers, names, units, signs,
   dates, and percentages. Record corrections and the responsible reviewer.
   Keep normalized or calculated values separate from the printed source values.

7. Export: keep document fields and member rows in separate tables joined by
   document ID. Validate columns and types before mapping to a downstream system.
   Legal effect, signing authority, controlling versions, and current ownership
   remain questions for the responsible professional reviewer.

The accompanying CSV registers are planning examples, not product import presets.
Any EXAMPLE-OA-001 rows are fictional and must be replaced before real use.