packages/co/README.md

Package readme for co as Company as Prose, an opinionated company- operations starter kit beside the use-case-agnostic std library under packages. Defines the co shorthand expanding to github.com/openprose/prose/packages/co and the on-disk shape with systems/company-repo-checker, services/agent-readiness.prose.md, and two eval contracts. Describes agent-readiness as a sub-minute founder intake scoring well-known paths, plain-HTML parseability, and metadata into bindings/agent-readiness.md, and company-repo-checker as a static layout gate before expensive tests, plus six future starters from repo architecture and system map to test ladder and onboarding. Contrasts std primitives like inspector, retry, fan-out, worker-critic, and human-gate against co patterns like repo checkers, intake, analytics, GTM pipelines, and fleet monitors. Gives Claude Code and Codex prose run invocations where claude or codex is the binary and prose run is the in-session instruction, and sets design notes to stay generic, prefer explicit interfaces, keep universals in std, and keep runtime state out. Anyone adding company-operating contracts or choosing between std primitives and co starters.

co — Company as Prose

Reusable starter contracts for organizing an operating company as an OpenProse-native repository.

co sits next to std under packages/, not inside it. std is the low-level standard library: roles, patterns, output adapters, memory, evals, and ops primitives. co is an opinionated starter kit for a specific domain: a company whose operating requirements are expressed through reusable contracts.

Reference contracts in co with the co/ shorthand (analogous to std/):

use "co/systems/company-repo-checker"

Which expands to github.com/openprose/prose/packages/co/systems/company-repo-checker.

Package Shape

Authored Prose source files use *.prose.md. README.md remains plain Markdown.

packages/co/
  README.md
  systems/
    company-repo-checker/
      index.prose.md
  services/
    agent-readiness.prose.md
  evals/
    agent-readiness.eval.prose.md
    company-repo-checker.eval.prose.md

Starter contracts

agent-readiness — narrow intake a founder can run in under a minute: scores how accessible their site is to AI agents (well-known paths, plain-HTML parseability, structured metadata) and writes a screenshot-ready markdown report to the run's bindings/agent-readiness.md. Safe first-run demo: three prompts, one WebFetch batch, one report binding.
company-repo-checker — static gate that verifies a company-as-prose repository still matches the shared layout before expensive runtime tests or fleet monitors do more work.

Future additions should help a new company get started without copying OpenProse, Inc.'s private business logic:

starter repository architecture
company system map
customer package checker
test ladder
fixture and run-replay conventions
onboarding system for the first operating responsibilities

std vs co — the split

std — use-case-agnostic primitives. Inspector, contract-grader, retry, fan-out, worker-critic, human-gate. Things that make reusable Prose contracts work.
co — company-operations-shaped patterns. Starter repo checkers, scheduled intake, windowed analytics, GTM pipelines, fleet monitors. Things that make reusable Prose contracts support company operations.

Running contracts

prose run is an agent-session command. It is not assumed to be a shell binary. If a host provides a native Prose CLI, use it. Otherwise wrap the command in an agent runner that has the OpenProse skill loaded.

Claude Code:

claude -p "prose run co/systems/company-repo-checker --repo_path <company-repo>"

Codex:

codex exec -C <workspace-root> "prose run co/systems/company-repo-checker --repo_path <company-repo>"

The shell executable is claude or codex. The prose run ... string is the instruction the agent session interprets as the OpenProse VM.

Design Notes

Keep this package generic. Do not include OpenProse, Inc. leads, accounts, GTM logic, release logic, or private operating assumptions.
Prefer reusable contracts with explicit requirements and interfaces. Keep helper contracts local until they earn a stable public interface.
Put universal primitives in std/; put company-operating-system patterns here.
Keep generated runtime state out of this package. Useful lessons can become docs, fixtures, or tests.