'time' 검색 결과

Use this skill for training drivers on effective pre-trip inspection technique. Covers the comprehensive walk-around, time investment, and common areas drivers miss.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill when a driver does not meet federal medical standards and needs to apply for a variance. Covers application steps, required documentation, and review timeline.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill when a driver is operating under the 150 air-mile short-haul exception and is asked to produce records. Covers the simplified time records required, when ELD is NOT required, and the documentation that satisfies inspectors.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill when a driver encounters adverse weather, road, or traffic conditions and needs to extend driving time. Covers eligibility criteria, the 2-hour maximum extension, documentation requirements, and what does NOT qualify.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill when a driver needs to edit their own ELD record. Covers what edits are allowed, what edits trigger annotations, the unassigned-driving-time procedure, and when carriers must accept or reject driver edits.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a driver has been disqualified or is at risk of disqualification — major offense convictions (DUI, leaving the scene, drug trafficking with CMV), serious traffic violations, RR-grade-crossing violations, imminent-hazard out-of-service, or Clearinghouse positive-test prohibited status. Also use when planning a return-to-duty pathway, SAP process, or reinstatement timeline. Covers 49 CFR 383.51, Part 40 Subpart O, and Part 391.15.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill to understand FMCSA cardiac certification standards. Covers what cardiac conditions disqualify, time-to-clearance, and what documentation is needed for examiner certification.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill to set proper expectations on how a DataQ challenge is actually reviewed. Covers state vs federal authority, typical timelines, and common review outcomes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill when the user asks about DataQ — FMCSA's data review system at dataqs.fmcsa.dot.gov — for disputing inspection violations, crash records, or other entries that appear in a carrier's CSA / SMS score. Covers Request for Data Review (RDR) process, success rates, common dispute grounds, what evidence to attach, timeline expectations, and how successful disputes reduce BSI (BASIC Severity Indicator) scores. Cite 49 CFR 392.7 and the FMCSA DataQs User Guide.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill when the user asks about CMV operation types — Dedicated, OTR (Over-the-Road), Regional, Local, and the differences in driver lifestyle, pay, equipment, home time, hours, and customer mix. Reference industry segmentation conventions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill to track recent and upcoming SMS methodology changes from FMCSA. Covers proposed rule changes, comment periods, and implementation timelines.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill when the user asks about CDL driver wellness, retention strategies, what causes driver turnover, common health issues (obesity, hypertension, sleep apnea, mental health), benefits packages, home-time policies, and how to build a culture that keeps drivers. Reference ATA Workforce Development + FMCSA Wellness Initiative.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill to investigate a crash effectively. Covers preservation of evidence, witness statements, dashcam review, and reporting timeline.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill to understand how FMCSA calculates the Crash Indicator BASIC. Covers what crashes count, severity weighting, time weighting, and the preventability program.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill if your operating authority has been revoked and you need to reinstate. Covers application, fees, and timeline.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill to obtain a Motor Carrier (MC) number from FMCSA. Covers application, fees, and timeline.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill when the user asks about accident claims management — first-notice-of-loss procedures, working with insurance adjusters, claim severity classification, subrogation, claim closure timelines, and how to influence claim outcomes. Different from accident-investigation-playbook (which covers facts); this covers the insurance + claim side.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill when the user asks about accident registers, DOT-recordable accident definitions, what counts as a "reportable accident" under 49 CFR 390.5 + 390.15, accident register retention, post-accident testing trigger logic, FMCSA accident reporting (no longer required to FMCSA directly for non-fatal accidents), insurance reporting timelines, and what to do after a CMV crash. Cite 49 CFR 390.5 + 390.15.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a carrier asks about disaster recovery (DR) and business continuity planning (BCP) — cyber incident, natural disaster, terminal loss, key-person departure, financial liquidity event, major customer loss, insurance crisis, or fuel supply disruption. Covers risk assessment, continuity strategy, communication plans, and recovery time objectives.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill to handle the subrogation and claim process after a crash. Covers when subrogation applies, how to pursue it, and timeline.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design error handling strategies for TypeScript and Python applications — exception hierarchies, Result/Either types, retry patterns, error boundaries, and structured error logging. Use when designing error handling architecture, choosing between exceptions and Result types, implementing retry logic, or building error recovery flows. Activate on "error handling", "exception hierarchy", "Result type", "retry pattern", "circuit breaker", "error boundary", "Pokemon exception". NOT for debugging specific runtime errors, logging infrastructure setup, or monitoring/alerting configuration.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Architects the encryption, codec/transport, and premium-feature layer of a group video-calling product, on top of an already-chosen SFU topology. Covers E2EE patterns (Zoom leader-fan-out, Signal pairwise-fan-out, MLS/TreeKEM as in Discord's DAVE, Telegram's ledger consensus), the SFrame (RFC 9605) + WebRTC Insertable Streams mechanism letting an SFU relay encrypted frames it can't read, codec/transport choice (AV1/VP9 SVC vs. simulcast, Opus, congestion control, Media-over-QUIC, WHIP/WHEP), and which "premium" features (virtual backgrounds, live captions, recording, breakout rooms, spatial audio) survive E2EE vs. structurally can't. Use when adding E2EE to an SFU-based call, choosing a 2026 codec/SVC strategy, or deciding which features to disable under E2EE mode. NOT for call topology/platform choice (see webrtc-adhoc-video-chat, which this composes with). NOT for one-way broadcast (see managed-video-streaming-pipeline). NOT for the DM/group-chat text backend (see realtime-messaging-backend-architecture).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when introducing a feature flag system, choosing between release flags / experiment flags / operational flags / kill switches / permission flags, designing percentage rollouts, building kill-switch + circuit-breaker patterns, structuring evaluation contexts (user IDs, plan tier, region), or building flag-cleanup discipline. Triggers: LaunchDarkly / GrowthBook / Unleash / Flagsmith / OpenFeature, percentage ramp, sticky bucketing, kill switch wired to alerting, "we still have flags from 2 years ago", flag debt, OpenFeature provider, evaluation context, default value on provider failure. NOT for A/B test statistical analysis (separate skill), traffic-split routing at the edge, build-time bundler defines, or environment-based config.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Environment configuration manager for 12-factor config, feature flags, and multi-environment management. Activate on: environment variables, ConfigMap, feature flags, 12-factor config, dotenv management, config per environment, runtime config. NOT for: secret storage (use secret-management-expert), IaC provisioning (use terraform-module-builder), CI/CD variables (use github-actions-pipeline-builder).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.