Methodology changes. Announced, dated, signed.
Every change to how we score is versioned, dated and published before it takes effect. Material changes carry at least 30 days' notice; safety fixes are immediate and disclosed within 24 hours. This log is machine-readable and signed with the same key that signs every score, and every revision links to its own outcome-validated series — a change here is not a promise, it is measured.
📜 The notice pledge four classes of change · four notice periods
| Class | Notice | What it means |
|---|---|---|
| Material | ≥ 30 days | Changes an input, weight, threshold, cap, band boundary or gating rule so that a subject's published band can move. Announced at least 30 days before it takes effect. The expected impact is measured, not guessed: a sample is re-scored under both revisions before the effective date. |
| Policy | ≥ 14 days | Changes what we publish, for whom, or when (publication and gating rules) rather than the scoring maths itself. Announced at least 14 days ahead. |
| Minor | ≥ 7 days | Presentation, coverage or the wording of reasons. No band can move. Announced at least 7 days ahead. |
| Safety | immediate | A fix that stops a flagged, killed or blacklisted actor from being under-rated, or closes a live abuse path. Takes effect immediately and is disclosed here within 24 hours. Safety never waits for a notice period. |
How we measure impact. Before a material change takes effect we re-score a sample under both revisions. If at least 25% of scored subjects would move a band we say most current scores expected to move; any smaller non-zero share is some. Questions or comments on a planned change: connect@trustifer.com. Trustifer is not a regulated credit rating agency. We mirror the disclosure elements of SEC Rule 17g-8 and EU CRA Regulation Article 8 voluntarily: what changed, why, the expected effect on current scores, the version that produced each score, and advance notice.
🔢 Current revisions the version behind every score you see today
| Methodology | Revision | In effect since | Validation |
|---|---|---|---|
| Trustifer Score | rev 1 | 2026-08-27 | no validation series yet for this revision |
| Trust Score | rev 3 | 2026-08-06 | no validation series yet for this revision |
| Agent Credit Score | rev 1 | 2026-08-27 | no validation series yet for this revision |
| Meta-Bureau consensus | rev 1 | 2026-08-27 | no validation series yet for this revision |
| Competence | rev 1 | 2026-08-27 | no validation series yet for this revision |
| Reliability | rev 1 | 2026-08-27 | no validation series yet for this revision |
| Control & Oversight | rev 1 | 2026-08-27 | no validation series yet for this revision |
| Reputation | rev 1 | 2026-08-27 | no validation series yet for this revision |
| Credible commitments | rev 1 | 2026-08-27 | no validation series yet for this revision |
| Insurability | rev 1 | 2026-08-27 | no validation series yet for this revision |
Every signed score from /api/v1/score carries methodology.rev — the revision that produced it — and a link back to this page.
📅 Planned changes announced, not yet in effect
There are no planned changes at the moment. When one is announced it appears here first, with its class, its effective date and the expected impact — before anything moves.
🗂 Change log newest first · append-only · every entry approved and referenced
2026-08-27 Policy The methodology version registry: every score snapshot now carries its revisionEach scoring methodology has a numbered revision in code, stamped onto every recorded score so that validation never mixes revisions. This is the baseline (revision 1) for every methodology except the Trust Score, which was already at revision 3.
Why: A score produced under one revision and one produced under another are different instruments. Validation cohorts must be segmented by revision to mean anything.
Applies to: All methodologies · rev 1 · Impact: no current score expected to move
Announced: 2026-08-27 (recorded retroactively — this entry documents history and does not claim advance notice was given) · Approved by: founder · Reference: src/lib/explorer/methodologyRev.ts · Docs/RESEARCH_STEP6_OUTCOME_LEDGER_2026-08-27.md
2026-08-11 Policy Evidence floor: below the floor we publish Unrated, not a numberWhen too little evidence backs a subject, the unified score publishes a signed Unrated envelope instead of a number. Fabricated-looking grades for evidence-less subjects are no longer possible.
Why: A junk address and a domain with no DNS were receiving confident-looking grades. A number with nothing behind it is worse than no number.
Applies to: Trustifer Score · pre-versioning (no revision number) · Impact: some current scores may move
Announced: 2026-08-11 (recorded retroactively — this entry documents history and does not claim advance notice was given) · Approved by: founder · Reference: docs/DESIGN_SCORING_HONESTY_EVIDENCE_FLOOR.md
2026-08-11 Material ERC-8004 registry feedback quarantined from certified reputationPermissionless, self-solicitable feedback from the ERC-8004 registry no longer carries weight in the certified reputation blend and cannot satisfy the competence validations factor. The rows stay visible for transparency.
Why: Registry feedback can be bought or self-generated; it must not move a certified score. Pre-versioning: this change predates the version registry, so it carries no revision number.
Applies to: Reputation, Competence · pre-versioning (no revision number) · Impact: some current scores may move
Announced: 2026-08-11 (recorded retroactively — this entry documents history and does not claim advance notice was given) · Approved by: founder · Reference: docs/DESIGN_SCORING_HONESTY_EVIDENCE_FLOOR.md (S5)
2026-08-11 Policy Agents-only mode: a plain wallet receives a safety answer, not an agent gradePlain wallets are out of scoring scope. They receive the safety screen (sanctions, threat intelligence) and an honest wallet caveat instead of an agent grade.
Why: An agent grade on a human wallet is a category error. Safety information is still owed to the reader.
Applies to: All methodologies · pre-versioning (no revision number) · Impact: some current scores may move
Announced: 2026-08-11 (recorded retroactively — this entry documents history and does not claim advance notice was given) · Approved by: founder · Reference: docs/DESIGN_SCORING_HONESTY_EVIDENCE_FLOOR.md
2026-08-06 Material Trust Score revision 3: the breadth gate and the neutral floorA passing security assessment may help a score or do nothing — it can never hurt it. A narrow certification no longer counts as broad coverage; the union of what was actually assessed is what counts.
Why: Revision 2 could score an agent with a passing audit lower than one never audited; that is a trust-breaking defect. Narrow certificates were being read as broad credit.
Applies to: Trust Score · rev 3 · Impact: some current scores may move
Announced: 2026-08-06 (recorded retroactively — this entry documents history and does not claim advance notice was given) · Approved by: founder · Reference: docs/TRUST_SCORE_ASSURANCE.md (REVISION 3)
2026-08-05 Material Trust Score revision 2: the contract-security input is activatedThe Trust Score began to use verified contract-security evidence (audits and attestations from allowlisted attestors) as an input. Absence of evidence is neutral; only verified evidence counts.
Why: Security evidence was collected but did not yet reach the score. Re-certified under the assurance protocol before activation.
Applies to: Trust Score · rev 2 · Impact: some current scores may move
Announced: 2026-08-05 (recorded retroactively — this entry documents history and does not claim advance notice was given) · Approved by: founder · Reference: docs/TRUST_SCORE_ASSURANCE.md (REVISION 2)
2026-07-30 Policy Scoring-scope gate applied to every scoring routeThe scope rule was found to hold on only a few routes; it was moved into one shared gate that every scoring route now passes through, verified in both positions of its switch.
Why: A rule that holds on two routes and not on the others is not a rule. One shared gate cannot drift route by route.
Applies to: All methodologies · pre-versioning (no revision number) · Impact: some current scores may move
Announced: 2026-07-30 (recorded retroactively — this entry documents history and does not claim advance notice was given) · Approved by: founder · Reference: docs/GATE_REGISTER.md (B2.2)
2026-07-23 Policy Scoring-scope gate: no grades for tokens or contractsSubjects outside our scope — token contracts, and contracts with no registered agent behind them — stopped receiving agent grades. They receive an honest out-of-scope answer instead.
Why: An agent grade for something that is not an agent misleads the reader. The rule had to hold on every scoring surface, not only the main one.
Applies to: All methodologies · pre-versioning (no revision number) · Impact: some current scores may move
Announced: 2026-07-23 (recorded retroactively — this entry documents history and does not claim advance notice was given) · Approved by: founder · Reference: docs/DESIGN_L1_SCORING_SCOPE.md
About this history. Dated change history begins 2026-07-23. Numbered revisions begin 2026-08-05 (Trust Score). Every recorded score carries its revision from 2026-08-27, when the version registry was created. Changes before a methodology was numbered are listed as pre-versioning entries and carry no revision number. Nothing in this log has been back-dated: entries marked retroactive record history and do not claim advance notice was given.
🔏 Verify this log don't trust us — check
The JSON feed carries a canonical digest of this log and an Ed25519 signature over it by did:web:trustifer.com#key-1 (issuer did:web:trustifer.com). Re-hash the canonical material (sorted keys, no whitespace, exactly as described in the feed's digestOf field), compare it with the digest below, and verify the signature against the public key in our DID document. If either check fails, the log you are reading is not ours.
Digest now: bdbe20bc2465ee11bf5d061f6f73deab4bf80bd6c9101254960719a8b5f55a3a
This page is rendered at most once every five minutes; the signed feed is generated on every request. If the two differ briefly after a change, the feed is authoritative.