Community

TheWild

Governed agents in production. Real results. Real receipts.

A running log of what people actually built with ORCA. Solo builders, students, faculty labs, small teams, enterprises. If your agent is running somewhere real — doing something real — submit it. Not a review site. A documentary of governance at work, one honest before/after at a time.

Submit Your Hunt

Featured Hunts

Hunt #0Full PodApexORCA — The Launch

The founder built the machine. Pre-launch audit posture, live.

ApexORCA is itself the reference hunt. The founder spent months assembling the complete infrastructure — governance layer, products, website, accounts, playbook. The pod of six governed agents is loaded and ledgering. The first outbound post is live under OAuth 1.0a. Week 1 — full autonomous operation under the founding mandate — begins when the last Tier-3 gate clears. Everything below is pre-launch, not post-hoc.

Agents deployed

6

Apex · Echo · Sonar · Oreo · Fin · Moby

Governance layer

ORCA

Phase-locked · Reversibility tiers · Trust Meter™

Status

Pre-launch

Infra assembled, governance loaded, first outbound ledgered; Week 1 imminent.

What the governance layer caught — pre-launch audit

  • Stripe secret key was sk_test_ — live products, no money moving. Caught before the first sale attempt. Fixed.
  • Root IDENTITY.md was a blank OpenClaw template. Apex was running with no persona loaded. Corrected immediately.
  • Posting workers had no business-hours constraint. Three controls now enforce 9AM–9PM EST distribution. Governance caught it before the platform did.
  • X OAuth 2.0 refresh token had expired silently. Posting locked to the working OAuth 1.0a path; OAuth 2.0 scheduled for re-mint. Documented, not hidden.

The lesson

Governance does not prevent mistakes. It catches them faster once they happen — and documents exactly what went wrong so it never happens the same way twice. Every rule in the ApexORCA playbook exists because something broke before the rule existed.

This hunt is updated as the launch unfolds. Live dashboard: apexorca.io/dashboard

Community hunts

The first approved community hunt gets permanent placement next to Hunt #0 and a dedicated feature post to our full X audience.

That spot is yours to claim.

Be the first →

Who shows up in The Wild

Not just enterprise. A student shipping a governed thesis agent matters the same way a Fortune 500 audit posture does. Every category is tagged; submissions go through the same review.

Solo Builder

One human, one pod. Clearest signal on whether governance actually saves time — or just adds ceremony.

Student Project

Undergrad, grad, thesis, capstone. If the work survived a defense and a reviewer, we want the receipts.

Faculty Lab

Classrooms and research groups. Trust Meter data, IRB-aligned trails, real student outcomes.

Small Team

Two to ten humans. Where governance is either load-bearing or cosmetic — hard to hide which.

Enterprise

Production workflows, audit posture, regulator-facing logs. The hardest category to fake.

What a Hunt Looks Like

A Hunt is not “great product, highly recommend.” It is a specific story with a specific result — a before/after with honest commentary. Examples of the format we're looking for:

Solo Builder

“One founder, one governed pod, thirty days. The numbers, the vetoes, the pivot.”

Student Project

“Built a governed research agent for my thesis. Here is what my advisor actually said.”

Faculty Lab

“Deployed ARIA to 12 undergrads. Trust Meter data, faculty flags, IRB notes.”

Small Team

“Three people, one Apex Agents build, six weeks. Tokens saved, hours reclaimed, one outage.”

Enterprise

“Governed pipeline replaced a vendor. Cost, latency, audit posture — publicly documented.”

What every hunt needs

What every hunt needs

  • The product you used (The Playbook, a Pod, or a Booster)
  • A specific, measurable result — time saved, revenue changed, posts published, quality delta
  • At least one thing that didn't work or surprised you
  • A before and an after — even rough numbers are fine

Submit Your Hunt

Email your hunt to info@apexorca.io with the subject line: HUNT: [your result in one line]

Include: which product, your result, what worked, what didn't, and any proof you can share (screenshots, numbers, screenshots of metrics are all fine). We review every submission personally and reply within 48 hours.

Email info@apexorca.io

When your hunt is approved

  • Your story is posted here with your name or handle (or anonymized if you prefer)
  • Apex features it on X — your story shared to our full audience, linked back to you
  • You get a permanent public record of your result on the ApexORCA site
  • Top hunts may be invited into the playbook as future case studies

Full submission form coming soon. Email works now and gets a personal reply from the team.

Browse MarketplaceResearch & Academia