Find files, editable templates and browser test targets by what you need to make or test. The directory below is cut by format; the two collections under it cut the same library by subject and by workflow.
Service charge year end reconciliation for Pine Property Services. The year end settlement: each demise share of the 102,476.00 USD actually spent against the 96,000.00 USD paid on account, with the difference as a balancing charge. Every row share of actual less on account equals its balancing charge, and the charges sum to 6,476.00 USD, the overspend. No unit is in credit, so the credit column is 0.00 throughout and is kept as a column rather than dropped.
Site daily log for Pine Property Services. 9 daily entries, one for each completed work order, recording the crew, the labour hours and the weather. Hours total 27 and equal the labour hours the job cost report records against the same work orders. The four scheduled work orders have no log entry because no crew has attended them.
Work order export for Pine Property Services. 12 work orders across 6 properties, two per property, raised daily from 2026-08-01. 9 are completed and 3 are still scheduled. total_cost equals labour_cost plus materials on every row and the column sums to 2838.00. Costs are recorded on scheduled work orders as well as completed ones because the materials were bought in advance.
Work order export JSON for Pine Property Services. The same 12 work orders as work-order-export.csv with a byProperty rollup. Each of the 6 properties carries exactly 2 work orders and the totalCost figures sum to 2838.00.
A PKCS#12 (.p12/PFX) bundle packaging the sample RSA key and certificate together, protected with the sample password 'novus-sample', for testing keystore importers and PKCS#12 parsers. (The PKCS#12 MAC salt is random, so this file is intentionally not byte-stable.)
A PlantUML sequence diagram of an order interaction (customer, store, warehouse) as diagrams-as-code, for testing PlantUML parsing and diagram rendering pipelines.
Where the original view of glass water bottle on a plain white studio background, soft light landed inside the expanded frame, as JSON: the rectangle 64,32 to 576,544 in a 768x640 canvas, the padding that produced it, and the 40-pixel feather that means the comparison must be inset. Authored BEFORE the expansion ran, so it is ground truth rather than a rectangle recovered afterwards by matching the original against the result - which is what a consumer would otherwise have to do, and which cannot distinguish a correct offset from a plausible one.
Where the original view of potted houseplant on a plain neutral background, soft daylight landed inside the expanded frame, as JSON: the rectangle 0,192 to 512,704 in a 512x704 canvas, the padding that produced it, and the 40-pixel feather that means the comparison must be inset. Authored BEFORE the expansion ran, so it is ground truth rather than a rectangle recovered afterwards by matching the original against the result - which is what a consumer would otherwise have to do, and which cannot distinguish a correct offset from a plausible one.
Where the original view of single running shoe on a plain white studio background, soft light landed inside the expanded frame, as JSON: the rectangle 128,0 to 640,512 in a 768x512 canvas, the padding that produced it, and the 40-pixel feather that means the comparison must be inset. Authored BEFORE the expansion ran, so it is ground truth rather than a rectangle recovered afterwards by matching the original against the result - which is what a consumer would otherwise have to do, and which cannot distinguish a correct offset from a plausible one.
A product object that deliberately violates the product JSON Schema in five ways (out-of-range id, empty name, non-positive price, wrong boolean type, an extra property): the negative case for testing validator error reporting.
A JSON Schema (draft-07) describing a product object, with required fields, types, and constraints, paired with a conforming and a deliberately non-conforming instance for testing validators.
A single protobuf User message in binary wire format (varint + length-delimited fields): the serialized counterpart to the user.proto schema. For testing protobuf decoders without the generated code.
The compatible proto3 Customer message for field-number and wire-compatibility testing. Backward compatible: existing field numbers/types are retained and optional email uses new field number 3.
The baseline proto3 Customer message for field-number and wire-compatibility testing. Reference wire contract: field 1 is string id and field 2 is string name.
The breaking proto3 Customer message for field-number and wire-compatibility testing. Breaking relative to baseline: field number 2 is reused with a different name and wire type.
A realistic Python traceback with a chained exception ('During handling of the above exception...') and a caret error indicator. A fixture for testing traceback parsers and error-reporting tools.
A property-listings dataset: 30 homes with address, type, price, beds/baths, size, year built, coordinates, and status. Synthetic data for testing listing importers, map plots, and price analytics.
The exact answer for the blur variant of this receipt: every one of the 23 words with its string and pixel box, plus the transform that produced this variant. Authored before the image existed, so it is ground truth by construction rather than a second opinion.
