strata:propose

strata:propose

The "open question" scope. Closes the gap between what we know (domain), what we've chosen (decisions), what we did (pr-context), and what we did wrong (lessons), with a fourth: what we're still Figuring out.

When to use

Situation	Skill
Open question, multiple positions, no choice yet	strata:propose
Chosen option with reasoning	strata:decide
Stable concept / vocabulary	strata:domain
Retrospective fact	strata:save --scope lessons
In-flight branch work	strata:save

A proposition is explicitly time-bounded. It exists to be resolved. A proposition that never gets settled or refuted is itself a signal.

How

Recall before you open it

Before creating a proposition, call recall to check it isn't already tracked. Two agents opening the same open question — or re-litigating one that's already decided — is the failure this prevents:

recall(query="<the question, in your words>", scope="propositions", layer=1)

Then run a second pass with scope="decisions". Adjudicate:

• existing open proposition → add a position to it (below), don't fork.
• already settled or decided → tell the user and point at the note; write nothing.
• genuinely new → create it.

Create

cat <<'EOF' | "${CLAUDE_PLUGIN_ROOT}/bin/strata" propose \
    --title "Should we move to Postgres for tenant data?"
# Should we move to Postgres for tenant data?

## What we're trying to figure out
<context — why this is open>

## Positions on the table
- Stay on SQLite: <reasons>
- Move to Postgres: <reasons>

## What evidence would settle this
- <what we'd need to know>
EOF

Default status is open. Pass --status contested if multiple positions are actively defended, or --status converging if one is winning.

Add a position (the debate log)

When someone weighs in on an open proposition, append a position — don't rewrite the note. Each entry is attributed, dated, and append-only: