Editorial governance and appeals

Packet identity

Packet ID

governance:editorial-governance

Packet SHA-256 identity

a74ffccfd14bfec554a0330c8bf57a63f319db3dc7a0c55e7528a3293b701c7b

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 · editorial-governance

   Editorial governance and independent review

   Record fingerprint

   ca45c6fde5591e6f3897e7c20927609a776d50ca3b6ba0c5cdedc132417baa0a

   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-editorial-governance-001

   Version

   0.1.0

   Status

   Foundation policy controls not yet staffed (exact value: foundation-policy-controls-not-yet-staffed)

   Adopted For Foundation

   2026-07-25

   Title

   Editorial governance and independent review

   Publisher

   GShips Project

   Maintainer

   Dammon Burden

   Publisher Interest

   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.

   Current Boundary

   No independent domain reviewer or review council is currently appointed. Foundation records and outlines may not be represented as independently reviewed.

   Reviewer Selection

   1. Publish the reviewer’s name, relevant credentials or lived expertise, review scope, compensation status, and declared conflicts with consent.
   2. Select for the actual claim domain rather than general prestige; include affected-community and disability-led expertise where rights or access are involved.
   3. Do not treat an employee, investor, customer, sponsor, source author, or directly supervised collaborator as independent for the affected claim.

   Review Process

   1. Provide the exact claim, sources, locators, assumptions, counterevidence, transfer limits, and proposed evidence dimensions.
   2. Record approve, revise, contest, or reject at claim level; silence and event attendance never count as review.
   3. Publish material minority findings and the editor’s reasoned response.
   4. High-consequence medical, reproductive, nuclear, radiation, cybersecurity, governance, and dual-use claims require two qualified independent reviewers with complementary scopes.
   5. A reviewer may recuse at any time; unresolved conflicts or missing expertise block the reviewed label.

   Appeal And Correction

   1. A correction receives a reference identifier and triage record; safety-critical allegations receive priority.
   2. A material editorial decision may be appealed to a reviewer not involved in the original decision once such a panel exists.
   3. Substantive reversals, unresolved disputes, and removed conclusions receive a dated public record that protects reporter privacy.
   4. No sponsor, customer, founder, or reviewer may purchase, suppress, or unilaterally assign an evidence grade.

   Publication Gate

   Public 1.0 requires named review coverage across every Academy track, documented high-consequence two-person review, a material-corrections log, reviewer conflict records, and an operating appeal path.

   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