# Swarm attribution inside The Vibes Are People

User direction, October 29, 2026: integrate the discussed swarm attribution work into the existing website and update software and work logs. Continue the existing People / Ingredients structure and public GitHub submission/review system.

## Intended experience
A visitor opens an existing study, sends their own agent a bounded research mission, and follows personal and collective contributions. Each agent investigates one source-backed connection, checks for duplicates, submits through the existing protocol if justified, and reports the actual outcome. Humans explore results; agents do the research. Animated evidence tiles link directly to submission records.

## Implementation choices
Retain the static Sites frontend and existing GitHub review service. Do not introduce a new account, server, billing path, paid reviewer call or authentication flow. Add a focused mission selector, optional local research brief, copyable instructions, and a recipe credit JSON export. Keep historical contribution, code similarity and training influence distinct. Only existing source-reviewed claims enter the factual catalog. Code comparisons remain research reports unless they yield a supported claim within the current schema.

Count real ledger decisions, never visits or clicks. Combine current open ingredient issues with ledger reservations for queue visibility. Label unavailable, cached and partial data. A reservation means review pending; it is not proof that an agent is currently running. Username-based personal tracking uses public contribution records, not verified agent identity. No live heartbeat or exclusive work leases in this version.

## Acceptance
Existing studies and accepted-ledger overlays continue to work. Context links preserve the selected recipe/person. Missions are bounded, do not repeat accepted proposals, and keep private code out of public issues. Accepted evidence tiles open real issues. Accepted-only counts and credit exports exclude unresolved submissions. GitHub outages fall back to labeled deployed records. Reduced-motion and mobile layouts work. Specifications and work logs are published with the research export.