Skip to content

sadpig70/orbiroam

Repository files navigation

OrbiRoam

OrbiRoam infographic

Orbital Tasking-to-Action Roaming Registry — bind orbital sensor tasking to an accountable jurisdiction, a human-review SLA, and a cross-jurisdiction roaming agreement, with a hash-chained authorization ledger.

LEO sensing increasingly triggers terrestrial autonomous action (agronomic intervention, defensive response, infrastructure control) at machine timescales, but no accountable primitive governs that tasking. OrbiRoam redraws the orbit/ground boundary (lens L24) so tasking authority and action liability are jointly registered and roamable: a ground system may act only on registered tasking, cross-jurisdiction action needs a roaming agreement (telecom-style), and action over the jurisdiction's latency SLA needs a human in the loop.

Indicative governance decision and evidence trail — not a command authority over real satellites or actuators.

Install

pip install -e .          # or: PYTHONPATH=src python -m orbiroam ...

Stdlib only (dependencies = []), Python ≥ 3.10.

Quick start

# 1) write a sample mixed-sensor tasking batch
orbiroam sample -o examples/tasking_sample.json

# 2) evaluate it -> JSON report (authorized/review/blocked rollups + ledger head)
orbiroam run -i examples/tasking_sample.json

# 3) full report + markdown governance view
orbiroam run -i examples/tasking_sample.json --full -o examples/tasking_report.json
orbiroam run -i examples/tasking_sample.json --markdown -o examples/governance_report.md

# 4) verify the authorization ledger has not been tampered with
orbiroam verify-ledger -i examples/tasking_report.json

How the registry decides

For one canonical tasking that triggers terrestrial autonomous action:

Condition Decision
tasking authority not registered BLOCKED — no accountable jurisdiction/SLA
action jurisdiction not registered BLOCKED
cross-jurisdiction with no roaming agreement BLOCKED
latency > jurisdiction autonomous-action SLA REVIEW_REQUIRED — human in the loop
registered + roamed (or same jurisdiction) + within SLA AUTHORIZED
tasking does not trigger autonomous action AUTHORIZED (informational)

Reference policies (orbiroam.models): jurisdiction SLAs e.g. US 60 s, EU 30 s, JP_KR 45 s, intl_waters 10 s, commercial 120 s; registered roaming agreements include US↔EU, US↔commercial, EU↔commercial, JP_KR↔commercial, US↔JP_KR.

Design

L24 BoundaryRedraw applied to insight INS-L6-004 (unowned orbital tasking governance). Pipeline: heterogeneous tasking events → adapters (canonical tasking) → roaming registry (AUTHORIZED/REVIEW_REQUIRED/BLOCKED) → hash-chained ledger → audit/markdown report. Deterministic given input timestamps. See .pgf/DESIGN-OrbiRoam.md.

Tests

PYTHONPATH=src python -m pytest -q

Covers same-jurisdiction allow, roamed allow, SLA review, no-roaming block, unregistered block, adapter normalization, determinism, and ledger tamper detection.

License

MIT © 2025-2026 sadpig70

About

Orbital Tasking-to-Action Roaming Registry: govern when orbit-sensed tasking may drive terrestrial autonomous action, via jurisdiction + SLA + roaming, with a hash-chained ledger.

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors

Languages