Session Handoff Note

Written at the end of every session, especially unfinished ones. A finished task carries its own record in the history; an unfinished one carries nothing. Holds state and pointers — never durable knowledge.

Syntax

implementor-onboarding

SESSION NOTE — [tenant] — [date]

Goal.            what this session was trying to achieve
Landed.          done AND verified. Not "worked on"
In flight.       half-done, and precisely where it stopped
Decisions made.  anything chosen where another option was reasonable, and why
Blocked on.      what is waiting, and on whom
Next.            one concrete action, startable cold
Do not.          what was tried and rejected, so it is not retried

Parameters

Parameter	Type	Description
Landed	verified state	Only things you have observed to be true. "Merged" is not "live".
Do not	rejected approaches	The most-skipped section and the highest-value one. Rejected approaches are knowledge you already paid for.
Next	action	Concrete enough that a cold start does not need to re-derive context.

Example

implementor-onboarding

Landed.    Gutter service page live and verified at the URL.
           Redirect from /gutters confirmed working.
In flight. Autumn banner — component built, not wired into the
           homepage. Stopped at src/components/home/Banner.tsx.
Decisions. Used the existing CTA component rather than a new one,
           so styling stays consistent if the CTA changes.
Blocked.   Waiting on the owner for the autumn promo end date.
Next.      Wire Banner into HomePage below the hero.
Do not.    Do not try the CSS grid approach for the banner layout —
           it breaks the mobile hero spacing. Flex works.