UCC Borrower Portfolio Monitor

Monitor organization borrowers for new UCC filing lifecycle events in Connecticut and Colorado using official public data sources.

This Actor is designed for business-to-business monitoring workflows where you already know the organization names you want to watch. It is an evidence feed, not a certified UCC search, legal opinion, perfection determination, consumer report, or FCRA product.

What it does

For each organization borrower in your input, the Actor:

1. reads recent official UCC data for the selected state;
2. matches organization names conservatively using exact normalized legal names or explicit aliases;
3. classifies supported lifecycle events such as initial financing statements, amendments, continuations, and terminations;
4. stores a persistent baseline for your monitorKey;
5. emits only newly observed matched events after the baseline is established.

Supported states:

• Connecticut (CT)
• Colorado (CO)

Individuals and consumer-debt monitoring are intentionally outside this Actor's contract.

Quick start

Use a stable monitorKey for the portfolio you want to monitor.

{
  "monitorKey": "synthetic-demo-portfolio",
  "borrowers": [
    {
      "state": "CT",
      "legalName": "R21 SYNTHETIC DEMO BORROWER LLC",
      "externalId": "demo-001",
      "aliases": [],
      "city": "HARTFORD",
      "zip": "06103"
    }
  ],
  "baselineMode": "storeOnly",
  "lookbackDays": 7
}

The example above is synthetic and is not intended to identify a real organization.

Input

monitorKey

A stable identifier for the monitored portfolio. It is used to derive the Actor's persistent state namespace.

Reusing the same monitorKey allows later runs to compare against previously observed events.

borrowers[]

One or more organization borrowers.

Required per borrower:

• state: CT or CO
• legalName: organization legal name

Optional:

• externalId: your own stable identifier
• aliases[]: explicit alternative organization names accepted for exact normalized matching
• city
• zip

City and ZIP are supporting evidence only. They do not enable fuzzy matching.

baselineMode

• storeOnly — recommended default. The first successful run stores the baseline without emitting historical snapshot events.
• emitSnapshot — the first successful run emits the matched snapshot and stores it as the baseline.

lookbackDays

Number of days in the bounded overlap window used for official-source reads.

• minimum: 1
• maximum: 30
• default: 7

Output

Dataset events

When new matched events are found, the default dataset contains final event records such as:

• eventId
• externalId
• state
• legalName
• eventType
• filingNumber
• filingDate
• lapseDate
• securedParty
• sourceUrl
• observedAt
• match
• sourceEvidence

Event IDs are deterministic and borrower-specific.

Run summary

The default key-value store record OUTPUT contains:

• monitorKey
• status
• borrowerCount
• emittedEventCount
• observedAt

Possible status values:

• SUCCESS
• PARTIAL
• FAILED

A PARTIAL or FAILED run does not advance persistent monitoring state.

Matching policy

Matching is deliberately conservative.

The Actor accepts:

• exact normalized legal-name matches;
• explicit aliases supplied by you.

It does not automatically accept:

• fuzzy names;
• phonetic similarity;
• edit-distance matches;
• inferred aliases.

An exact name with incomplete or mismatching city/ZIP evidence can be surfaced for review rather than silently promoted to a stronger match.

Official data sources

Connecticut

Official Connecticut UCC dataset:

• dataset ID: xfev-8smz
• source: Connecticut Secretary of State / data.ct.gov

The Actor processes the supported OFS subset conservatively.

Colorado

Official Colorado datasets:

• filings: wffy-3uut
• debtors: 8upq-58vz
• source: Colorado Department of State / data.colorado.gov

For amendments, the Actor resolves the filing lifecycle back to the original filing before joining organization debtors.

Persistent monitoring

State is stored in a named key-value store derived from monitorKey.

The raw monitorKey is not exposed in the storage name.

Successful runs can advance the baseline. PARTIAL and FAILED runs do not mutate the prior monitoring state.

Important limitations

This Actor:

• monitors organizations only;
• currently supports CT and CO only;
• is not a certified UCC search;
• does not determine lien priority, perfection, enforceability, or legal effect;
• is not legal advice;
• is not intended for consumer reporting or FCRA use;
• does not use fuzzy auto-matching;
• depends on the availability and completeness of the official public datasets.

For decisions with legal or lending consequences, verify the underlying official records and use qualified professional review when appropriate.

Data handling

The Actor reads official public filing data and stores monitoring state needed for deduplication under your monitorKey.

Avoid placing secrets or unnecessary personal information in monitorKey, borrower names, aliases, or other input fields.

Current release scope

This release focuses on a small, auditable monitoring core:

• Connecticut + Colorado;
• organization borrowers;
• exact/explicit-alias matching;
• persistent baseline and deduplication;
• evidence-rich event output.

Additional states or broader matching behavior should be treated as separate capabilities rather than assumed from the current release.