# noCV engineering task library

Content version 5

Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included.

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

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

## CLINK — Mobile invitation and session navigation

Fictional team-planning app Finch opens invitations and shared work items. All users and sessions are synthetic; implement the app in an emulator without external identity credentials.

**Field:** Mobile. **Suggested stack:** React Native, TypeScript, Emulator, Testing Library.

**Engineer value:** Practice navigation state, capability checks and session boundaries.

**Company value:** Inspect whether links remain useful without bypassing authorization.

**Delivery agreement:** Deliver local navigation behaviors; real identity integrations remain separate.

### Setup prerequisites

- Create a local session adapter with expiry and revocation.

- Define synthetic invitation and work-item links.

### Parse entry points

Establish safe route contracts.

#### CLINK-101 — Reject malformed mobile invitation routes before navigation

**Task · High priority · Foundational**

noCV practice brief v5 · CLINK-101 · Mobile invitation and session navigation

Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included.

Phase: Parse entry points. Depends on: No preceding ticket.

Difficulty: Foundational. Estimated focused work: 75 minutes; setup and prerequisite tickets are additional.

Estimated field mix: Mobile 70% · Security 30%.

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

Pasted links with missing invitation IDs crash route construction. Add strict parsing before mounting screens.

Acceptance criteria

- Valid IDs produce typed routes

- Malformed links show a recoverable state

- Unsupported schemes are rejected

Implementation constraints

- Do not render arbitrary link text as markup.

Verification

- Open valid fixture link

- Open empty and oversized IDs

Deliverables

- Link parser and invalid-input cases

Rollout and recovery: Disable invitation entry while keeping home navigation.

Project prerequisites: Create a local session adapter with expiry and revocation. Define synthetic invitation and work-item links.

Engineer value: Practice navigation state, capability checks and session boundaries.

Company value: Inspect whether links remain useful without bypassing authorization.

AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.

Planning status does not create Outcome Evidence or Ownership Evidence.

#### CLINK-102 — Explain expired mobile invitations without automatic retries

**Story · Medium priority · Foundational**

noCV practice brief v5 · CLINK-102 · Mobile invitation and session navigation

Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included.

Phase: Parse entry points. Depends on: CLINK-101.

Difficulty: Foundational. Estimated focused work: 75 minutes; setup and prerequisite tickets are additional.

Estimated field mix: Mobile 100%.

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

Expired invitations spin indefinitely because the client treats every response as transient. Render terminal expiry distinctly.

Acceptance criteria

- Expiry stops retry

- User can return home

- Temporary failures retain manual retry

Implementation constraints

- Follow typed adapter error codes.

Verification

- Open expired fixture

- Simulate temporary outage

Deliverables

- Invitation error states

Rollout and recovery: Restore static invitation failure page if classification breaks.

Project prerequisites: Create a local session adapter with expiry and revocation. Define synthetic invitation and work-item links.

Engineer value: Practice navigation state, capability checks and session boundaries.

Company value: Inspect whether links remain useful without bypassing authorization.

AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.

Planning status does not create Outcome Evidence or Ownership Evidence.

#### CLINK-103 — Retain a mobile link destination through local sign-in

**Story · Medium priority · Intermediate**

noCV practice brief v5 · CLINK-103 · Mobile invitation and session navigation

Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included.

Phase: Parse entry points. Depends on: CLINK-101, CLINK-102.

Difficulty: Intermediate. Estimated focused work: 120 minutes; setup and prerequisite tickets are additional.

Estimated field mix: Mobile 80% · Security 20%.

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

Signing in from an invitation lands on the dashboard. Preserve a validated destination until identity is available.

Acceptance criteria

- Valid destination resumes once

- External destinations are rejected

- Cancel sign-in clears pending intent

Implementation constraints

- Store route identity, not raw credentials or URL tokens.

Verification

- Sign in and resume

- Cancel then sign in normally

Deliverables

- Pending-route coordinator

Rollout and recovery: Disable continuation if validation fails.

Project prerequisites: Create a local session adapter with expiry and revocation. Define synthetic invitation and work-item links.

Engineer value: Practice navigation state, capability checks and session boundaries.

Company value: Inspect whether links remain useful without bypassing authorization.

AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.

Planning status does not create Outcome Evidence or Ownership Evidence.

