mirror of
https://github.com/magnus919/agent-skills.git
synced 2026-09-14 13:06:30 +03:00
Magnus Hedemarkandfactory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
c0c7690724
Move the 8 directories under bundles/ to the repo root via git mv and remove the now-empty bundles/ directory. Replace the "bundles" entry in pyproject.toml [tool.deptry] extend_exclude with the 8 moved dir names so the moved trees stay excluded from Python dependency analysis. Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
24 lines
2.8 KiB
Markdown
24 lines
2.8 KiB
Markdown
# Source Index
|
|
|
|
Checked 2026-08-05. These are official employer-authored role descriptions,
|
|
used only for role observations. The lifecycle, artifacts, authority protocol,
|
|
failure-mode mitigations, and generalization model are normative bundle design.
|
|
The sources come from large software and AI vendors; they do not establish that
|
|
the bundle applies universally across business, public-sector, nonprofit,
|
|
internal-service, or non-product settings. Portability is a design objective
|
|
that must be tested in the engagement context.
|
|
|
|
| Source | Authority | Supported claims | Limitations and refresh rule |
|
|
|---|---|---|---|
|
|
| [Palantir: A Day in the Life of a Palantir Forward Deployed Software Engineer](https://blog.palantir.com/a-day-in-the-life-of-a-palantir-forward-deployed-software-engineer-45ef2de257b1) | Official employer-authored role account | FDSEs embed with customers; configure existing platforms; combine software development, data engineering, customer engagement, and creative problem solving; implement collaboratively; use engineering review, deployment, maintenance, and monitoring; return configurations, workflows, and field expertise to product and deployment teams | One employee account with employer-specific products, titles, and examples. Do not universalize those details. Recheck the URL and role-account scope before materially revising source claims. |
|
|
| [OpenAI: Forward Deployed Engineer](https://openai.com/careers/forward-deployed-engineer-(fde)-sf-san-francisco/) | Current official employer role description | FDEs turn research into production systems with customers; own discovery, scoping, design, build, rollout; measure adoption and workflow impact; use eval-driven feedback; guide adoption; codify patterns and return field feedback | Employer-specific AI role description. Excludes universal employment qualifications, location, travel, mission, and stack. Recheck current role page before citing current responsibilities. |
|
|
| [Databricks: AI Engineer — FDE](https://www.databricks.com/company/careers/professional-services-operations/ai-engineer---fde-forward-deployed-engineer-8099751002) | Current official employer role description | A specialized customer-facing AI team builds and productionizes first-of-kind applications and works cross-functionally with engineering, product, developer relations, and internal SMEs | Retrieved overview exposes only these responsibilities. Do not infer missing qualifications or duties. Recheck the role page before adding claims. |
|
|
|
|
## Claim discipline
|
|
|
|
Source facts must cite one of these entries. Engagement evidence must cite the
|
|
charter, ledger, evaluation, deployment, adoption, or measurement artifact that
|
|
observed it. Inferences and recommendations must be labeled as such. A source
|
|
does not prove that a local engagement succeeded, that a pattern generalizes, or
|
|
that an authority exists.
|