ASCEND Conference

Packet identity

Packet ID

events:series-ascend

Packet SHA-256 identity

3248cdeb1f6157271a8b9fd0d850def82993f8c095e440174185b685851c877d

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)
   Do the official sources support the series identity and every current occurrence, date, deadline, access rule, and eligibility statement?
2. Required question 2 (exact ID: question-2)
   Are location, remote access, accommodations, cost, travel, visa, and participation uncertainty represented without invention?
3. Required question 3 (exact ID: question-3)
   Does the founder action remain proposed and separately authorized rather than implied as registration or attendance?

Explicit exclusions

• A listed event is not endorsed, sponsored, attended, booked, or affiliated with GShips.
• A current occurrence can expire; historical packet approval cannot establish a future event date.

Requested controlled scopes: accessibility-disability-justice, event-access-freshness

Frozen-evidence decision window: 14 days from the packet freeze. A current-occurrence approval must be decided no later than the frozen occurrence end date; a later review requires a refreshed record and packet.

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. event-series · series-ascend

   ASCEND Conference

   Record fingerprint

   79d65b47bac8e9c0b1b9fe458837d9df552858c668918cb40912f9bd71dd825f

   Minimum approvals

   1

   Required scope groups

   bounded-competence: event-access-freshness

   High-consequence domains

   None under the named two-person rule

   Review state

   pending

   Published human decisions

   0

   Inspect the complete frozen review surface

   ID

   series-ascend

   Slug

   ascend

   Name

   ASCEND Conference

   Occurrence IDs

   1. event-ascend-2027

   Organizer Organization IDs

   None recorded

   Relationship

   indexed only; no formal relationship

2. event-occurrence · event-ascend-2027

   ASCEND 2027

   Record fingerprint

   fb06b1f5709bbe7ba1556f5eae218cfa6995620fa802c658412886641cce39ac

   Minimum approvals

   1

   Required scope groups

   bounded-competence: accessibility-disability-justice, event-access-freshness

   High-consequence domains

   None under the named two-person rule

   Review state

   pending

   Published human decisions

   0

   Inspect the complete frozen review surface

   ID

   event-ascend-2027

   Slug

   ascend-2027

   Name

   ASCEND 2027

   URL

   https://www.ascend.events/↗ (opens external site in a new tab)

   Start Date

   2027-05-18

   End Date

   2027-05-20

   Location

   Washington, D.C., United States

   Focus

   Space systems, infrastructure, human spaceflight, policy, cross-cutting technology, and technical exchange

   Founder Action

   Evaluate a technical-paper abstract or session proposal only after a completed artifact, authorship and publication review, in-person presentation plan, and civil-and-defensive dual-use screen exist; do not submit or register without separate authorization.

   Deadline

   2026-10-08

   Deadline Label

   Technical-paper abstract and session-proposal deadline

   Access Notes

   The official homepage confirms May 18–20, 2027 in Washington, D.C., and an open call for technical-paper abstracts and session proposals due October 8, 2026. The organizer FAQ says technical-paper presentations are in person, registration is expected in late January 2027, early-bird rates end April 19, and refund requests close May 1. Final program, rates, accessibility, capacity, recording, publication, and submission terms require review.

   Eligibility

   The public call invites innovators, researchers, and thought leaders across the space enterprise; the submission guide and organizer terms control authorship, acceptance, paper, presentation, and registration requirements. No submission, registration, presentation, sponsorship, award, or AIAA relationship has been undertaken.

   Action Status

   proposed; not undertaken

   Status

   active call; civil-and-defensive review required

   Verified At

   2026-07-26

   Conflicts

   Publisher intends to explore a commercial venture based on some GShips work; no event registration, submission, sponsorship, attendance commitment, or organizer relationship exists. The program includes national-security material, so every proposed contribution and session plan requires the project's civil-and-defensive screen.

   Evidence Boundary

   The official ASCEND homepage and FAQ support the 2027 dates, Washington location, open call, October 8 deadline, in-person technical presentations, planned registration timing, early-bird date, and refund cutoff. They do not establish acceptance, publication suitability, program quality, GShips fit, accessibility, capacity, cost, recording terms, travel feasibility, or civil-and-defensive compatibility of every session.

   What Would Change

   A call amendment, submission-guide revision, acceptance decision, registration opening, program publication, access or accessibility update, or change to dates, venue, publication, recording, or refund terms would change this profile.

Linked records—not review targets here

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

• commons-standards-workforce · event-ascend-2027 event-task-match:event-match-commons-ascend-2027 · e261d3c37209b7bb4f97b82be5dfa52a5770554bc7f3ddd5ce874d4e7147585f

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