Civil and defensive dual-use boundary

Packet identity

Packet ID

governance:dual-use

Packet SHA-256 identity

53c7cc6662dfb929f29287eef8d64c9c90d5bf4b36cb2b0df124d7ebcb69e52f

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

0

Questions and exclusions

Required questions

1. Required question 1 (exact ID: question-1)
   Are authority, recusal, appeal, correction, conflict, stop-work, anti-retaliation, and public-accountability rules legitimate and operationally testable?
2. Required question 2 (exact ID: question-2)
   Do civil-and-defensive controls exclude offensive, coercive, weapon, surveillance, and autonomous-force uses without relying on intent labels?
3. Required question 3 (exact ID: question-3)
   Which prerequisites remain unstaffed or untested, and what evidence is required before activation?

Explicit exclusions

• A prepared policy is not an operating institution, legal opinion, appointment, screening decision, or activated authority.
• Founder preference, funding, urgency, or prestige cannot compensate for a failed rights, safety, security, or legitimacy gate.

Requested controlled scopes: affected-public-rights, dual-use-risk, editorial-governance

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. governance-control · dual-use

   Civil, defensive, and rights-preserving use boundary

   Record fingerprint

   114198e83a2803d975bbae46e110ca7dd644b9f93ff7669867dbff2474df9c30

   Minimum approvals

   2

   Required scope groups

   domain-method: dual-use-risk, editorial-governance, governance-law-rights; rights-public-interest: affected-public-rights

   High-consequence domains

   governance, dual-use

   Review state

   pending

   Published human decisions

   0

   Inspect the complete frozen review surface

   ID

   policy-dual-use-001

   Version

   0.1.0

   Status

   Planned controls not yet operational (exact value: planned-controls-not-yet-operational)

   Adopted For Foundation

   2026-07-25

   Title

   Civil, defensive, and rights-preserving use boundary

   Summary

   GShips may research safety, resilience, logistics, communications, recovery, and cyber defense only within explicit end-use, rights, and independent-review controls. Calling an activity defensive is never sufficient by itself.

   Scope Trigger

   Apply dual-use review before accepting or materially advancing customer, funder, collaborator, operational, procurement, or publication-sensitive work whose capability, data, end use, or transfer could reasonably enable a prohibited use. Public non-actionable education still follows prohibited-content and sensitive-publication controls.

   Allowed In Principle

   1. Safety engineering and independently assessed protection
   2. Resilience, graceful degradation, recovery, and disaster response
   3. Civil logistics, maintenance, communications, and knowledge continuity
   4. Cyber defense, secure software, incident response, and recovery
   5. Rights-preserving health, accessibility, ecology, education, and governance research

   Prohibited

   1. Identification, tracking, prioritization, or engagement of people or assets for force, weapons, repression, or offensive operations; safety navigation, astronomy, collision avoidance, search and rescue, and independently governed planetary defense are not prohibited by this clause
   2. Weapons command-and-control or targeting support
   3. Offensive access, persistence, exploitation, or destructive cyber payloads
   4. Mass surveillance, biometric repression, or political-control systems
   5. Autonomous force application
   6. Coercive reproductive, medical, genetic, disability, or civic control
   7. Nonconsensual experimentation or treating residents as research instruments

   Review Required Before Any Relevant Work

   1. Customer, funder, collaborator, jurisdiction, beneficial-owner, and end-use screening
   2. Export-control and sanctions review by qualified counsel when applicable
   3. Written scope, allowed-use, prohibited-use, audit, termination, and incident clauses
   4. Independent stop-work authority with a named alternate and founder recusal
   5. Sensitive-publication and information-hazard review
   6. Whistleblowing, escalation, incident response, appeal, and anti-retaliation paths
   7. Aggregate transparency reporting that protects legitimate privacy and security

   Current Boundary

   No screening body, independent stop-work authority, contractual controls, or appeal body currently exists. Therefore no relevant customer, defense, dual-use, or operational engagement is authorized by this policy.

   Change Control

   Material changes require a dated public rationale, independent review, and may not be approved by the founder alone.

   Correction Path

   /corrections

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