### Handle identity changes

Preserve only authorized navigation intent.

#### CLINK-104 — Recheck mobile work-item access after account switching

**Bug · High priority · Advanced**

noCV practice brief v5 · CLINK-104 · Mobile invitation and session navigation

Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included.

Phase: Handle identity changes. Depends on: CLINK-103.

Difficulty: Advanced. Estimated focused work: 180 minutes; setup and prerequisite tickets are additional.

Estimated field mix: Security 70% · Mobile 30%.

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

Switching accounts leaves the previous account's work screen visible. Clear account-scoped cache before refetching.

Acceptance criteria

- Old content clears on switch

- New identity requires authorized read

- Denied reads show no prior item data

Implementation constraints

- Account identity belongs in cache boundaries.

Verification

- Switch to authorized account

- Switch to denied account

Deliverables

- Account-switch isolation and checks

Rollout and recovery: Force full local session reset while repaired.

Project prerequisites: Create a local session adapter with expiry and revocation. Define synthetic invitation and work-item links.

Engineer value: Practice navigation state, capability checks and session boundaries.

Company value: Inspect whether links remain useful without bypassing authorization.

AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.

Planning status does not create Outcome Evidence or Ownership Evidence.

#### CLINK-105 — Serialize mobile session refresh for simultaneous requests

**Task · High priority · Advanced**

noCV practice brief v5 · CLINK-105 · Mobile invitation and session navigation

Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included.

Phase: Handle identity changes. Depends on: CLINK-103.

Difficulty: Advanced. Estimated focused work: 180 minutes; setup and prerequisite tickets are additional.

Estimated field mix: Mobile 50% · Security 30% · Performance engineering 20%.

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

Opening a linked screen triggers three refresh calls and conflicting session updates. Share one in-flight refresh.

Acceptance criteria

- Concurrent reads share refresh

- Failure releases waiting requests consistently

- Later retry can start anew

Implementation constraints

- Session tokens stay outside generic logs.

Verification

- Trigger three expired reads

- Reject refresh then retry

Deliverables

- Refresh coordinator and concurrency tests

Rollout and recovery: Stop automatic refresh and require explicit sign-in.

Project prerequisites: Create a local session adapter with expiry and revocation. Define synthetic invitation and work-item links.

Engineer value: Practice navigation state, capability checks and session boundaries.

Company value: Inspect whether links remain useful without bypassing authorization.

AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.

Planning status does not create Outcome Evidence or Ownership Evidence.

#### CLINK-106 — Cancel pending mobile navigation when invitation ownership changes

**Bug · High priority · Intermediate**

noCV practice brief v5 · CLINK-106 · Mobile invitation and session navigation

Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included.

Phase: Handle identity changes. Depends on: CLINK-104, CLINK-105.

Difficulty: Intermediate. Estimated focused work: 135 minutes; setup and prerequisite tickets are additional.

Estimated field mix: Mobile 50% · Security 50%.

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

An invitation opened before account switching completes under the wrong identity. Bind continuation to the initiating session generation.

Acceptance criteria

- Stale continuation is discarded

- Current session can reopen link

- No prior invitation details remain visible

Implementation constraints

- Cancellation must survive late adapter responses.

Verification

- Resolve current invitation

- Resolve old invitation after switch

Deliverables

- Session-scoped continuation guard

Rollout and recovery: Clear all pending routes on account change.

Project prerequisites: Create a local session adapter with expiry and revocation. Define synthetic invitation and work-item links.

Engineer value: Practice navigation state, capability checks and session boundaries.

Company value: Inspect whether links remain useful without bypassing authorization.

AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.

Planning status does not create Outcome Evidence or Ownership Evidence.

#### CLINK-107 — Recover mobile sign-in continuation after process restart

**Story · Medium priority · Expert**

noCV practice brief v5 · CLINK-107 · Mobile invitation and session navigation

Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included.

Phase: Handle identity changes. Depends on: CLINK-103, CLINK-105.

Difficulty: Expert. Estimated focused work: 240 minutes; setup and prerequisite tickets are additional.

Estimated field mix: Mobile 60% · Security 40%.

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

An emulator restart during local sign-in loses the requested destination. Persist minimal, expiring continuation state.

Acceptance criteria

- Valid continuation resumes once

- Expired continuation is discarded

