Public Log Taxonomy
A public log taxonomy separates reusable work records from raw diaries. The goal is to decide whether a cleaned note should remain a log, become a project milestone, update a concept, or become a Korean post.
The basic classification is:
where is a cleaned log candidate.
Log Types
| Type | Use when | Better destination if mature |
|---|---|---|
| Incident | A failure or debugging episode taught a reusable lesson | Public incident note or Infra |
| Experiment | A run tested a question or hypothesis | Research log or Projects |
| Decision | A design or research direction changed | Decision record |
| Milestone | A public project changed state | Project milestone format |
| Reading | Paper reading produced a reusable insight | Papers or Concepts |
| Operations | A workflow or runbook improved | Infra or Agent workflows |
Minimum Fields
- Context: generic public context.
- Trigger: what caused the log to be written.
- Evidence: command, observation, source, or artifact summary.
- Lesson: reusable diagnosis, decision, or pattern.
- Destination: stay as log, promote, merge, or drop.
- Boundary: what private detail was omitted.
Checks
- Is the log a reusable lesson rather than a private diary entry?
- Does it have enough evidence to support the lesson?
- Is the strongest destination a log, concept, project, paper, infra note, or post?
- Are unpublished results, private infrastructure, and collaborator context removed?
- Is there a next promotion rule if the log becomes important?