INCOSE Space Systems Working Group

Packet identity

Packet ID

organizations:entity-incose-space-systems-working-group

Packet SHA-256 identity

9affb4c25757e5fbea715c76ecb1722035757e3b9f6ee9800893eeb7681fd479

Corpus SHA-256 identity

8fa944604ca189f5a9216ca59f640ad2ca20972ad512f2f4970764716782e18d

Release ID

public-alpha-2026-07-26-research-visuals-r14

Source commit

3eb036fce3d711336c8c605625895e8a2e799ab0

Frozen corpus date

2026-07-25

Primary records

1

Reference sources

1

Questions and exclusions

Required questions

1. Required question 1 (exact ID: question-1)
   Does the official source establish the entity, current program, and bounded capability described?
2. Required question 2 (exact ID: question-2)
   Are potential fit, risks, access, geography, and engagement boundaries current and proportionate?
3. Required question 3 (exact ID: question-3)
   Could any wording imply partnership, endorsement, availability, procurement, authority, or affiliation that does not exist?

Explicit exclusions

• Indexing is not endorsement, due diligence completion, outreach, procurement, or a relationship.
• No aggregate organization score or sponsor-purchased ranking is permitted.

Requested controlled scopes: ecosystem-due-diligence, information-science

Frozen-evidence decision window: 90 days from the packet freeze. Not applicable to this packet family.

Complete primary record set

Every record below has one primary packet owner. Decisions must bind to the exact record and packet fingerprints; a changed lesson body, evidence grade, citation, locator, source snapshot, requirement, policy, release, or commit expires the old packet.

1. ecosystem-organization · entity-incose-space-systems-working-group

   INCOSE Space Systems Working Group

   Record fingerprint

   159a052b438a928f081a8a4d90dbe10a6442cf34f97ed8dfdc76e1e7519aec1c

   Minimum approvals

   1

   Required scope groups

   bounded-competence: ecosystem-due-diligence

   High-consequence domains

   None under the named two-person rule

   Review state

   pending

   Published human decisions

   0

   Inspect the complete frozen review surface

   ID

   entity-incose-space-systems-working-group

   Legacy ID

   org-interste-010

   Slug

   incose-space-systems-working-group

   Name

   INCOSE Space Systems Working Group

   URL

   https://www.incose.org/group/space-systems-working-group/↗ (opens external site in a new tab)

   Category

   Interstellar and settlement community

   Geography

   International

   Relevance

   direct

   Engagement

   Proposed only, subject to a future fit check and then-current access rules: consider INCOSE membership and a bounded contribution to a relevant work product only after checking current group rules and avoiding any endorsement implication. No outreach, eligibility determination, commitment, or procurement has occurred.

   Capability

   Space systems engineering, MBSE reference models, lifecycle methods, professional networking, and technical work products.

   Entity Kind

   professional-association working group

   Link Checked At

   2026-07-25

   Relationship

   indexed only; no formal relationship

   Engagement Status

   proposed; not undertaken

   Profile Summary

   The INCOSE Space Systems Working Group applies systems-engineering practices to government, industry, and academic space systems, provides professional exchange, and develops products including a CubeSat system reference model.

   Potential Fit

   Could provide methods critique for requirements, model-based systems engineering, lifecycle traceability, system-of-systems boundaries, and assurance governance.

   Risks

   1. Working-group membership is limited to INCOSE members and participation does not guarantee project adoption.
   2. CubeSat reference models and general systems methods require major tailoring for closed, multigenerational habitats.
   3. INCOSE includes defense domains; civil and defensive boundaries must remain explicit.

   Evidence Boundary

   Official-link review: the source URL returned an automated access barrier in direct fetch, while the official INCOSE working-group page was accessible through the web index and gives current mission, scope, leaders, and membership context. Public descriptions, performance, maturity, access, procurement, and current availability were not independently verified; independent review pending.

   Conflicts

   Conflicts were not assessed beyond publisher disclosure in this official-link review; financial, contracting, leadership, and institutional conflicts were not independently investigated.

   What Would Change

   A reviewed GShips model contribution, formal working-group feedback, and an applicable published reference architecture would materially strengthen fit.

Linked records—not review targets here

These records provide dependency or relationship context. Their decisions belong to their single primary packet, preventing double counting.

• habitat-assurance-pilot · entity-incose-space-systems-working-group partner-task-match:match-habitat-assurance-pilot-incose-space-systems · 098e8615e01299a5122ae4673a887894cd8065bbb0f6ce51e872b1f35533e45b

Frozen source snapshots

Source inclusion does not determine the disposition. Reviewers must inspect the cited locator and relation, note inaccessible material, and identify stronger or conflicting evidence.

Offline packet and worksheet

Downloads contain no reviewer contact details. Downloading does not create an account or store a review response in the GShips application. Ordinary provider request or analytics logs may record the download request. Work locally: the public site has no review account, upload endpoint, or decision-submission API.

Do not paste a completed decision, identity documents, private contact data, confidential conflict evidence, medical information, controlled material, or exploit details into a public form. Until a separately authorized private handoff exists, retain the completed worksheet locally.

Packet schema · JSON · Decision-bundle schema · JSON

Validate offline

Use Node.js 22.13.0 or later. Keep the packet, worksheet, completed decision, and all six kit files together in a local directory.

1. Download the six kit files below. Complete a copy of the JSON template offline and preserve its templateFingerprint.
2. Finalize a separate output file.

   node finalize-review-decision.mjs \
     --input DRAFT.json \
     --output COMPLETED.json

   This marks the copy complete and calculates an unkeyed canonical bundle fingerprint. A fingerprint detects changes; it is not a reviewer signature.

3. Validate the packet and completed copy.

   node check-review-decisions.mjs \
     --packet PACKET.json \
     --decision COMPLETED.json

   Add another --decision for each independent reviewer.

4. Interpret the result narrowly. A zero exit proves structural consistency only. Neither command appoints or qualifies a reviewer, establishes independence, accepts a decision, or authorizes publication.

• Bundle finalizer
• Validator command
• Decision policy module
• Fingerprint and packet-integrity module
• Review-domain policy module
• Canonical synthesis and interactive review specs