Packet identity

Packet ID
organizations:entity-nist-nccoe
Packet SHA-256 identity
3962a4dd88c8d8fadd7376be3afb110717fe3c529f9b6d29450f495f3f4d778d
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
2
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-nist-nccoe

    NIST NCCoE

    Record fingerprint
    52725a8f6cf64cd43eb01f07ed00804d3915f68bfe54580900bb287662d024eb
    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-nist-nccoe
    Legacy ID
    org-agency-s-027
    Slug
    nist-nccoe
    Name
    NIST NCCoE
    Category
    Agency, standards, and public research infrastructure
    Geography
    Maryland, United States
    Relevance
    enabling
    Engagement
    Proposed, not undertaken: use current public guides and monitor calls for comment, communities of interest, or collaborator notices; participate only through a published eligible route with separate authorization and civil-defensive scope.
    Capability
    Applied cybersecurity testbeds, public use-case development, industry collaboration, reference architectures, NIST Cybersecurity Practice Guides, and mappings to standards and frameworks.
    Entity Kind
    United States federal applied cybersecurity center within NIST
    Link Checked At
    2026-07-25
    Relationship
    indexed only; no formal relationship
    Engagement Status
    proposed; not undertaken
    Profile Summary
    The National Cybersecurity Center of Excellence is a NIST center that works with industry, government, and academia to build standards-based reference implementations and publish practical cybersecurity guidance for defined use cases.
    Potential Fit
    NCCoE methods and practice guides could inform zero trust, software supply-chain security, data protection, cryptographic migration, identity, and reproducible reference architectures for an autonomous habitat. They do not certify a particular implementation.
    Risks
    1. Reference designs are examples using particular technologies and do not guarantee security in another architecture.
    2. Formal collaborator roles may require a Federal Register notice, CRADA, contributed technology, and project-specific selection.
    3. Cyber threats, dependencies, cryptography, and guidance change quickly.
    4. Cybersecurity work is dual use and must remain civil and defensive.
    Evidence Boundary
    Official NCCoE pages establish NIST's collaborative testbed and publication process; they do not certify GShips, endorse vendors, promise a project slot, or validate operation under disconnected spacecraft conditions.
    Conflicts
    1. GShips could seek collaborator status or use NCCoE-aligned language to support its own assurance claims.
    What Would Change
    An applicable published project, accepted public input, selected formal collaboration, or independently reproduced reference build under representative offline conditions would change fit.
  2. ecosystem-relationship · relationship-nist-nccoe-provides-collaboration

    entity-nist-nccoe provides opp-nccoe

    Record fingerprint
    d79f4a838acffff2d45763bf82e17f06593af29c526e24caf9d1d21c41acefa5
    Minimum approvals
    1
    Required scope groups
    bounded-competence: affected-public-rights, 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
    relationship-nist-nccoe-provides-collaboration
    Subject Type
    organization
    Subject ID
    entity-nist-nccoe
    Predicate
    provides
    Object Type
    opportunity
    Object ID
    opp-nccoe
    Relationship State
    indexed only; no formal relationship
    Evidence Boundary
    The reviewed records identify a public collaboration route; no project acceptance, endorsement, access, or GShips relationship is implied.
Equivalent record table for this packet
RecordSubjectFingerprintApprovalsScope groups
ecosystem-organization:entity-nist-nccoe NIST NCCoE 52725a8f6cf64cd43eb01f07ed00804d3915f68bfe54580900bb287662d024eb 1 bounded-competence: ecosystem-due-diligence
ecosystem-relationship:relationship-nist-nccoe-provides-collaboration entity-nist-nccoe provides opp-nccoe d79f4a838acffff2d45763bf82e17f06593af29c526e24caf9d1d21c41acefa5 1 bounded-competence: affected-public-rights, ecosystem-due-diligence

Linked records—not review targets here

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

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.

Sources, verification dates, scope notes, and exact fingerprints
Source IDSourceCheckedScope boundaryFingerprint
official-ecosystem-organization-entity-nist-nccoe NIST NCCoE (opens external site in a new tab) 2026-07-25 Official NCCoE pages establish NIST's collaborative testbed and publication process; they do not certify GShips, endorse vendors, promise a project slot, or validate operation under disconnected spacecraft conditions. c9ee33e476e092d8d6d54176f7f0e7b7b71b5ed9b66897e7f95b03eeb7debf38

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.

Frozen packet · JSON

15.4 KB · packet identity 3962a4dd88c8d8fa…

Download packet

Blank decision worksheet · JSON

3.6 KB · template identity e30a823e61c51f68…

Download blank JSON

Review-notes worksheet · Markdown

Readable notes companion only—not a decision-bundle equivalent. Use the closed JSON template for structural validation.

Download notes worksheet

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.

Completion criteria

Every primary record must receive the required number of valid, current-fingerprint approvals; every complementary scope group and required domain must be covered; any unresolved revise, contest, or reject disposition blocks publication.

Named medical, reproductive, nuclear, radiation, cybersecurity, governance, and dual-use conclusions require two distinct qualified independent humans covering complementary domain-method and rights/public-interest scopes.

  • Reviewer identity, qualification, independence, conflicts, and compensation must be assessed by accountable human governance; local validation can only report structural validity.
  • Approve, revise, contest, reject, and recuse remain visible. A negative finding cannot be hidden by an aggregate approval percentage.
  • Revision creates a new record and packet fingerprint. Prior approvals do not carry forward automatically.
  • AI may assist with clerical comparison but cannot count as an independent reviewer, identity attestor, appeal authority, or second person.

Prepared review packet · 0 published human decisions · Independent review pending · Suggest a correction

Accountability record

How to inspect this page

Scope: Prepared review packet organizations:entity-nist-nccoe · 3962a4dd88c8d8fadd7376be3afb110717fe3c529f9b6d29450f495f3f4d778d

Page citations and accountability links

  • Exact frozen packet
    Complete packet payload; SHA-256 3962a4dd88c8d8fadd7376be3afb110717fe3c529f9b6d29450f495f3f4d778d · fingerprint-bound review artifact
  • Blank closed decision template
    Offline structured-decision starting point · unsubmitted local artifact
  • Review-notes worksheet
    Human-readable notes companion; not validator input · offline notes aid
  • Review corpus index
    Corpus SHA-256 8fa944604ca189f5a9216ca59f640ad2ca20972ad512f2f4970764716782e18d · release and ownership index

Assumptions and limits

  • The exact packet, record, source, policy, release, and source-commit fingerprints bound this prepared page; human review has not started.
  • Downloading, local structural validation, or completing notes does not appoint or qualify a reviewer, establish independence, accept a decision, authorize publication, or create a relationship.

What would change this page?

Staffed governance, appointed qualified reviewers, completed record-level decisions, published conflicts, minority findings, corrections, or changed review policy would change this page.

People, review, and conflicts

Prepared by
GShips Project
Editorial status
public-alpha accountability pass
Editorial reviewer
GShips Project AI-assisted editorial synthesis
Last editorial review
2026-07-26
Independent review
pending
Independent reviewer
No independent reviewer assigned
Last independent review
No independent-review date exists
Last content edit
2026-07-25

Declared conflicts

  • The maintainer intends to explore a commercial venture based on some GShips work. No entity, outside funding, customer, sponsor, or indexed-organization relationship currently exists.

Suggest a correction to this page