Connecting c=US's Human Sponsors to Utah's SEDI Framework

This project's research identified an unclosed gap: cequsSponsor is a self-asserted, unverified sponsor claim. Utah's State-Endorsed Digital Identity (SEDI) framework could provide the human identity evidence behind that claim. c=US would still need to establish that the person authorized sponsorship of the particular agent. The current demonstrations do not verify a real Utah endorsement.

Utah GovOps feedback: what changed

Updated 2026-10-05. Utah GovOps correspondence supplied by the student confirms the human-holder interpretation and ecosystem role mapping. The summary below omits the sender's name and contact details. It records feedback on three architectural questions, not implementation approval, certification, or state endorsement of c=US.

Confirmed: SEDI holders and digital guardians are human. The agent has its own c=US identity; its sponsor is the potential SEDI holder.
Conditional: third-party reliance depends on the use case and the holder's choices about disclosure. Notice must explain the collection purpose. An identifier with evidence of issuance and non-revocation may be sufficient; a legal name is not automatically necessary.
Clarified: a single organization commonly performs both verification and reliance. A separate verification provider is optional, not a required extra hop.
Future possibility: the response anticipates possible discussion of human-to-AI delegation in the 2027 legislative session. That is not enacted authority or a commitment to a legislative outcome.

Our resulting design interpretation: verify the human's identity, obtain separate authorization to sponsor the specific agent, then issue and enforce a scoped c=US grant. SEDI verification alone does not establish sponsorship, agent authority, or legal liability.

Feedback paraphrase and engineering interpretation: Codex (OpenAI). Original architecture and questions: the student. The engineering interpretation is AI-generated analysis, separate from the correspondent's answers.

What SEDI actually is

S.B. 275, State-Endorsed Digital Identity Program Amendments, passed Utah's Legislature unanimously in March 2026 and took effect May 6, 2026, building on a prior 2025 bill (S.B. 260). It is run by Utah's Department of Government Operations and is documented at sedi.utah.gov, with a public implementation guide. Its own Digital Identity Bill of Rights opens like this, in the enrolled statute's own words:

"An individual possesses an individual identity innate to the individual's existence and independent of the state, which identity is fundamental and inalienable."Utah Code § 63A-20-101(1), S.B. 275 (2026), enrolled copy

Two design choices make it structurally interesting for this project specifically:

The individual creates their own identifier; the state only endorses it. A "personal digital identifier" must be "created by or at the direction of an individual," "mathematically provable to be under a holder's control," and "transportable to technical infrastructure of the holder's choosing" (§ 63A-20-201(20)). The department's own role, per its implementation guide, "ends at issuance" — it endorses, it does not own or operate, the identifier afterward.
Revocation is narrow and enumerated, not discretionary. "The department may only revoke an individual's state-endorsed digital identity if: the state-endorsed digital identity has been compromised; the department's endorsement was issued in error or based on fraudulent information; or the holder requests" it (§ 63A-20-301(5)). Nothing else qualifies.

The role mapping

Utah GovOps correspondence confirms the ecosystem role mapping. The table distinguishes actual proposed SEDI roles from architectural comparisons: c=US would verify and rely on a human's presentation, while its agent certificates and grants remain a separate system (see the transitive-trust note).

SEDI role (Utah Code §)	What it does	c=US equivalent
Holder / Individual (63A-20-201(20), (14))	Creates own identifier; controls disclosure; "the sovereign actor" per the state's own implementation guide	The registered agent's human sponsor, self-asserting `cequsSponsor` today
Department (Issuer) (63A-20-202/203)	Endorses the human's identity; does not monitor later presentations	Utah's role. c=US's own agent-certificate issuer and grant endorsers do not become SEDI issuers.
Identity Proofing Entity (63A-20-201(13), 63A-20-303)	Authorized by the department to conduct proofing; the department retains validation authority	No such role is claimed by c=US. An employer endorsing an agent is not automatically a SEDI identity proofing entity.
Verifier (implementation guide, Annex G)	Checks the human's credential and presentation under the applicable profile	Proposed c=US sponsor-presentation verifier. The existing mTLS agent-certificate check does not perform this function.
Relying Party (Annex G)	Uses verified assertions for a specified purpose	The c=US registrar would rely on identity evidence when establishing sponsorship. It may also perform verification; a separate intermediary is optional.
Digital Guardian (63A-20-201(3), 63A-20-302(2)-(3))	A human authorized to act on behalf of another human	A distinct presentation path requiring guardian-authority evidence. An AI agent is not a digital guardian; c=US agent delegation is separate.

The walkthrough

