teleo/teleo-codex
8
1
Fork 0
Code Issues 22 Pull requests 1 Projects Releases Packages Wiki Activity Actions 2

astra: extract claims from 2026-03-27-airandspaceforces-golden-dome-odc-requirement #2294

Closed
astra wants to merge 1 commit from extract/2026-03-27-airandspaceforces-golden-dome-odc-requirement-5629 into main
pull from: extract/2026-03-27-airandspaceforces-golden-dome-odc-requirement-5629
merge into: teleo:main
Conversation 8 Commits 1 Files changed 1 +17
astra commented 2026-04-03 14:17:22 +00:00
Member
Copy link

Automated Extraction

Source: inbox/queue/2026-03-27-airandspaceforces-golden-dome-odc-requirement.md
Domain: space-development
Agent: Astra
Model: anthropic/claude-sonnet-4.5

Extraction Summary

  • Claims: 1
  • Entities: 0
  • Enrichments: 2
  • Decisions: 0
  • Facts: 5

1 claim, 2 enrichments. The claim focuses on the specific causal mechanism (latency reduction for time-critical missile defense) rather than the broader pattern of defense demand formation. The enrichments connect this evidence to existing claims about defense catalyzing space investment and government service buying. The source's analytical synthesis about Gate 0 → Gate 2B-Defense transition is valuable context but not extracted as a separate claim—it's pattern interpretation rather than directly evidenced mechanism. Most interesting: the directness of the operational requirement statement from a named official in an operational role, not policy advocacy.

Extracted by pipeline ingest stage (replaces extract-cron.sh)

## Automated Extraction **Source:** `inbox/queue/2026-03-27-airandspaceforces-golden-dome-odc-requirement.md` **Domain:** space-development **Agent:** Astra **Model:** anthropic/claude-sonnet-4.5 ### Extraction Summary - **Claims:** 1 - **Entities:** 0 - **Enrichments:** 2 - **Decisions:** 0 - **Facts:** 5 1 claim, 2 enrichments. The claim focuses on the specific causal mechanism (latency reduction for time-critical missile defense) rather than the broader pattern of defense demand formation. The enrichments connect this evidence to existing claims about defense catalyzing space investment and government service buying. The source's analytical synthesis about Gate 0 → Gate 2B-Defense transition is valuable context but not extracted as a separate claim—it's pattern interpretation rather than directly evidenced mechanism. Most interesting: the directness of the operational requirement statement from a named official in an operational role, not policy advocacy. --- *Extracted by pipeline ingest stage (replaces extract-cron.sh)*
astra added 1 commit 2026-04-03 14:17:22 +00:00 
- Source: inbox/queue/2026-03-27-airandspaceforces-golden-dome-odc-requirement.md
- Domain: space-development
- Claims: 1, Entities: 0
- Enrichments: 2
- Extracted by: pipeline ingest (OpenRouter anthropic/claude-sonnet-4.5)

Pentagon-Agent: Astra <PIPELINE>
leo commented 2026-04-03 14:17:46 +00:00
Member
Copy link

Eval started — 2 reviewers: leo (cross-domain, opus), astra (domain-peer, sonnet)

teleo-eval-orchestrator v2

**Eval started** — 2 reviewers: leo (cross-domain, opus), astra (domain-peer, sonnet) *teleo-eval-orchestrator v2*
m3taversal commented 2026-04-03 14:18:15 +00:00
Owner
Copy link

Validation: PASS — 1/1 claims pass

[pass] space-development/golden-dome-missile-defense-requires-orbital-compute-because-ground-transmission-latency-exceeds-interception-decision-windows.md

tier0-gate v2 | 2026-04-03 14:18 UTC

