Proposals and revisions

A proposal is a suggested change to the canonical model. It is the only way anything enters or leaves the model.

What a proposal can carry

A new direction, which may bring its first capabilities with it (up to 20). An epic and the features that make it real are agreed as one decision.
A capability under a live direction, with what it includes and its boundaries.
A change to a capability, made by replacing it. The new capability starts from the old one as it stands. Give the reason for replacing it: an upgrade, a rework, a correction, a move to another direction, or something else.
Constraints: what the proposed item will not do. Each becomes its own item in the model when the proposal is accepted.

Writing one

Open New proposal and add what the proposal brings, one item at a time: a direction, a capability or a constraint. You never choose what kind of proposal it is; that follows from what it holds. The proposal structure under the form shows every item as a tree.

A capability cannot go without a direction. Choose a direction in this proposal, a live one, or A new direction.
To change a capability, open it on the model and choose Propose a change.
Say why. The signal records what raised the proposal (an idea, meeting notes, a pain point, something observed, or a requirement), in the words of whoever raised it where possible.

Drafting with AI

Draft with AI takes a sentence or two about what you want, reads the project, and fills in the form. Anything the model could not settle is listed above the draft. Revise with AI then takes instructions such as “split the second capability in two” and keeps the rest. Each run uses the team’s model credits.

Checking before you send

Check runs the audit that sending would run, before you send. It looks for:

Duplicates. Something already in the model, or in review, that expresses the same intent. This includes one filed under a different direction, which is the duplicate an author is least likely to notice.
Crossed constraints. A boundary the proposal would violate.
Delivered work undone. A replacement that removes what a delivered capability gave users, rather than extending it.

Findings are flags, not verdicts. The audit is measured, and it is wrong often enough that you should never treat it as final. A clean result is not proof that nothing is there. You can clear a flag in two ways:

Rewrite the draft. The flags described the old text, so they drop.
Acknowledge them and send anyway. The acknowledgement goes on the record and reaches reviewers with the proposal. Replacing something the team already has can be exactly right.

One flag cannot be acknowledged: a capability with no direction to live under. Attach it to the direction the audit suggests, or propose a new direction to carry it.

Checking uses one model credit. Sending the same text into an unchanged project reuses that verdict, so checking first costs nothing extra.

Sending for review

Send for review opens the proposal to every project member. From then on, it is visible to the whole team and every edit is recorded.

Revising a proposal in review

A proposal under review is never rewritten. Edit proposal appends the next numbered revision. Only the author, the project owner or an organization admin can revise.

When you save a revision, you must choose:

Reviewers should look again (a material edit). Every answer already given is cleared and the team decides again. Changing what kind of proposal it is always counts as material.
Typo-level, keep their answers. Answers carry forward to the new revision and are marked as carried.

The proposal’s Versions list shows every revision: who wrote it, what changed, and who answered it.

A version an agent left waiting

If you ask an agent to change a proposal in review, it writes the next version and leaves it waiting. A new version is waiting for you appears on the proposal’s page. Open it to read, change and submit it, choosing there whether it is material, or Discard it. Nothing about the proposal moves until you do.

How a proposal ends

Accepted, when every current project member has answered the current revision and nobody objects. A commitment is created in the same moment.
Rejected, by a project owner or organization admin, or withdrawn by its author. A rejected proposal can be started again with Propose again.