# Alma Next Steps
Alma's next work should be a sequence of truth tests, not a broad plugin
platform expansion.
## Truth Test 1: One Safe Useful Plugin
Host one tiny Wasm plugin that trims trailing whitespace in the current
selection.
The plugin receives only a buffer snapshot or selection handle, observes text
under `buffer.observe`, computes a small edit, and submits a
`buffer.propose_edit` proposal against the observed base revision. The buffer
does not change during plugin execution.
Success means the WIT boundary, handle resolution, capability check, proposal
type, stale revision guard, and owner rejection path all work together.
## Truth Test 2: Proposal Lane
Build the smallest visible lane for non-owner editor changes.
The lane should show the proposer identity, target, capability, base revision,
status, and diff preview. The current chrome controls already route apply
through the buffer owner, reject without mutation, and record bounded
in-session receipts for the resulting decisions. Buffer edit proposals now use
per-plugin config policy: `auto_apply` preserves compatibility, and
`manual_review` keeps proposals visible until explicit apply or reject. Chrome
now shows pending status and latest receipt status. Stale proposals fail at the
owner boundary and remain explainable.
This is not an AI cockpit. It is the editor primitive that later plugins, LSP
code actions, formatters, codemods, external agents, and macros can all use.
## Truth Test 3: External Worktree Review
Review an existing branch or worktree without running an agent.
Alma should show changed files, diffs, test output, and review notes as
observable artifacts. The goal is to make Alma useful in an AI coding loop
before Alma starts agents itself.
## Truth Test 4: Narrow Review Extensions
Allow plugins to add review value without becoming omnipotent.
Examples: test-output parsers, hunk annotators, conventional commit
suggesters, migration-risk detectors, or generated-artifact publishers. Each
extension should require a small capability set and should publish proposals,
annotations, status, or artifacts through the same owner-mediated lanes.
## Truth Test 5: Receipts
For accepted and rejected proposals, Alma now produces a bounded in-session
receipt:
- proposer identity
- capability atom
- observed source or handle generation
- target and base revision
- owner decision
- result revision or rejection reason
Receipts are the audit surface that makes proposal-based editing trustworthy.
Future work can decide whether to persist or export them beyond the editor
session.