Turn sources into governed knowledge
Captured communication will move through five stages: Capture, Extract, Contextualize, Govern, and Expose. The original source and the useful records derived from it stay separate so an answer can be fast to find and still traceable to what happened.
SMS/MMS now has Contextualize and Govern infrastructure. After Extract records the parties on a text, the worker files its artifacts from the roster or raises the appropriate Review Queue item. Govern then assigns the structural access ceiling and level, or withholds the artifact behind an access question when a party is unregistered. Expose remains unbuilt, so this is not yet a customer-ready workflow.
If an administrator later registers an unfamiliar participant or adds that person to a roster, the worker can revisit that person's earlier texts with the same Contextualize and Govern rules. It updates the recorded context rather than calling a model again, and closes the questions that the new roster information settles. It only settles: texts with no job yet can be filed, and a text already on a job stays there. Administrators' own filings are never changed. See How records are filed, and what roster changes do. Removing someone from a roster affects only texts that arrive afterward. Earlier texts are reconsidered once organizing has been turned on.
Deposit and Catalog
The Deposit holds each raw source unchanged for its authorized retention period. The Catalog holds discrete, categorized artifacts extracted from those sources. Queries search the Catalog; citations lead back to the Deposit.
Extraction is queued work. For an SMS/MMS message, it gives the model the decoded message, roster labels for the people on its thread, the configured category descriptions, and qualifying images or short PDFs. Every attachment is also recorded as a file artifact. Accepting an inbound source does not wait for a model, and a source cannot leave the pipeline without producing either artifacts or work for a business administrator.
Review Queue
The Review Queue is the destination for ambiguity, not a generic error log. It surfaces unknown parties, uncategorized content, unassigned communication sources, failed extraction, unresolved reference rows, and reconciliation decisions. Each item type has a defined action that settles its work. A Which category? card can be resolved a project section at a time; unanswered records continue on a new open card.
The administrator-only Review Queue workflow is built for the current SMS/MMS item types. An administrator can supply a category, filing, or access answer; retry a failed extraction; replace it with manual records; or exclude it.
Once a record is filed and governed, an administrator can browse it and correct its access, category, or filing in Artifacts.
Business administrators will also be able to add a recurring pattern to the tenant or project typology. New categories apply going forward; a specific project can be reprocessed deliberately.
When a reprocess run finishes, a reprocessing-review card opens in the Review Queue. The current records stay in place while the new ones wait. An administrator compares the two in the Site, then confirms the new records, which carries applicable administrator corrections across, or discards the rerun. See Reprocessing a project.
Signals and close-out
Stated signals—such as a budget, estimate, preference, or timeline—and actual outcomes are captured as soon as they appear. They are not paired while a project is active. Closing the project runs a sweep that proposes relationships and outcomes for a business administrator to confirm.
Close-out also releases the project's phone number. A project cannot become fully closed while its reconciliation review remains open.
Learn how the resulting records are governed and exposed.