mirror of https://github.com/openprose/prose.git synced 2026-09-19 05:55:05 +08:00

Files

T

irl-dan 63c8ce4b23 Migrate std and co into packages/ monorepo layout

Move the standard library (previously `github.com/openprose/std`) and
the company-as-prose library (previously local dir
`/Users/sl/code/openprose/company-as-prose`) into this repository
under `packages/std/` and `packages/co/` respectively.

Motivation: concentrate attention on one repository so stars,
discussions, and issues aggregate. `openprose/std` was a genuinely
useful asset nobody could find because ~50 stars on its own repo
told a much worse story than 1,106 stars on `openprose/prose`
would have. Same logic applies to co.

Layout choice: `packages/{std,co}/` rather than `std/` + `co/` at
the repo root. Root siblings accumulate over time, and a flat
top-level made future libraries (hub, kit, dev, etc.) compete with
spec infrastructure. `packages/` is bounded — new libraries land
there without cluttering root. Matches pnpm/Deno/monorepo tooling
conventions.

Changes:

- New: `packages/std/` (copied from openprose/std, `.git` excluded)
- New: `packages/co/` (copied from company-as-prose, README updated
  for new name and location)
- `packages/std/README.md`: updated shorthand expansion reference
- `packages/co/README.md`: renamed "company-as-prose" to "co" in
  self-references, added std-vs-co split heuristic, updated
  `prose run` examples to use `co/` shorthand
- `skills/open-prose/deps.md`:
  - `std/` shorthand now expands to
    `github.com/openprose/prose/packages/std/`
  - `co/` shorthand added, expands to
    `github.com/openprose/prose/packages/co/`
  - Both shorthands resolve into the same clone of
    `openprose/prose` under `.deps/github.com/openprose/prose/`;
    `packages/std/` and `packages/co/` are sibling subdirectories
  - `prose.lock` format row updated to `host/owner/repo sha`
    (matches the explicit-host resolution that landed in #35)
  - `.deps/` directory structure example redrawn to show the
    `{host}/{owner}/{repo}/packages/{std,co}/...` shape
  - Error message and Interaction tables refreshed accordingly
  - Resolution Algorithm step 1 now documents both shorthands
- `skills/open-prose/forme.md`: Step 2 resolution list updated to
  include co/ shorthand and the host-keyed `.deps/` layout
- `skills/open-prose/help.md`: Q&A "How do dependencies work?"
  rewritten to name both shorthands and the new explicit-host model
- `skills/open-prose/state/filesystem.md`: `.deps/` directory
  tree re-drawn to include the `{host}/` layer with std/co as
  sibling packages inside the clone
- `skills/open-prose/guidance/patterns.md`,
  `skills/open-prose/guidance/antipatterns.md`: examples now use
  the `std/` shorthand or explicit `github.com/...` rather than
  the deprecated bare `openprose/std/` form
- `skills/open-prose/examples/registry-import/index.md`: sample
  service reference switched to `std/evals/inspector`
- `README.md`: Stdlib badge replaced with internal `packages/std/`
  link plus new `packages/co/` link; "Standard Library" section
  rewritten as "Libraries" with both packages described

Out of scope for this PR (deliberately):
- Tooling changes to `prose install` and Forme's `.deps/` writer
  to adopt the `{host}/{owner}/{repo}/` layout in practice — this
  PR is spec-only. Existing tooling continues to work against
  whatever layout it currently implements; the spec now describes
  the target.
- Retiring the `openprose/std` GitHub repo. Delete that repo
  separately after this merges.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-04-21 14:14:31 -07:00

2.3 KiB

Raw Permalink Blame History

name, kind

name	kind
proposer-adversary	composite

Proposer-Adversary

One proposes, another attacks. The composite returns both — the parent decides.

Description

One agent proposes, another attacks the proposal, and the unresolved tension is returned for the parent to judge.

Metadata

version: 0.1.0

Slots

proposer (primary)
- requires: task_brief
- ensures: proposal text
adversary
- requires: proposal, original task_brief
- ensures: attack identifying flaws, edge cases, and counterexamples

Config

task_brief (string, default: none): What the proposer should propose on

Invariants

The composite does not resolve the tension — it returns both proposal and attack
Proposer is unaware it will be attacked
Adversary is unaware its output will be weighed against the proposal

Shape

self: delegate to proposer, delegate to adversary, return both outputs
delegates:
- proposer: produce a proposal given the brief
- adversary: find flaws in the proposal
prohibited: none

Requires

&compositeState exists at __compositeState with: proposer: string -- component name for the proposer adversary: string -- component name for the adversary task_brief: string -- what to propose

Ensures

Proposer receives only the task brief
Adversary receives the proposal and the task brief — its job is to find flaws, edge cases, and counterexamples
This composite does NOT resolve the tension
Returns { proposal, attack } — the parent reasons about the disagreement
&compositeState.result contains { proposal, attack }

Delegation

const { proposer, adversary, task_brief } = __compositeState;

const proposal = await rlm(task_brief, null, { use: proposer });

const adversaryBrief = `Find flaws, edge cases, or counterexamples in this proposal.\n\nOriginal task: ${task_brief}\n\nProposal:\n${proposal}`;
const attack = await rlm(adversaryBrief, null, { use: adversary });

const result = { proposal, attack };
__compositeState.result = result;
return(result);

Notes

This is a seed pattern. The proposer does not know it will be attacked. The adversary does not know its output will be weighed against the proposal. The parent composes both perspectives and makes the final judgment.

2.3 KiB Raw Permalink Blame History