proposals

work becomes a candidate

A proposal packages a branch for review. Its changes remain contained and outside the Team's accepted managed state until an authorized reviewer merges them.

what an authorized reviewer should receive

• Semantic diff. A meaningful account of changed facts, files, or outputs beyond raw storage operations.
• Provenance. The starting basis, agent, tools, and sources behind the work.
• Cost. The resources consumed against the task's bound.
• Rationale. What the agent tried, what it concluded, and where judgment is still required.

review decides what becomes official

Merge incorporates the proposal into accepted managed state. Discard ends the attempt while preserving its attempt and decision history. An authorized reviewer may also request another bounded attempt.

Human review is the current default for consequential work.

conflicts stay visible

If the parent has changed since the proposal's basis, conflict handling reveals competing changes and leaves them separate. The proposal remains inspectable while an authorized reviewer resolves the conflict, requests a revision, or discards the attempt.

Architecture connection. Simmis owns the product and review interface.