본문으로 건너뛰기
cccskills
무료GitHub에 공개

is-gps-200n

Knowledge base from IS-GPS-200 Rev N (NAVSTAR GPS Space Segment / Navigation User Segment Interfaces). Use as a worked ICD/IS exemplar: what an interface specification is, DIST-A and IRN/CCB change control, interface definition vs identification, composite-signal criteria patterns, NAV data as payload families, and time/definition hygiene. Covers Rev N synthesized notes only; does not transcribe Apps II–IV bit fields or PRN/Gold-code tables, and does not replace faa-std-025 preparation rules.

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

jgsystemsconsulting/jgs-se-knowledge-packs

실행 점수 미검증

설치 방법 보기

포함된 파일(12)

  • SKILL.md5.1 KB
  • chapters/ch01-is-scope-and-change-control.md4.1 KB
  • chapters/ch02-interface-definition-and-identification.md4.2 KB
  • chapters/ch03-interface-criteria-pattern.md4.0 KB
  • chapters/ch04-nav-data-as-payload.md3.6 KB
  • chapters/ch05-time-and-definition-hygiene.md3.8 KB
  • chapters/ch06-appendices-as-a-map.md3.6 KB
  • cheatsheet.md1.0 KB
  • glossary.md1.3 KB
  • LICENSE1.5 KB
  • PACK.yaml2.0 KB
  • patterns.md1.9 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

<!-- argument-hint: [topic, ICD pattern, or chapter number] -->

NAVSTAR GPS Space Segment / Navigation User Segment Interfaces (IS-GPS-200N)

Source: IS-GPS-200 Rev N (cover 01-AUG-2022) (US Government work, public domain, DIST-A) | Chapters: 6

When to use

Reach for this pack when you need a worked Interface Specification / ICD — how a live IS defines RF links, identifies codes and NAV payload, writes interface-criteria shalls, and keeps time/definition hygiene — complementary to faa-std-025 (how to prepare an IRD/ICD, not a live ICD).

Prerequisites: none — plain Markdown; no MCP server, API key, or licence tier needed at runtime.

How to Use This Skill

  • Without arguments — load the core frameworks below.
  • With a topic — ask about ICD-as-contract, IRN/CCB, L1/L2 criteria, LNAV vs CNAV families, URA/CEI, or which appendix to open.
  • With a chapter — ask for ch01 through ch06.

Supporting files: glossary.md, patterns.md, cheatsheet.md.

Core Frameworks & Mental Models

Document-as-contract

An IS states the Space Segment / User Segment interface. It does not alter contracts or purchase orders (cover notice). Users implement against numbered shalls; exceptions live in Appendix I letters, not in silent receiver folklore.

Definition → identification → criteria

  1. Definition (3.1) — what the interface is (L1 and L2 RF links carrying ranging codes + NAV data to a user with RF visibility).
  2. Identification (3.2) — which codes and data families exist, and that they are CDMA-separated.
  3. Criteria (3.3) — measurable shalls (frequency plan, levels, phasing, polarization, time).

Change / IRN discipline

ICC prepares PIRNs; ICWG has 45 days; GPS Directorate CCB (with DOT representing civil/public interest) makes the IS effective. Rev N incorporates IRN-IS-200M-001 (RFC-467). Distribution status changed to Public Release on an earlier revision.

Payload vs bits

Body text names LNAV D(t) and CNAV DC(t) families. Bit layouts, FEC polynomials, and PRN tables live in Apps II–IV — open those only when implementing a decoder, not when learning ICD structure.

Chapter Index

#SectionKey content
ch01IS Scope and Change ControlWhat an IS/ICD is; DIST-A; ICC/ICWG/CCB/IRN
ch02Definition vs IdentificationL1/L2 contract; code families; document-as-contract
ch03Interface Criteria PatternFrequency, levels, phasing, polarization as shalls
ch04NAV Data as Interface PayloadLNAV/CNAV families, not bit fields
ch05Time and Definition HygieneGPS time / Z-count; URA; CEI; reserved/invalid
ch06Appendices as a MapWhen to open App I–IV; do not dump payloads

Topic Index

  • CCB / PIRN / IRN → ch01
  • CEI data set → ch05
  • Change / IRN → ch01
  • CM (configuration of the IS) → ch01
  • CNAV / LNAV families → ch04, ch06
  • DIST-A / public release → ch01
  • ICD / IS → ch01, ch02
  • Interface criteria (RF pattern) → ch03
  • Interface definition vs identification → ch02
  • Interface Management → ch01, ch02
  • PRN / ranging codes (as identifiers) → ch02, ch06
  • Requirements Traceability → ch02, ch03
  • Reserved / invalid / dummy SV → ch05
  • URA → ch05
  • Z-count / GPS time → ch05

Supporting Files

Scope & Limits

