Server-rendered directory
Transparent task/pathway relationships, current events, monitored opportunities, and indexed organizations; no qualification or eligibility assessment.
Authorization boundary: Choosing a task or viewing a match does not assess qualifications, establish eligibility, register anyone, contact an organization, authorize a GShips action, or create a relationship. GShips has not applied, registered, contacted, partnered, sponsored, or committed unless a record explicitly says otherwise.
Selected bounded task
Can a safety-critical habitat restore trusted software, procedures, keys, and configuration without cloud access or offensive capability?
Threat-model and rehearse a strictly civil, defensive recovery path for disconnected infrastructure with deterministic safety boundaries.
These are mapped work pathways, not a “best fit,” personality type, credential, or leadership-fitness result.
Leadership pathway · not a qualification assessment
Preserve trustworthy software, procedures, archives, keys, and recovery while excluding offensive use and life-critical AI authority.
First artifact: A bounded threat model and rehearsed recovery record.
Decision boundary: Independent cyber stop-work; no offensive scope and no generative model with direct authority.
| Event | Tier | Dates | Why this appears | Artifact | Verified |
|---|---|---|---|---|---|
| NIST Software and Supply Chain Assurance Forum | monitor | 2026-09-22–2026-09-23 | Relevant to SBOMs, provenance, reproducible builds, and long-life supply-chain assurance. | A public defensive recovery requirements crosswalk; no implication of NIST approval. | 2026-07-26 |
| Opportunity | Tier | Status | Why this appears | Eligibility boundary | Verified |
|---|---|---|---|---|---|
| NIST NCCoE collaboration | monitor | active; project-specific | Project-specific public collaboration may fit a civil recovery use case; acceptance and independence are not implied. | Formal collaborators must offer products, technologies, or engineering expertise that meet a project's published technical requirements, submit a letter of interest, and sign a CRADA if selected. NIST evaluates technically acceptable letters on a first-come, first-served basis. | 2026-07-25 |
| Organization | Tier | Why this appears | Bounded next action | Relationship |
|---|---|---|---|---|
| NIST NCCoE | monitor | The public profile and collaboration opportunity support defensive reference-architecture relevance; no collaboration, endorsement, or project acceptance is implied. | Map the synthetic recovery scenario against published NCCoE and NIST guidance before considering a public community-of-interest route. | indexed only; no formal relationship |
| Space Information Sharing and Analysis Center | monitor | The reviewed profile supports civil-space cybersecurity and information-sharing relevance, but membership, classification, independence, and exact civil scope require verification. | Use only public materials to clarify membership, classification, and civil-and-defensive participation boundaries. | indexed only; no formal relationship |
Accountability record
Scope: Starting points for Disconnected cyber recovery server-rendered directory results
Changed public records, indexing rules, query parsing, or review state would change these results.