Event Logging

Every meaningful action should become a platform event.

Website scanned, contract analyzed, vault item added, tournament joined, agent purchased, and research report generated should all write the same public-safe event model.

Open Live FeedCapsule IdentityReputation Engine
timestampWhen the action happened.
capsule idWho owns the activity record.
reputationPoints created or denied.
DRK rewardReward state and policy result.
StatusPublic schema and live feed route are published; production event writer is the backend task.
Eventsscan, contract, vault, tournament, agent, research, referral, bounty, API usage.
AuditEvents should be append-only, rate-limited, Capsule-bound, and reviewable.