- Unknown schema versions fail closed

Implementation constraints

- Persist no session secrets in navigation storage.

Verification

- Restart before continuation

- Tamper with saved destination

Deliverables

- Versioned continuation store and restart checks

Rollout and recovery: Delete continuation metadata and return home.

Project prerequisites: Create a local session adapter with expiry and revocation. Define synthetic invitation and work-item links.

Engineer value: Practice navigation state, capability checks and session boundaries.

Company value: Inspect whether links remain useful without bypassing authorization.

AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.

Planning status does not create Outcome Evidence or Ownership Evidence.

### Test interruption

Recover process and session transitions.

#### CLINK-108 — Keep the mobile Back stack free of completed sign-in screens

**Bug · Medium priority · Intermediate**

noCV practice brief v5 · CLINK-108 · Mobile invitation and session navigation

Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included.

Phase: Test interruption. Depends on: CLINK-106, CLINK-107.

Difficulty: Intermediate. Estimated focused work: 105 minutes; setup and prerequisite tickets are additional.

Estimated field mix: Mobile 100%.

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

After joining a team, Back returns to a completed sign-in screen that resubmits. Replace transient routes on success.

Acceptance criteria

- Back reaches prior meaningful screen

- Completed forms cannot resubmit

- Failed sign-in remains editable

Implementation constraints

- Specify stack behavior for cold and warm launches.

Verification

- Complete cold-launch sign-in

- Fail then retry warm launch

Deliverables

- Stack transition and navigation tests

Rollout and recovery: Reset to home after sign-in if replacement fails.

Project prerequisites: Create a local session adapter with expiry and revocation. Define synthetic invitation and work-item links.

Engineer value: Practice navigation state, capability checks and session boundaries.

Company value: Inspect whether links remain useful without bypassing authorization.

AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.

Planning status does not create Outcome Evidence or Ownership Evidence.

#### CLINK-109 — Expose revoked mobile sessions before showing cached team content

**Bug · High priority · Advanced**

noCV practice brief v5 · CLINK-109 · Mobile invitation and session navigation

Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included.

Phase: Test interruption. Depends on: CLINK-104, CLINK-108.

Difficulty: Advanced. Estimated focused work: 180 minutes; setup and prerequisite tickets are additional.

Estimated field mix: Security 70% · Mobile 30%.

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

A resumed app flashes old team details before learning the session was revoked. Gate sensitive cached rendering.

Acceptance criteria

- Resume enters verification state

- Revocation clears scoped cache

- Offline uncertainty has an explicit locked view

Implementation constraints

- Public shell may render without private records.

Verification

- Resume valid session

- Revoke during background pause

Deliverables

- Resume gate and revocation checks

Rollout and recovery: Clear private cache on every resume until fixed.

Project prerequisites: Create a local session adapter with expiry and revocation. Define synthetic invitation and work-item links.

Engineer value: Practice navigation state, capability checks and session boundaries.

Company value: Inspect whether links remain useful without bypassing authorization.

AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.

Planning status does not create Outcome Evidence or Ownership Evidence.

#### CLINK-110 — Record mobile deep-link failure categories without invitation tokens

**Chore · Low priority · Intermediate**

noCV practice brief v5 · CLINK-110 · Mobile invitation and session navigation

Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included.

Phase: Test interruption. Depends on: CLINK-109.

Difficulty: Intermediate. Estimated focused work: 90 minutes; setup and prerequisite tickets are additional.

Estimated field mix: Privacy engineering 60% · Mobile 40%.

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

Support logs raw invitation URLs while diagnosing failures. Emit categories and route types only.

Acceptance criteria

- Logs exclude IDs and tokens

- Known failures have stable categories

- Unexpected errors use bounded safe summaries

Implementation constraints

- Verify with synthetic secret-like links.

Verification

- Log valid route outcome

- Reject token-bearing malformed URL

Deliverables

- Diagnostic event contract

Rollout and recovery: Disable link diagnostics on redaction failure.

Project prerequisites: Create a local session adapter with expiry and revocation. Define synthetic invitation and work-item links.

Engineer value: Practice navigation state, capability checks and session boundaries.

Company value: Inspect whether links remain useful without bypassing authorization.

AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.

Planning status does not create Outcome Evidence or Ownership Evidence.
