Protect people
Civilian, medical, school, cultural, surrender, and declared protected status can stop an otherwise valid command.
Local interlock demonstrator
The last word before motion.
Bounder sits beside the actuator. It checks signed authority, current policy, and local conditions before a requested state change can proceed. A failed rule becomes a hold, with a receipt explaining why.
Scenario laboratory
Test the interlock.
Change one condition at a time. Watch the same request move from permitted to held as the local evidence changes.
Guided operator demonstration
Verify the signed baseline
Start with a permitted recovery state and inspect the signed decision receipt.
Inspect: The issuer, subject, sequence, evidence age, and policy hash.
Report a reproducible finding
Creed Space Fleet
One signed protective rule, locally enforced by every Guardian.
Loading software pilot evidence
- Fleet
- Loading
- Guardians
- Loading
- Policy
- Loading
- Evidence
- Loading
100-Guardian pilot evidence · Resilience evidence · Resilience schema · Signed envelope · Policy schema · Checkpoint schema
Creed Space contract round trip
Verify signed Fleet authority before it reaches motion.
Load the published cross-language vector or inspect your own compatible JSON. Bounder verifies the exact Ed25519-signed payload bytes, validates the device policy, and links the policy profile to a recorded Go interlock receipt. Nothing uploaded leaves this browser.
Ready
Choose the published vector or a local compatible file.
- EnvelopeAwaiting signed bytes
- SignatureAwaiting Ed25519 verification
- PolicyAwaiting schema checks
- ReceiptAwaiting matching Go evidence
- Issuer
- Not loaded
- Subject
- Not loaded
- Fleet
- Not loaded
- Sequence
- Not loaded
- Key
- Not loaded
- Policy ID
- Not loaded
- Payload digest
- Not loaded
- Recorded receipt
- Not loaded
The browser verifies the published contract and displays recorded evidence. It does not issue authority or generate a deployment receipt. Signed vector · Signed receipt · Receipt schema · Integration guide
Fleet resilience laboratory
Introduce a failure. Watch every boundary fail safe.
Download evidence
The local laboratory streams verified Fleet events. The public demonstrator replays the same deterministic evidence when no laboratory endpoint is present.
Selected fault
Choose a scenario
The fault description will appear here.
- Device
- None
- Expected
- None
- Safe response
- None
- Proof
- None
Rollback-proof checkpoint
Verified
- Local
- Current floor
- Fleet
- Matching signed floor
- Lease
- 05:00 signed
- Authority
- ACTIVE
Ready
Bounder monitoring
evaluating
The 3D scene could not start. The decision panel remains available.
Why Bounder
A narrow component with a serious job.
Bounder does not plan missions or choose goals. It sits between decision software and physical actuation, checking whether a requested change is authorized, current, and within policy.
Prevent friendly harm
Authenticated friendly positions and minimum separation rules reduce blue-on-blue risk at the final point of control.
Enforce ordinary limits
Altitude, time, weather, communications, battery, identity, geography, and policy freshness are first-class constraints.
Demonstrator, not deployment assurance.
The displayed decisions come from deterministic Go interlock receipts and a signed Fleet contract published with their JSON schemas. Bounder is a simulation-only reference, not certified safety software or an engagement system.