This pack covers IS-GPS-200 Rev N (cover date 01-AUG-2022; public-release revision record) as synthesized reference notes from the official gps.gov PDF (248 pages per extraction metadata). It is an ICD exemplar, not a signal-processing dump: Apps II–IV bit fields, PRN/Gold-code tables, and FEC polynomials are not transcribed. It complements faa-std-025, which teaches IRD/ICD preparation rules (outlines, VRTM, FAA CM) and is not itself a live ICD — same slug-distinction pattern as dote vs dod-te-guidebook. It does not ingest IS-GPS-705J, IS-GPS-800J, ICD-GPS-153, or a non-existent IS-300. US Government public domain work (DIST-A). No source-material download link is published.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

automotive-signpost

무료

Signpost (not a knowledge pack) for the automotive standards landscape: ISO 26262, ASPICE, SAE J3016, UNECE R155, UNECE R156, and the NHTSA vehicle set. Contains NO source content: designation, edition, owner, status, and an official catalogue URL only. Use when you need to identify or locate an automotive standard. Most are paywalled or carry no redistribution grant and cannot be packaged; the one open path is the nhtsa-vehicle pack.

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

jgsystemsconsulting/jgs-se-knowledge-packs82026년 10월 15일 업데이트

avionics-signpost

무료

Signpost (not a knowledge pack) for the avionics development assurance standards landscape: RTCA DO-178C / EUROCAE ED-12C and its supplements (DO-330/ED-215, DO-331/ED-218, DO-332/ED-217, DO-333/ED-216); RTCA DO-254 / EUROCAE ED-80; SAE ARP4754B and ARP4761A; and the free regulator documents that recognise them (FAA AC 20-115D, AC 20-152A, Order 8110.49A; EASA AMC 20-115D and AMC 20-152A). Contains no source content: each row carries only the designation, title, edition, owner, redistributability status, and the owner's URL. Use when you need to identify, cite, or locate an avionics standard; paywalled rows point to the owner, free rows point to the regulator text, and the FAA rows also name the in-repo faa-8110-49 pack.

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

jgsystemsconsulting/jgs-se-knowledge-packs82026년 10월 15일 업데이트

cisa-cpg

무료

Knowledge base from CISA Cross-Sector Cybersecurity Performance Goals 2.0. Use for prioritized IT/OT baseline cyber goals aligned to NIST CSF 2.0 (including GOVERN), critical-infrastructure hygiene, MSP/supply-chain expectations, and board-friendly outcome language. Covers CPG 2.0 goals only; does not replace full CSF programs, sector-specific goals (SSGs), or CSET tooling detail.

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

jgsystemsconsulting/jgs-se-knowledge-packs82026년 10월 15일 업데이트

dafman-63-119

무료

Knowledge base from DAFMAN 63-119 (15 April 2021), Mission-Oriented Test Readiness Certification. Use for continuous MOTRC replacing single-point OTRR thinking: framework/applicability, Certification Official vs PM roles, review cycle and exit criteria, certification memo/decertify gates, DT&E/contractor evidence, ITT integration and cyber resiliency, and the 31-template matrix. DAF T&E readiness process only—does not replace DoDI 5000.89, AFI 99-103, or multi-service lead policies.

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

jgsystemsconsulting/jgs-se-knowledge-packs82026년 10월 15일 업데이트

dau-se-guidebook

무료

Knowledge base from the DoD Systems Engineering Guidebook (OUSD R&E, February 2022). Use for the DoD SE process model — the 16 SE processes (8 technical management + 8 technical) mapped to ISO/IEC/IEEE 15288, the event-driven technical reviews and audits across the Major Capability Acquisition life cycle (ASR, SRR, SFR, PDR, CDR, SVR/FCA, PRR, PCA), the Systems Engineering Plan (SEP), risk/issue/opportunity management, TPMs and leading indicators, system-of-systems and digital engineering, and the 24 design considerations (RAM, system safety, HSI, system security engineering, MOSA, supportability, etc.). Acquisition-program oriented: thin on detailed cost estimating, contracting law, and non-DoD or commercial life cycles.

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

jgsystemsconsulting/jgs-se-knowledge-packs82026년 10월 15일 업데이트

digital-systems-engineering

무료

Knowledge pack from 'Towards Digital Engineering: The Advent of Digital Systems Engineering' (Huang et al., Old Dominion University, arXiv:2002.11672, 2020). Use when reasoning about digital engineering, the DoD Digital Engineering Strategy and its five goals, the Authoritative Source of Truth, digitalization vs. digitization, digital augmentation, digitalized models, provenance, unique identification, and the four-level (vision/strategy/action/foundation) DSE research framework. Covers the conceptual/vision layer of the field. SCOPE LIMITS: this is a single ~28-page vision paper, not a methods handbook — it is thin on step-by-step procedures, tooling, case studies, and quantitative evaluation, and it predates 2020 so it does not cover later digital-engineering standards or recent AI/LLM advances. Use the sebok pack for established SE canon and MBSE depth.

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

jgsystemsconsulting/jgs-se-knowledge-packs82026년 10월 15일 업데이트

jgsystemsconsulting의 스킬 모두 보기

이 스킬의 문제 신고