Skip to content
FedTrustFederated TrustDocs

Enter at least two characters.

Type to search all documentation pages and sections. Use ↑ ↓ to move, Enter to open, and Esc to close.

Platform statuses are part of the claim

Platform documentation

Start with the role you hold.

Federated Trust supports people and organizations working through applications, partners, and agents across company boundaries. These pages explain the authority, custody, and data-plane boundaries each audience should expect.

Audience-ledStatuses are part of the claim

Audience-led guidance

Choose the question you need answered.

PeopleFor peopleWhat people should expect from identity, recovery, privacy, and delegated application or agent access in Federated Trust.BusinessesFor organizationsHow Federated Trust separates tenant policy, data-plane control, custody, support access, and portability for businesses.BuildersApps and licensingThe Federated Trust application model for publishers, partners, customers, internal software, external software, consent, and revocation.BusinessesVault and custodyThe planned Federated Trust Vault model: encrypted payloads, customer custody, organization recovery, BYOK/HYOK profiles, agents, and crypto agility.Security teamsAuthorizationHow Federated Trust cloud authentication and ReBAC authorization interoperate with per-app authorization, capability delegation, and offline or edge enforcement.Security teamsSecurity and standardsThe Federated Trust public security posture, with implemented, limited, designed, planned, independently validated, and governing-reference claims kept distinct.BuildersFor developersHow developers integrate the two-layer trust model through first-class UI, CLI, MCP, packages, skills, workload identity, and local authorization.

Read the status with the claim

Six labels prevent false equivalence.

Maturity labels describe the public engineering posture; governing-reference labels identify design inputs. These labels are not a certification, agency authorization, FIPS-validated cryptographic-module claim, or guarantee that every deployment has the same controls. Assurance and responsibilities are established for a named service, integration, evidence date, and risk context.

Implemented

Implemented in a Federated Trust service path with current evidence. The named deployment and evidence scope still matter.

Limited / pilot

Code or contracts exist, but integration, operational, or assurance gates still prevent general availability.

Designed

An approved target shape or contract that is not represented as generally available. A validated deployment package is still required.

Planned

A stated engineering target that is not represented as implemented, generally available, or deployed today.

Independently validated

Implemented and assessed independently for a named scope and evidence date. This label does not extend beyond that evidence.

Governing reference

Authoritative material used to guide design and review. This status is not a certification or a universal conformance claim.