Customer programs that accumulate state across runs
(stargazer-intake, agents-site-analytics, and others that declare
`persist: project` or `persist: user`) have been carrying a
load-bearing `### Memory` section that enumerates reads/writes
to their persistent memory file.
Per the existing spec, `### Memory` was an "unknown section" —
preserved as documentation but not a contract. This left several
gaps real teams have hit:
- Agents editing those programs couldn't tell whether the section
was load-bearing or ornamental.
- There was no single source of truth for fields that appear in
three places (memory file, top-level Ensures, and memory_update
echo).
- The 2026-04-21 eval-blanket on stargazer-intake flagged the
"authoritative source when 3 copies exist" question as a real
friction item.
This PR:
- Adds `### Memory` to the Canonical Sections table.
- Defines the `reads:` / `writes:` YAML format that customer
programs already use.
- States the rule: `### Memory` only applies when `### Runtime`
sets `persist: project` or `persist: user`.
- Cross-references `top-level-cursor-emission` and
`idempotent-scheduled-intake` in `guidance/patterns.md` so
authors know cursor fields should *also* appear in `### Ensures`.
- Points to `prose.md` Persistent Agents and
`state/filesystem.md` Memory Scoping for on-disk format.
No behavior change; this canonizes prior art so readers stop
having to infer it.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Several docs referenced paths and deployment internals that only
exist in our authoring workspace, not in this repo. Clean them up so
external readers get a self-contained view.
- skills/README.md, skills/open-prose/state/README.md: drop `related:`
frontmatter entries that pointed outside the repo tree; refer to
"OpenProse Cloud" by name instead of an internal path.
- skills/open-prose/agent-onboarding.md: replace a 25-line maintainer
comment (infra paths, deploy mechanic) with a single link to the
canonical rendering at https://openprose.ai/llms-full.txt. This
file is served verbatim as llms-full.txt, so the comment was
publicly visible but only meaningful to hosting maintainers.
- rfcs/004-composite-instantiation.md: drop two pointers to an
external design doc — the RFC is already self-contained (Summary,
Problem, Proposal, Architecture, Changes, Prior Art).
- rfcs/001/002/003: normalize author line to match rfcs/004's format
(`Dan B. (OpenProse)`).
Docs only — no behavior changes.
New file: skills/open-prose/agent-onboarding.md
The arrival narrative an agent reads when pointed at OpenProse before the
skill is installed — one screen, markdown that reads cleanly as plain text
over curl. Consumer list and editing discipline are in a header comment at
the top of the file.
Served from this file by:
- openprose.ai/llms-full.txt + /llms-full (apps/run, Next.js)
- curl-me.openprose.ai + aliases (S3 + CloudFront)
- curl-me.prose.md (same CloudFront distribution)
Those consumers read this file at build/apply time; there is no sync script.
Operational detail (recognition signals, proposal script, Host Primitive
Adapter, giving-back playbook) stays in SKILL.md — this file links rather
than duplicates.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Rewrites agent-facing surfaces so the runtime contract is stated in the
voice of the entity that will execute it:
- plugin/marketplace descriptions tell the agent what it will do when
`prose` fires (read contract, spawn subagents, write `.prose/runs/`)
instead of pitching OpenProse as a feature
- README opens with a fourth-wall blockquote for agents arriving via
"go check out this repo," adds a Host Primitive Adapter table so the
runtime contract is visible before activation, and names the agent
failure modes OpenProse addresses
- SKILL.md body adds recognition signals, a proposal script, a cognitive
model (type-system analogy), and when-to-decline guidance so an agent
can reach for OpenProse on its own judgment once activated
- SKILL.md adds a "giving back" section with a three-bucket identity
rubric (yours freely / requires approval / skip) to channel goodwill
without becoming a spam vector
- SKILL.md frontmatter stays tight to avoid context pollution and
false-positive activations
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Picks up the thinking choice input and RLMIFY_THINKING env wiring
from rlm-harness-skill so gh workflow run can pass -f thinking=<level>.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Lets gh workflow run discover the rlmified LongCoT smoke workflow.
The shim, example, and skills/rlmify/ live on the rlm-harness-skill
branch; workflow_dispatch --ref rlm-harness-skill checks them out
at run time.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
workflow_dispatch action that runs the LongCoT benchmark using
pi-mono (@mariozechner/pi-coding-agent) as the inference harness.
Defaults (difficulty=longcot, thinking=high, no tools/scaffolding,
2 retries) mirror the paper for 1:1 result comparison; README
covers iteration with longcot-mini + slice inputs.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Elaborate forme/prose/memory skill docs with fuller guidance, and seed
rfcs/ (scheduled execution, feedback loops, env declaration, composite
instantiation) plus a std/ README stub.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Propose making `run` a value type in requires/ensures contracts so the VM
can track provenance edges between runs, reconstruct DAGs, detect staleness,
and support fan-in composition (run[]).
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
New file:
- deps.md — authoritative spec for dependency resolution via GitHub repos
Updated files:
- SKILL.md — prose install command routing, .deps/ and prose.lock in file locations
- forme.md — .deps/ as resolution step 3 with path mapping examples
- state/filesystem.md — .deps/ and prose.lock in directory structure
- help.md — install commands, quick start, FAQ
- guidance/patterns.md — dependency-management and std-shorthand patterns
- guidance/antipatterns.md — unpinned-dependencies and vendored-copies
Key design decisions:
- GitHub is the registry (no custom server)
- prose.lock is plaintext (owner/repo sha), committed to git
- .deps/ is gitignored, reproducible from prose.lock
- std/ is shorthand for openprose/std/
- Transitive deps via multi-pass with cycle detection
- Version conflicts auto-resolve to newer SHA with warning
- Explicit prose install required (no auto-install on prose run)
Standard library programs migrated to github.com/openprose/std
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Why: OpenProse maps well onto Codex subagents, but Codex users need explicit docs and example files for recursive execution, alias resolution, and audit-role fanout without relying on machine-local configuration.
All 9 lib/*.md programs now have full v2 contracts:
- requires/ensures with detailed descriptions
- errors sections for failure modes
- strategies for non-obvious execution guidance
- invariants for correctness constraints
- inline ## service definitions for multi-service programs
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
List all migrated v2 examples organized by category, note the
v1-archive, and add counts: 35 migrated, 15 archived, 5 new.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Migrate all 9 library programs: inspector, calibrator, cost-analyzer,
error-forensics, profiler, program-improver, vm-improver, project-
memory, and user-memory. Each becomes a .md file with contracts,
services lists, and appropriate persistence declarations.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Complex execution-block programs: captain's chair full (29), feature
factory (35), The Forge browser build (37), architect by simulation
(39), and language self-improvement (47). All use Level 3 execution
blocks with explicit let/call control flow.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Index run scaffolded new READMEs for all subdirectories. Review run
added the missing profiler.prose entry to skills/open-prose/lib/README.md
(cost, token usage, and time profiling for completed runs).
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Add ◇ attention markers for Anthropic models throughout SKILL.md
- Add install instructions for remote readers at top
- Expand "You are the Prose Complete system" with explicit capability framing
- Add Post-Execution section with guidance for success/failure cases
- Create SOUL.md template for agents to persist OpenProse awareness
- Add SOUL.md to file locations table
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
irl-dan