Template — Finding
FND-NNN — <short statement>
| Field | Value |
|---|---|
| System | <server/client/tool> |
| Status | hypothesis / observed / confirmed / rejected / superseded |
| Confidence | low / medium / high |
| Recorded | YYYY-MM-DD by <maintainer-id> |
| Related issue | <link> |
| Supersedes | <finding or none> |
Question
One falsifiable question.
Inputs
Artifact IDs, full Git commits, hashes, client build, database revision, and access class. Do not paste restricted bytes.
Environment
Operating system, architecture, locale, time behavior, network layout, and tool versions.
Procedure
Numbered, repeatable steps. State the control and the single variable changed.
Observation
What happened, without interpretation. Link sanitized logs, traces, captures, screenshots, or minimal fixtures.
Interpretation
What the observation may mean, alternative explanations, and confidence.
Result
Confirmed fact, rejected hypothesis, or next experiment.
Impact
Affected baselines and whether installation, compatibility, integrity, security, or preservation is involved.
Follow-up
<issue, patch, regression test, missing artifact>
Private Server Preservation
- Home
- Preservation Status
- Compatibility Matrix
- Ecosystem Map
- Vision and Scope
- Server Catalog
- Client Preservation
- Archive Layout
- Repository Mirroring
- Mirror Inventory
- Preservation Metadata
- Reverse Engineering
- Findings Log
- Bug Tracker
- Toolbox
- Reproducible Baselines
- Operational Runbooks
- Backup and Recovery
- Governance and Safety
- Contributing
- Templates
PrivateServer-RS preservation wiki · Originals remain immutable · Every artifact must be attributable and verifiable