LienDrop Project detail Blocked documents System health

Simulated date 2026-09-25 Back to the fleet overview

P1

Any Concrete LLC Travis County Commercial Active

Dollars at risk

$86,350.00

Money on this job still protected by a deadline that is running. This is the rules engine's own figure, counting every unpaid dollar once: a month's dollars are protected by its notice and then again by the affidavit, and counting both would count the same money twice.

Figure copied from rules_engine.ComplianceCalendar.total_amount_at_risk.

Rights timeline

One lane per right, soonest deadline first. Every date and every state on a lane was computed by the rules engine and recorded by the docket. This screen reads them and counts the days left, which is the engine's answer too.

  1. Monthly notice 2026-05 work Expired

    Due 2026-08-15 Rolled to 2026-08-17 Days left 41 days past At risk $31,200.00

    Tex. Prop. Code §53.056(a-1)(1)(A) last moved 2026-09-02

  2. Monthly notice 2026-06 work Due soon

    Due 2026-09-15 Rolled to 2026-09-15 Days left 10 days past At risk $28,750.00

    status from the last sweep, taken before this deadline passed. Run the docket to bring it up to this date.

    Tex. Prop. Code §53.056(a-1)(1)(A) last moved 2026-09-02

  3. Monthly notice 2026-07 work Running

    Due 2026-10-15 Rolled to 2026-10-15 Days left 20 days At risk $26,400.00

    Tex. Prop. Code §53.056(a-1)(1)(A) last moved 2026-09-02

  4. Lien affidavit triggered by 2026-07 Running

    Due 2026-11-15 Rolled to 2026-11-16 Days left 51 days At risk $86,350.00

    Tex. Prop. Code §53.052(b) last moved 2026-09-02

  5. Suit to foreclose Not yet running

    Due 2027-11-15 Rolled to 2027-11-16 Days left 416 days At risk $86,350.00

    Tex. Prop. Code §53.158(a) last moved 2026-09-02

A deadline that lands on a weekend or a Texas holiday rolls to the next business day, so the rolled date is the one that counts. Where the two agree, the deadline did not have to roll.

1 lane above carry a state the docket wrote before the deadline passed, because it has not swept this simulated date. The days left are counted against the date at the top of this page. Run the docket to settle the two.

Service ledger

What was mailed on this job, to whom, and whether it arrived. The date a letter went in the mail is the date compliance turns on, under section 53.003(c) of the Property Code. The return receipt is evidence on top of that, which is why delivery proof has a column of its own rather than sharing one with the mailing date.

Nothing has been served on this project.

When the notice agent dispatches a monthly fund-trapping notice or a retainage notice, the certified mail rail issues a tracking number and this section fills with one row per letter: the recipient and their role, the date it went in the mail, and the return receipt once the article lands.

The county clerk audits this same ledger before it accepts an affidavit, and what it looks for is a notice deposited to the owner in time. A letter that comes back undeliverable does not take that deposit back; it opens the corrected-address work, which is recorded on this page beside it.

Documents on this job

Add an invoice, a delivery ticket, a change order, or a site photograph. Every file is filed under the SHA-256 of its own bytes, which is the reference every figure taken out of it has to carry. The name you give it is a label beside that hash and is never part of where the file is stored.

A PDF, a JPEG, or a PNG, up to 5 MiB. The file type is decided by reading the first bytes of the file, not by its extension, so renaming a file changes nothing.

Left blank, the file's own name is used. Letters, digits, spaces, and the punctuation a file name uses.

25 of 25 uploads left in this demo world, and 3 a minute. Reading a document is a separate step an operator runs, so nothing here starts a model on its own.

Nothing has been uploaded to this project.

What arrives here is what the claim rests on. Each file is hashed on the way in, the bytes are stored under that hash, and whatever the evidence pass can read out of it goes into the claim file below under that same hash.

Claim File

Every unpaid dollar and the month of work it was earned in. That mapping is what decides which notice preserves it. Two accounts of each month sit side by side here, what the artifacts evidence and what the project's own records bill, and where they disagree the file says so rather than averaging them.

Mapped and unpaid

$86,350.00

In a month the records bill and the artifacts evidence.

Unpaid, nothing evidences it

$0.00

No notice can be built from it until something backs it.

Could not be placed in a month

$0.00

In no month total, so no notice can claim it.

Held for review

$0.00

0 line items came back under the confidence threshold and wait on a person.

