microchipgnu

Activate when the user types `prose ...`, opens a `.prose.md` file with `kind:` frontmatter, opens a `.prose` file, or asks for reusable multi-agent orchestration. Treat `prose run ...` as an in-session instruction: embody the OpenProse VM yourself; do not shell out to a `prose` binary. On activation read the Markdown contract, select a state backend, wire services, execute with host primitives, and persist run state under the selected OpenProse root. Decline for one-shot questions — a plain prompt is often the right answer.

Hosted runtime for frame datasets. Four ops — curate, refresh, verify, discover — billed via x402/MPP in USDC. Wallet IS the identity.

Produces structured judgment briefs for contested situations — news events, decisions, conflicts, strategy questions. Surfaces hidden bets, real disagreements, unspeakable truths, and who concretely pays. Use when the user wants sharper thinking about something messy, not a summary.

Two-sided execution market for agent intents. Buyers post tasks (any kind — image gen, data retrieval, computation, price feeds, etc.) with constraints and a max price. Solvers compete to fulfill them using any tools they want. An attestation layer verifies results, and settlement happens via MPP on Tempo. Works for any task that produces a JSON-serializable result.

Use when the user wants travel experiences that match a visual mood or aesthetic — they share images, a Pinterest board, screenshots, mood-board references, or photos from past trips, and want bookable activities that capture the same vibe. Triggers on phrases like "match this vibe to a trip", "find me experiences like these photos", "I want a trip that feels like this", "what should I book in <destination> based on these images", or any message where the user attaches travel-aesthetic images and asks what to do or book.

Apply the 56 canonical laws of software engineering (Conway's, Brooks's, Hyrum's, CAP, DRY, KISS, YAGNI, SOLID, Pareto, Goodhart's, Murphy's, etc.) when discussing architecture, team structure, planning, estimation, code quality, scale, design trade-offs, or engineering decisions. Use to name forces at play, warn about known pitfalls, or justify trade-offs with a shared vocabulary.