noCV
CPRES-101 · Define presence meaning

Define online presence as an unexpired connection lease

Practice briefTaskFoundational

A green dot remains after the browser closes. Replace the permanent flag with explicitly expiring presence.

Focused work estimate
1h 15m + prerequisites
Priority in the scenario
Medium
Engineering practice
TTL · State modeling

Estimated field mix

  • Real-time systems60%
  • Distributed systems40%

Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.

Your next step

Review it, then add it to your workspace.

The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.

Project context

Fictional document team Pine shows collaboration presence for synthetic accounts. Build a loopback WebSocket server and injected clocks; no message content or activity surveillance is required.

Setup prerequisites

  • Create synthetic memberships and session identifiers.
  • Implement controllable sockets and an in-memory TTL adapter.

Preceding work

No earlier ticket is required. Complete the project setup above.

Acceptance criteria

  • Active lease shows connected
  • Expiry removes connected state
  • UI explains connection meaning

Implementation constraints

  • Do not infer human attention from a socket.

Verification to include

  • Advance clock before expiry
  • Advance beyond expiry without disconnect

Deliverables

  • Lease contract and clock cases

Rollout and recovery

Hide presence if lease freshness cannot be established.

Value of the work

For the engineer: Practice ephemeral state, ordering and reconnect semantics.

For the team: Inspect whether online indicators avoid stale or unauthorized claims.

Evidence boundaries

Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.

Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.