Each month of work, from the artifacts and from the project's records
Month Evidenced Billed Paid Unpaid Reading
2026-04 $24,500.00 $24,500.00 $24,500.00 $0.00 Evidence and records agree
2026-05 $31,200.00 $31,200.00 $0.00 $31,200.00 Evidence and records agree
2026-06 $28,750.00 $28,750.00 $0.00 $28,750.00 Evidence and records agree
2026-07 $26,400.00 $26,400.00 $0.00 $26,400.00 Evidence and records agree

Months a notice may cover: 2026-05, 2026-06, 2026-07. A month qualifies when the records bill it, an artifact evidences it, and it is still unpaid.

Built by evidence on September 2, 2026 (simulated), from 4 line items. Every one of them carries the content hash of the artifact it was quoted from. A fact with no source artifact is not a fact this system holds, which is the same rule the validity check applies before anything is filed.

This project's activity

The decision log, filtered to this job, newest first. Every time a right arms, goes critical, is preserved, or is refused a move it should not make, the reason lands here with the statute it rests on.

  1. The docket applied a payment of $24,500.00 to April 2026 work

    Recorded as PAY-P1-2026-04. April 2026 now shows $0.00 unpaid of $24,500.00 billed.

    as of 2026-09-02

  2. Monthly notice moved from not yet running to running

    the engine classified this deadline as pending as of September 2, 2026 against a nominal due date of October 15, 2026

    Tex. Prop. Code §53.056(a-1)(1)(A)as of 2026-09-02

  3. Monthly notice moved from running to expired

    the engine classified this deadline as lapsed as of September 2, 2026 against a nominal due date of August 15, 2026

    Tex. Prop. Code §53.056(a-1)(1)(A)as of 2026-09-02

  4. Monthly notice moved from running to due soon

    the engine classified this deadline as due_soon as of September 2, 2026 against a nominal due date of September 15, 2026

    Tex. Prop. Code §53.056(a-1)(1)(A)as of 2026-09-02

  5. Lien affidavit moved from not yet running to running

    the engine classified this deadline as pending as of September 2, 2026 against a nominal due date of November 15, 2026

    Tex. Prop. Code §53.052(b)as of 2026-09-02

  6. Monthly notice moved from not yet running to running

    the engine classified this deadline as lapsed as of September 2, 2026 against a nominal due date of August 15, 2026

    Tex. Prop. Code §53.056(a-1)(1)(A)as of 2026-09-02

  7. Monthly notice moved from not yet running to running

    the engine classified this deadline as due_soon as of September 2, 2026 against a nominal due date of September 15, 2026

    Tex. Prop. Code §53.056(a-1)(1)(A)as of 2026-09-02

  8. The evidence agent rebuilt the claim file for this project

    4 line items over 4 months. Mapped unpaid 86350.00, unevidenced unpaid 0.00, unmapped 0.00, held for review 0.00. Months a notice may cover: May 2026, June 2026, July 2026.

    as of 2026-09-02

  9. The evidence agent filed an artifact under the hash of its own bytes

    invoice 'Invoice RC-2026-0714', 454 bytes of text/plain, stored under sha256:f983e9b4c2630fa167e45896948b3219f90074cacf1566cad1c119b58a422696. That hash is the provenance ID every fact taken out of this artifact carries.

    as of 2026-09-02

  10. The evidence agent filed an artifact under the hash of its own bytes

    invoice 'Invoice RC-2026-0615', 454 bytes of text/plain, stored under sha256:59e57dfa9b6a075bb59f7db4646aa2f5d6847d947a20089c144b90557d8f70f8. That hash is the provenance ID every fact taken out of this artifact carries.

    as of 2026-09-02

  11. The evidence agent filed an artifact under the hash of its own bytes

    invoice 'Invoice RC-2026-0518', 454 bytes of text/plain, stored under sha256:e9b482fa2bb55967fbef69156851a9f080679a448fbb804e903b78ed8535f8be. That hash is the provenance ID every fact taken out of this artifact carries.

    as of 2026-09-02

  12. The evidence agent filed an artifact under the hash of its own bytes

    invoice 'Invoice RC-2026-0412', 454 bytes of text/plain, stored under sha256:7d33c1ce32a9d15991839501554144b25fc0810645a81af115d534f59affdce5. That hash is the provenance ID every fact taken out of this artifact carries.

    as of 2026-09-02