{
  "schemaVersion": "gships-review-packet-1",
  "packetId": "opportunities:opp-nasa-techleap-robotically-manipulated-payload-2026",
  "stableId": "opp-nasa-techleap-robotically-manipulated-payload-2026",
  "family": "opportunities",
  "slug": "opp-nasa-techleap-robotically-manipulated-payload-2026",
  "title": "NASA TechLeap Robotically Manipulated Payload Challenge",
  "status": "prepared-human-review-not-started",
  "release": {
    "releaseId": "public-alpha-2026-07-26-research-visuals-r14",
    "sourceCommit": "3eb036fce3d711336c8c605625895e8a2e799ab0",
    "corpusGeneratedAt": "2026-07-25",
    "frozenAt": "2026-07-26T22:50:50.000Z",
    "canonicalOrigin": "https://gships.dammonburden.com"
  },
  "paths": {
    "human": "/review/opportunities/opp-nasa-techleap-robotically-manipulated-payload-2026",
    "family": "/review/opportunities",
    "packet": "/review-packets/opportunities/opp-nasa-techleap-robotically-manipulated-payload-2026.c333b44cd0a4a208.json",
    "decisionTemplate": "/review-packets/opportunities/opp-nasa-techleap-robotically-manipulated-payload-2026.c333b44cd0a4a208.decision-template.json",
    "worksheet": "/review-packets/opportunities/opp-nasa-techleap-robotically-manipulated-payload-2026.c333b44cd0a4a208.worksheet.md",
    "byFingerprint": "/review-packets/by-fingerprint/c333b44cd0a4a2088dfda34947104eb374cd3936ebf49fc8f27343518bf69108.json"
  },
  "boundary": "Prepared review packet; human review has not started. This packet is not a completed review, endorsement, reviewer appointment, partnership, or authorization to act.",
  "governingPolicies": [
    {
      "id": "policy-editorial-governance-001",
      "version": "0.1.0",
      "path": "/editorial-policy",
      "recordType": "governing-policy",
      "fingerprint": "1f6a1f823e8bfe891b6a707c5dce2ee2337c0bb7d915b48d6060ca82b8da1b47",
      "snapshot": {
        "id": "policy-editorial-governance-001",
        "version": "0.1.0",
        "status": "foundation-policy-controls-not-yet-staffed",
        "adoptedForFoundation": "2026-07-25",
        "title": "Editorial governance and independent review",
        "publisher": "GShips Project",
        "maintainer": "Dammon Burden",
        "publisherInterest": "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.",
        "currentBoundary": "No independent domain reviewer or review council is currently appointed. Foundation records and outlines may not be represented as independently reviewed.",
        "reviewerSelection": [
          "Publish the reviewer’s name, relevant credentials or lived expertise, review scope, compensation status, and declared conflicts with consent.",
          "Select for the actual claim domain rather than general prestige; include affected-community and disability-led expertise where rights or access are involved.",
          "Do not treat an employee, investor, customer, sponsor, source author, or directly supervised collaborator as independent for the affected claim."
        ],
        "reviewProcess": [
          "Provide the exact claim, sources, locators, assumptions, counterevidence, transfer limits, and proposed evidence dimensions.",
          "Record approve, revise, contest, or reject at claim level; silence and event attendance never count as review.",
          "Publish material minority findings and the editor’s reasoned response.",
          "High-consequence medical, reproductive, nuclear, radiation, cybersecurity, governance, and dual-use claims require two qualified independent reviewers with complementary scopes.",
          "A reviewer may recuse at any time; unresolved conflicts or missing expertise block the reviewed label."
        ],
        "appealAndCorrection": [
          "A correction receives a reference identifier and triage record; safety-critical allegations receive priority.",
          "A material editorial decision may be appealed to a reviewer not involved in the original decision once such a panel exists.",
          "Substantive reversals, unresolved disputes, and removed conclusions receive a dated public record that protects reporter privacy.",
          "No sponsor, customer, founder, or reviewer may purchase, suppress, or unilaterally assign an evidence grade."
        ],
        "publicationGate": "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.",
        "correctionPath": "/corrections"
      }
    },
    {
      "id": "policy-dual-use-001",
      "version": "0.1.0",
      "path": "/dual-use",
      "recordType": "governing-policy",
      "fingerprint": "81637e2849f9c0866d23f7174eb9a2ce522b86313167ebf5022fca122d6e506c",
      "snapshot": {
        "id": "policy-dual-use-001",
        "version": "0.1.0",
        "status": "planned-controls-not-yet-operational",
        "adoptedForFoundation": "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.",
        "scopeTrigger": "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.",
        "allowedInPrinciple": [
          "Safety engineering and independently assessed protection",
          "Resilience, graceful degradation, recovery, and disaster response",
          "Civil logistics, maintenance, communications, and knowledge continuity",
          "Cyber defense, secure software, incident response, and recovery",
          "Rights-preserving health, accessibility, ecology, education, and governance research"
        ],
        "prohibited": [
          "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",
          "Weapons command-and-control or targeting support",
          "Offensive access, persistence, exploitation, or destructive cyber payloads",
          "Mass surveillance, biometric repression, or political-control systems",
          "Autonomous force application",
          "Coercive reproductive, medical, genetic, disability, or civic control",
          "Nonconsensual experimentation or treating residents as research instruments"
        ],
        "reviewRequiredBeforeAnyRelevantWork": [
          "Customer, funder, collaborator, jurisdiction, beneficial-owner, and end-use screening",
          "Export-control and sanctions review by qualified counsel when applicable",
          "Written scope, allowed-use, prohibited-use, audit, termination, and incident clauses",
          "Independent stop-work authority with a named alternate and founder recusal",
          "Sensitive-publication and information-hazard review",
          "Whistleblowing, escalation, incident response, appeal, and anti-retaliation paths",
          "Aggregate transparency reporting that protects legitimate privacy and security"
        ],
        "currentBoundary": "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.",
        "changeControl": "Material changes require a dated public rationale, independent review, and may not be approved by the founder alone.",
        "correctionPath": "/corrections"
      }
    }
  ],
  "reviewContract": {
    "questions": [
      {
        "id": "question-1",
        "text": "Does the official source support the opportunity identity, status, timing, eligibility, and access constraints?",
        "required": true
      },
      {
        "id": "question-2",
        "text": "Is the proposed fit specific and proportionate without implying availability, invitation, selection, or funding?",
        "required": true
      },
      {
        "id": "question-3",
        "text": "What deadline, rule, jurisdiction, cost, conflict, or accessibility fact would change the proposed next action?",
        "required": true
      }
    ],
    "exclusions": [
      "Review does not submit, register, apply, contact, commit, purchase, or establish eligibility.",
      "Provider prestige and apparent fit cannot replace current official terms."
    ],
    "requestedScopeCodes": [
      "ecosystem-due-diligence",
      "opportunity-eligibility-access"
    ],
    "dispositions": [
      "approve",
      "revise",
      "contest",
      "reject",
      "recuse"
    ],
    "prohibitedInputs": [
      "private legal names or contact details",
      "identity documents or raw credential files",
      "accessibility or medical records",
      "confidential conflict evidence",
      "classified, export-controlled, proprietary, or exploit material"
    ],
    "freshness": {
      "maximumDecisionAgeFromFreezeDays": 30,
      "eventOccurrenceRule": "Not applicable to this packet family."
    },
    "completionRule": "Every primary record must receive the required number of valid, current-fingerprint approvals; every complementary scope group and required domain must be covered; any unresolved revise, contest, or reject disposition blocks publication.",
    "highConsequenceRule": "Named medical, reproductive, nuclear, radiation, cybersecurity, governance, and dual-use conclusions require two distinct qualified independent humans covering complementary domain-method and rights/public-interest scopes."
  },
  "primaryRecords": [
    {
      "recordType": "opportunity",
      "recordId": "opp-nasa-techleap-robotically-manipulated-payload-2026",
      "title": "NASA TechLeap Robotically Manipulated Payload Challenge",
      "publicPath": "/opportunities/opp-nasa-techleap-robotically-manipulated-payload-2026",
      "recordFingerprint": "5d0e583fe4e9c41715b3a4a4e25a9ba3e0add9ce684e7371d4aac6819fff5748",
      "reviewRequirements": {
        "minimumIndependentApprovals": 1,
        "highConsequenceDomains": [],
        "requiredDomainCodes": [],
        "requiredComplementaryScopeGroups": [
          {
            "id": "bounded-competence",
            "scopeClass": "bounded-competence",
            "oneOf": [
              "ecosystem-due-diligence",
              "opportunity-eligibility-access"
            ]
          }
        ],
        "unresolvedNegativeFindingBlocksPublication": true,
        "currentUntil": "2026-08-02"
      },
      "referenceIds": [],
      "snapshot": {
        "id": "opp-nasa-techleap-robotically-manipulated-payload-2026",
        "name": "NASA TechLeap Robotically Manipulated Payload Challenge",
        "url": "https://www.nasa.gov/stmd-flight-opportunities/access-flight-tests/nasa-techleap-prize-information/",
        "provider": "NASA Flight Opportunities",
        "kind": "Prize challenge and orbital flight demonstration",
        "timing": "Active challenge: registration is due July 29, 2026 and applications are due August 12, 2026. NASA says winner selection is planned for September 2026, with development toward an expected late-2027 host launch and early-2028 payload launch.",
        "fit": "Modular payloads, robotic manipulation, inspection, assembly, sensor deployment, processing, upgrade, and serviceability",
        "status": "active; registration deadline imminent",
        "verifiedAt": "2026-07-26",
        "currentUntil": "2026-08-02",
        "eligibility": "NASA describes TechLeap as open to qualified commercial businesses, academic institutions, entrepreneurs, and other innovators. Exact challenge rules control applicant and team eligibility, registration, technical requirements, intellectual property, export, safety, submission, award, and flight obligations.",
        "accessNotes": "The challenge requests payloads that can interact with, be manipulated by, or be reconfigured by a robotic arm in low Earth orbit for applications such as inspection, assembly, sensor deployment, material processing, or modular upgrade. NASA states that up to three winners may receive up to $500,000 each to develop flight-ready payloads and an orbital demonstration opportunity at no additional cost. It is not a concept-only generation-ship grant, and development, integration, flight, launch schedule, award, and public relationship are not guaranteed.",
        "founderAction": "Read the public challenge page, rules, and recorded webinars and write a no-registration fit memo. Default to no-go unless a genuinely robotic-orbital payload, ground evidence, capable team, schedule, matching funds and operations, safety and integration plan, intellectual-property and export review, civil-and-defensive clearance, and separate registration and application authorization already exist; do not register merely to preserve an option.",
        "evidenceBoundary": "NASA's official TechLeap page supports the challenge status, July 29 and August 12 dates, robotic-arm payload scope, example applications, broad applicant classes, up-to-three-winner and up-to-$500,000 statements, development purpose, no-additional-cost demonstration opportunity, recorded webinars, and planning dates. It does not establish exact rule compliance, eligibility, award, adequate funding, flight readiness, provider performance, launch, safety, export status, schedule, or relationship.",
        "relationship": "indexed only; no formal relationship",
        "actionStatus": "proposed; not undertaken",
        "conflicts": "Deadline pressure, prize visibility, NASA name proximity, award funding, payload and provider interests, launch risk, intellectual property, export, safety, and possible dual use require independent review.",
        "whatWouldChange": "A challenge rule or date amendment, a completed relevant payload and ground test, a qualified team and budget, independent flight-safety and civil-and-defensive review, or an organizer decision would change this assessment."
      }
    }
  ],
  "linkedRecords": [
    {
      "recordType": "opportunity-task-match",
      "recordId": "opportunity-match-maintenance-techleap-2026",
      "title": "autonomous-maintenance-circular-industry · opp-nasa-techleap-robotically-manipulated-payload-2026",
      "publicPath": "/partners",
      "recordFingerprint": "b2dff96a86c63885dcd3bfcd2932b0429796fcf8fe9b2edfbd444214efb7acdd"
    }
  ],
  "referenceSnapshots": [
    {
      "sourceId": "official-opportunity-opp-nasa-techleap-robotically-manipulated-payload-2026",
      "sourceRecordType": "reference-source",
      "sourceFingerprint": "cba29a7e4f8a649fb994ac473375b08f95ca7f534ab9598b42222293cfb99511",
      "snapshot": {
        "title": "NASA TechLeap Robotically Manipulated Payload Challenge",
        "url": "https://www.nasa.gov/stmd-flight-opportunities/access-flight-tests/nasa-techleap-prize-information/",
        "checkedAt": "2026-07-26",
        "scopeNote": "NASA's official TechLeap page supports the challenge status, July 29 and August 12 dates, robotic-arm payload scope, example applications, broad applicant classes, up-to-three-winner and up-to-$500,000 statements, development purpose, no-additional-cost demonstration opportunity, recorded webinars, and planning dates. It does not establish exact rule compliance, eligibility, award, adequate funding, flight readiness, provider performance, launch, safety, export status, schedule, or relationship.",
        "subjectRecordType": "opportunity",
        "subjectRecordId": "opp-nasa-techleap-robotically-manipulated-payload-2026"
      }
    }
  ],
  "packetFingerprint": "c333b44cd0a4a2088dfda34947104eb374cd3936ebf49fc8f27343518bf69108"
}
