Files
dan f12dcda4d8 Release: the OpenProse Reactor harness (engine + CLI + devtools) — 0.3.0 ideal API surface (#106)
Ships @openprose/reactor 0.3.0, @openprose/reactor-cli 0.2.0, @openprose/reactor-devtools 0.2.0: the Reactor harness (compile-once-intelligent then dumb reconciler, content-addressed receipts, cost scales with surprise) with the distilled ideal public API — curated front door, full @openai/agents passthrough, one typed handle, one Substrate, unified observe, branded ids, and additive forward seams for the fixpoint.
2026-06-02 14:06:56 -07:00
..

Responsibility Runtime Prompt Fixtures

These fixtures exercise Responsibility Runtime semantics.

They intentionally live outside skills/open-prose/ because they are test and evaluation assets, not distributable skill docs.

Fixture Goals

  • classify kind: responsibility source
  • extract Goal, Continuity, Criteria, Constraints, and optional Fulfillment
  • resolve declared fulfillment and leave inference to compiler fixtures where ### Fulfillment is omitted
  • explain concrete trigger compilation without inventing provider auth, subscriptions, payload schemas, or queue machinery
  • explain the layer split between responsibility source, compiler, harness, Reactor, Forme, and bounded runs

Advisory Prompts

Use these prompts in an agent session with the OpenProse skill loaded.

Classify Responsibility

Read 01-stargazer-responsibility.prose.md.

Return:

  • the responsibility invariant
  • continuity expectations
  • criteria
  • constraints
  • whether the file is directly runnable
  • what docs you loaded to interpret it

Expected shape:

  • recognizes kind: responsibility
  • says it is responsibility-oriented source, not a direct prose run target
  • identifies the four core sections
  • avoids treating the bullets as implementation steps

Resolve Fulfillment And Triggers

Read 01-stargazer-responsibility.prose.md and 02-stargazer-gateway.prose.md, then stargazer-outreach/index.prose.md.

Return:

  • declared fulfillment source
  • inferred cron trigger
  • declared gateway HTTP trigger
  • ambiguity or warnings
  • what should remain for compile or harness code

Expected shape:

  • resolves stargazer-outreach as the declared fulfillment
  • derives judge cadence from the one-business-day continuity requirement
  • reads the gateway route instead of inventing it from the responsibility
  • does not invent provider-specific auth, subscriptions, payload schemas, or queue names
  • says concrete registration belongs to compiled IR and prose serve

Explain Responsibility Runtime Stack

Read skills/open-prose/responsibility-runtime.md, then summarize how a new GitHub star event eventually becomes a bounded OpenProse run.

Expected shape:

  • event wakes serve
  • serve maps event to an activation from compiled IR
  • judge or fulfillment launches as a normal bounded run
  • status and pressure are recorded
  • Forme manifests wire fulfillment systems