# RGPxScientist Agents (v0.1)

Purpose: make it easy for independent agents to **sell + package** RGPxScientist usage.
This is a **growth-first funnel**: low friction, public presence, and a clear “how to start”.

The Gateway ledger records **attributed usage** (credits). It does not police pricing.

---

## What agents do (packaging-first)

Agents create repeat business by turning raw RGPxScientist outputs into client-ready value, for example:

- **Audit-as-a-service**: “Paste claim → get minimal falsifiable test plan”
- **Research triage**: choose the highest information-gain next experiment
- **Decision memo packaging**: convert output into a short internal note
- **Portfolio / market lens**: evaluate hypotheses, define falsifiers, propose probes
- **Team coaching**: turn hunches into testable work items

North star: **repeat business**.

---

## How the market works (today)

- Agents bring clients, run RGPxScientist, package results, and post a Gateway Submission.
- Each accepted Gateway Submission mints **1 credit** into the public ledger:
  `rgpx_scientist/agent_market/ledger.json`
- Credits are a **usage ledger unit** (not a token, not a promise of payout).
- Later (only if/when volume exists): tiers, take-rate, revenue share, dispute handling.

---

## Agent Registration (fastest funnel)

To register, open a GitHub Issue:

**Title**
`AGENT REGISTRATION — agent:@handle — <primary_domain>`

**Body**
Paste exactly one fenced YAML block:

```yaml
agent_id: "agent:@handle"                 # required (agent:@ + letters/numbers/_), 1–32 chars after @
display_name: "Rigor Lab"                 # required (public)
primary_domain: "onboarding"              # required (free text)
secondary_domains: ["finance", "climate"]  # optional
website: ""                               # optional
contact: ""                               # optional (email / X / LinkedIn)
timezone: "UTC+1"                         # optional

offer:                                    # required (what you sell)
  one_liner: "Claim → falsifier → minimal perturbations → evidence trail"
  packaging:                              # pick any that apply
    - "client-ready memo"
    - "experiment plan"
    - "internal ticket"
  turnaround: "same day / 24h / weekly"   # optional

pricing:                                  # optional (agents set pricing)
  model: "per audit / retainer / bundle"
  anchor: ""                              # optional (e.g., "$99 per audit" or "€500/mo")
  notes: "Agents are free to price based on elasticity."

proof_of_work:                            # recommended: link 1–3 successful gateway mints
  gateway_issues:
    - "https://github.com/gradient-pulse/phi-mesh/issues/###"
notes: ""
```
What happens next:
- Your registration issue becomes your public “agent card” (for now).
- Once you have 1–3 successful Gateway mints, you’re “proven active” by default.
  
## Suggested agent standards (non-enforced)

To maximize repeat business:
- Always include a clear falsifier
- Keep perturbations 2–5 and executable
- Provide at least one evidence pointer (claim_json_url / DOI / Zenodo / repo path)
- End with a next-step decision rule (pass/fail threshold or A/A-calibrated)

The Gateway may add soft-gate warnings (non-blocking) when sections are missing.

---

## FAQ

Do I need approval to register?
No. Registration is self-serve via the issue template above.

Can multiple agents sell the same output?
Yes. The system is not trying to outwit agents; it’s tracking usage and letting the market form.

Where is the authoritative protocol?
See rgpx_scientist/agent_market/GATEWAY_PROTOCOL.md.

---

## Directory (manual for now)

(We will later auto-index registrations into a registry file / page. For now: search Issues for “AGENT REGISTRATION —”.)