STEP01
Intake
Lock the input
Fix the input boundary, byte count, hash, and processing start point without changing the original.
AI VENDOR EXPORT FORENSICSLOCAL // 001
Turn GenAI exports into reproducible evidence.生成AIのエクスポートを、再現可能な証拠へ。
Keep originals immutable. Verify offline. Reconstruct branches, roles, timestamps, tool events, missing values, and references without flattening the record.原本を変えず、オフラインで検証。分岐、役割、時刻、ツールイベント、欠損値、参照関係を平坦化せず再構成します。
NO LIVE EVIDENCE IS CONNECTED TO THIS SITE
PROLOGUECASE FILE // 001
THE EXPORT ARRIVES
“The records exist.
The path does not.”「記録はある。
けれど、経路が見えない。」
A massive export lands on disk. The branches are fading into a flat list. Before drawing conclusions, the workbench restores the path while leaving the original untouched.巨大なエクスポートが届く。分岐は平坦な一覧へ消えかけている。結論を急がず、原本に触れず、証拠がたどった経路を復元する。
SYNTHETIC DEMO // NO SOURCE TEXT
Trace a fictional case with the analyst.架空ケースを、彼女と追体験する。
This experience uses fixed abstract data only. It contains no production extractor, vendor conditions, thresholds, or message content.固定された抽象データだけを使う体験版です。実際の抽出器、ベンダー条件、閾値、メッセージ原文は含みません。
CASE // SYNTH-001ACQUIREDEMO ONLY
INPUTHASH
ROLE04
EVENT18
NULL02
REPORTREADY
CONTAINER01
HASHVERIFIED
MUTATIONNONE
PUBLIC-SAFE SIMULATION Counts, identifiers, and transitions are fictional. They do not represent the production candidate detector.件数・識別子・遷移は説明用の架空データで、実際の候補検出器を表しません。
01Originals remain immutableNever alter the evidence source
02Offline processingKeep case processing local
03Candidate ≠ proofDo not confuse a lead with causation
CHAPTER 01 // METHOD
Make every step of the evidence path traceable.証拠がたどった道を、誰でも追えるように。
Traceability outranks speed. The work before the conclusion is preserved as four explicit stages.
STEP02
Reconstruct
Restore structure
Preserve branches, roles, timestamps, tool and system events, missing values, and references explicitly.
STEP03
Reconcile
Verify independently
Recount records and candidate logic deterministically instead of inheriting prior conclusions.
STEP04
Report
Make it auditable
Package reproducible steps, constraints, safe stops, open questions, and source-text-free deliverables.
CHAPTER 02 // LINEAGE
Do not erase branches. Treat blanks and duplicates as events.分岐を消さない。空白も重複も、出来事として残す。
Two conversations can look identical while carrying different ancestry, timing, and tool events. The workbench keeps structure intact and converts it into verifiable units.
INPUTByte-level hash
BRANCH ARoles + timestamps
BRANCH BTool + system events
BRANCH CMissing + duplicates
OUTPUTAuditable record
DELIVERABLES
Show the verification path before the conclusion.
MANIFEST
Evidence manifest
Trace inputs, hashes, counts, safe stops, and processing history.DATA DICTIONARY
Data dictionary
Define roles, timestamps, branches, references, duplicates, and missing values.AUDIT REPORT
Audit report
Present reproducible conditions, differences, limits, and candidate findings.BOUNDARY PROTOCOL
Choosing not to inspect can be part of evidence preservation.見ないことも、証拠保全の一部です。
Suspected unrelated-person, out-of-scope, or privileged containers stop before inspection. Live cases, source text, secrets, and sensitive filenames never enter the public experience.
- LOCAL ONLYEvidence processing stays offline
- NO LIVE CASESNo case is connected to the public site
- CAUTIOUS CLAIMSReappearance is not proof of causation
NEXT CASE?CONTROLLED
EVALUATION
EVALUATION
VENDOR-SUPPLIED TEST EXPORTS
Test it with logs you control.あなたが管理するテストログで、確かめてください。
The next step is an invitation-only evaluation using an AI vendor’s synthetic or benchmark export. No customer data is required. The test stays inside an immutable, offline, source-text-free boundary.
VIEW THE EVALUATION PROTOCOL ＋
- 01Receive a vendor-controlled synthetic export through a local read-only path
- 02Establish byte hashes and record counts before interpreting content
- 03Reconstruct with a private, tightly scoped adapter
- 04Return reproducible counts and an audit result without source text
