Automate redaction · Autessa Redact
Redaction decision cache
Autessa’s redaction decision cache stores the decisions for a document under its content hash, so when an identical copy arrives later, the earlier redactions are reused instead of repeating the work. Decisions are stored per company, encrypted at rest, versioned, and can record who reviewed them and when.
The problem
Redacting the same attachment for the hundredth time
The same form, policy or attachment turns up again and again across a document set. Without a memory, every copy is analyzed and reviewed from scratch. The decision cache lets a reviewed decision travel to every identical copy.
- Look up a document’s prior decisions by its SHA-256 content hash.
- A hit returns the stored classifications and redactions, the record version, provenance and how often it has been reused.
- Store decisions as JSON the caller defines; the cache returns them unchanged.
- Encrypted at rest and kept per company.
- Provenance records who adjudicated a document and when, building a review history.
- Supersede replaces an earlier decision and bumps its version; an optional expiry sets retention in days.
How it works
How does redaction decision cache work in Autessa Redact?
Extract
Extract Text returns the document’s content hash.
Look up
Look Up Decision Cache checks for an earlier decision on the same content.
Reuse or decide
On a hit, reuse the redactions; on a miss, run detection and review.
Store
Store Decision Cache saves the result with provenance for next time.
Every option
Cache options
| Option | What it does |
|---|---|
| sha256 | The content hash to look up or store under. |
| classificationsJson / redactionsJson | Your decisions, round-tripped unchanged. |
| provenanceJson | Non-sensitive review metadata, such as reviewer and date. |
| supersede | Replace an existing record and bump its version. |
| expiresInDays | Retention window; omit for no expiry. |
| sourceRequestId | Tag decisions with the request that produced them. |
Permissions
Who can do what?
| Who | Can |
|---|---|
| Builders (roles that can create tools and scripts) | Use the cache blocks in pipelines and scripts. |
FAQ
Questions about redaction decision cache
How does Autessa avoid redacting duplicates twice?
The decision cache stores decisions by content hash. An identical document later gets the stored redactions back instead of being analyzed again.
Is cached data encrypted?
Yes. Decisions are stored per company and encrypted at rest.
Can a decision be corrected later?
Yes. Store with supersede set and the new decision replaces the old one with a higher version.
100% customizable, code and all
Make Autessa Redact fully your own.
Use it out of the box, then change anything. Ask Autobot, Autessa’s AI builder, for a new field, screen, report, workflow or agent and it builds it into your copy of the app. Or open the code and edit it yourself. Nothing is locked: the app, its data and its code are yours.
Start free and make it yours