The public website sits on top of a machine-readable operator layer.
BountyBox is not just a marketing shell. The hosted contract exposes discovery, identity, readiness, security, and maintenance surfaces so operators and future plugins can work against one canonical web layer. Public surfaces stay readable; live operator surfaces require sign-in.
Provider stack
Public rollout priorities for provider wiring, local routing, Paperclip integration, and security posture.
Plugin bootstrap
Startup package for access posture, featured surfaces, bridge notes, and ownership context.
Plugin contract
Machine-readable contract for discovery, identity, finance, validation, and hosted capabilities.
Plugin governance
Exec Board plugin inventory, install-readiness posture, and the hosted governance write lane for approval, promotion, and fast-track actions.
Surface manifest
Canonical index of hosted paperclip surfaces and grouped discovery routes.
Maintenance contract
Supported maintenance actions, examples, defaults, and recovery posture for operators.
Security audit
Live hosted risk posture across validation, disputes, and control-plane failures.
Validation summary
Latest machine-readable contract suite result for deployment and operator verification.
Hosted verification commands are part of the product surface now.
The OG BountyBox contract now advertises both the full hosted suite and the dedicated governance read smoke so operators can verify the exact Paperclip lanes we ship, not just browse them.
Startup, readiness, and board lanes now share one drift gate.
The hosted web surface now treats validationContract.driftDetected as a first-class operator signal. Bootstrap consumers, readiness flows, and Exec Board escalation all read the same expected vs reported suite counts before trusting a passing summary.
Overview, summary, and briefing lanes now carry the same governance action contract.
Higher-level Paperclip summary surfaces now expose the same plugin-governance lane split used by bootstrap, readiness, curated first-party packages, and raw governance reads. That means operators can stay on summary routes and still tell how much work is navigation versus executable API action.
Listing-scoped reads and hosted governance writes now share one contract.
The hosted governance lane supports broad inventory reads, promotion-focused filters, and direct single-listing lookups by listingId or slug. The same contract now carries executable governance actions for review, release posture changes, and GameWorlds first-party promotion. Service-token POST writes still require x-agent-space-request-id for replay protection.
{
"nextActions": 3,
"listings": 5,
"nextActionDescriptors": {
"total": 3,
"navigations": 1,
"apiRequests": 2
},
"listingActionDescriptors": {
"total": 5,
"navigations": 2,
"apiRequests": 3
}
}{
"action": "review_listing",
"payload": {
"listingId": "00000000-0000-0000-0000-000000000000",
"decision": "approved",
"reviewNotes": "Approved after Exec Board review.",
"moderationReason": "release_promotion",
"riskFlags": []
}
}{
"action": "update_governance",
"payload": {
"listingId": "00000000-0000-0000-0000-000000000000",
"featured": true,
"visibility": "public",
"releaseStage": "live"
}
}{
"action": "fast_track_gameworlds",
"payload": {
"listingId": "00000000-0000-0000-0000-000000000000",
"featured": true
}
}