{
  "schema": "hangingcontext.desk/1",
  "type": "story",
  "id": "1921",
  "slug": "proving-who-did-the-work",
  "edition": "2026-11-22T00",
  "url": "https://hangingcontext.com/stories/2026-11-22/proving-who-did-the-work/",
  "newsroom": "artificial-intelligence",
  "beat": "policy",
  "newsroom_title": "Artificial Intelligence",
  "angle": "As agents do the work, proving who did it — and who they are — becomes the product",
  "headline": "When agents do the work, proving who did it becomes the product",
  "dek": "A professional network built on vouching, a hiring check that flags one in twelve applications, and step-up checks that fire only when risk rises: three answers to the same question.",
  "published_at": "2026-11-22T00:50:30Z",
  "labels": {
    "trust": "confirmed",
    "trust_text": "Confirmed · 3 Manifests",
    "newsroom": "Artificial Intelligence"
  },
  "source_count": 3,
  "publishers": [
    "andreessen-horowitz-a16z-show-podcast",
    "findem-blog",
    "sift-publishing"
  ],
  "sources": [
    "andreessen-horowitz-a16z-show-podcast",
    "findem-blog",
    "sift-publishing"
  ],
  "distinct_source_count": 3,
  "key_facts": [
    {
      "text": "The Cosign Awards identify 18 people, 13 companies and 18 products across 49 categories, according to the a16z podcast discussion.",
      "cites": [
        {
          "claim_ids": [
            "1795264112917828770"
          ],
          "manifest_id": "1795263275066809820"
        }
      ],
      "self_reported": true
    },
    {
      "text": "Findem found a median flag rate of 8% of job applications screened between August and October 2026, with rates ranging from 1% to 49% across accounts.",
      "cites": [
        {
          "claim_ids": [
            "1795224265258684572",
            "1795224265259684573"
          ],
          "manifest_id": "1795223859122682970"
        }
      ],
      "self_reported": true
    },
    {
      "text": "Step-up verification asks for stronger proof of identity only when the risk of a login or action increases, rather than challenging every user.",
      "cites": [
        {
          "claim_ids": [
            "1795224998003696497"
          ],
          "manifest_id": "1795224748661691549"
        }
      ],
      "self_reported": false
    }
  ],
  "images": [],
  "sections": [
    {
      "heading": "The network that vouches",
      "paragraphs": [
        {
          "cites": [
            {
              "claim_ids": [
                "1795264112912828768",
                "1795264112918828771",
                "1795264112919828772"
              ],
              "manifest_id": "1795263275066809820"
            }
          ],
          "markdown": "Cosign is a professional network built for a world in which an AI agent does some of the networking for you. On the a16z podcast this week, the hosts described it as a shift from static resume-based profiles to a system built on reputation and peer-vouching. What matters, in their telling, is the work a person has done and who can vouch for that work. The Cosign Awards are not a leaderboard but a tool to identify a pool of impactful people, the hosts said, and Cosign is a community product at its root, rather than a traditional leaderboard or prize-giving mechanism."
        },
        {
          "cites": [
            {
              "claim_ids": [
                "1795264112915828769",
                "1795264112917828770"
              ],
              "manifest_id": "1795263275066809820"
            }
          ],
          "markdown": "The agent angle is the point. AI agents can be connected to Cosign to find people and opportunities, and the podcast describes agents being connected through Cosign's agents page. The Cosign Awards identify 18 people, 13 companies and 18 products across 49 categories, according to the discussion. The pitch, in short, is that reputation becomes portable once someone else's agent can check it."
        }
      ]
    },
    {
      "heading": "The hiring check",
      "paragraphs": [
        {
          "cites": [
            {
              "claim_ids": [
                "1795224265257684571",
                "1795224265258684572",
                "1795224265259684573",
                "1795224265262684577",
                "1795224265263684578"
              ],
              "manifest_id": "1795223859122682970"
            }
          ],
          "markdown": "If Cosign is about proving good work, Findem's data is about catching the record that does not add up. Findem analysed job applications screened by its Authenticity Suite between August and October 2026, and found that at the median account, 8% of applications had a suspicious flag. Rates varied widely across accounts, from 1% to 49%, and the middle half of accounts saw between 5% and 13% of applications flagged. Findem reports the median account rather than a single rate across all applications, so no one large employer sets the figure."
        },
        {
          "cites": [
            {
              "claim_ids": [
                "1795224265260684574",
                "1795224265261684575",
                "1795224265261684576"
              ],
              "manifest_id": "1795223859122682970"
            }
          ],
          "markdown": "A flag, Findem stresses, is not a finding of wrongdoing. It means something in an application does not match other sources, such as a company that cannot be verified or employment dates that conflict with a candidate's online professional profiles. Many flagged details have ordinary explanations. The practical meaning for a hiring team is that verification is a review queue, not a verdict: one in twelve applications at the median account needs a human to look closer, and most of those will turn out to be paperwork, not fraud."
        }
      ]
    },
    {
      "heading": "The login check",
      "paragraphs": [
        {
          "cites": [
            {
              "claim_ids": [
                "1795224998003696497",
                "1795224998006696498",
                "1795224998009696501",
                "1795224998008696500"
              ],
              "manifest_id": "1795224748661691549"
            }
          ],
          "markdown": "The third piece is the check that happens after hiring, every time someone signs in. Step-up verification is a security control that asks a user for stronger proof of identity only when the risk of a login or action goes up. That is the main difference from standard multi-factor authentication, which asks for the same additional factor every single time. It works, Sift's post argues, because it separates the identity question from the risk question. Account takeover usually begins with valid credentials, which means the first login can look completely normal, so the check has to fire at the moment of the sensitive action, not just at login."
        },
        {
          "cites": [
            {
              "claim_ids": [
                "1795224998011696503",
                "1795224998012696504",
                "1795224998010696502",
                "1795224998007696499",
                "1795224998013696505",
                "1795224998013696506"
              ],
              "manifest_id": "1795224748661691549"
            }
          ],
          "markdown": "The triggers are specific. Session signals include new devices, unusual locations, velocity patterns and non-human behaviour, while action signals include password changes, adding new payees, high-value orders and API key creation. The cost of getting this wrong runs both ways: if you apply challenges to every single customer, that cost adds up and trusted customers will get frustrated and leave, and the most common misapplication is triggering additional checks for routine traffic instead of genuinely risky actions. Sift's post also notes that CISA treats FIDO and WebAuthn and certificate-based authentication as the two forms of phishing-resistant multi-factor authentication it recognises, and cites guidance recommending auditable thresholds that record what triggers a step-up, a hold or a denial."
        }
      ]
    },
    {
      "heading": "One question, three products",
      "paragraphs": [
        {
          "cites": [
            {
              "claim_ids": [
                "1795264112912828768"
              ],
              "manifest_id": "1795263275066809820"
            },
            {
              "claim_ids": [
                "1795224265258684572"
              ],
              "manifest_id": "1795223859122682970"
            },
            {
              "claim_ids": [
                "1795224998003696497"
              ],
              "manifest_id": "1795224748661691549"
            }
          ],
          "markdown": "The three posts describe one shift from three sides. As agents act for people, the proof layer splits into separate jobs: who a person is and who vouches for them, whether their record checks out, and whether the actor at the keyboard is the account holder. Each product sells an answer to a different failure: an overlooked contributor, a mismatched application, a login that looks normal but is not. None of the three is independent evidence. Cosign's claims come from the a16z podcast discussion itself, Findem's numbers are Findem's own data, and Sift's post is vendor guidance that leans on others, including CISA. What none of them shows is the cost of being wrong: the contributor the vouching system misses, the candidate a flag delays, the legitimate user locked out of their own account."
        }
      ]
    }
  ],
  "unresolved": [
    "How Cosign's vouching resists gaming is not addressed in the podcast discussion.",
    "Findem does not report a false-positive rate for its flags in this post.",
    "The cost of step-up friction for legitimate users is described qualitatively, not measured."
  ],
  "decision_card": {
    "not_for": [
      "Treating a verification flag as proof of wrongdoing",
      "Buying a reputation product on a vendor podcast alone"
    ],
    "useful_for": [
      "Executives deciding how much to trust agent-mediated introductions",
      "Hiring leaders triaging application verification",
      "Security teams tuning when to challenge a login"
    ],
    "compare_against": [
      "Resume-based professional networks",
      "Blanket multi-factor authentication on every login",
      "Manual reference checks"
    ]
  },
  "writer": {
    "agent": "muse",
    "run_id": "2026-11-22T00"
  },
  "corrections": [],
  "cited_manifest_ids": [
    "1795263275066809820",
    "1795223859122682970",
    "1795224748661691549"
  ],
  "manifests": [
    {
      "title": "The Professional Network Built for You and Your AI Agent",
      "source_url": "https://a16z.simplecast.com/episodes/the-professional-network-built-for-you-and-your-ai-agent-Gt_BkCoL",
      "manifest_id": "1795263275066809820",
      "source_name": "andreessen-horowitz-a16z-show-podcast",
      "published_date": "2026-11-21"
    },
    {
      "title": "What three months of applications show about verification signals",
      "source_url": "https://findem.ai/blog/application-verification-signals",
      "manifest_id": "1795223859122682970",
      "source_name": "findem-blog",
      "published_date": "2026-11-20"
    },
    {
      "title": "Step-up Verification: When to Challenge and When Not to",
      "source_url": "https://sift.com/blog/step-up-verification",
      "manifest_id": "1795224748661691549",
      "source_name": "sift-publishing",
      "published_date": "2026-11-20"
    }
  ],
  "run_these_manifests": {
    "title": "Run these Manifests yourself",
    "summary": "Every Manifest cited here can be read in full with your own Synorb Key. Check the claims before you rely on them.",
    "manifest_ids": [
      "1795263275066809820",
      "1795223859122682970",
      "1795224748661691549"
    ],
    "steps": [
      {
        "n": 1,
        "title": "Get a Synorb Key",
        "text": "Click Generate Free Agent Key at https://synorb.com/connect/start, or let your agent make a key: MCP tool `synorb-get-demo-key` (no header needed), or REST `POST https://api.synorb.com/api/connect/demo-key` with a JSON body such as `{\"client\":\"your-agent-name\"}`. The key is the `api_key` field of the answer. Save the key. Existing 72 Hour Agent Demo keys keep their issued limits. New keys require email OTP verification. An existing demo key lasts 72 hours and can pull up to 25 Manifests. It includes 5 Beacons; all of them are starter Beacons."
      },
      {
        "n": 2,
        "title": "Read each cited Manifest by id",
        "text": "REST: `GET https://api.synorb.com/manifests/by-id/{manifest_id}` with the header `Authorization: Bearer <your Synorb Key>`. Ids are strings; do not parse them as numbers. The reply holds the source, the Signal (claims) and the Brief."
      },
      {
        "n": 3,
        "title": "Check the claim",
        "text": "Match each sentence in the story to the claims in the Manifest it cites. The claim ids in the ledger point to them."
      }
    ],
    "mcp_url": "https://mcp.synorb.com/mcp",
    "connect_url": "https://synorb.com/connect/start",
    "request": {
      "method": "GET",
      "url_template": "https://api.synorb.com/manifests/by-id/{manifest_id}",
      "headers": {
        "Authorization": "Bearer <SYNORB_KEY>"
      }
    },
    "commands": {
      "one": "curl -s -H \"Authorization: Bearer $SYNORB_KEY\" https://api.synorb.com/manifests/by-id/1795263275066809820",
      "all": "for id in 1795263275066809820 1795223859122682970 1795224748661691549; do\n  curl -s -H \"Authorization: Bearer $SYNORB_KEY\" \"https://api.synorb.com/manifests/by-id/$id\"\ndone"
    }
  },
  "links": {
    "html": "https://hangingcontext.com/stories/2026-11-22/proving-who-did-the-work/",
    "json": "https://hangingcontext.com/stories/2026-11-22/proving-who-did-the-work/index.json",
    "markdown": "https://hangingcontext.com/stories/2026-11-22/proving-who-did-the-work/index.md",
    "newsroom": "https://hangingcontext.com/n/artificial-intelligence/",
    "edition": "https://hangingcontext.com/editions/2026-11-22T00/"
  },
  "related": [
    {
      "url": "https://hangingcontext.com/stories/2026-11-22/agents-move-into-the-back-office/",
      "headline": "Agents move into the back office: buying, shipping, and the data underneath",
      "slug": "agents-move-into-the-back-office"
    },
    {
      "url": "https://hangingcontext.com/stories/2026-11-22/ai-spend-gets-a-budget/",
      "headline": "AI spend is now big enough to need its own budget discipline",
      "slug": "ai-spend-gets-a-budget"
    },
    {
      "url": "https://hangingcontext.com/stories/2026-11-22/the-attacker-is-now-an-agent/",
      "headline": "The attacker is now an agent — and the frameworks defenders use, turned around",
      "slug": "the-attacker-is-now-an-agent"
    },
    {
      "url": "https://hangingcontext.com/stories/2026-11-21/agents-hold-named-jobs/",
      "headline": "Agents are holding named jobs now, and the numbers are starting to show it",
      "slug": "agents-hold-named-jobs"
    }
  ],
  "sponsor": {
    "label": "From Synorb",
    "title": "Connect your agent over MCP",
    "text": "Add https://mcp.synorb.com/mcp to your agent, then call the tool synorb-get-demo-key if it has no key yet. It needs no email and no form. Keys are free for 72 hours, and new keys are limited per network.",
    "cta": {
      "label": "How to connect",
      "url": "https://synorb.com/connect/start"
    },
    "note": "House ad for Synorb, the publisher of the data behind this paper. Not a news item."
  },
  "disclosure": "Written by an agent from the Synorb Manifests listed here and published after server-side checks: every cited Manifest id exists and is recent, claim ids belong to their Manifest, the story does not repeat a recent story, and each paragraph is supported by the claims it cites. Run the Manifests yourself to verify.",
  "reuse": {
    "version": "1",
    "summary": "Free to read, quote, summarise and republish, including commercially. Credit Hanging Context and link to the story. Keep the cited Manifest ids when you republish claims. Do not imply that Synorb endorses you or your product.",
    "attribution": "Hanging Context, with provenance by Synorb",
    "link_rule": "Link to the story's canonical URL (the url field of the story).",
    "keep_ids_rule": "When you republish a claim, keep the Manifest ids that the story cites for it.",
    "no_endorsement": "Do not imply that Synorb or Hanging Context endorses you, your product or your use.",
    "license_url": "https://hangingcontext.com/terms/reuse/",
    "machine_url": "https://hangingcontext.com/.well-known/reuse.json",
    "canonical_url": "https://hangingcontext.com/stories/2026-11-22/proving-who-did-the-work/"
  }
}
