Skip to content

Day 2 — Interpret, Steward, and Share

Wednesday, September 16, 2026 · half day

Day 2 protects a short finish window, then turns the build into an honest and reusable story. Do not begin a new direction unless the Day 1 approach cannot answer the scoped question.

Edit your team page Open Home See the OLC example

Event rhythm

Time Event and team focus
8:30 a.m. Check-in
9:00–10:00 a.m. Finish and proportionally validate the most useful artifact
10:00 a.m. Break
10:15–10:45 a.m. Prepare the public page, evidence boundary, stewardship handoff, and report-out
10:45–11:45 a.m. Team sharing
11:45 a.m.–noon Reflection
Noon Adjourn

Times follow the source OLC event schedule; facilitators may announce local adjustments.

9:00–10:00 — Finish and validate

Reconfirm the smallest useful finish. Validation should match the artifact and available time. It might mean:

  • Checking a sample of records or outputs
  • Comparing against a known example or baseline
  • Reproducing the workflow from a clean start
  • Running one sensitivity check
  • Asking a teammate to challenge the interpretation
  • Recording why a stronger check was not possible

Keep a partial artifact when it is informative. State what works, what does not, and what another person would need to continue.

10:15–10:45 — Interpret, steward, and prepare

Complete the Home story in this order:

  1. Observation: What happened?
  2. Evidence: What artifact or analysis supports it?
  3. Interpretation: What do you think it means?
  4. Uncertainty: What do you not know or should not claim?
  5. Stewardship: Who should help frame, interpret, or review a continuation?
  6. Next step: What is the smallest responsible continuation?

Use sovereignty checkpoint 3 before public sharing. Naming a person, office, Tribe, community, or organization as a possible future reviewer does not mean review, permission, approval, authority, partnership, or endorsement has occurred.

Turn Instructions off and check that only public-safe content remains. Review the non-blocking site completion coach; it finds common omissions but cannot judge the science or social context.

10:45–11:45 — Share from OASIS

Select Hackathon Report Out on Home. Do not create a separate slide deck unless facilitators request one. Aim for 5–6 minutes unless the facilitator assigns a different team allotment.

Walk through:

  • Our Question
  • Why This Matters
  • What We Tried to Build
  • What We Learned
  • What Remains Uncertain
  • What’s Next

Point to the artifact rather than reading every sentence. A useful report-out can center a null result, failed approach, evidence mismatch, or well-defined limitation.

Day 2 finish line

Someone outside the team should be able to understand:

  • The question and public-data boundary
  • What the artifact does and how it was checked
  • What the evidence supports
  • What remains uncertain or did not work
  • Which roles or relationships a continuation needs
  • What can be reused and what should happen next

Only public-safe material belongs on the published page. Keep sensitive, private, restricted, or community-controlled information in an approved location.