noCV
CPRES-102 · Define presence meaning

Validate presence room identifiers before subscribing

Practice briefBugFoundational

Malformed room names reach the broker and create unbounded keys. Parse a bounded typed room identifier.

Focused work estimate
1h 15m + prerequisites
Priority in the scenario
High
Engineering practice
Input validation · Pub-sub

Estimated field mix

  • Security50%
  • Real-time systems50%

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

  • Valid room IDs subscribe
  • Malformed IDs fail before broker access
  • Error omits raw oversized input

Implementation constraints

  • Room parsing does not replace membership checks.

Verification to include

  • Subscribe valid fixture room
  • Send oversized room identifier

Deliverables

  • Room parser and rejection tests

Rollout and recovery

Reject new subscriptions if parsing fails.

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.