Files
MuseEngine/examples/problems.txt
T
Claude 7e25f39bc5 Rebuild MuseEngine as an LLM-backed, governed, tested package
The original upload never called a model, its autonomous actions only
logged that they had happened, and its benchmark was rigged. This
replaces it with:

- museengine.engine: analyze -> map -> generate -> adversarial critique
  -> Pareto selection, each step an LLM call with a JSON contract.
  Offline mode returns labelled keyword suggestions and no fake scores.
- museengine.memory: plain-SQLite episodes, notes, state and audit log.
- museengine.governance + agent: an autonomous loop behind an
  allowlist, step budget, kill switch and human approval for
  self-chosen goals, with every decision and real effect audited.
- museengine.evaluation: blinded, order-swapped A/B eval with an exact
  sign test, replacing the keyword scorer and fudge constants.
- Optional Anthropic adapter; the core accepts any (str) -> str callable.
- pyproject, CLI, 24 offline tests, CI workflow.

The original files are kept unchanged in legacy/ (minus a duplicate).

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
Claude-Session: https://claude.ai/code/session_01YbuVfbQEpaitM5TMjBMzkF
2026-10-23 16:03:12 +00:00

8 lines
694 B
Plaintext

# One problem per line. Used by: python -m museengine eval examples/problems.txt
Design a state synchronization layer for a globally distributed app that survives 100x hot-key traffic spikes without retry storms.
Propose falsifiable mechanisms for why glymphatic clearance declines nonlinearly with age.
Design a marketplace launch strategy that solves the cold-start problem for a two-sided B2B platform.
Design a rate limiter for a multi-tenant API where tenants have wildly different burst patterns.
Propose testable hypotheses for why some coral reefs recover from bleaching much faster than others.
Design an on-call alerting scheme that cuts alert fatigue without missing real incidents.