prose-programs is a collection of OpenProse programs for turning evidence, repositories, workflows, and failures into reusable prose artifacts.
Each directory is a self-contained program with a small service pipeline and a clear contract:
requires: the inputs the program expectsensures: the artifacts the program should producestrategies: the operating rules that shape the output
prosify: extract workflows and reusable patterns from evidence.frameworkify: separate stable primitives from project-specific implementation and package a reusable framework.productize: turn internal tools or prototypes into shippable products with packaging and docs.distillify: compress a corpus into core invariants and a reduced mental model.repairify: analyze failures, identify root causes, and produce fixes with regression guards.reviewify: read reviews and synthesize findings or patterns.composify: combine prose assets into new variants or higher-level compositions.datasetify: derive datasets and labeling/splitting plans from source corpora.instrumentify: design telemetry, schemas, and instrumentation surfaces.traceify: normalize traces and design trace schemas and readers.migratify: plan and execute migrations between source and target systems.stabilify: reduce instability and design deterministic environments.syncify: analyze synchronization work and design planner/writer workflows.updatify: plan upstream merges and repository updates.adoptify: design adoption and rollout strategies for change.benchmarkify: design benchmarks, harnesses, and evaluation plans.debtify: prioritize and sequence debt reduction work.evalify: design evaluation rubrics, judges, and scoring systems.guardraily: define policy, risk, and enforcement boundaries.
Most programs follow the same shape:
- A reader or auditor service gathers evidence.
- A designer or planner service turns that evidence into an actionable model.
- A writer service produces the final prose artifact.
This repository is intentionally lightweight: the directories contain the program definitions rather than a large application framework.
Use the program directory that matches the task:
- Choose
prosifywhen you want reusable workflows extracted from real evidence. - Choose
distillifywhen you need a compact mental model of a corpus or codebase. - Choose
repairifywhen something is broken and you need a root-cause and fix plan. - Choose
frameworkifyorproductizewhen the goal is reuse or release readiness.
SUMMARY.mdgives a compact overview of the repository and its program groups.- The individual
index.mdfiles define each program contract.