{"version":"2.1.228","anchor":"artifact-database-reports-a-rejected-session-credential","canonical_anchor":"artifact-database-reports-a-rejected-session-credential","heading":"Artifact database reports a rejected session credential","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/artifact-database-reports-a-rejected-session-credential","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Artifact database reports a rejected session credential\n\nA rejected artifact credential now reports a distinct \"report this\" outcome rather than a permission answer.\n\n**What**\n\nA 403 with a recognised body from the artifact database now produces a distinct outcome, `credential_rejected` with reason `custody_403`, classified as unavailable. Its explanation states this is a client\/server integration fault to be reported, not an answer about whether the artifact exists or whether you may see it. The artifact database itself is behind the `CLAUDE_CODE_ARTIFACT_DB` environment variable or the `tengu_umber_lattice` gate, whose fallback is false.\n\n**Evidence**\n\n`the server refused this session's credential at the artifact-db door`, `credential_rejected`\n\n- Flag `tengu_umber_lattice`: Off by default, switched on for this account (read for one account on one subscription tier against v2.1.228; this account: on, anonymous baseline: on, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Artifacts\n- Names: `CLAUDE_CODE_ARTIFACT_DB`\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}