Cachet Presence and Type Note Classifier

Compare independently annotated cachet presence/type witnesses; no semantic classification of arbitrary notes. Independently established positive evidence requirements; overlapping compatible classes and unknowns retained. Caller independently verifies observations, reference edition, units and applicability; not a grading-service certificate, authentication, conservation treatment, actual market price or legal/insurance entitlement.

Description

Cachets can be categorized by production or design features under an explicit reference scheme.

Cachets can be categorized by production or design features under an explicit reference scheme.^[1]

This classifier compares caller-observed evidence with caller classes and preserves ambiguity instead of analyzing an illustration.

When to use Cachet Presence and Type Note Classifier

Use this tool when you need to compare explicit positive evidence requirements while keeping compatible and fully witnessed classes separate. Prepare independently verified observations, reference edition/context, and matching units or currency basis.

How to use Cachet Presence and Type Note Classifier and understand its results

Prepare independently verified observations, reference edition/context, and matching units or currency basis.
Enter callerCachetTypeClassIds, callerCachetTypeRequirements, observedCachetTypeEvidence, knownCachetTypeFlags, following the field table and calculation rules below, then run the tool.
Read compatibleCallerClasses, fullyWitnessedCallerClasses. For result objects, inspect the nested output fields below, including any missing evidence or selected indices.
Correct any input issues and run again. Before using a successful result, review its units, signs, evidence coverage, and stated model or reference assumptions.

Input field	Meaning	Value type	Requirement
callerCachetTypeClassIds	Caller cachet type class ids	list of string	Required
callerCachetTypeRequirements	Caller cachet type requirements	numeric matrix	Required
observedCachetTypeEvidence	Observed cachet type evidence	list of number	Required
knownCachetTypeFlags	Known cachet type flags; binary 1 means assessed and 0 means unknown.	list of number	Required

Prepare unique nonblank caller class IDs and a nonempty rectangular binary requirement matrix, with rows aligned to classes and columns to observed evidence and known flags. Every class must require at least one positive feature. A one requires positive evidence; zero ignores the feature and does not require its absence. Both evidence and known flags must be binary. Known required evidence equal to zero excludes a class; unknown required evidence leaves it compatible but unwitnessed. Return every compatible class and the subset for which all required positive evidence is known and present. Requirements can overlap and do not imply a single winner.

compatible_c=∀j(requirement_cj=0 or known_j=0 or evidence_j=1); witnessed_c=∀j(requirement_cj=0 or (known_j=1 and evidence_j=1))

Read these symbols with the field meanings and branch or reference rules above.

Output field	Meaning	Value type
compatibleCallerClasses	All supplied classes with no contradiction in known required positive evidence, preserving reference order.	list of string
fullyWitnessedCallerClasses	Compatible supplied classes whose required positive evidence is entirely known and present.	list of string

json

{
  "input": {
    "callerCachetTypeClassIds": [
      "a",
      "b"
    ],
    "callerCachetTypeRequirements": [
      [
        1,
        0
      ],
      [
        0,
        1
      ]
    ],
    "observedCachetTypeEvidence": [
      1,
      0
    ],
    "knownCachetTypeFlags": [
      1,
      0
    ]
  },
  "output": {
    "compatibleCallerClasses": [
      "a",
      "b"
    ],
    "fullyWitnessedCallerClasses": [
      "a"
    ]
  }
}

Limitations and assumptions

Class definitions and evidence observations must be independently established for the relevant issue and reference context. Compatibility with incomplete evidence is not a positive identification, and fully witnessed classes satisfy only the supplied requirements.

Missing required fields, unknown fields, wrong types, and violated calculation rules return input issues. Numeric values must be finite; nonfinite numeric outputs are rejected. Arrays must be dense, with no missing cells. Numeric lists allow at most 10000 entries, subject to smaller tool-specific bounds above. Ordinary string lists allow at most 128 strings of at most 128 UTF-16 units each. Numeric matrices allow at most 128 rows and 128 entries per row, with exact shape requirements stated above.

Alternative or Complementary methods

For a related task, use First Day Cover Postmark Date Match Validator: A first-day cancellation should be compared with the relevant issue date under an explicit calendar convention. This validator reports exact date equality and the signed postmark-to-issue interval. For a complementary step, use Printing Method Identifier (recess/litho/typo) Decision Tree: Printing methods leave physical features that require independent observation and contextual interpretation. This decision aid returns caller classes compatible with supplied evidence rather than a single inferred printing method.

References

Cachet Presence and Type Note Classifier — tool.io

Similar or alternative tools

First Day Cover Postmark Date Match Validator
A first-day cancellation should be compared with the relevant issue date under an explicit calendar convention. This validator reports exact date equality and the signed postmark-to-issue interval.
Printing Method Identifier (recess/litho/typo) Decision Tree
Printing methods leave physical features that require independent observation and contextual interpretation. This decision aid returns caller classes compatible with supplied evidence rather than a single inferred printing method.