Bendik Aagaard LynghaugandClaude Fable 5
ad9dd1762b
develop/ holds the whole proposal flow (index = owners desk, proposal = public form, proposed = chain-gated receipt) with relative actions; review/ gains _section.yaml (one owners gate for the directory) and a [record].yaml dynamic page - /review/<chain-hash> shows a single proposal. Top-level files drop their now-derived id: and fossil route: fields. URLs /develop-proposal and /proposed become /develop/proposal and /develop/proposed (no automation references them - n8n filters checked). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
26 lines
1.0 KiB
YAML
26 lines
1.0 KiB
YAML
followup: true
|
|
name: What happens now that you've applied?
|
|
description: >
|
|
We're not filling a seat — we're looking for exactly what you bring
|
|
that we don't already have. We read every one of these ourselves, in
|
|
full, and write back.
|
|
alternatives:
|
|
- name: Thanks — it's in front of us
|
|
description: ""
|
|
features:
|
|
- name: We need your specific angle
|
|
description: >
|
|
Not a generic fit — the particular thing you're good at, the
|
|
problem you'd actually notice, the take nobody else here
|
|
has. That's what we're reading for.
|
|
- name: Work happens through dialogue, not tickets
|
|
description: >
|
|
What you bring shapes what gets built, in an ongoing back
|
|
-and-forth — not a queue of pre-decided tasks handed down to
|
|
execute.
|
|
- name: You receive a personal invitation
|
|
description: >
|
|
A match earns you a real key — access, a measure of
|
|
responsibility, and eventually, the standing to invite
|
|
someone else in.
|