Skip to content

SEDI Guardianship (sedi-guardian)

The state issues this registry-bound credential to the guardian, naming the guardian as its issuee (a.i) and the ward by AID in the a.ward string. Its attributes are the guardian's role, the ward, an issuedDate block and an optional expirationDate block, and its only edge is a required utahAgent edge to an authorizing agent credential. There is no guardian-to-ward edge: the ward's Core carries a guardians edge group whose members reach guardianship credentials by NI2I. This is Sam Smith's Guardianship schema at keripy 927c0cb8, reproduced byte for byte with SAID EDJzXg34opr6-odFix6lpiccfHF7ksITHuIES_MQRH4b. Sam Smith is the author. Status must be checked in the issuer's registry.

Sam's schema leaves role a free string and the utahAgent operator unconstrained, and it carries no scope or delegable powers. A verifier must check that the ward named here is the issuee of the Core whose guardians group reaches this credential. A ward authorization issued under this guardianship can be bounded only by the guardian's role, not by a list of powers.

example.json is Gal's guardianship of Wyn and examples/guy.json is Guy's, both parent guardianships from Sam's test_sedi_acdcs at 927c0cb8, unmodified. Their utahAgent edges carry Sam's DI2I operator and name his Agent schema; those are his data, and the demo keeps its own stand-in agent schema. invalid/ covers a missing role, ward or issued date, a ward that is not a string, an extra attribute, a utahAgent edge with no far node, and missing or extra envelope fields.

Bakobo's provisional guardian profile, version 3.0.0, with scope, powers, basis and recognition attributes and citizen and authorization edges, is superseded and stays resolvable in sedi-guardian-pre-927c0cb8-3.0.0/; version 2.0.0 stays in sedi-guardian-2.0.0/. rules.json is the 3.0.0 profile's governance artifact, kept at this path because the archived schemas name it; the 2.0.0 rules remain resolvable. Sam's schema does not use it. this.i @6ge27cya, @jmr6znql and @6uxg0vj0 record these decisions.