Logos Field Guide
16 · Field Note — Logos LAN (Dev Workshop)

Appendix · 16

Field Note — Logos LAN (Dev Workshop)

Appendix · 16

Post-event summary for a technical-led event (Logos LAN / dev workshop), posted to forum.logos.co. A field note is a clear account of what happened, what was learned, and what comes next.

Placeholders in {{ }}. Italic lines are guidance, delete when filling.

# {{Event name · Date, e.g. Logos LAN / Berlin · 16 June 2026}}

{{One line: what it was and where, e.g. "A technical-led build room at Radialsystem, Berlin, run adjunct to DappCon."}}

*Context, 2-3 lines. What ran, who it was for. Link out for the mission, do not restate it. No hype.*

## What worked
*The sessions and setups that landed. Plain, specific.*
- {{...}}

## What was learned
*Insights and surprises worth carrying to the next event.*
- {{...}}

## What broke
*Debug sessions and friction, treated as product data, not failures to bury.*
- {{...}}

## What was produced
*Concrete outputs. Credit by handle, tied to the work, never a roll-call.*
- {{e.g. Logos node brought up via Basecamp, setup debugged by @handle}}

## What happens next
*The plan. Owners where known.*
- {{...}}

## Build on this
*What a reader who was not there can use, and the route to plug in. Each item once.*
- {{Documented fix or setup path the next person can follow, link}}
- Open RFPs and λPrizes: {{link}}
- Next Logos LAN: {{link}}

Build the parallel. λ

Checklist

  • Sanitise before publishing. The whole note passes Protect first ("published when safe").
  • Credit only by consented handle, tied to the specific work. Never an attendee list or roll-call, no tagging without consent.
  • Voice: declarative, sparse, precise, dry.
  • Current stack names, not Nomos/Waku/Codex.
  • Lambda where work happens, not as wallpaper.
  • Close on the work, then the credo line. No inspirational ending.
Logos Field Guidev0.1