Skip to content

A real day of pacing: anchors, invites, and going quiet (spec 07 §5.16) #81

Description

@wine-fall

What it is

spec 07 is built at the mechanism level, but every constant in it is a by-ear guess: AWAY_GAP_FACTOR, INVITE_EVERY_N, INVITE_WINDOW_SEGMENTS, INVITE_WINDOW_MS, and the ENGAGED_MS / PRESENT_MS thresholds. The acceptance is a whole real day with the radio on: do the time anchors land at the right moments? Does an invite read as inviting rather than needy? Does walking away make it go quiet without making it feel dead?

Spec

specs/spec07/07-proactive-pacing.md §5.16.

Done when

The user has lived a day with it and the constants that were wrong have been moved — in the spec and the code together. Expect several to move; that is the point of the pass, not a failure of it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    by-earUser-run sensory acceptance; not assertable in a test

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions