AIAA SciTech

Packet identity

Packet ID

events:series-aiaa-scitech

Packet SHA-256 identity

ff17310779eb05d20a00a58304cda863a52040793e4cdf698bf64761a9593e0f

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-aiaa-scitech

   AIAA SciTech

   Record fingerprint

   c9d9da2771d2386298ed7a8dfd5bb453f961498d81df1ecfd025763358082705

   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-aiaa-scitech

   Slug

   aiaa-scitech

   Name

   AIAA SciTech

   Occurrence IDs

   1. event-aiaa-scitech-2027

   Organizer Organization IDs

   None recorded

   Relationship

   indexed only; no formal relationship

2. event-occurrence · event-aiaa-scitech-2027

   AIAA SciTech 2027

   Record fingerprint

   e8659353f4444eba4798ef9760d137261c6f6082a6fdd59ae718ee0df0cdbd37

   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-aiaa-scitech-2027

   Slug

   aiaa-scitech-2027

   Name

   AIAA SciTech 2027

   URL

   https://scitech.aiaa.org/↗ (opens external site in a new tab)

   Start Date

   2027-01-11

   End Date

   2027-01-15

   Location

   Orlando, United States

   Focus

   Aerospace R&D, structures, propulsion, autonomy, power, and systems

   Founder Action

   Evaluate attendance for systems, autonomy, cyber, power, and committee learning; do not present this as an open paper opportunity because the abstract deadline has passed.

   Access Notes

   AIAA confirms January 11–15, 2027 and exposes a registration path. The May 21 abstract deadline has passed; accepted authors are notified August 24 and manuscripts are due December 1. Registration cost, Orlando venue details, accessibility, capacity, and the still-evolving program require review.

   Eligibility

   Attendance follows AIAA registration terms. The December manuscript deadline applies only to authors whose abstracts were accepted through the closed process. No registration, submission, presentation, committee role, or AIAA relationship has been undertaken.

   Action Status

   proposed; not undertaken

   Status

   monitor

   Verified At

   2026-07-25

   Deadline

   2026-12-01

   Deadline Label

   Accepted-author manuscript deadline

   Conflicts

   Publisher intends to explore a commercial venture based on some GShips work; no event registration, submission, sponsorship, attendance commitment, or organizer relationship exists.

   Evidence Boundary

   The official forum pages support the dates, registration signal, closed abstract deadline, notification date, and accepted-author manuscript deadline; they do not establish final program quality, GShips fit, accessibility, capacity, cost, venue logistics, or acceptance.

   What Would Change

   An AIAA update to dates, venue, registration, program, author milestones, access, or accessibility information would change this profile.

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