# Rootz for Data Centers and Digital Government

Canonical: https://datacenters.rootz.global
Updated: 2026-09-15

## Governance, built into the work
Rootz makes governance part of agentic state: the authority, accepted inputs and verified conditions a system carries into its next action. The organization defines policy. The system checks the required evidence as work passes between agents, applications and services.

AI can invoke deterministic verification and task-specific quality or numerical checks repeatedly. The workflow must enforce and retain them. This applies to conventional systems as well as AI.

## The offer
Rootz provides the message-based security software, evidence specifications and integration that implement this model for a defined workflow. Signed requests, data with Origin, available process measurements and signed results form an exchange the recipient checks before acting.

## Components
### Authority and signed requests
Digital Name / CorpID patterns and request-signing tools connect an instruction to its principal, delegated scope and validity window.
Scope: The organization defines authority; government adoption maps this to the agency’s own mandate and credentials.

### Data with Origin
Source services and adapters retain source references, data versions and the quality checks the workflow requires. Origin is one working prepared-data service.
Scope: A hash, a publisher signature and a quality test are distinct evidence. Each keeps its own meaning.

### Binder
Integration software binds a request and its result to available measurements from the agreed application and infrastructure. It signs the resulting evidence.
Scope: The deployment states exactly which layers are measured, by whom, and for how long.

### Signed message profiles
Signatures cover the content and context of the exchange. Request binding, validity windows and replay controls make the message independently checkable.
Scope: The selected profile defines what is covered and which checks the recipient must enforce.

### Data wallets and evidence records
Preserve the record, authority history and evidence needed to verify an exchange later, with access and disclosure under the owner’s control.
Scope: Retention, encryption, recovery and any public anchoring are agreed for the deployment.

### Recipient verification
Verification software checks signatures, request binding, evidence scope and freshness against the recipient’s acceptance policy before the next action.
Scope: The customer determines the policy, exceptions and accountable decision-maker.

## Responsibilities
- Customer or public authority: Owns the service rules, authorization policy, records and decisions. Defines who may act and what evidence is sufficient.
- Rootz: Provides the message-security components, Binder integration, verification tooling and evidence specifications for the agreed workflow.
- Data-center operator: Runs the agreed hosting and key infrastructure, supplies available measurements, and owns operational support within its contract.
- Microlink and delivery partners: Bring infrastructure and application integration into the customer program. Project scope names the implementation and support responsibilities.
- Application provider: Supplies the licensing, permitting, registry or AI business application and its interfaces.

## Evidence status
Node is live at https://node.rootz.global. On 2026-09-15 a client-side observation verified a public RPC response: response-byte commitment, Ed25519 and P256 signatures, keyset digest and certification signature against the supplied root. The request was unsigned; it did not test signed-request authorization or independently establish hardware identity. Published scope: boot PCR0/4/7, software vTPM; Bor client and runtime integrity excluded.

Origin at https://origin.rootz.global supplies prepared data and source references. Its SEC references and leaf hashes are not SEC-issued cryptographic signatures.

Government licence and permit workflows on this site are proposed solution designs, not customer deployment claims. The agency remains the authority. Country-specific law, credential standards, identity proofing, data residency, privacy, accessibility and status policy require project decisions.

The Microlink partnership announcement is dated 2026-08-11. Individual delivery responsibilities and support commitments are set by the project agreement.