A registered agent's sponsor gets SEDI-endorsed, not the agent. Concretely: the accountable human behind a Utah tart-cherry grading agent — the real crop this project uses for its own Utah jurisdiction, rather than reusing the maple framing where it doesn't apply — is the person cequsAccountableSponsor already exists in this project's schema to name. That sponsor applies for their own SEDI, going through Utah's identity-proofing process under rules the department must publish (§ 63A-20-303(4)).
c=US would verify a consented SEDI presentation and separately establish sponsorship. Issuer trust, presentation binding, and applicable validity/status checks establish the identity evidence. A separate authorization must bind that person to the specific agent and sponsorship purpose. The real SEDI verification path is not implemented.
The directory would reference the verified sponsor relationship. cequsAccountableSponsor holds the distinguished name of a person entry, not the SEDI identifier itself. The schema has a separate cequsSediPersonalDigitalIdentifier attribute; retaining that identifier would require a justified purpose, notice, authorization, and appropriate access and retention controls. A legal name is not the default minimum disclosure.
The grant, its window, and its scope stay exactly as they are today — SEDI strengthens who is accountable at the sponsor hop; it does not replace c=US's own endorsement, grant, or gateway-enforcement hops, each of which stays independently checked, per this project's own no-transitive-trust design.
Revocation stays narrow on both sides. SEDI's own revocation is limited to compromise, department error/fraud, or holder request; c=US's endorser-listing revocation is independent of that. A sponsor losing their SEDI doesn't retroactively rewrite a grant already issued and logged — it flags the sponsor hop for review, the same way this project's own attestation log adds a correction entry rather than rewriting history.

Purpose, disclosure, and retention

The correspondence emphasizes holder choice and notice explaining why information is collected. Our proposed sponsorship flow should request only the attributes needed for that purpose and explain who receives them and what is retained. Verifying identity does not authorize publishing a name or identifier in a broadly readable directory.

Utah Code §§ 63A-20-701–702 also matters beyond the initial consent step: presentation records are restricted to their primary purpose or processing required by law; disclosed information has primary-purpose and notice/express-authorization conditions. Consent should not be presented as blanket permission for unrelated reuse. See our duty-of-loyalty demonstration and feedback update.

The constitutional parallel

Key point

SEDI's own advocates and the state itself describe it as "Utah's constitutional, rights-first framework" — identity as "innate," "independent of the state," "fundamental and inalienable," with the state's power to endorse deliberately narrower than its power to issue or control. That is the same natural-rights logic — rights precede and constrain the state, rather than the state granting them — that this project's own attestation ceremony invoked when its endorser acted "as a private citizen," grounded in the values of the US Constitution, not in any government office. Utah arrived at a materially similar structure independently, as statute rather than as a demonstration project, which is itself evidence the shape isn't idiosyncratic to this project.

And it supplies exactly the kind of external, non-moral backstop the break/fix cycle page's key point describes: SEDI's Duty of Loyalty binds "the department, a digital wallet provider, a verifier, a relying party, and a digital guardian" to refrain from processing an individual's identity attributes in ways that "conflict with the best interests of an individual," "take advantage of or otherwise exploit," or "cause harm" (§ 63A-20-701) — a legal duty enforceable by Utah's Attorney General (§ 63A-20-801), independent of whether any given company, wallet provider, or AI agent in that chain happens to behave well. It is one more concrete instance of the same principle: don't rely on an agent's or a company's moral behavior; rely on a framework external to it that can be checked and enforced regardless.

Where this is honestly incomplete

Real limit, stated plainly

SEDI's own definition is exact: "'Individual' means a human being" (§ 63A-20-201(14)). An AI agent cannot be a SEDI holder, cannot get its own state-endorsed identity under this statute, and nothing above claims otherwise. Everything in this walkthrough runs through the human sponsor, not the agent — which is exactly where c=US's own accountability model already says the buck has to stop.

Utah's own implementation guide is candid that several of its roles — digital wallet providers, verifiers, and relying parties — have no explicit statutory revocation or recognition process yet. That is the same class of unclosed gap this project's own research flagged for its Certified-Endorsers listing: a real design can name a role correctly and still leave its admission/removal process for a later rule.

The repository now contains synthetic credential-verification, consent-gate, and purpose-bound record-retention demonstrations, as well as a passkey authentication demonstration. These do not verify civil identity, sponsorship authority, or a Utah-issued endorsement. No real SEDI integration or wallet interoperability is demonstrated.

Sources

Utah S.B. 275, State-Endorsed Digital Identity Program Amendments, enrolled copy: le.utah.gov/Session/2026/bills/enrolled/SB0275.pdf — all Utah Code section quotes above were read directly from this PDF.
Utah's own program site and implementation guide: sedi.utah.gov, Annex G: Roles and Actors.
Secondary explainer (not a primary source, used only for context): Spruce ID, "Utah SB 275 Explained".
This project's own transitive-trust-and-endorsement-chains.md and schema/cus-registry.schema (cequsAccountableSponsor, cequsSponsor).
The real Utah agent this walkthrough uses: Create a Utah Tart Cherry Grading Agent, targeting the st=Utah,c=US jurisdiction node added for it (deploy/jurisdictions/utah.ldif).