Bendik Aagaard LynghaugandClaude Fable 5
981a448b30
Desk/receipt titles become questions (What's been proposed? / What happens to your proposal? / What came in? / Which proposal is this?), Where to send it and Record a prospect explain why before the field, lucide icons on input-bearing features, README's alternatives rule reworded (draw people in with a real path, not necessarily a slogan) and its stale /develop-proposal + followup references fixed. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
19 lines
744 B
YAML
19 lines
744 B
YAML
# Reached from the proposal form only - and provably so: the visitor
|
|
# must hold a ?chain= lineage ending at an answer to proposal.yaml.
|
|
requires_chain: proposal
|
|
name: What happens to your proposal?
|
|
description: >
|
|
It's in the queue. An owner reads every proposal in full — approved
|
|
ones open a real pull request, and the same checks every human
|
|
commit passes gate the merge.
|
|
alternatives:
|
|
- name: The path from here
|
|
description: ""
|
|
features:
|
|
- name: A person decides
|
|
description: Nothing merges on autopilot — approval is a deliberate act.
|
|
- name: The linter has no favorites
|
|
description: >
|
|
Approved or not, your YAML faces the same validation as
|
|
everything else in the repo.
|