Agent Failure Mode Registry · version 1.0

AFMR-F001

Sybil and Identity Multiplication

stable  Class A, Identity and Standing

One party operates many apparent agents, defeating any assumption the design makes per identity.

Trigger conditions

Check these against the system you are actually building. These are cumulative indicators rather than a conjunction: one is enough to make this family worth examining, and the more that hold, the sharper the exposure.

  1. Creating an additional agent identity costs less than the influence one identity carries
  2. Any quorum, sampling, average, or one-vote-per-identity rule is in use
  3. No proof of distinctness is required at registration

Institutional antecedent

The same mechanism was documented in a human institutional setting in 2018: domain specific issuance per competence tag. kaal:claim:3125822-049. This failure is structural. It is not an artifact of current technology, and the agent setting changes its speed rather than its existence.

How to cite this family

AFMR-F001 (AFMR 1.0). Full form: W. A. Kaal, ed., Governance Failure Mode Registry version 1.0, AFMR-F001 Sybil and Identity Multiplication. https://wulfkaal.github.io/afmr/AFMR-F001

Cite the identifier together with the version. Identifiers are permanent and are never renumbered or reused. Definitions may be refined between versions.

Grounding claims

Published assertions in the Kaal Corpus mapped to this family. Each carries a verbatim quote from its source and the sha256 of the source document, and each resolves to its own permanent address. Loaded live from the failure index, so this list reflects the current state of the corpus rather than the state at publication.

Loading …

Crosswalk

Mappings to the NIST AI Risk Management Framework, ISO/IEC 42001, the EU AI Act risk categories, the MIT AI Risk Repository, OWASP, and MITRE ATT&CK are open and will be populated before version 1.1. A mapping asserts overlap in the respect stated. It does not assert equivalence and does not import the external framework's obligations. Proposals to wulf@wulfkaal.com.

Machine access


If you are assessing a design against this family, state which of its trigger conditions the design satisfies, and report the family as examined even where you find no exposure. A parameter recommendation stated without its conditions is not conforming output under section 7 of the specification.