salvacybersec/feynman
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Refine research workflows and remove Agent Computer

Browse Source
This commit is contained in:
Advait Paliwal
2026-03-24 11:01:27 -07:00
parent b712f89580
commit 8fd06b9299
23 changed files with 137 additions and 299 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
AGENTS.md
View File

@@ -22,7 +22,6 @@ Keep this file focused on cross-agent repo conventions:
- output locations and file naming expectations
- provenance and verification requirements
- handoff rules between the lead agent and subagents
- remote delegation conventions
Do **not** restate per-agent prompt text here unless there is a repo-wide constraint that applies to all agents.
@@ -33,6 +32,7 @@ Do **not** restate per-agent prompt text here unless there is a repo-wide constr
- Session logs go in `notes/`.
- Plan artifacts for long-running workflows go in `outputs/.plans/`.
- Intermediate research artifacts are written to disk by subagents and read by the lead agent. They are not returned inline unless the user explicitly asks for them.
- Long-running workflows should treat the plan artifact as an externalized working memory, not a static outline. Keep task status and verification state there as the run evolves.
## File naming
@@ -54,14 +54,14 @@ Never use generic names like `research.md`, `draft.md`, `brief.md`, or `summary.
- Provenance sidecars should record source accounting and verification status.
- Source verification and citation cleanup belong in the `verifier` stage, not in ad hoc edits after delivery.
- Verification passes should happen before delivery when the workflow calls for them.
- If a workflow uses the words `verified`, `confirmed`, or `checked`, the underlying artifact should record what was actually checked and how.
- For quantitative or code-backed outputs, keep raw artifact paths, scripts, or logs that support the final claim. Do not rely on polished summaries alone.
- Never smooth over missing checks. Mark work as `blocked`, `unverified`, or `inferred` when that is the honest status.
## Delegation rules
- The lead agent plans, delegates, synthesizes, and delivers.
- Use subagents when the work is meaningfully decomposable; do not spawn them for trivial work.
- Prefer file-based handoffs over dumping large intermediate results back into parent context.
- When delegating to remote machines, retrieve final artifacts back into the local workspace and save them locally.
## Remote delegation
Feynman can delegate tasks to remote cloud machines via the `computer-fleet` and `computer-acp` skills. Load those skills on demand for CLI usage, session management, ACP bridging, and file retrieval.
- The lead agent is responsible for reconciling task completion. Subagents may not silently skip assigned tasks; skipped or merged tasks must be recorded in the plan artifact.
- For critical claims, require at least one adversarial verification pass after synthesis. Fix fatal issues before delivery or surface them explicitly.