Resume a project
Recover the working ramp around a project without starting from a generic summary.
Local continuity for AI-assisted projects
Find the thread in long AI projects.
threadVault turns exported AI conversations into a local working vault. Search by project, review the history by authorship, and open a useful result back to the exact message and nearby chronology.
Built by neuroVectoring. RC3 is Windows-first, and the original provider export remains higher-authority evidence than every derived layer.
- Runs locally
- Maps back to source
- Preserves authorship
- Windows RC3
ILLUSTRATIVE FLOWSYNTHETIC FIXTURE
PROJECT ANCHORDopamine Trailsrider · bloom · spiral
Human Decision CandidateOpen exact source
Origin CandidateView chronology
Assistant Proposal CandidateKeep authorship visible
SOURCE CONTEXT
exact messagehash-linkedWhere it helps
An archive stores messages. A project needs context.
Long-running work is shaped by sequence: where an idea began, which paths were rejected, what the human decided, and what the assistant only proposed.
Separate decisions from suggestions
Review human decisions and assistant proposals as different kinds of evidence.
Check the source
Move from a continuity result to the exact message, locator, hash, and neighboring chronology.
The working model
From provider export to source-linked continuity
The original export stays above the derived intake. Retrieval remains connected to exact messages.
- 1Preserve the export
Keep the original provider file intact in the raw-export area.
- 2Create derived intake
Use the supplied prompt to normalize the export into threadvault_intake.jsonl.
- 3Build the local vault
Import stable message records with source mappings and integrity checks.
- 4Retrieve by project
Use a distinctive project anchor and supporting terms to reduce unrelated recall.
- 5Return to evidence
Open the exact source message, locator, hash, and surrounding chronology.
What it brings into view
A working map of how the project developed.
threadVault does not ask one summary to carry the whole history. It surfaces different candidates for review and keeps their relationship to source visible.
Why threadVault exists
The conversations were still there. Re-entering the work was the problem.
threadVault began with a recurring failure while resuming Project Ikigai. The source conversations had not disappeared, but the project no longer returned as a coherent whole. Facts could be searched. The sequence that made them useful had to be reconstructed by hand.
That experience produced a simple hierarchy: preserve the provider export; treat normalized intake as derived; treat retrieval results as candidates for review; and keep an exact path back to source.
Project Ikigai is referenced only as the real origin context. No private project details or conversation content are used on this page.
FULL WALKTHROUGHIN PRODUCTION
From a raw export to an exact source message
The finished film will combine the origin story with the complete tutorial. It will use a real RC3 session and synthetic data—not a sales montage.
- 01Why summaries were not enough
- 02Export, intake, and source authority
- 03Project anchors and continuity retrieval
- 04Origins, decisions, and proposals
- 05Authoritative Context and verification
- 06Limits, setup, and the tested boundary
What was tested
RC3 has a defined test record.
The release moved through three candidates. RC3 received an independent GO within the stated scope after the earlier security, packaging, and Windows restore-path findings were repaired.
Read the complete verification record →RC3 ZIP SHA-256
EF957F6BB3F3B35297EA52EF8218855EE35FEDB5A6FBDE3322F78221F4A6F5FERelease status
The current release is ready.
The manual-intake edition is available at no cost. It is the complete tested RC3 package—not a hosted demo—and it continues to run locally after delivery.
- Windows-first local application
- Intake prompts and setup documentation
- Release verifier and published SHA-256
- 30 days of best-effort delivery and basic setup help
Practical questions
What to know before deciding whether it fits
Does threadVault replace my original export?
No. The provider export remains the higher-authority evidence. threadVault creates a local, normalized working vault while preserving a path back to source.
Does threadVault send my archive anywhere?
The tested RC3 application runs locally. Independent testing observed loopback-only listeners and no telemetry, update checks, activation, or outbound connections within the tested scope.
What does the AI do during intake?
A supplied prompt helps an AI normalize a provider export into threadvault_intake.jsonl. That intake is derived material—a navigation layer, not a replacement for the original export.
What can I use it for?
threadVault is designed for returning to long-running AI-assisted work: finding where a project began, distinguishing human decisions from assistant proposals, reviewing relevant chronology, and opening a continuity result back to an exact source message.
What platforms does RC3 support?
RC3 is Windows-first and uses standard-library Python. It requires no package installation or administrator privileges within the tested scope.
Is RC3 available now?
Yes. The current manual-intake release is available at no cost through approved platform-release links. Each link sends a private, time-limited download by email; the ZIP is not hosted at a permanent public address.