openprose__prose/tests/open-prose/compiler

Compiler Prompt Fixtures

These fixtures exercise the pinned ProseScript compiler program, responsibility lowering, and structured Forme manifest emission.

The compiler output convention is:

• <openprose-root>/dist/manifest.next.json: next generated OpenProse root IR
• <openprose-root>/dist/manifest.active.json: active IR used by prose serve

The checked v0 manifest stays intentionally small. Its exact schema is defined in skills/open-prose/compiler/ir-v0.md and contains:

• kind
• version
• sources
• responsibilities
• triggers
• activations
• formeManifests
• diagnostics

Trigger records are concrete serve-facing registrations. The compiler may infer them from responsibility Continuity or declare them from optional kind: gateway source. Activation records reference trigger ids deterministically.

Source paths in IR are root-relative and ready to pass to prose run from <openprose-root>.

Forme manifests are compiled as structured JSON. They are the canonical runtime wiring object for systems; no separate Markdown run manifest is required.

Advisory Prompts

Use these prompts in an agent session with the OpenProse skill loaded.

Compile Empty Source

Run prose compile against an empty temporary repository.

Expected shape:

• writes <openprose-root>/dist/manifest.next.json
• emits a valid v0 manifest matching expected/empty.manifest.next.json
• reports no discovered sources as an informational diagnostic

Compile Stargazer Fixture

Run prose compile tests/open-prose/responsibility-runtime.

Expected shape:

• discovers the responsibility and local fulfillment system
• emits a v0 manifest shaped like expected/stargazer.manifest.next.json
• preserves the responsibility sections in semantic IR
• discovers the optional gateway source
• emits concrete cron and HTTP trigger registrations
• emits judge and fulfillment activation intent
• emits a structured Forme manifest for the fulfillment system
• links the fulfillment activation to the compiled Forme manifest
• does not invent provider-specific auth, subscription setup, queue names, or payload schemas

Compile Ambiguous Fulfillment Fixture

Run prose compile tests/open-prose/compiler/fixtures/ambiguous-fulfillment.

Expected shape:

• discovers one responsibility and multiple plausible systems
• emits a v0 manifest shaped like expected/ambiguous-fulfillment.manifest.next.json
• emits a warning instead of guessing the fulfillment target
• emits judge activation intent, but no fulfillment activation intent

Compile Invalid Responsibility Fixture

Run prose compile tests/open-prose/compiler/fixtures/invalid-responsibility.

Expected shape:

• reports an error for the missing core Criteria section
• refuses to write manifest.next.json until deterministic validation passes

Reject Invalid IR

Validate invalid/missing-version.manifest.next.json.

Expected shape:

• fails deterministic validation
• says the version field is missing or incorrect

Validate invalid/malformed-responsibility.manifest.next.json.

Expected shape:

• fails deterministic validation
• reports malformed responsibility, trigger, and activation records

Validate invalid/malformed-forme.manifest.next.json.

Expected shape:

• fails deterministic validation
• reports malformed Forme graph, execution order, environment, and activation references