2026-05-19 Example RFC

RFC ID: RFC-2026-05-19-001 Status: Example Date: 2026-05-19 Owner: Founder

Context

The founder wants to introduce a new cross-package capability that may affect app contracts and shell runtime behavior.

Problem

Implementing directly would mix design, contract, runtime, docs, and QA in one large agent transaction.

Goals

• Clarify the target behavior.
• Identify ownership boundaries.
• Split implementation into safe slices.

Non-goals

• No implementation in the RFC.
• No dependency installation.
• No route or contract change before acceptance.

Options

1. Keep as documentation only.
2. Add a local prototype.
3. Change app contract and runtime.

Proposed Direction

Start with docs and a prototype task graph. Promote to contract work only after the prototype clarifies the interface.

Risks

• Contract churn.
• Shell/runtime coupling.
• Test gap.

Acceptance

• Owner approves scope.
• Task graph lists allowed and forbidden paths.
• Validation commands are named.

Rollout Plan

1. Accept RFC.
2. Write ADR if a durable contract decision is made.
3. Implement one slice per worker task.

Open Questions

• Does this belong in app contract or app-local code?
• Is it needed for the current milestone?