Module field 

Credential field definitions — what a field name means to this host.

There is no registry of well-known field names, and that is deliberate. ACT-CONSTANTS.md §8 registers field types (std:string, std:oauth2) and the members of an OAuth value, because those are mechanical: the type decides how a value is encoded and how it is acquired, and both ends must agree. A field’s name is not mechanical. Whoever stores the credential names it, in their own namespace, and the component that reads it is the same party that asked for it — by declaring the field, or by printing the exact act secret set --field … command a user copies.

An earlier model registered std:username, std:password and std:token as shared vocabulary. Two components spelling the same upstream credential identically is a convention benefit, not a mechanical one, and it cost more than it bought: because a component may not declare a std: name (§4.3 rule 1), the components using the most standard credential shape were the ones that could not declare their fields at all, and so lost the zero-argument act login the declaration exists to provide.

What remains here is the operator’s own vocabulary: *.toml files naming a field’s label, type and whether it is material. Everything else resolves to a secret std:string labelled by its own name.

Structs

FieldDef

What one field name means.

FieldRegistry

What this host knows about field names: whatever the operator defined, and nothing else. Default is an empty one, which is the common case.