Files
questions/questions/invested.yaml
T
Bendik Aagaard LynghaugandClaude Sonnet 5 8d10e99726
Lint and reload / lint-and-reload (push) Successful in 2s
Actor state machines: employee lifecycle, investors, organizations wired, development proposals
- 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>
2026-08-12 22:04:11 +02:00

17 lines
530 B
YAML

id: /invested
route: ^/invested
name: What happens now?
description: >
Your interest is on its way to a real inbox. Expect a considered,
personal reply — not a pitch deck on autopilot.
alternatives:
- name: In short
description: ""
features:
- name: We read it
description: In full, before we write back.
- name: Dialogue before commitment
description: >
We'll want to understand each other properly first — what
you're looking for, and whether we're actually it.