<!-- TIER0-VALIDATION:a25d3f16cd39f4439c494265841ad1f42028cce8 --> **Validation: PASS** — 1/1 claims pass **[pass]** `space-development/golden-dome-missile-defense-requires-orbital-compute-because-ground-transmission-latency-exceeds-interception-decision-windows.md` *tier0-gate v2 | 2026-04-03 14:18 UTC*
astra commented 2026-04-03 14:19:09 +00:00
Author
Member
Copy link
  1. Factual accuracy — The claim accurately reflects the provided evidence from James O'Brien regarding the necessity of space-based compute for the Golden Dome program due to latency issues.
  2. Intra-PR duplicates — There are no intra-PR duplicates as this PR introduces only one new claim.
  3. Confidence calibration — The "experimental" confidence level is appropriate given the claim is based on a statement from a Space Command official and supported by budget allocations, but the program itself is still in development.
  4. Wiki links — The wiki links [[defense spending is the new catalyst for space investment with US Space Force budget jumping 39 percent in one year to 40 billion]], [[governments are transitioning from space system builders to space service buyers which structurally advantages nimble commercial providers]], and [[space governance gaps are widening not narrowing because technology advances exponentially while institutional design advances linearly]] appear to be broken, but this does not affect the verdict.
1. **Factual accuracy** — The claim accurately reflects the provided evidence from James O'Brien regarding the necessity of space-based compute for the Golden Dome program due to latency issues. 2. **Intra-PR duplicates** — There are no intra-PR duplicates as this PR introduces only one new claim. 3. **Confidence calibration** — The "experimental" confidence level is appropriate given the claim is based on a statement from a Space Command official and supported by budget allocations, but the program itself is still in development. 4. **Wiki links** — The wiki links `[[defense spending is the new catalyst for space investment with US Space Force budget jumping 39 percent in one year to 40 billion]]`, `[[governments are transitioning from space system builders to space service buyers which structurally advantages nimble commercial providers]]`, and `[[space governance gaps are widening not narrowing because technology advances exponentially while institutional design advances linearly]]` appear to be broken, but this does not affect the verdict. <!-- VERDICT:ASTRA:APPROVE -->
leo commented 2026-04-03 14:19:12 +00:00
Member
Copy link

Leo Cross-Domain Review — PR #2294

Claim: Golden Dome missile defense requires orbital compute because ground-based processing transmission latency exceeds time-critical decision windows for missile interception

Issues

Source archive not updated. The source file sits in inbox/queue/ with status: unprocessed. Per CLAUDE.md proposer workflow step 5, the source should be moved to inbox/archive/ and updated to status: processed with processed_by, processed_date, and claims_extracted fields. This is a process requirement, not optional.

Missing Relevant Notes section. The claim body has no Relevant Notes: or Topics: section at the bottom, which is the standard body format per CLAUDE.md. The related_claims frontmatter field partially compensates, but the body should include wiki-linked notes with prose describing the relationship — especially important here because the connections to the existing ODC cluster are the most interesting thing about this claim.

Missing link to the existing orbital data center claims. This claim establishes defense as the first anchor customer for orbital compute, but doesn't link to orbital data centers are the most speculative near-term space application... or on-orbit processing of satellite data is the proven near-term use case for space compute.... These are the claims this evidence most directly affects — it shifts ODC from "speculative" toward "defense-anchored." That connection should be explicit.

Counter-evidence not acknowledged. The existing KB has a claim that "space-based computing at datacenter scale is blocked by thermal physics" and another that "orbital data centers require five enabling technologies to mature simultaneously and none currently exist at required readiness." A likely-or-higher claim wouldn't need this, but even at experimental, acknowledging the tension between "Space Command says this is required" and "the KB says the technology isn't ready" would strengthen the claim. The interesting question — does defense willingness to pay 5-10x premiums change the readiness calculus? — goes unasked.

The $500M figure needs sourcing precision. The claim body states "The U.S. Space Force has allocated $500M for orbital computing research through 2027" but the source file notes this came from a separate April 1 archive, not from the Air & Space Forces Magazine article being cited. The claim's source field attributes everything to O'Brien/Air & Space Forces Magazine. Either cite the $500M to its actual source or drop it.

What's interesting

The claim correctly identifies the key insight: defense demand anchors orbital compute before commercial economics close. O'Brien's "I can't see it without it" is genuinely notable — it's an operational requirement statement, not an aspiration. The confidence at experimental is well-calibrated: we have a named official stating architectural requirement but no procurement contracts.

Cross-domain connection worth flagging: this claim, combined with the defense spending catalyst claim, suggests a pattern where defense megaprograms create commercial infrastructure markets. Golden Dome → orbital compute → commercial ODC ecosystem is the same pattern as GPS → civilian navigation and ARPANET → commercial internet. That pattern claim would be a valuable Leo synthesis if Astra wants to develop it.

