nScrypt

Packet identity

Packet ID

organizations:entity-nscrypt

Packet SHA-256 identity

db2a7207b6f338fd52ce238db80f82d0ac1be2b337aff35c2849103dcf2e027d

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-nscrypt

   nScrypt

   Record fingerprint

   91a2594e4af9bd9705028e6f8b4371fd6e2815e9d6a16ac8c5fbc174f8bb6f0d

   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-nscrypt

   Legacy ID

   org-company--034

   Slug

   nscrypt

   Name

   nScrypt

   URL

   https://www.nscrypt.com/↗ (opens external site in a new tab)

   Category

   Company and applied technology

   Geography

   Florida, United States

   Relevance

   enabling

   Engagement

   Proposed, not undertaken: define a representative repair and electronics test coupon set, materials inventory, metrology, operator burden, and acceptance criteria; pursue a paid demonstration only after procurement authorization.

   Capability

   Microdispensing, printed electronics, material extrusion, micro-milling, pick-and-place, photonic processing, computer vision, and integrated digital manufacturing equipment.

   Entity Kind

   privately held commercial advanced manufacturing company

   Link Checked At

   2026-07-25

   Relationship

   indexed only; no formal relationship

   Engagement Status

   proposed; not undertaken

   Profile Summary

   nScrypt is a commercial manufacturing-equipment company specializing in high-precision microdispensing, direct digital manufacturing, printed electronics, and multi-tool Factory in a Tool systems combining deposition, milling, pick-and-place, inspection, and related processes.

   Potential Fit

   A Factory in a Tool platform could support bounded experiments in local electronics production, conformal repair, tool switching, recipe control, inspection, and spares reduction. It does not establish closed-loop feedstocks or fabrication of all safety-critical components.

   Risks

   1. Manufacturer specifications and demonstrations require independent application-specific verification.
   2. Feedstocks, curing, calibration, contamination control, replacement tools, software, and consumables remain external dependencies.
   3. Commercial price, data rights, support lifetime, export status, and customization availability are unknown.
   4. Printed or repaired electronics may not meet radiation, vacuum, thermal-cycle, or safety-critical qualification.

   Evidence Boundary

   The official site establishes equipment and stated process capabilities; it does not independently validate spacecraft-qualified products, indefinite autonomous operation, feedstock closure, or commercial availability to GShips.

   Conflicts

   1. GShips could become an equipment customer or publicize a demonstration that supports its autonomous-manufacturing product thesis.

   What Would Change

   Representative qualified parts, transparent yield and maintenance data, independent testing, radiation and vacuum evidence, and an authorized commercial response would change readiness.

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