Lint and reload / lint-and-reload (push) Successful in 2s
- applicants grows past the one decision: invited -> active (onboarded) -> departed, one continuous graph per person. - investors: open -> in_dialogue -> committed -> divested, with decline edges; submission via a new "I want to invest" alternative on /. - organizations (prospect -> client -> past_client) finally gets pages: a review listing with its transitions and a record-a-prospect form. - development_proposals: the question architecture dogfooding its own development - /develop-proposal takes proposals from anyone (human today, an LLM later through the same public form), /develop lets an owner approve or reject, and approval hands off to the automation that opens the PR (see infrastructure's development-commit workflow). The repo's own lint CI gates the merge, same as any human commit. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
27 lines
687 B
YAML
27 lines
687 B
YAML
id: /develop
|
|
route: ^/develop
|
|
name: Development proposals
|
|
qualifies: owners
|
|
description: >
|
|
Proposed changes to the questions repo, awaiting a decision.
|
|
Approval hands off to the automation that opens the pull request —
|
|
lint gates the merge, not this page.
|
|
alternatives:
|
|
- name: Proposals
|
|
description: ""
|
|
action: /develop
|
|
consequence: [Confirm]
|
|
features:
|
|
- name: ""
|
|
description: ""
|
|
resource:
|
|
source:
|
|
kind: kv
|
|
bucket: development_proposals
|
|
requires_group: owners
|
|
transitions:
|
|
- to: approved
|
|
label: Approve
|
|
- to: rejected
|
|
label: Reject
|