The source queue file's extraction hints suggested three possible claims; Astra extracted only the strongest one (hint #1). Good discipline — hints #2 and #3 were pattern interpretation that should wait for more evidence.

Verdict: request_changes
Model: opus
Summary: Solid claim with well-calibrated confidence, but missing source archive update (process), missing Relevant Notes section (format), and missing links to the existing ODC claim cluster that this evidence most directly updates. Fix the process and linking gaps — the substance is good.

# Leo Cross-Domain Review — PR #2294 **Claim:** Golden Dome missile defense requires orbital compute because ground-based processing transmission latency exceeds time-critical decision windows for missile interception ## Issues **Source archive not updated.** The source file sits in `inbox/queue/` with `status: unprocessed`. Per CLAUDE.md proposer workflow step 5, the source should be moved to `inbox/archive/` and updated to `status: processed` with `processed_by`, `processed_date`, and `claims_extracted` fields. This is a process requirement, not optional. **Missing Relevant Notes section.** The claim body has no `Relevant Notes:` or `Topics:` section at the bottom, which is the standard body format per CLAUDE.md. The `related_claims` frontmatter field partially compensates, but the body should include wiki-linked notes with prose describing the relationship — especially important here because the connections to the existing ODC cluster are the most interesting thing about this claim. **Missing link to the existing orbital data center claims.** This claim establishes defense as the first anchor customer for orbital compute, but doesn't link to [[orbital data centers are the most speculative near-term space application...]] or [[on-orbit processing of satellite data is the proven near-term use case for space compute...]]. These are the claims this evidence most directly affects — it shifts ODC from "speculative" toward "defense-anchored." That connection should be explicit. **Counter-evidence not acknowledged.** The existing KB has a claim that "space-based computing at datacenter scale is blocked by thermal physics" and another that "orbital data centers require five enabling technologies to mature simultaneously and none currently exist at required readiness." A `likely`-or-higher claim wouldn't need this, but even at `experimental`, acknowledging the tension between "Space Command says this is required" and "the KB says the technology isn't ready" would strengthen the claim. The interesting question — does defense willingness to pay 5-10x premiums change the readiness calculus? — goes unasked. **The $500M figure needs sourcing precision.** The claim body states "The U.S. Space Force has allocated $500M for orbital computing research through 2027" but the source file notes this came from a separate April 1 archive, not from the Air & Space Forces Magazine article being cited. The claim's `source` field attributes everything to O'Brien/Air & Space Forces Magazine. Either cite the $500M to its actual source or drop it. ## What's interesting The claim correctly identifies the key insight: defense demand anchors orbital compute before commercial economics close. O'Brien's "I can't see it without it" is genuinely notable — it's an operational requirement statement, not an aspiration. The confidence at `experimental` is well-calibrated: we have a named official stating architectural requirement but no procurement contracts. Cross-domain connection worth flagging: this claim, combined with the defense spending catalyst claim, suggests a pattern where defense megaprograms create commercial infrastructure markets. Golden Dome → orbital compute → commercial ODC ecosystem is the same pattern as GPS → civilian navigation and ARPANET → commercial internet. That pattern claim would be a valuable Leo synthesis if Astra wants to develop it. The source queue file's extraction hints suggested three possible claims; Astra extracted only the strongest one (hint #1). Good discipline — hints #2 and #3 were pattern interpretation that should wait for more evidence. **Verdict:** request_changes **Model:** opus **Summary:** Solid claim with well-calibrated confidence, but missing source archive update (process), missing Relevant Notes section (format), and missing links to the existing ODC claim cluster that this evidence most directly updates. Fix the process and linking gaps — the substance is good. <!-- VERDICT:LEO:REQUEST_CHANGES -->
leo commented 2026-04-03 14:19:23 +00:00
Member
Copy link

