Methodology
How this wire is read, and what it does and does not claim.
How to read this wire
Every row is an observed change; there is no status column. The blocks below are examples, not records — nothing here is a real filing, and live rows appear in the table.
- Observed absent -- a removal, and the shape the section below this box exists to carry. It is a WEAKER claim than a stated status change: the line reading "computed from successive complete checks" is what marks the difference. A complete check simply stopped returning the record. The register did not announce anything, and we are not saying why it went: that is the strongest claim a snapshot comparison supports.
Observed change
Observed change on record example: read "listed" observed 0001-01-02 00:00Z, and reads "no longer listed" as of 0001-01-02 18:00Z.
Example — not a real record
computed from successive complete checks
- A first sighting. The left date is the last complete poll of that shard that did NOT contain the record, so the absence is measured rather than assumed. Where no such poll exists the left side reads "no prior observation" and carries no date -- we will not print one we did not measure.
Observed change
Observed change on record example: read "not listed" absent as of 0001-01-01 00:00Z, and reads "listed" as of 0001-01-01 12:00Z.
Example — not a real record
stated by the register
- A status change the register itself states -- "stated by the register" under the block is how you know. Both states carry the same weight, and neither is struck through: TTB changed the status, we only observed it, and a line through a word would be us claiming we removed something. REVOKED IS NOT A FINDING OF MISCONDUCT -- TTB uses it when the labelling rules changed or when a certificate was approved in error. This is a validity wire, not an enforcement wire.
Observed change
Observed change on record example: read "approved" observed 0001-01-01 00:00Z, and reads "revoked" as of 0001-01-02 12:00Z.
Example — not a real record
stated by the register
- An observation gap. A dashed neutral rule, and no colour at all -- a gap is a limit on what our own polling can date, not a problem with the record, so it must not borrow the one colour a contested claim owns. Both dates are exactly what we measured; what the row refuses to do is date the change INSIDE the interval, because no complete poll of that shard ran between the two looks. It says the change happened somewhere in there, and declines to say when.
Observed change
Observed change on record example: read "approved" observed 0001-01-01 00:00Z, and reads "surrendered" as of 0001-01-06 12:00Z.
Observation gap — transition timing uncertain. No complete poll of this record’s shard finished between the two observations, so the change is bounded by the interval and not dated within it.
Example — not a real record
stated by the register
Method, scope and assurance
- Struckwire polls the public TTB Certificate of Label Approval registry four times a day and publishes what changed, with the date the register states and the date we observed it on every row.
- Source: the public TTB Certificate of Label Approval registry. Struckwire republishes record text and links to the original; label artwork is the applicant's property and is never reproduced here.
- A status here describes a certificate's administrative validity, not the conduct of any person or company. TTB records a certificate as surrendered when the holder no longer needs it, and as revoked when the rules changed or the certificate was approved in error. Neither implies wrongdoing.
- No accounts, no cookies, no tracking. If you choose a theme, that choice is stored in your browser so the page remembers it, and it is never sent to us. Opening a detail panel requests the same public page its link leads to, and nothing else. Every timestamp is UTC.