blob: 713246876db50645a93d16ff152f22b3c46a3edb (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
|
# Report Naming Standard
## Filename
Use:
```text
YYYY-MM-DD--{experiment-line}--r{round}--{purpose}.md
```
Rules:
- date must be the report date,
- `experiment-line` should be short and stable,
- `round` should be zero-padded only if that is already the project convention; otherwise `r3` / `r03` are both acceptable if used consistently,
- `purpose` should describe why the report exists, not a vague label like `summary` unless that is truly the purpose.
Recommended purpose values:
- `transfer-summary`
- `ablation-report`
- `failure-analysis`
- `robustness-check`
- `round-review`
## Title
Use:
```text
{Experiment Line} / Round {N} / {Purpose} / {YYYY-MM-DD}
```
## Frontmatter fields
Required:
- `type: results-report`
- `date`
- `experiment_line`
- `round`
- `purpose`
- `status`
- `source_artifacts`
- `linked_experiments`
- `linked_results`
## Placement in Obsidian
Internal reports go to:
```text
Results/Reports/{filename}
```
Do not put internal experiment reports in `Writing/` unless they are already manuscript/slides/rebuttal material.
|
