Beam
Spec

Beam spec

TODO: Concrete spec outcome

TODO: One sentence stating what will be true after this work is executed.

Status: Draft Audience: Engineering Owner: TODO Source: TODO Confidence: TODO
Executive summary. TODO: Write 2-4 sentences that make the decision, constraint, or action gate obvious before the reader enters the details.

#01 Goal

TODO: One concrete outcome. Avoid multiple artifacts.

Downstream task: TODO.

#02 Context

Source files
  • TODO/path
Product context

TODO: user, workflow, customer, or operating model.

Assumptions
  • TODO
Constraints
  • TODO

#03 Scope

In Out Human decisions
TODO TODO TODO

#04 Execution Plan

  1. AI TODO: Inspect current state and identify files to edit.
  2. AI TODO: Implement the smallest safe change.
  3. Human TODO: Approve any decision that changes scope or product behavior.

#05 Acceptance Criteria

Criterion Proof required Status
TODO: Binary outcome. TODO: Command, screenshot, manual check, or artifact link. Open

#06 Verification

Check Command or walkthrough Expected result
Static checks pnpm run lint && pnpm run build Passes without new warnings or errors.

#07 Risks

Implementation risk

TODO

Product risk

TODO

#08 Handoff

TODO: Destination, next owner, unresolved ambiguity, and rollback or fallback notes.

Beam spec artifact. Replace TODOs before sharing. Bundle with node scripts/bundle-html.mjs resources/beam-spec-template.html out.html when the deliverable must be one portable file.