Direction & tasking
Requirements become owned tasks with parent tasks and prerequisite gates. Every task keeps its original question.
Board · Flow · Funnel · Cascade
Platform Brief · Document UW-PB-001
Version 2026.10 · Published
Conclusions you can defend
Executive summary
Uverwatch brings direction, collection, field reporting, processing, assessment, mapping and reporting into one evidence record. Every assertion keeps a path back to its original source. Every judgment records who made it and why. The workspace runs on infrastructure you control.
| Document | UW-PB-001 |
|---|---|
| Version | 2026.10 |
| Status | Published |
| Distribution | Public |
| Issued by | Uverwatch |
| Intended for | Mission leads, analysts, oversight |
Key points
- One record from the first question to the final brief.
- Receipts for every claim. Originals stay attached.
- Disagreement is data. Conflicts stay visible until resolved, with reasons.
- Works where you work. Offline in the field, on your node at the desk.
- ALocal-first
- The evidence store and signed provenance run on your own node.
- BHuman-reviewed automation
- OCR, transcription and classification propose. Analysts decide.
- COffline field capture
- Requests reach devices. Signed reports sync when the network returns.
- DRole-based access
- Roles, invitations, sessions and access reviews, by design.
Section 1The problem
Intelligence breaks at the seams.
Most teams don’t lack information. They lose its context every time it moves between tools, people and drafts.
- 1.1
Evidence lives everywhere.
Reports in inboxes, data in spreadsheets, field notes on phones. Each copy-paste strips a little more context away.
- 1.2
Claims lose their sources.
A line in a brief can’t be traced to the sentence that supports it, or to the one that contradicts it.
- 1.3
Judgment isn’t recorded.
Corrections overwrite. Nobody can say who changed what, or why. Audits turn into archaeology.
If you can’t trace it, you can’t brief it.
Section 2Capabilities
One record.
Every step.
Each step adds to the same record instead of starting a new file. Point at any part of the record below to see what it holds.
Fig. 1 · One evidence record
Every node keeps its original; every edge is typed and attributable. The contradiction is a first-class relationship, not a footnote. Point at a node to see what it holds.
Phase IDirect
Human sources
Contacts, contact cadence and source-linked directions. Value, credibility and timeliness assessed separately; identities restricted.
Human sources
Phase IICollect
Collection
Web and structured feeds, documents, email, social channels, audio, video and human contributions, each recording how and when it was collected.
Sources · Setup
Field reporting
Requests reach devices. Observations save offline with location, attachments and a signature, then sync with their context intact.
Field app
Communications & transactions
Supported communications and transaction statements from authorised uploads, with every source row retained.
Subscriber records
Phase IIIProcess
Processing
OCR, transcription, classification and entity extraction, with local model options.1 Every result links to its original region.
Validation · Media tools
Entities & graph
Connect mentions and sightings into entities and inspect their history. A candidate match stays a candidate until reviewed.
Entities · Graph
Phase IVAssess
Claims & assessment
Compare precise claims. A denial is a stance toward one proposition. Confidence, reasons and corrections sit beside the signed original.
Reports · Validation
Geography & time
Map, timeline, movement trails and event evolution. Reconstruction charts lay out entity lanes and dated incidents on one canvas.
Picture · Evolution · Reconstruction
Ask Uverwatch
Ask questions of the evidence. Answers cite records, suggest next questions, and feed a working set you can save.
Ask · Working set
Phase VReport & govern
Reporting
Briefs whose assertions cite their sources, with review records, schedules, distribution and edition history.
Briefs
Access & oversight
Guided owner setup, invitations, program keys, roles, sessions and access reviews.
Access
Section 3Benefits
What changes.
Outcomes, and the mechanism behind each one. None of them depends on trusting a model blindly.
Receipts for every claim.
Assertions open the exact sentence, row or image region they rely on.
Disagreement is data.
Conflicting accounts stay side by side, so the gap shapes the next question.
Your node, your rules.
Evidence, keys and processing stay on infrastructure you run.
| Role | Outcome | Because |
|---|---|---|
| Mission leads | See what is known, disputed and missing before deciding. | Direction, assessments and gaps live in the same record. |
| Analysts | Spend time judging, not reconciling. | Sources, extractions and entity matches arrive already linked. |
| Field teams | Report from anywhere; nothing is lost on the way back. | Offline capture, signed saves and sync with request context. |
| Decision-makers | Read a brief you can interrogate. | Each assertion opens its source and its confidence. |
| Oversight | Audit by reading, not by reconstructing. | Corrections, reasons and access are recorded as they happen. |
Section 4Use cases
Five questions.
One workspace.
The same workspace, applied to different questions. Each one also runs as a guided mission in the 3D walkthrough, with fictional data.
“What explains the unlisted cargo movements at the port?”
Typical sources
Harbor notices, manifests, field observations, communications exports, human sources.
Where Uverwatch helps
- Field teams report offline; signed notes sync later.
- Conflicting duty reports and observations stay side by side.
- Rules replay against history, separate from analyst judgment.
Output
A situation brief whose assertions cite their sources, plus a targeted follow-up.
“Can our supplier still deliver next quarter’s volume?”
Typical sources
Supplier statements, customs and shipping data, trade press, site visits, expert calls.
Where Uverwatch helps
- A supplier’s statement is weighed against what a buyer sees on site.
- Licensed data rows stay intact and traceable.
- Candidate company links stay candidates.
Output
A supplier-risk brief for the S&OP or board decision, open questions named.
“Can aid still reach the communities cut off by the flood?”
Typical sources
Official bulletins, satellite layers, shelter lists, hotline calls, partner reports, field assessments.
Where Uverwatch helps
- Assessments work without signal and sync on reaching a network.
- Lists and hotline audio become countable needs.
- Partners see what their role allows; beneficiary data stays restricted.
Output
An inter-agency situation report with access status, needs and the next assessment.
“Is this viral video real, recent, and where it says it is?”
Typical sources
The post and its copies, frames and audio, statements, emergency logs, stringers, eyewitnesses.
Where Uverwatch helps
- Text in frames and audio linked to the exact moment.
- A reporter’s site check recorded with time and place.
- Eyewitness identities stay with the verification desk.
Output
A verification note your editor can stand behind, or a reasoned decision to hold.
“Is this customer moving money its declared business can’t explain?”
Typical sources
Transaction rows, KYC files, invoices, registry filings, adverse media, relationship-manager notes, site visits.
Where Uverwatch helps
- Declarations compared with what a site visit finds.
- Patterns stay leads for review, never findings by themselves.
- Need-to-know access keeps the review from customer-facing staff.
Output
A case report that survives audit, ready for the MLRO’s decision.
Also suited toDue diligence · ESG and supply-chain audits · Brand protection · Corporate investigations · Research programmes
Section 5Trust
Built for scrutiny.
Intelligence work gets examined: by reviewers, by courts, by the public. The platform assumes it will be.
Provenance
Originals are kept with capture time, contributor and signed provenance. Derived records point back to them.
Corrections with reasons
Corrected interpretations sit beside the signed original, with who changed it and why.
Need-to-know access
Roles, mission membership and handling restrictions govern each record.
People decide
Models and rules propose classifications, matches and alerts. Analysts accept, reject or correct.
Signals stay separate
Reported is not verified. A rule alert is not an assessment. The record keeps the difference.
Clear data boundaries
Evidence and keys stay on your node. Each external integration is a choice you configure.
What Uverwatch is not.
- Not a dragnet. Collection is directed and authorised. There is no live interception.
- Not an autopilot. Models assist; saving review labels does not quietly retrain anything.
- Not a black box. Every result links to its input.
- Not a data broker. Your evidence stays yours, on your infrastructure.
Section 6Deployment
Runs where your evidence lives.
A server and a browser-based workspace on a node you control, with optional local tools for OCR, media analysis and model inference.
Sources
- Feeds & web
- Documents & email
- Social channels
- Audio & video
- Field app (offline)
- Human sources
- Communications & transactions
Your Uverwatch node
CollectionConfigured per mission and source
Evidence storeOriginals · signed provenance · node keys
ProcessingOCR · transcription · extraction · optional local models
AnalysisClaims · entities · map & time · Ask
ReportingBriefs · review · distribution
Access & oversightRoles · invitations · sessions · access reviews · recorded corrections
People
- Mission leads
- Analysts
- Field teams
- Reviewers
- Readers
Options
Section 7FAQ
Questions, answered briefly.
Does Uverwatch replace our existing tools?
It becomes the record that connects them. Sources and integrations are configured per mission, and originals are kept as received.
Can it run without internet access?
The workspace runs on your own node, with local processing options. Field devices keep working offline and sync when they reach a network.
Does the AI make the decisions?
No. Models and rules propose classifications, extractions, matches and alerts. Analysts accept, reject or correct them, and the reasons are recorded.
How is sensitive source information protected?
Through roles, mission membership and handling restrictions. Human-source identities need a separate role, and access is reviewable.
Can we prove where a statement came from?
Yes. Originals are kept with capture time and contributor under signed provenance, and citations open the exact region they rely on.
What do we need for a demo?
A question you actually care about. We’ll walk it through the cycle with you, end to end.
Glossary
- Requirement
- The question a mission exists to answer. Every task keeps it as its parent.
- Assertion
- A statement in a brief, linked to the evidence and assessment behind it.
- Provenance
- Where a record came from, who captured it and when, signed so it can be checked.
- Stance
- A speaker’s position toward one specific proposition, for example a denial.
- Working set
- A saved selection of records gathered from answers, maps and searches.
Notes
- Model inference is optional and configured locally. Heuristics remain available when it is not. ↩
- Missions in the 3D walkthrough use fictional people, places, organisations and data.
Issuance
This brief describes the Uverwatch platform as it stands at version 2026.10. It is published for public reference and will be revised as the platform changes.
- Issued by
- Uverwatch
- Date of issue
- October 2026
- Enquiries
- contact@uverwatch.com
Bring a
real question.
Next
We’ll show you how Uverwatch takes it from direction to a brief you can defend.