Technology & Patent Portfolio

The architecture behind execution control.

Twelve U.S. patent applications are pending on the execution architecture, plus one provisional exploring verification. All of it comes from more than two years of daily production use at an affiliated operator.

See the Mechanisms → Talk to the Team
12+1
U.S. Applications
2+ yrs
Production Validated
1M+
Units Captured
4
Filing Waves
Four Patent-Pending Mechanisms

What the patent portfolio
actually covers.

The filings describe four mechanisms. Three govern how the compliance record gets created. The fourth turns that same record into tomorrow's production decision. Each is a specific way the floor has to work, not a generic feature.

01 / GATING
Workflow-gated task completion
Compliance steps execute in a defined sequence, enforced by the system rather than by training. The intent is that the record cannot run ahead of the work it describes.
Floor-level enforcement
02 / TEMPORAL
Temporal authenticity enforcement
Records are designed to reflect what happened when — binding the creation of a compliance record to the moment of the work rather than to a later write-up.
Time bound to the work
03 / DUAL-SOURCE
Dual-source corroborative verification
Human attestation paired with independent machine-generated evidence, so a record does not rest on a single unverifiable input.
Independent corroboration
04 / CLOSED-LOOP
Closed-loop capture and adjust
Shrink is captured as a unit-level event at the point of work, tied back to the production order and lot that produced it, and carried into the next production and purchasing cycle. The loop closes without anyone re-entering anything.
Captured where the work happens
Where This Leads

Most systems are told
what already happened.

That one difference is why the architecture is built the way it is.

The conventional pattern
Work happens on the floor. Later, someone tells the software about it — a form at end of shift, a spreadsheet on Monday, a binder assembled before an audit. The data is a description of the work, written by someone remembering it.
The execution-layer pattern
Data creation is embedded in the work itself. The record is a condition of proceeding, not a report written afterward — so the data arrives as a structured account of what was done, at the moment it was done.
Once physical operations become machine-readable, they become machine-intelligible.

Automation and AI are only as good as the data underneath them. A model working from records reconstructed from memory is working from someone's recollection.

Today What Shrink Manager does now
Comply. Lot-level receiving, transformation and shipping captured at the point of work.
See. Produced, sold and shrink visible the same day rather than at month-end.
Understand. The produced-vs-sold gap broken out by site, product, shift and SKU.
Decide. The gap feeds the next production order.
The end state is management by exception rather than by inspection. Not more dashboards for someone to read, but an operation where the ordinary case handles itself and a person's attention goes to the case that doesn't.
From Execution to Evidence

The work creates the record.
Then ask what the evidence can establish.

Shrink Manager® creates the record at the point of work, tied to the order and lot. That raises a bigger question: can those records establish what actually happened when a person, another system or an AI asks? We call that longer-term direction making the physical world queryable.

Execution layer · Shrink Manager®
Capture the work as it happens. Keep receiving, transformation, compliance, labeling and delivery tied to the operational event that produced the record.
Evidence layer · Shrink Verify™
Explore what the available evidence could establish across a product’s history, without rewriting the underlying record.
Traceability tells you what the records say. Verification asks what they can prove. Shrink Verify™ is in development and is not currently a product offering. Explore Shrink Verify™ →
The Patent Estate

Twelve non-provisional applications.
One provisional points toward verification.

The twelve applications describe pieces of one architecture, not separate inventions. They build from gated execution through capture to the closed loop. A separate provisional extends the architecture toward verifying a product’s history.

Wave 1 · Foundational execution-control claims
4 applications · Wave 1
The core pattern: steps run in a set order, the record is created by doing the work, and it all sits alongside the ERP.
Wave 2 · Expansion across adjacent workflows
5 applications · Wave 2
Carries that pattern into lot transformation, label generation, multi-site operations and operator sign-off.
Wave 3 · Production-anchored execution claims
2 applications · Wave 3
Ties execution control to the two events that happen most on the floor: the shift change and the customer order.
Wave 4 · Closed-loop capture and adjust
1 application · Wave 4
Closes the loop: shrink counted at the point of work feeds the next production and purchasing cycle.
On the filings themselves. Shrink Manager is patent pending in the United States. Shrink Software does not publish current application numbers, specifications, or claim language on this page. Diligence-stage investors, acquirers, and channel partners can review the filing record under NDA.
Architectural Validation

Two years in production.
Ten sites. Over a million units.

Every mechanism above has run daily for more than two years at Anu Sushi LLC, an affiliated operator, across 10 institutional food production sites, capturing more than a million units a year.

Portfolio Roadmap

From filing
to examination.

Filed · 2026
Non-provisional applications
Twelve U.S. non-provisional applications pending, plus one provisional on verification.
In Progress
USPTO examination & production hardening
The applications move through examination while the product keeps running in daily production.
Under Review
International strategy
Foreign filings follow the markets where customers and partners justify the cost.
Where The Architecture Goes
Two doors into the rest of the platform.

An execution-control architecture
built for the long horizon.

Evaluating Shrink Manager as an operator, partner or investor? We're glad to walk you through how it works.

Channel partner inquiries welcome: partners@shrinksoftware.com

Patent status reflects twelve U.S. non-provisional patent applications pending, plus one U.S. provisional application filed, as of September 29, 2026. Patent pending does not mean a patent has been granted, and no enforceable patent rights arise unless and until patents issue. All third-party trademarks referenced elsewhere on this site are the property of their respective owners.