spot-fix-elevate — Workgraph

Metadata

Status	abandoned ‖ paused
Created	2026-05-02T03:32:47.389478479+00:00
Tags	`grant,urgent,spot-fix,vaughn`

Description

Erik flagged a real gap. Vaughn Tan has designed 'the agency' subsystem of WorkGraph — the system that develops, manages, and evaluates agent primitives (the named roles like 'Default Evaluator', 'Careful Programmer', 'Default Documenter' visible in coordinator logs as 'Lightweight assignment: agent=...'). The agency framework is based on Vaughn's organizational research on hybrid teams under uncertainty, applied directly to making WorkGraph itself function as a coordinated multi-agent system.

This means Vaughn is NOT just a co-founder doing ethnographic case studies of others' WorkGraph use. He is the architect of a specific product subsystem with concrete outputs (the agency primitives, the evaluator framework, the role-assignment logic). His organizational research shapes how WorkGraph allocates work to agents.

Currently v3.1 positions Vaughn primarily as the methodologist studying use, with a 36-month deliverable of an organizational design framework targeting ASQ or Research Policy. That undersells him. Spot fixes needed.

Time-boxed: produce edit specs in ≤15 min. No big audit, no synthesis. Just edits.

What to read

workgraph_google_application_FINAL_v3_1.md (commit 986222f on main)
~/poietic.life/notes/v3-1-form-mapping-paste-guide-20260502.md (the form-mapping paste guide just produced)
~/poietic.life/index.html (the live landing page, especially mission p3)
CLAUDE.md for Vaughn's track record (Harvard PhD, ASQ, Columbia book, FLF, etc.)
Optional: .wg/agency/ directory in this repo if it has metadata about agency primitives that informs technical accuracy

What to do

Identify the SMALLEST set of edits across v3.1 and the website that bring out:

Vaughn designed 'the agency' subsystem of WorkGraph
Agency primitives (the named agent roles) are concrete artifacts of his organizational research applied to product
His role is co-architect, not just methodologist studying others' use

Most likely affected:

v3.1 §17 (approach) — likely needs one sentence on agency subsystem
v3.1 §26 (uniquely positioned) — Vaughn line needs to mention agency design, not just framework deliverable
Form §30 (key team members, drafted in paste guide) — the role description for the organizational researcher should mention 'designed the agency framework'
v3.1 §43-§46 (milestones) — possibly one milestone tied to agency framework evolution
Website mission p3 — currently 'Vaughn uses the resulting traces as material for his research on hybrid teams' is backwards; he DESIGNS the system that uses the traces. Suggest reframe.

For each affected section, produce a structured spec:

Section anchor (file + line range OR form §)
Current text (verbatim)
Proposed text (verbatim)
Word count check (before / after / cap)
Why this elevates Vaughn's role concretely

If a section's current text already does the work, leave it alone. Don't manufacture edits.

Output

~/poietic.life/notes/vaughn-agency-spot-fixes-20260502.md (under 600 words):

Headline: how many spots need editing, total word delta
One spec per affected section
Which spec is the SINGLE most important if Erik only has time for one (probably the form §30 role description, since that's actively being pasted right now)

wg log a one-paragraph summary on this task.

Constraints

HARD: respect every word cap. Recount.
HARD: no em-dashes. No PI language. Founder order Erik / Luca / Vaughn.
HARD: don't make claims about 'the agency' that aren't defensible. If unsure about technical detail, hedge with general framing ('a subsystem for agent primitive development') rather than overcommit.
HARD: time-boxed. Don't go on a research expedition. 15 min max.
SOFT: prefer surgical (≤2 sentence) edits over rewrites.

Validation

v3.1 §17, §26 evaluated; edits proposed only where current text undersells Vaughn
Form §30 (paste guide draft) evaluated; if revised, full revised text included
Website mission p3 evaluated
Each spec has before/after with word counts
'Most important if only one' identified
Output at ~/poietic.life/notes/vaughn-agency-spot-fixes-YYYYMMDD.md

## Description

## Time-boxed: produce edit specs in ≤15 min. No big audit, no synthesis. Just edits.

## What to read

1. `workgraph_google_application_FINAL_v3_1.md` (commit 986222f on main)
2. `~/poietic.life/notes/v3-1-form-mapping-paste-guide-20260502.md` (the form-mapping paste guide just produced)
3. `~/poietic.life/index.html` (the live landing page, especially mission p3)
4. CLAUDE.md for Vaughn's track record (Harvard PhD, ASQ, Columbia book, FLF, etc.)
5. Optional: `.wg/agency/` directory in this repo if it has metadata about agency primitives that informs technical accuracy

## What to do

Identify the SMALLEST set of edits across v3.1 and the website that bring out:
- Vaughn designed 'the agency' subsystem of WorkGraph
- Agency primitives (the named agent roles) are concrete artifacts of his organizational research applied to product
- His role is co-architect, not just methodologist studying others' use

Most likely affected:
- v3.1 §17 (approach) — likely needs one sentence on agency subsystem
- v3.1 §26 (uniquely positioned) — Vaughn line needs to mention agency design, not just framework deliverable
- Form §30 (key team members, drafted in paste guide) — the role description for the organizational researcher should mention 'designed the agency framework'
- v3.1 §43-§46 (milestones) — possibly one milestone tied to agency framework evolution
- Website mission p3 — currently 'Vaughn uses the resulting traces as material for his research on hybrid teams' is backwards; he DESIGNS the system that uses the traces. Suggest reframe.

For each affected section, produce a structured spec:
- Section anchor (file + line range OR form §)
- Current text (verbatim)
- Proposed text (verbatim)
- Word count check (before / after / cap)
- Why this elevates Vaughn's role concretely

If a section's current text already does the work, leave it alone. Don't manufacture edits.

## Output

`~/poietic.life/notes/vaughn-agency-spot-fixes-20260502.md` (under 600 words):
1. Headline: how many spots need editing, total word delta
2. One spec per affected section
3. Which spec is the SINGLE most important if Erik only has time for one (probably the form §30 role description, since that's actively being pasted right now)

`wg log` a one-paragraph summary on this task.

## Constraints

- HARD: respect every word cap. Recount.
- HARD: no em-dashes. No PI language. Founder order Erik / Luca / Vaughn.
- HARD: don't make claims about 'the agency' that aren't defensible. If unsure about technical detail, hedge with general framing ('a subsystem for agent primitive development') rather than overcommit.
- HARD: time-boxed. Don't go on a research expedition. 15 min max.
- SOFT: prefer surgical (≤2 sentence) edits over rewrites.

## Validation
- [ ] v3.1 §17, §26 evaluated; edits proposed only where current text undersells Vaughn
- [ ] Form §30 (paste guide draft) evaluated; if revised, full revised text included
- [ ] Website mission p3 evaluated
- [ ] Each spec has before/after with word counts
- [ ] 'Most important if only one' identified
- [ ] Output at `~/poietic.life/notes/vaughn-agency-spot-fixes-YYYYMMDD.md`

Depends on

(none)

Required by

(none)

Log

2026-05-02T03:32:47.372917847+00:00 Task paused
2026-05-02T03:33:02.339537701+00:00 Task abandoned