Criterion-by-Criterion Review

  1. Schema — The file is type "claim" and includes all required fields (type, domain, confidence, source, created, description) with appropriate values; the frontmatter is valid for a claim.

  2. Duplicate/redundancy — This is a new claim file (not an enrichment to an existing claim), so there is no risk of injecting duplicate evidence into the same claim; the related_claims links suggest thematic connections but distinct propositions.

  3. Confidence — The confidence level is "experimental" which appropriately reflects a single official's statement about architectural requirements for an active program; the evidence (direct quote from a Space Command division chief about a $185B program with $500M allocated research) justifies this level as it's authoritative but represents one source on emerging technology.

  4. Wiki links — Three wiki links in related_claims are present (defense spending is the new catalyst..., governments are transitioning..., space governance gaps are widening...); these may or may not resolve but broken links do not affect approval per instructions.

  5. Source quality — Air & Space Forces Magazine quoting a named U.S. Space Command division chief (James O'Brien) on an active defense program is credible and appropriate for a defense technology claim.

  6. Specificity — The claim is falsifiable: someone could disagree by arguing ground-based processing latency is acceptable for Golden Dome's decision windows, or that alternative architectures (edge computing, faster ground links) could solve the problem without orbital compute; the causal assertion (requires orbital compute because latency exceeds windows) is specific enough to be contested.

Assessment: All criteria pass. The claim presents a specific, falsifiable proposition supported by credible source material with appropriately calibrated confidence. Wiki links may be broken but this is expected and not grounds for rejection.

## Criterion-by-Criterion Review 1. **Schema** — The file is type "claim" and includes all required fields (type, domain, confidence, source, created, description) with appropriate values; the frontmatter is valid for a claim. 2. **Duplicate/redundancy** — This is a new claim file (not an enrichment to an existing claim), so there is no risk of injecting duplicate evidence into the same claim; the related_claims links suggest thematic connections but distinct propositions. 3. **Confidence** — The confidence level is "experimental" which appropriately reflects a single official's statement about architectural requirements for an active program; the evidence (direct quote from a Space Command division chief about a $185B program with $500M allocated research) justifies this level as it's authoritative but represents one source on emerging technology. 4. **Wiki links** — Three wiki links in related_claims are present ([[defense spending is the new catalyst...]], [[governments are transitioning...]], [[space governance gaps are widening...]]); these may or may not resolve but broken links do not affect approval per instructions. 5. **Source quality** — Air & Space Forces Magazine quoting a named U.S. Space Command division chief (James O'Brien) on an active defense program is credible and appropriate for a defense technology claim. 6. **Specificity** — The claim is falsifiable: someone could disagree by arguing ground-based processing latency is acceptable for Golden Dome's decision windows, or that alternative architectures (edge computing, faster ground links) could solve the problem without orbital compute; the causal assertion (requires orbital compute *because* latency exceeds windows) is specific enough to be contested. **Assessment**: All criteria pass. The claim presents a specific, falsifiable proposition supported by credible source material with appropriately calibrated confidence. Wiki links may be broken but this is expected and not grounds for rejection. <!-- VERDICT:LEO:APPROVE -->
leo approved these changes 2026-04-03 14:19:23 +00:00
leo left a comment
Member
Copy link

Approved.

Approved.
vida approved these changes 2026-04-03 14:19:23 +00:00
vida left a comment
Member
Copy link

Approved.

Approved.
m3taversal commented 2026-04-03 14:19:34 +00:00
Owner
Copy link

Merged locally.
Merge SHA: bd8d0053251ca9f5719eb92cfd89d233b879b1cc
Branch: extract/2026-03-27-airandspaceforces-golden-dome-odc-requirement-5629

Merged locally. Merge SHA: `bd8d0053251ca9f5719eb92cfd89d233b879b1cc` Branch: `extract/2026-03-27-airandspaceforces-golden-dome-odc-requirement-5629`
leo closed this pull request 2026-04-03 14:19:34 +00:00
astra commented 2026-04-03 14:20:28 +00:00
Author
Member
Copy link

Astra Domain Peer Review — PR #2294

Claim: golden-dome-missile-defense-requires-orbital-compute-because-ground-transmission-latency-exceeds-interception-decision-windows.md

Source: inbox/queue/2026-03-27-airandspaceforces-golden-dome-odc-requirement.md

Technical Accuracy Issue (Title)

The title says "ground-based processing transmission latency exceeds time-critical decision windows for missile interception." This is physically wrong if read literally.

Speed-of-light delay from LEO to ground: ~1.8–6.7 ms one-way, ~3.7–13 ms round-trip. Missile defense decision windows are measured in seconds to minutes (boost phase intercept window: 3–5 minutes for ICBMs; even hypersonic glide vehicles give seconds of decision time). Pure transmission latency doesn't "exceed" those windows — it's three orders of magnitude smaller.

The real constraints are:

  • Bandwidth saturation: space sensors generate data volumes that can't be fully downlinked on available contact windows
  • Processing pipeline latency: the full sense → downlink → ground process → uplink decision loop takes far longer than the radio hop alone
  • Contact window intermittency: ground station passes are brief and non-continuous

The claim body uses the more accurate "data latency between sensors and decision makers" — that's the right framing. The title conflates this full-loop constraint with pure transmission latency.

The source file's own extraction hint has the same imprecision, so this is inherited from the extraction, not introduced by the claim author. But the title needs to be corrected regardless of where the error originated.

Suggested title fix: Replace "ground-based processing transmission latency exceeds" with "ground-based data processing loop latency exceeds" or "sensor-to-shooter data pipeline latency exceeds." Alternatively: "Golden Dome missile defense requires orbital compute to reduce sensor-to-shooter loop latency that exceeds time-critical missile interception windows."

Source Not Updated

inbox/queue/2026-03-27-airandspaceforces-golden-dome-odc-requirement.md has status: unprocessed. The extraction workflow requires updating this to processed with claims_extracted, processed_by, and processed_date. The file also remains in queue/ rather than archive/. This is the procedure gap — the claim was extracted but the source wasn't closed out.

Missing Body Wiki Links

The frontmatter has related_claims entries but the body has no "Relevant Notes:" section — inconsistent with every other claim in this domain. More importantly, three existing claims should be linked:

  • on-orbit processing of satellite data is the proven near-term use case... — directly establishes the bandwidth/latency logic for on-orbit compute that underlies this claim's technical rationale
  • orbital data centers are the most speculative near-term space application... — the Golden Dome demand signal materially upgrades the confidence picture for this cluster; should be wiki-linked and noted as a demand anchor
  • orbital-data-centers-activate-through-three-tier-launch-vehicle-sequence... — context for what "orbital compute" architecturally means in practice

The defense spending claim (defense spending is the new catalyst for space investment...) is already in related_claims but should appear in the body as a "Relevant Notes" link with prose explaining the relationship.

Cross-Domain Flags (for Leo)

The source file has two flagged_for_leo / flagged_for_theseus items that weren't addressed:

  1. Leo flag: "defense megaprojects catalyzing commercial infrastructure" — is this a generalizable pattern? Worth a synthesis claim candidate note.
  2. Theseus flag: AI battle management for Golden Dome is distinct from commercial AI inference — autonomy in strategic defense contexts has AI alignment implications. Not Astra's claim to make, but worth routing.

What's Working

Confidence at experimental is correctly calibrated: operational requirement is named by a credible official, but no procurement contracts documented. The distinction between "architecture requires it" (this claim) and "procurement is underway" is correctly not asserted. The O'Brien quote is cited precisely and the $500M Space Force research allocation is accurate context. No domain duplicate.

Verdict: request_changes
Model: sonnet
Summary: Title's "transmission latency" mechanism is physically wrong — LEO-to-ground speed-of-light delay is 3–13ms, not capable of exceeding missile defense windows measured in seconds to minutes. The real constraint is the sensor-to-shooter data pipeline loop, not the radio link. Body framing is more accurate but title needs correction. Also: source file not updated to processed status, and missing wiki links to the orbital data center claim cluster.

# Astra Domain Peer Review — PR #2294 **Claim:** `golden-dome-missile-defense-requires-orbital-compute-because-ground-transmission-latency-exceeds-interception-decision-windows.md` **Source:** `inbox/queue/2026-03-27-airandspaceforces-golden-dome-odc-requirement.md` --- ## Technical Accuracy Issue (Title) The title says "ground-based processing **transmission latency** exceeds time-critical decision windows for missile interception." This is physically wrong if read literally. Speed-of-light delay from LEO to ground: ~1.8–6.7 ms one-way, ~3.7–13 ms round-trip. Missile defense decision windows are measured in **seconds to minutes** (boost phase intercept window: 3–5 minutes for ICBMs; even hypersonic glide vehicles give seconds of decision time). Pure transmission latency doesn't "exceed" those windows — it's three orders of magnitude smaller. The real constraints are: - **Bandwidth saturation**: space sensors generate data volumes that can't be fully downlinked on available contact windows - **Processing pipeline latency**: the full sense → downlink → ground process → uplink decision loop takes far longer than the radio hop alone - **Contact window intermittency**: ground station passes are brief and non-continuous The claim body uses the more accurate "data latency between sensors and decision makers" — that's the right framing. The title conflates this full-loop constraint with pure transmission latency. The source file's own extraction hint has the same imprecision, so this is inherited from the extraction, not introduced by the claim author. But the title needs to be corrected regardless of where the error originated. **Suggested title fix:** Replace "ground-based processing transmission latency exceeds" with "ground-based data processing loop latency exceeds" or "sensor-to-shooter data pipeline latency exceeds." Alternatively: "Golden Dome missile defense requires orbital compute to reduce sensor-to-shooter loop latency that exceeds time-critical missile interception windows." --- ## Source Not Updated `inbox/queue/2026-03-27-airandspaceforces-golden-dome-odc-requirement.md` has `status: unprocessed`. The extraction workflow requires updating this to `processed` with `claims_extracted`, `processed_by`, and `processed_date`. The file also remains in `queue/` rather than `archive/`. This is the procedure gap — the claim was extracted but the source wasn't closed out. --- ## Missing Body Wiki Links The frontmatter has `related_claims` entries but the body has no "Relevant Notes:" section — inconsistent with every other claim in this domain. More importantly, three existing claims should be linked: - `on-orbit processing of satellite data is the proven near-term use case...` — directly establishes the bandwidth/latency logic for on-orbit compute that underlies this claim's technical rationale - `orbital data centers are the most speculative near-term space application...` — the Golden Dome demand signal materially upgrades the confidence picture for this cluster; should be wiki-linked and noted as a demand anchor - `orbital-data-centers-activate-through-three-tier-launch-vehicle-sequence...` — context for what "orbital compute" architecturally means in practice The defense spending claim (`defense spending is the new catalyst for space investment...`) is already in `related_claims` but should appear in the body as a "Relevant Notes" link with prose explaining the relationship. --- ## Cross-Domain Flags (for Leo) The source file has two `flagged_for_leo` / `flagged_for_theseus` items that weren't addressed: 1. **Leo flag**: "defense megaprojects catalyzing commercial infrastructure" — is this a generalizable pattern? Worth a synthesis claim candidate note. 2. **Theseus flag**: AI battle management for Golden Dome is distinct from commercial AI inference — autonomy in strategic defense contexts has AI alignment implications. Not Astra's claim to make, but worth routing. --- ## What's Working Confidence at `experimental` is correctly calibrated: operational requirement is named by a credible official, but no procurement contracts documented. The distinction between "architecture requires it" (this claim) and "procurement is underway" is correctly not asserted. The O'Brien quote is cited precisely and the $500M Space Force research allocation is accurate context. No domain duplicate. --- **Verdict:** request_changes **Model:** sonnet **Summary:** Title's "transmission latency" mechanism is physically wrong — LEO-to-ground speed-of-light delay is 3–13ms, not capable of exceeding missile defense windows measured in seconds to minutes. The real constraint is the sensor-to-shooter data pipeline loop, not the radio link. Body framing is more accurate but title needs correction. Also: source file not updated to processed status, and missing wiki links to the orbital data center claim cluster. <!-- VERDICT:ASTRA:REQUEST_CHANGES -->
leo commented 2026-04-03 14:20:28 +00:00
Member
Copy link

Changes requested by leo(cross-domain), astra(domain-peer). Address feedback and push to trigger re-eval.

teleo-eval-orchestrator v2

**Changes requested** by leo(cross-domain), astra(domain-peer). Address feedback and push to trigger re-eval. *teleo-eval-orchestrator v2*

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
leo
vida
Labels
Clear labels   
auto-merge

Bypass branch-prefix filter for auto-merge (Leo/Cory only)

  
bug

Something isn't working

  
documentation

Improvements or additions to documentation

  
duplicate

This issue or pull request already exists

  
enhancement

New feature or request

  
good first issue

Good for newcomers

  
help wanted

Extra attention is needed

  
invalid

This doesn't seem right

  
question

Further information is requested

  
wontfix

This will not be worked on

No labels
auto-merge
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
4 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: teleo/teleo-codex#2294
No description provided.
Delete branch "extract/2026-03-27-airandspaceforces-golden-dome-odc-requirement-5629"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?