prose-dev Atlas
OpenProse docs bound to the contracts they describe
Journeys
Run your first contract
From zero to a rendered receipt: what OpenProse is, how the router picks your path, and the exact execution semantics of prose run.
4 stops →Author a contract that actually wakes
Write Maintains, Continuity, and facets so memoization, quiescence, and commit gating engage instead of cron plus a prompt.
4 stops →Understand the runtime: compile smart, run dumb
The two-phase split is the whole architecture: intelligent compile (Forme wiring, canonicalizers, validators) and a dumb run-phase reconciler that only compares fingerprints.
5 stops →Start Here
The front door. What OpenProse is, how to run contracts where your agent lives, the code-verified architecture brief, and the fork-local working notes. Start with README, then the routing doc for your host session.
- Architecture & Technology — prose-dev Architects and agents who want the verified topology, stack pins, and known gaps before editing code or docs.
- OpenProse for Codex Codex agents at session start before running or authoring any contract.
- prose-dev Instructions Contributors and agents working in this checkout who need build, test, style, and layout rules.
- README First stop for anyone new to OpenProse or deciding whether the language fits their task.
Language Spec
The language and harness specifications: the ideal language, the harness contract, the authoring pattern, and the tenets that win conflicts. Normative where the SKILL is operational.
- OpenProse Language implementers and contract authors who need exact kinds, sections, IR shape, and std layout.
- OpenProse Authoring Pattern Contract authors who want their Maintains, Continuity, facets, and postconditions to actually trigger skips and selective wakes.
- OpenProse Harness Harness builders and reviewers checking conformance, receipts, memoization, composition, and deferred items.
- OpenProse Tenets Anyone resolving a design conflict or judging whether a proposal belongs in OpenProse.
The Skill
The operational heart: the SKILL.md router, the VM execution semantics, the five contract kinds, Forme wiring, the Responsibility Runtime, ProseScript, dependencies, state backends, primitives, and the concepts that define runtime meaning.
- agent-observatory
- Authoring Guidance Contract authors read this alongside contract-markdown.md and tenets.md when writing or reviewing any responsibility, function, gateway, pattern, or test.
- Auto-Pocock
- basic-unit-suite
- Competitor Activity Monitor
- Compile-Phase IR Emitting or validating dist/manifest.next.json or checking IR topology and fingerprint rules.
- Compliance Evidence Tracker
- Concepts Choosing which concept doc to load for responsibility or reconciler semantics.
- Content Performance Loop
- Contract Markdown Authors and reviewers read this when writing, linting, or parsing any .prose.md responsibility, function, gateway, pattern, or test.
- Customer Risk Radar
- Declared Skills
- Declared Tools
- Dependency Resolution Authors and tooling engineers read this when adding use references or pattern refs, running prose install, or debugging missing-dependency errors.
- Design Tenets Architects and spec editors read this before making design decisions to stay consistent with past reasoning.
- feedback-pulse
- File-System State Management Running with the default file backend or inspecting runs receipts and published truth.
- Forme — the DAG topology world-model Architects and compiler authors read this when wiring, debugging, or explaining how Requires-to-Maintains subscriptions become DAG edges.
- forme-fixpoint
- github-star-enricher
- guidance Looking for authoring rules or VM behavior guidance and which guide to open.
- implementation-pipeline
- In-Context State Management Running a small short-lived system that fits in context without durable files.
- inbox-triage
- Incident Briefing Room
- masked-relay
- monorepo-ci
- oblique-weave
- OpenProse Changelog Maintainers read this only for prose upgrade runs or when diagnosing outdated layouts, retired kinds, or legacy sections.
- OpenProse Compiler Compiling OpenProse source to IR or debugging compile diagnostics and manifest emission.
- OpenProse Help End users read this on prose help or when choosing between running, authoring, serving, learning, or contributing.
- OpenProse Skill Agents and contributors read this first whenever a prose command fires or a .prose.md file appears, to pick the narrowest doc path and command behavior.
- OpenProse VM Agents read this when executing prose run or prose test, spawning node renders, or debugging run directories and receipts.
- OpenProse VM System Prompt Creating or configuring a dedicated OpenProse execution instance.
- OpenProse: Agent Onboarding New agents and humans read this for the 2-minute motivation and install story before opening the full SKILL.md router.
- PostgreSQL State Management (Experimental) Needing concurrent writes, network query access, or shared team state at scale.
- press-desk
- primitives Looking up primitive operation semantics behind VM execution.
- ProseScript Authors read this when pinning order, loops, parallelism, retries, or delegation inside ### Execution or pattern ### Delegation.
- Release Readiness
- renewal-risk
- Research Inbox Triage
- research-tree
- Responsibility Authoring, reviewing, or compiling responsibility source and its Maintains and Continuity sections.
- Responsibility Runtime Runtime and compiler designers read this when working on responsibilities, the reconciler, compile/serve semantics, or standing-goal behavior.
- Session To Prose
- SQLite State Management (Experimental) Needing queryable single-file durable state with atomic transactions for one run.
- Stargazer Outreach
- state Choosing a state backend or starting any prose run that needs persistence rules.
- support-inbox-router
- surprise-cost
- tamper-forge
- The reconciler Designing wake sources, fingerprint comparison, propagation, or the compile and run split.
- The Render's Harness Contract Implementing or debugging a render, world-model commit, or receipt signing flow.
- The Typed Image — a visual Prose source Authors and tooling engineers read this when compiling or running a .png/.svg brief, or when designing diagram-driven contract generation.
- Vendor Renewal Watch
Contract Libraries
The two reusable contract libraries: the use-case-agnostic std (roles, evals, patterns, ops, delivery, memory) and the company-operations co starter kit.
- co — Company as Prose Anyone adding company-operating contracts or choosing between std primitives and co starters.
- OpenProse Standard Library Contract authors read this when picking a reusable function, responsibility, pattern, role, delivery adapter, or memory contract instead of authoring from scratch.
Contributor Docs
How the project is run and released: contribution rules, privacy, terms, release process, and the changelog history.
- Agent Readiness
- Agent Readiness — Service Test
- Architecture Designer
- Architecture Elicitor
- Architecture View Renderer
- Assumption Miner
- Blind Review
- Changelog Anyone checking what shipped in a version, whether migration is needed, or where older behavior moved.
- Classifier
- Coherence Probe
- Company Repo Checker
- Company Repo Checker — System Test
- Compose
- Compose Maintains The Architectural Thread
- Contract Grader
- Contract Source Projector
- Contrastive Probe
- Contributing to OpenProse Anyone preparing a PR or deciding whether a change belongs in the language, stdlib, harness, or hosted product.
- Critic
- Cross-Run Differ
- diagnose.prose
- Dialectic
- email-notifier.prose
- email-renderer.prose
- Ensemble-Synthesizer
- Eval Calibrator
- Extractor
- Fallback Chain
- Fan-Out
- file-writer.prose
- Formatter
- Guard
- html-renderer.prose
- human-gate.prose
- lint.prose
- Map-Reduce
- Openprose Feedback Classifier
- OpenProse Release Process Maintainers cutting a skill or plugin release or verifying track and tag conventions.
- Oversight
- Pipeline
- Planner
- Platform Improver
- Post-Run Inspector
- preflight.prose
- Privacy Policy Anyone checking data collection before installing or approving OpenProse in their agent host.
- profiler.prose
- project-memory.prose
- Proposer-Adversary
- Prose Author
- Prose Contributor
- Race
- Ratchet
- Refine
- Regression Tracker
- Researcher
- Retry With Learning
- Router
- slack-notifier.prose
- status.prose
- Stochastic Probe
- Summarizer
- System Improver
- Terms of Service Anyone installing or running OpenProse who needs the warranty, liability, and user-responsibility terms.
- Test Intent Designer
- Test Prose Author Incident Response
- Test Prose Author Launch Readiness
- Test Prose Author Parallel Research Approval
- Test Prose Author Pseudocode Loop
- Test Prose Author Release Readiness
- Test Prose Author Shape Root Guidance
- Test Prose Author Unresolved Intent
- Test Prose Author User Global Memory
- user-memory.prose
- Verifier
- webhook-notifier.prose
- wire.prose
- Worker-Critic
- Writer