← graph

voice-b-concrete

Voice B: concrete/example-driven — show by doing

Metadata

Statusdone
Assignedagent-253
Agent identity3184716484e6f0ea08bb13539daf07686ee79d440505f1fdf2de0357707034c3
Created2026-05-02T02:42:44.539056637+00:00
Started2026-05-02T02:45:46.492824243+00:00
Completed2026-05-02T02:49:20.609477358+00:00
Tagsgrant,urgent,website,voice-study, eval-scheduled
Eval score0.96
└ blocking impact1.00
└ completeness1.00
└ coordination overhead1.00
└ correctness0.95
└ downstream usability1.00
└ efficiency0.95
└ intent fidelity0.73
└ style adherence1.00

Description

Voice B: concrete, example-driven

Lead with named uses. Erik's pangenome work in the Garrison lab. Pinello's clinical genomics analysis. Tan's research on hybrid teams. The grant submission you're reading was coordinated through this. The incorporation trace is browsable at ulivo.poietic.life. Instead of describing what WorkGraph IS abstractly, show what it's DOING right now and let the reader infer the architecture. Concrete > abstract.

Rough paragraph to replace

AI agents can now search literature, write code, analyze data, and design molecules. But the durable problem is organizational: how people and machines coordinate across days or weeks, preserve judgment, expose evidence, and stay responsive to participants.

We build open-source products, live demonstrations, and organizational methods that make hybrid human-AI work auditable, reproducible, and inspectable. Our first product is WorkGraph: a Rust task-coordination system where humans and AI agents work in the same dependency graph, with claims, execution logs, handoffs, completions, artifacts, and histories preserved for review.

WorkGraph is the instrument, not the whole institution. It gives Poietic a proof surface for the theory of organizational patterns: product, demos, research practice, and organizational design should all make human and machine collaboration legible and responsive to its participants. That public-benefit purpose is the operating constraint: the tools should expose the work, the handoffs, the failures, and the evidence trail.

Shared context

Erik diagnosis

"too self-aware. lol. can you run a team on it? it's kind of uncanny."

The current text describes itself meta-philosophically ("WorkGraph is the instrument, not the whole institution. It gives Poietic a proof surface for the theory of organizational patterns"). It is text talking ABOUT itself rather than text DOING the work of explaining the company. A reader asking "can you run a team on it?" should be able to look at the page and answer YES, here is how. Not get a paragraph about proof surfaces.

Constraints all voices share

  • PBC public benefit statement is the foundation: "to make human and machine collaboration legible and responsive to its participants" (Delaware filing, verbatim).
  • Founder order Erik / Luca / Vaughn whenever named.
  • Erik dogfooding instruction: "they build this because they want to USE it. Their track records prove they know scientific organizations and how to run real resource projects."
  • No em-dashes (style rule).
  • No PI / lead PI language.
  • No "in production today" or "we wrote this proposal with WorkGraph" recursion overclaim — instead: WorkGraph is in active use across founders' research and operations; the incorporation trace is publicly browsable at https://ulivo.poietic.life/wg/feeds/incorporation-trace/
  • Length: roughly the same as the rough paragraph (3 paragraphs, ~200-250 words). Can compress further if it works.
  • Match the existing dark monospace landing page aesthetic (no flowery prose, no marketing fluff).

Output

A single drop-in replacement section. Plus 50-word self-justification ("here is the voice I am writing in and why it answers Erik's diagnosis").

Output

~/poietic.life/notes/website-voice-b-concrete.md containing:

  • The replacement text (3 paragraphs, drop-in)
  • 50-word self-justification

Depends on

Required by

Log