draft v0.1.0 claude-opus-4-8 pattern · harness

Content Arc Declare

Author or amend an org's arc manifest in abacus _arcs/ (through-line, acts, windows) so a planned content run becomes checkable, not just intended.

  • content
  • abacus
  • arc
  • multi-org
  • pattern:sequential

inputs

namerequireddefault
org_key yes —
through_line yes —
acts no —
abacus_path no —

routing

triggers

  • declare a content arc for this org
  • write the arc manifest
  • plan the content run for stratt-blue/null0-blue/devaqua-blue/devarno-downlink
  • supersede this arc's schedule

not for

  • checking an existing arc against reality (abacus's own validator does this on read; fathom's check_drift.py does the idea-space projection check)
  • deciding pacing/saturation within an already-declared arc (Yáo's arc-state, not this)
  • drafting the actual content (jazz)
  • opening/closing a PETROVA phase (petrova-phase-open/petrova-phase-close) — an arc is a plan, not a phase, per abacus _arcs/README.md's stated asymmetry with docs/decisions/

prompt

notes

Does not invent a new arc format — this is a thin authoring wrapper
around the schema abacus already ships. The only genuinely new thing
is making arc declaration for stratt-blue/null0-blue/devarno-downlink
as routine as it currently is for calella/devaqua.

description

Wraps abacus's existing arc contract (_arcs/schema/arc.schema.yaml,
documented in _arcs/README.md) so declaring a new org's arc is a
repeatable prompt invocation instead of hand-written YAML each time.
Modeled on the one arc that already exists (_arcs/calella, for devaqua).
Target orgs for the first wave: devarno-cloud (devarno-downlink),
null0-blue, stratt-blue, devaqua-blue already has one.

Supersession happens in place (an itemised `supersedes:` block), never a
second file — this prompt edits the existing manifest for an org that
already has one rather than creating a competing one.

Where the source repo is PETROVA-governed (stratt-hq, per its own slug
pin) and the arc counts as a governance-relevant plan, this prompt hands
off to petrova-decide / petrova-plan rather than writing the arc
unilaterally — it drafts the arc manifest content, the governed repo's
own petrova flow is what actually opens it.