Skip to content

Add ENTITY v3.4.0 Robotics domain guide #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
blackmore-technology-group merged 1 commit into from
Sep 25, 2026
Merged

Add ENTITY v3.4.0 Robotics domain guide #1

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
40 changes: 40 additions & 0 deletions docs/V3_4_0_DOMAIN_GUIDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,40 @@
# Robotics — ENTITY v3.4.0 Domain Guide

This repository is an executable **domain package for the one ENTITY Global Passport**. It does not create a separate passport protocol or sovereignty silo.

- [ENTITY v3.4.0 core release](https://github.com/blackmore-technology-group/ENTITY/releases/tag/v3.4.0)
- [v3.4.0 documentation portal](https://github.com/blackmore-technology-group/ENTITY/blob/main/docs/v3.4/README.md)
- [All six domain packages](https://github.com/blackmore-technology-group/ENTITY/blob/main/docs/v3.4/DOMAIN_PACKAGES.md)

## Standards mappings

ROS 2 · Open-RMF

Mappings describe correspondence only. External standards remain externally authoritative and no normative equivalence is claimed.

## Deploy

1. Clone and verify ENTITY core.
2. Clone this repository.
3. Run `python tools/verify_package.py`.
4. Replace all `CONFIGURE-ME` values in `deployment.example.json` with organization-specific facts.
5. Connect governed systems/data through the provided mappings.
6. Ingest and derive the Global Passport.
7. Verify the passport and package conformance before deployment.

Required deployment facts:

- `organization`
- `jurisdiction`
- `authority_source`
- `safety_policy`

## Package integrity

Sealed package SHA-256: `3a0e68fa6c63b2ef9cf79ccf463335af72d49ffb3cd028c88b6a998d8678f38f`

The existing sealed README/package files are intentionally unchanged. This guide is additive documentation outside the sealed package manifest.

## Claim boundary

Package verification does not establish objective external truth, legal title, regulatory compliance, independent security review, market adoption or accounting fair value. Provider custody does not create ENTITY authority.
Loading