lore-create-fieldnote

Document non-obvious snags by creating a structured fieldnote entry. This converts failed operations like authentication quirks and encoding edge cases into a standardized knowledge-base record stored as a FIELDNOTE.md manifest.

Capture environmental knowledge using standardized fieldnotes. This process records specific parameter tricks and platform incompatibilities from failed operations so teams avoid repeating the same surprises across development, testing, and production.

Create a fieldnote by converting the failed operation into a structured entry. The file is automatically stored as FIELDNOTE.md under the designated path at ~/.lore/knowledge-base/fieldnotes/<fieldnote-name>/.

Yes, troubleshooting fieldnotes must follow a standardized format with a controlled content window. Each FIELDNOTE.md entry is enforced to stay within a strict 30-80 line limit to maintain concise environmental knowledge records.

Fieldnotes are applicable for tracking failures across CI and production environments. They handle platform-related surprises, authentication quirks, and encoding edge cases encountered during development, testing, and production runs.

Standardized fieldnotes prevent teams from repeating operational surprises. Unlike informal documentation, they enforce a structured 30-80 line FIELDNOTE.md format that reliably captures non-obvious snags for the knowledge-base.