Bring seed material
Start with two to five papers, article links, abstracts, BibTeX entries, lecture notes, or supervisor comments. Public or synthetic material is best for first tests.
ZeroThink research lane | Public or synthetic data first
Paper Creator evidence workflow for survey expansion.
ZeroThink Paper Creator turns a small set of articles, research notes, abstracts, or public documents into a source ledger, claim/evidence graph, reviewable outline, and draft. QuantumEncryption1 uses this lane to explain how provenance-aware evidence work can be audited before any sensitive deployment is discussed.
What students asked
How to expand a survey from a few papers
The safest route is staged. Do not ask a chatbot to invent a finished paper in one step. Give Paper Creator seed sources, force a source ledger, then draft only after the claim/evidence graph is visible.
Create the evidence map
Run Search Protocol, Evidence Plan, Evidence Graph, and Source Ledger. Every claim should be tied to a supplied source, retrieved result, full-text note, or candidate lead.
Draft after review
Only then run Outline, Draft, Reviewer Critique, and Revision. The result is still a working draft, but the evidence status is easier to inspect and improve.
QE1 connection
Why this belongs on QuantumEncryption1
QE1 is not only a file-protection story. It is also a provenance story: what was claimed, what evidence supports it, which source produced it, what was compared, and what still needs human review.
Controlled PoC
Public document evidence before sensitive files
A partner can begin with public policies, open research papers, synthetic incidents, or generated test documents. The workflow can then produce an auditable report without uploading confidential records to the public website.
Workflow
From papers to a provenance graph
This is the practical route for survey expansion, public-sector evidence packs, and research briefs.
ZeroThink / paper creator
Seed papers -> source ledger
Source ledger -> claim/evidence/provenance graph
Graph -> gaps, contradictions, and confidence notes
Graph -> classical baseline checks
Graph -> optional quantum/simulator optimisation tests
Review -> outline -> draft -> critique -> revision
Optimisation lane
What the quantum or simulator part actually tests
QuantumEncryption1 does not claim that quantum computers understand documents. The measurable work is constrained optimisation over a graph that AI and humans already created.
Evidence-path selection
Choose a compact chain of sources that supports a claim while exposing gaps and contradictions.
Clustering and routing
Group related claims, route weak claims to review, and prioritise the sources that need human checking first.
Auditability scoring
Compare candidate routes against a classical baseline and record what was tested, not what was assumed.
Connected ecosystem
Where the pieces live
QuantumEncryption1 is part of a larger TalkToAI research, AI, and security ecosystem. These links help reviewers move from public explanation to working tools.
Main ecosystem
TalkToAI explains the wider stack: ZeroThink, OpenZero, ZMath, ZSEC, FreeWebPanel, CallChat, and research routes.
Secure communications lane
CallChat connects Matrix-compatible messaging, ZMath Shield licensing, and Zero Bot-style assistant routes for communication workflows.
Public research repo
The public research repository contains working papers, source ledgers, and a safe release boundary without private ZMath implementation code.
Boundaries
What this page does not expose
The public page explains behaviour and workflow. It does not publish private encryption source, secret prompts, API keys, server credentials, customer records, or confidential research files.
Private ZMath stays private
Public docs describe file-container behaviour, entitlement policy, and audit purpose. Proprietary implementation belongs in private modules only.
No provider endorsement claim
IonQ, IBM, UKRI, NQCC, DSIT, or government names must not be treated as approval unless explicit written approval exists.
Use safe data first
Initial tests should use public, synthetic, or non-sensitive materials. Confidential work needs a reviewed private route.
Next step
Use Paper Creator for the research draft, then use QE1 for the evidence workflow discussion.
Start with public sources, build the evidence ledger, and bring the result into a controlled PoC conversation when the review path is clear.