Why evidence text has no clickable link: tokenization, HTTPS and URL admission
Clickable means admitted shape, not trusted, redacted evidence
Radar retains evidence text and extracts clickable URLs. Parsing splits whitespace/newlines and listed delimiters, trims edge punctuation, requires HTTPS/nonempty host/no embedded user-password/valid port, then deduplicates by absoluteString. This is not full Markdown parsing, security scanning or business-evidence certification.
Different from provenance and evidence truth checks
Provenance maps claims; second checks assess truth. Here why text does not produce a link and which URL shapes are admitted matters. Delimiters include Latin/Chinese comma/semicolon and vertical bar. No example URL is fetched or source rewritten.
| Check | Verified scope | Manual review | Not established |
|---|---|---|---|
| Null/empty | Empty URL list | Original evidence versus placeholder | No business evidence exists |
| Tokenization | Whitespace/newlines/listed punctuation | Comma can split valid URL text | All reference syntax understood |
| Edge punctuation | Trims brackets/quotes etc. | Actual candidate | Full labeled Markdown parsing |
| Scheme/host | HTTPS, nonempty host | Protocol/destination | Safe-domain allowlist or authority |
| Embedded credentials | No user/password | Keep credentials out of URLs | Paths/queries automatically redacted |
| Port | Explicit 1…65535 | Shape versus access permission | Every endpoint tested |
| Deduplication | First absoluteString retained | Spellings/reference relationships | Universal semantic normalization |
| Result | Clickable candidates only | Body/evidence quality/destination | Harmless, true, read or handled |
Synthetic URL review
Standalone https://example.com/review illustrates shape, not real project evidence. Labeled Markdown need not expand through a full grammar. Inspect original/tokenization rather than deleting evidence or inventing safety conclusions.
Paths, queries and fragments can disclose information despite no user/password. Existing access/destination permission applies; safe in a method name is neither a malware scan nor universal network safety.
FAQ
Does no link mean no evidence?
No. Text may not meet tokenization/URL rules. Inspect originals.
Are labeled Markdown links always extracted?
No guarantee. This is not a full Markdown parser supporting all nesting.
Does HTTPS prove trust and access permission?
No. Shape differs from origin, content, identity and authority.
Is no embedded user/password equivalent to redaction?
No. Paths/query/fragments can remain sensitive.
Are all equivalent URLs merged?
No semantic-normalization guarantee; deduplication uses absoluteString.
Were example URLs opened?
No. No site-security or business-evidence acceptance was performed.
Reading and source
Evidence review · Claim provenance · Sensitive layers · Start · Privacy
