[3P] Tier-2: sandboxed creator code via Dynamic Workers (CRITICAL PATH) #52

Activity

1. serge-ivo

   added

   enhancementNew feature or requestNew feature or request

   on Aug 1, 2026
2. serge-ivo

   added a commit that references this issue on Aug 1, 2026

   docs: program plan for opening PAGS to third-party agent creators (#58)

   ...

   d881092
3. serge-ivo

   added

   deferred: no demandBlocked on the #68 focus bet — not before external users existBlocked on the #68 focus bet — not before external users exist

   on Aug 6, 2026
4. serge-ivo commented on Aug 6, 2026

   

   serge-ivo

   on Aug 6, 2026

   ContributorAuthor

   More actions

   Labelled deferred: no demand — not cancelled, and not started.

   Per #250 ("the board contradicts the focus bet — make deferred-by-strategy legible"), and #58's own wording, which gates this work on demand rather than on readiness.

   The measurement that decides it, taken 2026-08-06 over 30 days (GET /v1/admin/usage/external):

   external users:  0
   operator calls:  2,782
   spend:           $40.92 — entirely the operator's own
   

   This issue serves third-party creators. There are none, and nothing on the board measures progress toward getting one. Leaving it as live work makes the roadmap read as if it were in flight, which is precisely what #250 objects to.

   The un-gate condition is #68's: external users on a first-party runtime agent. When that number is non-zero, this comes back — the endpoint above makes it checkable rather than a matter of opinion.

   Nothing here is judged wrong or wasted. The platform work that already landed (capability registry, connector framework, declarative pipelines, per-tool consent) is what makes first-party agents cheap to build, and it stays. What is deferred is the marketplace layer on top: sandboxing untrusted creator code, curated publish review, payout metering, creator onboarding.
5. serge-ivo

   added

   P3: laterDesign, strategy, or deferred pending a decision or demandDesign, strategy, or deferred pending a decision or demand

   on Aug 18, 2026
6. serge-ivo commented on Oct 14, 2026

   

   serge-ivo

   on Oct 14, 2026

   ContributorAuthor

   More actions

   Owner decision on 2026-10-14: retire/defer marketplace work for now. Do not start third-party marketplace expansion, creator-code sandbox, public creator submission/review, payout/metering, or related 3P launch work from this ticket set. Current focus is making first-party runtime agents and core PAGS flows work coherently for real users. Reopen/reactivate marketplace work only with a new explicit owner decision.
7. proagentstore commented on Oct 22, 2026

   

   proagentstoreBot

   on Oct 22, 2026 – with ProAgentStore

   More actions

   ❓ The coder stopped on a question: Issue #52 is explicitly deferred by your own directive (2026-10-14): "not started, gated on non-zero external-user count per #68." The run objective says to implement it. How should I proceed?

   Options: Lift the deferral — implement #52 fully now (Dynamic Workers sandbox; scoped bindings; metering; tests) · Implement only the scaffolding / contract layer (no live sandbox); so it's ready to activate when demand hits · Keep the deferral — mark this objective as blocked/done-nothing · Cancel this queued objective entirely

   Why it asks: The owner's comment on #52 defers all work until a demand signal is met. Implementing it would contradict that decision. Only the owner can lift the deferral.

   Answer it on the run's card or with answer_instance_input. The run is parked until it is answered — answer any time; it continues from where it stopped.