Being developed as an offline-first evidence workspace. Current RC26 validation covers bounded repository inspection and engineering assistance. Broader Windows investigation workflows remain a development direction.
Choose the repository question and the small set of files you are permitted to inspect.
02
Inspect
Keep selected excerpts, redaction boundaries, and missing context visible.
03
Review
Connect each finding to its source and keep unresolved questions beside the evidence.
04
Decide separately
A person reviews the evidence before proposing a change. Inspection does not authorize execution.
Illustrative workflow · Synthetic data
Why does this example app accept a spaces-only name?
Explore a fictional three-file repository. This is a teaching example, not a live RC26 execution or an application screenshot.
01 · Select a bounded scope
Three files. One question.
All names and excerpts below are fabricated. No local files are read or uploaded.
README.md · expected behavior
A project name must contain at least one non-space character.
src/settings.py · selected source
def valid_name(value):
return len(value) > 0
tests/test_settings.py · selected test
assert valid_name("example") is True
assert valid_name("") is False
Excluded: credentials, environment files, dependencies, user data, and unrelated source.
02 · Connect the evidence
The selected code checks length.
The README describes non-space characters. The selected function checks whether the string has any characters. The displayed tests cover a name and an empty string.
Evidence gap: the selected tests do not show what should happen for a spaces-only name.
03 · Keep uncertainty visible
Is whitespace normalized elsewhere?
That cannot be answered from these three excerpts. A caller might trim the input before validation. No test has been executed in this example.
04 · Review before changing
A bounded next question.
A reviewer can decide whether to inspect the caller and add a spaces-only test. The website does not modify source, run a model, or apply a fix.
Discovery fit
A narrow audience and a bounded promise.
Designed for
Independent Windows IT consultants and small technical teams who need to preserve and explain the basis of a technical finding.
Intended outcome
System observations become understandable evidence with visible sources, scope, age, and limits.
Example use
Inspect selected repository evidence before proposing a change, preserving the source and uncertainty behind each finding.
Related application
Trace would capture and investigate evidence. The proposed Insight application would analyze permitted evidence for human decision support.
Thirteenfold Trace is an offline-first evidence workspace in development. Its documented internal workflow focuses on bounded repository inspection and engineering assistance, with sources and missing context kept visible for human review.
Does the Trace demonstration upload my repository?
No. The website walkthrough displays fictional files and synthetic examples. It does not read or upload your local repository.
What does expressing pilot interest provide?
It records your use case for discovery. It does not provide a public installer, a subscription, or guaranteed access. Selection, native Windows qualification, and release remain separate decisions.