SYNTHETIC INVESTIGATION WORKSPACE
Synthetic M6 Subject
This mirrors the operator evidence hierarchy using fixed synthetic data. No provider requests are executed from this demo and no visitor can submit a real-person research job.
- observations
- 5
- candidates
- 2
- claims
- 1
- hard conflicts
- 1
Candidate factors below are deterministic evidence-strength triage. They are grouped by evidentiary direction, remain uncalibrated and non-probabilistic, and a hard contradiction can veto positive evidence.
REVIEWED DOCUMENT / SAFE SIMULATION
Extracted clues stay inert until human review
This fixture mirrors the private reviewed-document workflow without accepting a file, retaining a document, creating an operator session or calling an API. Every control below changes browser-memory demo state only.
01 / SOURCE EXECUTION
Typed source-run states
These rows are deterministic demonstrations of the private operator state vocabulary. They do not describe live requests and do not add observations to this synthetic case.
02 / CORRELATION
Account candidates
GitHub
https://github.com/synthetic-m6Non-probabilistic factor assessment. Direction follows retained M5 weight/veto semantics; rationale wording alone does not create negative evidence.
Supporting factors · 1 retained
- same usernameSame public handle only.+10
Conflicting factors · 0 retained
No retained factors in this direction.
Neutral / withheld factors · 0 retained
No retained factors in this direction.
Inspect model mechanics
https://www.reddit.com/user/synthetic-m6Non-probabilistic factor assessment. Direction follows retained M5 weight/veto semantics; rationale wording alone does not create negative evidence.
Supporting factors · 1 retained
- exact confirmed identifier overlapSynthetic confirmed email overlap.+55
Conflicting factors · 1 retained
- hard contradictionSynthetic hard contradiction.veto
Neutral / withheld factors · 1 retained
- independent cross linkSynthetic cross-link is stale.stale
Inspect model mechanics
03 / EVIDENCE
Observation timeline
- Expired synthetic cross-link.
synthetic-stale-cross-link · public_web · stale
retrieved 2026-07-27 10:00:00 UTC · expires 2026-08-15 10:00:00 UTC
https://archive.example.test/profile - Synthetic portfolio repeats the confirmed email.
synthetic-email-proof · public_web · fresh
retrieved 2026-08-15 10:00:00 UTC · expires 2026-08-21 10:00:00 UTC
https://portfolio.example.test/contact - Synthetic source establishes incompatible account ownership.
synthetic-contradiction · public_web · fresh
retrieved 2026-08-16 06:00:00 UTC · expires 2026-08-21 10:00:00 UTC
https://contradiction.example.test/fact - Reddit
sherlock · provider · fresh
retrieved 2026-08-16 07:00:00 UTC · expires 2026-08-21 10:00:00 UTC
https://www.reddit.com/user/synthetic-m6 - GitHub
sherlock · provider · fresh
retrieved 2026-08-16 08:00:00 UTC · expires 2026-08-21 10:00:00 UTC
https://github.com/synthetic-m6
04 / EVIDENCE PATH
Clue → evidence → operator decision
This compact graph view traces how a retained clue reaches a candidate, which observations influence M5, where a contradiction enters, and which non-probabilistic outcome remains for human review.
same username → GitHub → decision insufficient evidence
exact confirmed identifier overlap → Synthetic portfolio repeats the confirmed email. · hard contradiction → Synthetic source establishes incompatible account ownership. → contradiction veto · independent cross link → Expired synthetic cross-link. → decision contradicted
05 / CLAIM REVIEW
Claims, exceptions and open questions
Synthetic portfolio lists the confirmed email address.
- supportsSynthetic portfolio repeats the confirmed email.
- unresolvedSynthetic source establishes incompatible account ownership.
Positive signals do not erase the contradiction.
The Reddit candidate remains contradicted because a hard conflict veto is present; stale supporting evidence is still shown rather than silently removed.
Synthetic source establishes incompatible account ownership. · Contradiction remains visible for operator review.
The retained M5 outcome does not support an identity conclusion; more independent evidence or human review is required.
06 / OPERATOR LIFECYCLE
Private actions, public-safe states
The private workbench includes write-capable and authenticated lifecycle steps. This observer mirrors their meaning without creating a session, accepting an upload, retaining a case or exposing an enabled mutation path.
The observer shows accepted clue concepts but never accepts a real-person submission or creates storage.
The safe simulation above mirrors confirm, reject, re-review, promotion and case-start boundaries without a file input, upload endpoint or document retention.
Case-switching semantics are represented with fixed labels; the visitor cannot list or read private retained cases.
The destructive boundary is visible but cannot mutate the fixture or call a deletion endpoint.
Logout and expiry concepts are shown as product states; this static observer never creates an admin session.
07 / WORKSPACE STATES
Loading, failure and coverage semantics
The private workbench keeps empty, error, partial and complete states distinct so missing evidence is not over-interpreted. These examples are fixed explanatory states and never trigger network activity.
The private workbench marks the case list busy and locks remote actions while loading. This observer demonstrates that state without making a request.
A failed index is not an empty workspace. The operator must refresh before concluding that no retained cases exist.
Usable evidence stays visible while incomplete source coverage remains explicit. Review source states before treating the case as complete.
Missing observations from an unattempted path are a coverage limit, not negative evidence about the subject or claim.
Source silence is not evidence that the subject or claim does not exist elsewhere.
Completion applies only to the bounded configured source set; it does not imply exhaustive coverage.