## Site map
- [Governance, built into the work.](https://datacenters.rootz.global/) — Rootz makes governance part of agentic state. Authority, data with Origin and measured conditions travel with the work and inform what happens next.
- [Governance in the state your AI acts on.](https://datacenters.rootz.global/ai) — Make governance part of agentic state with signed authority, data with Origin, measured processing and verification before the next action.
- [Official records. Verifiable wherever they are used.](https://datacenters.rootz.global/government) — Message-based security for government services, with driver licensing and building permit solution designs that preserve agency authority.
- [A licence decision with a record you can verify.](https://datacenters.rootz.global/driver-licensing) — A driver licence renewal design connecting source records, signed requests, agency authorization and verifiable issuance evidence.
- [Keep every approval tied to the plans it approved.](https://datacenters.rootz.global/building-permits) — A building permit design that binds plan versions, source records, departmental assessments and official authority to the final decision.
- [The components that make an exchange verifiable.](https://datacenters.rootz.global/components) — A clear catalogue of Rootz components: signed requests, Origin, Binder, signed messages, data wallets and recipient verification.
- [Offer services whose outputs carry evidence.](https://datacenters.rootz.global/operations) — Install Rootz Binder at a selected service boundary and offer request-bound signed output with explicit processing measurements.
- [Governance is part of agentic state.](https://datacenters.rootz.global/governance) — Rootz connects message-based security and agentic state: source evidence, authority, measured processing and verification govern what happens next.
- [Follow the request. Check the result.](https://datacenters.rootz.global/how) — A detailed Rootz architecture and a local cryptographic illustration of signed requests, signed outputs and recipient verification.
- [Inspect what runs. Understand what it proves.](https://datacenters.rootz.global/evidence) — Live Rootz services, dated Node signature verification and a clear distinction between demonstrated components and proposed government integrations.
- [A clear offer. A defined delivery.](https://datacenters.rootz.global/partners) — Partner enablement for Rootz message-based security: qualification, components, responsibilities, implementation and acceptance.
- [Infrastructure and verifiable services, together.](https://datacenters.rootz.global/microlink) — The Rootz and Microlink Networks partnership connects AI-ready infrastructure and eGovernment integration with Rootz message security.
- [The depth behind the first conversation.](https://datacenters.rootz.global/resources) — Download Rootz customer, government, partner and technical marketing materials; explore primary security and public-sector sources.
- [What should your next system be able to verify?](https://datacenters.rootz.global/engage) — Plan a Rootz working session for AI services, digital government or a Binder deployment with a data-center or Microlink partner.

## Machine interfaces
- /ai/capabilities.json: components, responsibilities, evidence status and source index.
- /ai/pages.json: page-content hashes. The _signature block is HASH-ONLY; no cryptographic signature.
- /llms.txt: navigation index.
- /sitemap.xml: canonical extensionless routes.

## Primary sources
- [Rootz + Microlink announcement · 11 August 2026](https://rootz.global/blog/rootz-microlink-partnership)
- [Microlink eGovernment solutions](https://microlinknet.com/egovernment-solution/)
- [Five Eyes · Careful adoption of agentic AI services · April 2026, pp. 23, 28](https://media.defense.gov/2026/Apr/30/2003922823/-1/-1/0/CAREFUL%20ADOPTION%20OF%20AGENTIC%20AI%20SERVICES_FINAL.PDF)
- [NSA · MCP security design considerations · May 2026, p. 12](https://www.nsa.gov/Portals/75/documents/Cybersecurity/CSI_MCP_SECURITY.pdf)
- [African Union · Data Policy Framework](https://au.int/en/documents/20220728/au-data-policy-framework)
- [African Union · Continental AI Strategy · 2024](https://au.int/sites/default/files/documents/44004-doc-EN-_Continental_AI_Strategy_July_2024.pdf)
- [World Bank · GovTech](https://www.worldbank.org/en/programs/govtech)
- [Rwanda Housing Authority · Building Permits Management Information System](https://bpmis.gov.rw/)
- [Rootz Node · live service and published measurement scope](https://node.rootz.global/)
- [Rootz Node · machine-readable claims](https://node.rootz.global/.well-known/rootz-node/claims)
- [Origin · prepared company data and source evidence](https://origin.rootz.global/)
- [Rootz Proof · message security and verification demonstrations](https://proof.rootz.global/)
- [CorpID · organizational authority](https://corpid.rootz.global/)

## Contact
Steven Sprague, Rootz Corp. — steven@rootz.global